Hi John,
> One of the examples in the docstring for DisjointUnionEnumeratedSet
> goes something like this:
>
> sage: U = DisjointUnionEnumeratedSets(Family(NonNegativeIntegers(),
> Permutations))
> sage: it = iter(U)
> sage: it.next()
> []
>
> If I try the same thing, replacing "Permutatio
Hi,
a few weeks ago I noticed the code for the GSL ode solver in Sage
doesn't support parameters in compiled functions, although the native
API supports it and I found that feature quite useful for solving with
different parameter sets.
I wrote a patch to enable it. The only problem I see is that
One of the examples in the docstring for DisjointUnionEnumeratedSet
goes something like this:
sage: U = DisjointUnionEnumeratedSets(Family(NonNegativeIntegers(),
Permutations))
sage: it = iter(U)
sage: it.next()
[]
If I try the same thing, replacing "Permutations" with "Partitions",
it doesn't wo
> On 05/31/10 08:36 AM, François Bissey wrote:
> >> I think you've found a bug in the makefile.
> >>
> >> We have
> >>
> >> LINBOX depends on ATLAS
> >>
> >> ATLAS depends on LAPACK and PYTHON
> >>
> >> LAPACK depends on FORTRAN
> >>
> >> It is just a lucky coincidence that
On 05/31/10 08:36 AM, François Bissey wrote:
I think you've found a bug in the makefile.
We have
LINBOX depends on ATLAS
ATLAS depends on LAPACK and PYTHON
LAPACK depends on FORTRAN
It is just a lucky coincidence that the Sage build has actually worked.
We need to add BLAS as a
>> I've brought this one up before. How do folks feel about having the
>> named permutation groups available like graphs are? In other words,
>> rather than each family of permutation groups being a new class, there
>> is a single system-wide object ("groups", or "perm_groups") whose
>> methods p
On May 31, 2010, at 12:52 PM, Dr. David Kirkby wrote:
On 05/31/10 05:51 PM, Robert Bradshaw wrote:
On May 30, 2010, at 2:27 PM, Dr. David Kirkby wrote:
On 05/30/10 10:10 PM, Mike Hansen wrote:
On Sun, May 30, 2010 at 2:04 PM, Dr. David Kirkby
wrote:
3) I want to add some patches.
I've sav
On 31 Mai, 20:23, "Dr. David Kirkby" wrote:
> Building on my own Sun Blade 1000, then running
>
> 'make ptestlong', I get:
>
> The following tests failed:
>
> sage -t -long devel/sage/sage/graphs/generic_graph.py # 1 doctests
> failed
See ticket #9086.
http://trac.sagemath.org/sage_tra
On 05/31/10 05:51 PM, Robert Bradshaw wrote:
On May 30, 2010, at 2:27 PM, Dr. David Kirkby wrote:
On 05/30/10 10:10 PM, Mike Hansen wrote:
On Sun, May 30, 2010 at 2:04 PM, Dr. David Kirkby
wrote:
3) I want to add some patches.
I've saved Robert's changes to files /tmp/robert1 and /tmp/rober
Building on my own Sun Blade 1000, then running
'make ptestlong', I get:
The following tests failed:
sage -t -long devel/sage/sage/graphs/generic_graph.py # 1 doctests
failed
sage -t -long devel/sage/sage/schemes/elliptic_curves/BSD.py # 1
doctests failed
sage -t -
On May 30, 2010, at 2:27 PM, Dr. David Kirkby wrote:
On 05/30/10 10:10 PM, Mike Hansen wrote:
On Sun, May 30, 2010 at 2:04 PM, Dr. David Kirkby
wrote:
3) I want to add some patches.
I've saved Robert's changes to files /tmp/robert1 and /tmp/
robert2, but when
I import them, hg log shows:
Hi there,
Though sphinx is perfectly working with target in the local module he isn't
able to find reference target from other modules even if they are exported in
all.py. For example, if I want to link Parent from anywhere but parent.pyx, I
have to write the full path (ie. :class:`~sage.
On May 30, 2010, at 4:46 PM, Rob Beezer wrote:
On May 30, 2:46 pm, Mike Hansen wrote:
I've been working on this over the next few days, cleaning up the
code, and making permutation groups act over an "arbitrary" domain.
I'll be posting these in the next few days.
Mike H - thanks for your wor
On May 30, 2010, at 3:33 PM, Jason B Hill wrote:
Sweet!
I'm assuming you're using a dictionary map? I think this could kill
two birds with one stone. If we want to make Sage act more like GAP
and consider the domain of a permutation group to be the collection
of non-fixed points
To cla
On 05/31/10 04:26 PM, MartinX wrote:
You could try making a package using the latest (unstable) ATLAS snapshot. The
ChangeLog shows many new processors added since the release in Sage.
Successful build using ATLAS 2.9.24 directly on LAPACK 3.2.1 tar file
today - no failures running checks and
>
> You could try making a package using the latest (unstable) ATLAS snapshot. The
> ChangeLog shows many new processors added since the release in Sage.
>
Successful build using ATLAS 2.9.24 directly on LAPACK 3.2.1 tar file
today - no failures running checks and timing stages which is
encouragin
I believe the ATLAS package has modifications to the upstream source code, as
some files in the 'patches' subdirectory are identical to those in the original
source code directory. This is now:
http://trac.sagemath.org/sage_trac/ticket/9103
Furthermore, ATLAS was apparently updated to the late
Note that there are many different rings of modular forms, not one,
but to be consistent we should probably change ModularFormsRing to
ModularFormRing. Compare also the general constructor PolynomialRing
which is not PolynomialsRing!
John
On 31 May 2010 11:59, Tim Joseph Dumol wrote:
> On Mon,
On 05/31/10 10:45 AM, Dr. David Kirkby wrote:
On 05/31/10 01:58 AM, MartinX wrote:
PS I meant type i5-750 processor not 750i in the original post.
I've never used such a processor myself, but I'm not surprised there are
not tuning parameters as that processor is quite new. Fortunately, ATLAS
On Mon, May 31, 2010 at 6:30 PM, Nicolas Borie wrote:
> Hello all!
>
> I have a language question: which one of the following is the correct
> name for the semiring of non-negative integers:
>
> - NonNegativeIntegerSemiring
> - NonNegativeIntegersSemiring
>
> On IRC, Tim suggested :
> (12:15:44
Hello all!
I have a language question: which one of the following is the correct
name for the semiring of non-negative integers:
- NonNegativeIntegerSemiring
- NonNegativeIntegersSemiring
On IRC, Tim suggested :
(12:15:44) nborie: English Language question : we say Integer Ring,
not Integers R
On 05/31/10 01:58 AM, MartinX wrote:
Luck was never my strong point. nothing like a problem to get one up
the learning curve though.
True
If I do fix it I'll post back here.
That would be good. Do you have a trac account? If so, can you create a ticket
for this. If not, either I can crea
On 05/31/10 10:17 AM, Dr. David Kirkby wrote:
It might be different on 't2' (I've not tried), since ATLAS of the T2+
processors on 't2.math', whereas ATLAS is aware of the older UltraSPARC
III+ processors I have.
What I mean is ATLAS is unaware of the T2+ processors, whereas it has
informatio
On 05/31/10 05:52 AM, William Stein wrote:
I've never had this problem building on 32-bit SPARC, or 64-bit OpenSolaris
x64. I only see it on 64-bit Solaris 10 SPARC. Perhaps the behavior is
undefined if the dependency is missing, and it just happens by luck to work
on the other systems. Either th
> Although I am used to learning the hard way, I
> find that there are few free resources (as in beer) for learning
> JavaScript, so I don't really know how to start with the existing
> code.
These are nice, though not definitive:
https://developer.mozilla.org/en/Core_JavaScript_1.5_Guide
https:/
> I think you've found a bug in the makefile.
>
> We have
>
>LINBOX depends on ATLAS
>
>ATLAS depends on LAPACK and PYTHON
>
>LAPACK depends on FORTRAN
>
>
> It is just a lucky coincidence that the Sage build has actually worked.
> We need to add BLAS as a dependency of LAPACK, e.
Hi,
just FYI..
I uploaded a paper of http://accc.riken.jp/maho/slides/mpack-0.6.4.pdf (sorry
in Japanese)
thanks
-- Nakata Maho http://accc.riken.jp/maho/ , JA OOO http://ja.openoffice.org/
http://blog.goo.ne.jp/nakatamaho/ ,GPG: http://accc.riken.jp/maho/maho.pgp.txt
--
To post to this group
27 matches
Mail list logo