On Fri, Jun 11, 2010 at 7:30 PM, Minh Nguyen wrote:
> The Developer's
> Guide lacks a list of general areas against which testing should be
> performed and test code written.
This is now ticket #9241:
http://trac.sagemath.org/sage_trac/ticket/9241
--
Regards
Minh Van Nguyen
--
To post to
Hello,
I'm trying to test some patches and I want to try them on t2. I
downloaded a binary [1], untarred it, and started it -- and it failed:
ImportError: ld.so.1: python: fatal: relocation error: file
/disk/scratch/drake/t2/sage-4.4.2-t2.math/local/lib//libgmpxx.so.3: symbol
_ZNKSt5ctypeIc
Dear sage-devel,
I believe that the following:
sage: gamma(x).full_simplify()
factorial(x - 1)
is not correct, because in Sage factorial(x) is defined only if x is a
non-negative integer. The problem arises because behind the scenes
full_simplify() uses Maxima, and for Maxima factorial(x) is e
Dear sage-devel,
Applying full_simplify() to gamma functions sometimes causes an
error. For example, this is correct:
sage: gamma(4/3).full_simplify()
1/3*gamma(1/3)
but this fails:
sage: gamma(1/3).full_simplify()
boom!
The error occurs because full_simplify() here runs the following
Maxima
On Mon, 14 Jun 2010 at 11:17AM -0500, Jonathan Gutow wrote:
> Testers needed! I think I finally solved all my asynchronicity
> problems with Jmol and the notebook. I have now opened a ticket in
> trac (ticket #9238) with the new javascript libraries attached (Hope
> that was the right thing to do:)
I really think that spliting users into "developers" and "non
developers" is very much against the spirit of open source
Any barrier of entrance to development is against that.
Moreover, I think that the idea of that all the environment has to be
controlled when building sage and therefore all th
On Mon, Jun 14, 2010 at 5:12 PM, Bill Hart wrote:
> Just a note: the standard gcc with Debian Lenny is gcc 4.3.2. This is
> so buggy it fails to compile MPIR correctly. And yes, we've checked
> that it is a gcc bug and it has been reported.
Is there a workaround? E.g., using -O0 or something? J
On Mon, Jun 14, 2010 at 2:52 PM, David Kohel wrote:
> Hi,
>
> Backwards compatibility or not, I consider this either a bad design
> or a bug:
>
> sage: M = Matrix([[1,-1],[1,0]])
> sage: f = M.minimal_polynomial()
> sage: f.roots()
> []
> sage: M.eigenvalues()
> [0.5? - 0.866025403
> Nope. You can (and I hope will) *definitely* safely just delete that
> whole function.
> [...]
> This is now http://trac.sagemath.org/sage_trac/ticket/9239
Done
Florent
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sa
Just a note: the standard gcc with Debian Lenny is gcc 4.3.2. This is
so buggy it fails to compile MPIR correctly. And yes, we've checked
that it is a gcc bug and it has been reported.
It is fixed in a later gcc. But that means all Debian Lenny users will
not be able to get correct results until t
On 6/14/10 6:19 PM, Florent Hivert wrote:
So basically you still want to write
A = copy(B) # create a semantic copy but no actual copy is done
A[1,2] = 4 # the copy is triggered...
An since the actual entries of the matrix are stored in an attributes called
_entries, two different mat
Why are they trying to link directly with the C++ standard library and
libgcc_s anyway. That looks wrong. The system is supposed to do that,
assuming you have the correct LD_LIBRARY_PATH.
I doubt libtool does this automatically. As we've discovered before,
libtool has bugs on solaris.
Bill.
On J
On Mon, Jun 14, 2010 at 3:50 PM, Florent Hivert
wrote:
> Hi Jason,
>
>>> Looking into sage library, I found the following code: file matrix0.pyx
>>>
>>> cdef class Matrix(sage.structure.element.Matrix):
>>> ...
>>> def __copy__(self):
>>> """
>>> ...
>>> "
Hi David,
On Mon, 14 Jun 2010 15:13:53 -0700 (PDT), daveloeffler
wrote:
> I looked for examples where TestSuite doctests already exist (and
> pass), but in all the ones I found either the element class didn't
> really do anything (e.g. the examples in sage/categories/examples) or
> the element
On Mon, Jun 14, 2010 at 4:11 PM, Dr. David Kirkby
wrote:
> On 06/14/10 11:23 PM, akuloncmir wrote:
>>
>> When building Sage as a user without root privileges on a machine with
>> CPU throttling enabled, is ATLAS built or does Sage just rely on
>> standard BLAS?
>
> I don't know.
Sage builds ATLAS
Hi Robert,
>>> Copy on write *should* be rather easy to implement for matrices at least.
>>
>> This is both true and false:
>>
>> Making the data-structure for having copy-on-write object is fairly easy.
>> This
>> is just aving an extra level of indirection and we have something good for
>
On 06/14/10 11:23 PM, akuloncmir wrote:
When building Sage as a user without root privileges on a machine with
CPU throttling enabled, is ATLAS built or does Sage just rely on
standard BLAS?
I don't know.
=
It appears you have cpu throttling enabled, which makes timings
unreliable and an
Hi Jason,
>> Looking into sage library, I found the following code: file matrix0.pyx
>>
>> cdef class Matrix(sage.structure.element.Matrix):
>> ...
>> def __copy__(self):
>> """
>> ...
>> """
>> return self.__copy__()
>>
>> what is the intention
Hi,
On Mon, Jun 14, 2010 at 03:13:53PM -0700, daveloeffler wrote:
> I've been doing some work adding doctests to some files that don't
> have them, and the coverage script kept telling me to put in a
> "TestSuite.run()" doctest.
>
> Can someone tell me how on earth I can get one of these to
On Fri, May 21, 2010 at 02:19:37PM -0700, John H Palmieri wrote:
> If I'm defining a new class and I want to implement a TestSuite for
> it, well, there is some stuff built in, but I should perhaps also add
> methods called "_test_X" for various values of X. If I doctest these
> via
>
> sage: o
David,
All good points.
> I don't agree that this is the most natural result for first year
> calculus or linear algebra. Many will only consider real
> solutions to be valid.
I wish I had my bookshelf of roughly thirty intro linear algebra
textbooks handy, but I'll go out on a limb and suggest
On 6/14/10 5:10 PM, Florent Hivert wrote:
Hi there,
Looking into sage library, I found the following code: file matrix0.pyx
cdef class Matrix(sage.structure.element.Matrix):
...
def __copy__(self):
"""
...
"""
return self.__copy__()
what
When building Sage as a user without root privileges on a machine with
CPU throttling enabled, is ATLAS built or does Sage just rely on
standard BLAS?
http://math-atlas.sourceforge.net/errata.html#cputhrottle
I'm aware of this,
=
http://wiki.sagemath.org/faq
QUESTION: Sage 2.9 and higher fa
I believe several of you here (William, Burchan perhaps Robert) are the Pynac
developers. Perhaps you have some idea why this is failing to build on 64-bit
OpenSolaris
Whilst compiling pynac, it is creating 64-bit objects, but then tries to link
them to the 32-bit libraries in /usr/local/gcc-4
I've been doing some work adding doctests to some files that don't
have them, and the coverage script kept telling me to put in a
"TestSuite.run()" doctest.
Can someone tell me how on earth I can get one of these to actually
work? No matter what I do, if X is a parent object,
"TestSuite(X).run()"
Hi there,
Looking into sage library, I found the following code: file matrix0.pyx
cdef class Matrix(sage.structure.element.Matrix):
...
def __copy__(self):
"""
...
"""
return self.__copy__()
what is the intention here ? I hope this code is never e
Hi,
Backwards compatibility or not, I consider this either a bad design
or a bug:
sage: M = Matrix([[1,-1],[1,0]])
sage: f = M.minimal_polynomial()
sage: f.roots()
[]
sage: M.eigenvalues()
[0.5? - 0.866025403784439?*I, 0.5? +
0.866025403784439?*I]
First of all, wh
On 6/14/10 11:17 AM, Jonathan Gutow wrote:
Dear all,
Testers needed! I think I finally solved all my asynchronicity problems
with Jmol and the notebook. I have now opened a ticket in trac (ticket
#9238) with the new javascript libraries attached (Hope that was the
right thing to do:). Please try
On Mon, Jun 14, 2010 at 11:05 AM, Dr. David Kirkby
wrote:
> On 06/14/10 06:39 PM, William Stein wrote:
> OK, we will agree to differ. I can't see what harm issuing a warning does -
> especially for novice users.
>
> In contrast, deepening on your point of view, logging data with fake files
> can b
On 06/14/10 06:39 PM, William Stein wrote:
On Mon, Jun 14, 2010 at 9:11 AM, Dr. David Kirkby
wrote:
On 06/14/10 04:28 PM, William Stein wrote:
On Mon, Jun 14, 2010 at 3:49 AM, Dr. David Kirkby
Hence I'd propose that any attempt to set CC, CXX, FC, or F77 caused the
build to exit with a wa
On Mon, Jun 14, 2010 at 9:11 AM, Dr. David Kirkby
wrote:
> On 06/14/10 04:28 PM, William Stein wrote:
>>
>> On Mon, Jun 14, 2010 at 3:49 AM, Dr. David Kirkby
>
>>> Hence I'd propose that any attempt to set CC, CXX, FC, or F77 caused the
>>> build to exit with a warning. Then allow an environment v
On Mon, Jun 14, 2010 at 9:28 AM, Simon King wrote:
> Hi William!
>
> On Jun 14, 5:16 pm, William Stein wrote:
>> If you just google the error message, you get this thread, which
>> explains where it comes from (Singular's libfac):
>>
>> http://groups.google.com/group/macaulay2/browse_thread/thre
Miguel,
Having read #8974 carefully, I could see the default for endomorphisms
going either way. My main concern is that matrices follow practice
and default to providing eigenvalues (and eigenvectors) outside the
base field. Endomorphisms could default to behave identically to
matrices, or they
On Jun 14, 5:24 pm, mmarco wrote:
> I am OK with keeping the default extend=True. But i would like it to
> be the opposite in the case of endomorphisms (i know it is not a good
> idea to have different default behaviours for matrices and
> endomorphisms, so i won't argue if its decided to keep it
Hi William!
On Jun 14, 5:16 pm, William Stein wrote:
> If you just google the error message, you get this thread, which
> explains where it comes from (Singular's libfac):
>
> http://groups.google.com/group/macaulay2/browse_thread/thread/c3311f3...
Thanks! This would also explain why it happene
I am OK with keeping the default extend=True. But i would like it to
be the opposite in the case of endomorphisms (i know it is not a good
idea to have different default behaviours for matrices and
endomorphisms, so i won't argue if its decided to keep it alwais true
as default).
My reason to pref
On 06/14/10 04:28 PM, William Stein wrote:
On Mon, Jun 14, 2010 at 3:49 AM, Dr. David Kirkby
Hence I'd propose that any attempt to set CC, CXX, FC, or F77 caused the
build to exit with a warning. Then allow an environment variable like
SAGE_ALLOW_SETTING_OF_COMPILERS
(better name?)
that wil
On 14 June 2010 17:16, William Stein wrote:
> On Mon, Jun 14, 2010 at 7:11 AM, Simon King wrote:
>> Hi all!
>>
>> In my computations, I sometimes have to do factorisation of
>> multivariate polynomials over GF(2). Sometimes this crashes with the
>> "last words" (note the misspelling)
>> convertF
I am happy with that. After all:
sage: a=3
sage: a.sqrt()
sqrt(3)
works like this since the extend parameter defaults to True. Compare:
sage: a.sqrt(extend=False)
...
ValueError: square root of 3 not an integer
John
On 14 June 2010 16:24, William Stein wrote:
> On Mon, Jun 14, 2010 at 8:22 A
I certainly agree that not all code has the same status as regards the
need for it to be tested on all platforms, etc.
Alex G and I extended coverage on databases/cremona.py but did not
achieve 100%. The reason: there are functions here which are *only*
needed to rebuild the elliptic curve datab
Dear all,
Testers needed! I think I finally solved all my asynchronicity problems with
Jmol and the notebook. I have now opened a ticket in trac (ticket #9238) with
the new javascript libraries attached (Hope that was the right thing to do:).
Please try it out and let me know of problems. I
On Mon, Jun 14, 2010 at 7:11 AM, Simon King wrote:
> Hi all!
>
> In my computations, I sometimes have to do factorisation of
> multivariate polynomials over GF(2). Sometimes this crashes with the
> "last words" (note the misspelling)
> convertFacCF2NTLGF2X: coefficient not immidiate!
If you just
I could not find "immidiate" in Sage source or NTL source or Flint
source. So where is that error message coming from?
John
On 14 June 2010 15:11, Simon King wrote:
> Hi all!
>
> In my computations, I sometimes have to do factorisation of
> multivariate polynomials over GF(2). Sometimes this cr
On Mon, Jun 14, 2010 at 3:49 AM, Dr. David Kirkby
wrote:
> The recent thread:
>
> "Error building Sage 4.4.3 under vanilla Debian lenny amd64: Error while
> installing flint"
>
> http://groups.google.com/group/sage-devel/browse_thread/thread/54531b50412b9882/2f45257c5e56ab00?lnk=gst&q=Error+buildi
On Mon, Jun 14, 2010 at 8:22 AM, Rob Beezer wrote:
> On Jun 14, 6:12 am, mmarco wrote:
>> So, what do you think?
>
> Sure, but can the default remain extend = True and maintain your
> desire for correctness?
It has to. I think it would be a very bad idea to change the default
behavior, since
On Mon, Jun 14, 2010 at 5:17 AM, Dr. David Kirkby
wrote:
> On 06/14/10 12:18 PM, Tim Joseph Dumol wrote:
>>
>> On Mon, Jun 14, 2010 at 7:09 PM, Dr. David Kirkby
>> wrote:
>>>
>>> On 06/14/10 11:41 AM, Tim Joseph Dumol wrote:
Doctests are used to prevent regressions and (unwanted) backw
On Jun 14, 6:12 am, mmarco wrote:
> So, what do you think?
Sure, but can the default remain extend = True and maintain your
desire for correctness?
If a student has to read examples to get complex eigenvalues out of a
real (or rational) matrix, the utility of Sage for teacing
introductory line
I'm happy with the proposed change; as John points out, we already
have a sqrt() function that behaves similarly.
David
On Jun 14, 3:15 pm, mmarco wrote:
> On 14 jun, 15:45, John Cremona wrote:
>
> > I think that sounds a good idea; but can we call the parameter
> > "extend" and not "base_exte
On 06/14/10 02:03 PM, ross kyprianou wrote:
Its unlikely that someone will sometime declare "we dont need any more
tests for existing code" so are we just debating over the order that
the tests will be incorporated?
But what is happening is even worst. There is now the assumption that "It's sa
On 14 jun, 15:45, John Cremona wrote:
> I think that sounds a good idea; but can we call the parameter
> "extend" and not "base_extend"? First, as that is less frightening
> for users (who will need examples to show that for a real matrix, if
> you want complex eigenvalues you have to ask for
Hi all!
In my computations, I sometimes have to do factorisation of
multivariate polynomials over GF(2). Sometimes this crashes with the
"last words" (note the misspelling)
convertFacCF2NTLGF2X: coefficient not immidiate!
It is not really reproducible (sorry that I am not able to provide a
prop
I think that sounds a good idea; but can we call the parameter
"extend" and not "base_extend"? First, as that is less frightening
for users (who will need examples to show that for a real matrix, if
you want complex eigenvalues you have to ask for them), and also for
consistency with (for example
That sounds like a very good idea, especially if there will be someone
there who has given such an introductory talk before.
John
(a speaker at, but not an organiser of, SD23)
On 14 June 2010 13:15, Francesco Biscani wrote:
> Hello list,
>
> I just noticed on the website that the next SAGE days
AMS-SIAM Special Session on Mathematics of Computation: Algebra and
Number Theory
http://www.ams.org/meetings/national/jmm/2125_program_ss11.html#title
Not sure if relevant but anyway wanted to point it out.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe fro
During the discusion about ticket 8974
https://webmail.unizar.es/horde/imp/login.php
i noted that the behaviour of eigenvectors, eigenspaces and
eigenvalues method of matrices is not mathematically correct. Or being
more precise, it does not translate directly into mathematically
correct methods fo
It seems harmless as a short term strategy to use the 130 modules that
have been identified to get Sage to 90% coverage.
Once that is met, I imagine the next goal would be 95% then 100% coverage.
And from what Ive seen of the Sage developer community there would
then be a revisiting and addition of
On 06/14/10 01:17 PM, Dr. David Kirkby wrote:
On 06/14/10 12:18 PM, Tim Joseph Dumol wrote:
As for Cython and gcc, the Sage notebook uses pure Python. I do
acknowledge that there's a minuscule chance that a Python update could
change runtime behaviour.
But what is used to build python? - gcc
On 06/14/10 12:18 PM, Tim Joseph Dumol wrote:
On Mon, Jun 14, 2010 at 7:09 PM, Dr. David Kirkby
wrote:
On 06/14/10 11:41 AM, Tim Joseph Dumol wrote:
Doctests are used to prevent regressions and (unwanted) backward
incompatibilities. Since the code used in these modules are not ever
going to
Hello list,
I just noticed on the website that the next SAGE days will be held in
Leiden. I'm currently working as a research fellow at the European
Space Agency establishment ESTEC in Noordwijk (~10 km from Leiden). I
was wondering if there is any interest in giving a presentation about
SAGE to m
On Mon, Jun 14, 2010 at 7:09 PM, Dr. David Kirkby
wrote:
> On 06/14/10 11:41 AM, Tim Joseph Dumol wrote:
>>
>> Doctests are used to prevent regressions and (unwanted) backward
>> incompatibilities. Since the code used in these modules are not ever
>> going to be modified, it does not seem necessar
On 06/14/10 11:41 AM, Tim Joseph Dumol wrote:
Doctests are used to prevent regressions and (unwanted) backward
incompatibilities. Since the code used in these modules are not ever
going to be modified, it does not seem necessary to provide doctests,
IMHO.
Personally I'd beg to differ. A change
The recent thread:
"Error building Sage 4.4.3 under vanilla Debian lenny amd64: Error while
installing flint"
http://groups.google.com/group/sage-devel/browse_thread/thread/54531b50412b9882/2f45257c5e56ab00?lnk=gst&q=Error+building+Sage+4.4.3+under+vanilla+Debian+lenny+amd64%3A+Error+while+ins
Doctests are used to prevent regressions and (unwanted) backward
incompatibilities. Since the code used in these modules are not ever
going to be modified, it does not seem necessary to provide doctests,
IMHO.
On Mon, Jun 14, 2010 at 6:34 PM, Dr. David Kirkby
wrote:
> On 06/14/10 05:15 AM, Minh N
On 06/14/10 05:15 AM, Minh Nguyen wrote:
Hi folks,
In a recent thread [1] on sage-notebook, it was suggested that files
under the component
sage/server
need not contribute to the total doctest coverage.
That seems a slightly strange decision to me. From the link it is apparent the
code is s
64 matches
Mail list logo
