On 03/13/11 03:34 PM, Julien PUYDT wrote:
Hi,
running "make ptestlong" gave (in part -- the rest is in other mails) :
sage -t -long -force_lib devel/sage/sage/tests/cmdline.py # 2 doctests
failed
sage -t -long -force_lib devel/sage/sage/calculus/riemann.pyx # Time out
But when I ran the first o
On 03/12/11 02:23 PM, Volker Braun wrote:
On Saturday, March 12, 2011 1:49:40 PM UTC, Dr. David Kirkby wrote:
There have been several instances of where doctests have been found to be
wrong,
There have been several instances where stated results in published papers
have been found to be wron
On 03/12/11 08:43 PM, David Roe wrote:
As I've mentioned on a related thread, I think that increasing the quality
of doctests is a valuable goal
Good.
but that we shouldn't add more impediments
to getting code accepted into Sage.
I doubt it is possible to increase the quality of the tests,
> Does anyone have any idea why using a sage integer to index a numpy
> matrix would give me a row vector?!
9 times out of 10 behaviour like that's due to explicit type-checking
at some point instead of try-it-and-see duck typing.. and that seems
to be the case here (discussion on trac).
Doug
-
I've just discovered a confidence-shattering bug with numpy matrices.
sage: mymat = numpy.matrix(numpy.arange(6).reshape(3,2))
sage: mymat[:,0]
matrix([[0, 2, 4]])
sage: mymat[:,int(0)]
matrix([[0],
[2],
[4]])
This caused the value of expressions to change when placed inside a
for
> What Sage version are you using? Since #9734, merged in 4.6.2.alpha3,
> this code no longer gets called unless the base ring is a finite
> field, and for non-finite or non-field base rings there's another code
> path. (Note that this issue has already been reported, see #10008).
Thanks, it works
On Mar 13, 2011, at 13:09 , daveloeffler wrote:
> On Mar 13, 6:34 pm, "Justin C. Walker" wrote:
>> Perhaps I should have expected this, but
>>
>> sage: R=Integers(5)
>> sage: L=R.list()
>> sage: L
>> [0, 1, 2, 3, 4]
>> ## I just want the *non-zero* elements:
>> sage: L.__delitem__(0)
>> sage:
On Mar 13, 6:34 pm, "Justin C. Walker" wrote:
> Perhaps I should have expected this, but
>
> sage: R=Integers(5)
> sage: L=R.list()
> sage: L
> [0, 1, 2, 3, 4]
> ## I just want the *non-zero* elements:
> sage: L.__delitem__(0)
> sage: L
> [1, 2, 3, 4]
> ## Ah!
> ## Uh-oh
> sage: R.list()
> [1,
On Mar 13, 5:04 pm, Christian Stump wrote:
> Hello,
>
> I am trying to get matrix groups for the universal cyclotomic field
> (which I am currently implementing) working. I encountered two
> problems in this context:
>
> 1. the method MatrixGroup_gap.list contains the lines
>
> a = F.prime
Perhaps I should have expected this, but
sage: R=Integers(5)
sage: L=R.list()
sage: L
[0, 1, 2, 3, 4]
## I just want the *non-zero* elements:
sage: L.__delitem__(0)
sage: L
[1, 2, 3, 4]
## Ah!
## Uh-oh
sage: R.list()
[1, 2, 3, 4]
## Better fix that...
sage: R=Integers(5)
## Oops! I've broken Z
Hello,
I am trying to get matrix groups for the universal cyclotomic field
(which I am currently implementing) working. I encountered two
problems in this context:
1. the method MatrixGroup_gap.list contains the lines
a = F.prime_subfield().multiplicative_generator()
b = F.multip
Hi,
the most serious problem I see in my ARM port is the following :
File
"/home/jpuydt/sage-4.6.2/devel/sage/sage/structure/sage_object.pyx",
line 1053:
sage: print "x"; sage.structure.sage_object.unpickle_all() # long
time (4s on sage.math, 2011)
Expected:
x...
Successfully un
Hi,
running "make ptestlong" gave (in part -- the rest is in other mails) :
sage -t -long -force_lib devel/sage/sage/tests/cmdline.py # 2 doctests
failed
sage -t -long -force_lib devel/sage/sage/calculus/riemann.pyx # Time out
But when I ran the first of them again, I got :
$ ./sage -t -lon
Hi,
among the few failing tests with my ARM built, two are because of
accuracy reasons :
File "/home/jpuydt/sage-4.6.2/devel/sage/sage/functions/other.py", line 497:
sage: gamma1(float(6))
Expected:
120.0
Got:
119.97
File "/home/jpuydt/sage-4.6.2/devel/sage/sage/symbol
Le 13/03/2011 06:19, Rob Beezer a écrit :
Are the changes at
"Rewrite ATLAS spkg-install"
http://trac.sagemath.org/sage_trac/ticket/10226
helpful or relevant with the ATLAS install/build?
Orthogonal. I change places where atlas uses the "-m32" flag so that it
doesn't use it on ARM. The "-m32"
15 matches
Mail list logo