I know this is late, but all tests passed and the build went fine on
my work machine, which runs amd64 hardy heron.
On Tue, Nov 11, 2008 at 7:24 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> here is 3.2.rc0 and I have to confess that I cheated: I did build this
> on numerous platf
On Nov 11, 2008, at 04:24 , mabshoff wrote:
>
> Hello folks,
[snip]
>
> Sources and a sage.math only binary can be found at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/
Built w/o problems on Mac OS X, 10.5.5 (Dual Quad Xeon). Testing
revealed two failures (see below)
> > sage: numpy.linalg.inv(a)
> >
> > array([[ 2.25125019e+15, -4.50250038e+15, 2.25125019e+15],
> > [ -4.50250038e+15, 9.00500077e+15, -4.50250038e+15],
> > [ 2.25125019e+15, -4.50250038e+15, 2.25125019e+15]])
>
> I get this:
> sage: scipy.linalg.inv(a)
>
> array([[
John H Palmieri wrote:
> sage: scipy.linalg.det(a)
> 0.0
> sage: scipy.linalg.inv(a)
>
> array([[ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15],
>[ 9.00719925e+15, -1.80143985e+16, 9.00719925e+15],
>[ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15]])
> sage: nump
mabshoff wrote:
>
>
> On Nov 12, 4:28 pm, Jason Grout <[EMAIL PROTECTED]> wrote:
>> John H Palmieri wrote:
>
>
>
>>> Oh, this is the problem. I'm running tcsh (I got used to it years
>>> ago, and keep deciding it's too much work to switch). When I switch
>>> to bash, everything works.
>> I
> One more time, could you do the following sequence of commands so that I
> can report them to the numpy mailing list. I've left the output from my
> run; it's interesting that the numpy.linalg.inv on my computer gives the
> same ridiculous answers that your scipy.linalg.inv command gives. It
>
On Nov 12, 4:28 pm, Jason Grout <[EMAIL PROTECTED]> wrote:
> John H Palmieri wrote:
> > Oh, this is the problem. I'm running tcsh (I got used to it years
> > ago, and keep deciding it's too much work to switch). When I switch
> > to bash, everything works.
>
> I get the same error (using ba
John H Palmieri wrote:
> On Nov 11, 12:07 pm, mabshoff <[EMAIL PROTECTED]> wrote:
>> On Nov 11, 12:02 pm, John H Palmieri <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>> On Nov 11, 11:57 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
John H Palmieri wrote:
> On Nov 11, 4:24 am, mabshoff <[EMAIL PROTEC
Actually, I have a numpy question, and since we're on the topic ...
The following is somewhat frustrating:
sage: R = RDF['x']
sage: f = R([4, 4, 1, 4, 2, 0, 1])
sage: f.roots(algorithm='pari')
[(-1.0, 1), (-1.0, 1)]
sage: f.roots() # uses numpy
[]
sage: import numpy
sage: numpy.roots(f.reverse(
John H Palmieri wrote:
> On Nov 12, 6:41 am, Jason Grout <[EMAIL PROTECTED]> wrote:
>> John H Palmieri wrote:
>>> an error in matrix_double_dense, which I couldn't find on trac (should
>>> I create a ticket?):
>>> sage -t devel/sage/sage/matrix/matrix_double_dense.pyx
>>>
On Nov 12, 8:20 am, Jason Grout <[EMAIL PROTECTED]> wrote:
> John H Palmieri wrote:
> > On Nov 12, 6:41 am, Jason Grout <[EMAIL PROTECTED]> wrote:
> >> John H Palmieri wrote:
> >>> an error in matrix_double_dense, which I couldn't find on trac (should
> >>> I create a ticket?):
>
> Yes, please cre
John H Palmieri wrote:
> On Nov 12, 6:41 am, Jason Grout <[EMAIL PROTECTED]> wrote:
>> John H Palmieri wrote:
>>> an error in matrix_double_dense, which I couldn't find on trac (should
>>> I create a ticket?):
Yes, please create tickets for both of these errors.
> sage: scipy.linalg.det(b)
> 0.
On Nov 12, 6:41 am, Jason Grout <[EMAIL PROTECTED]> wrote:
> John H Palmieri wrote:
> > an error in matrix_double_dense, which I couldn't find on trac (should
> > I create a ticket?):
>
> > sage -t devel/sage/sage/matrix/matrix_double_dense.pyx
> >
John H Palmieri wrote:
>> Expect some numerical noise doctest failures and some other related
>> known issues. Please report issues here and check trac for existing
>> tickets.
>
> On an intel mac running 10.5 (after changing my stone-age shell :),
> sage -testall has two or three problems:
>
>
Hi all,
So there's one annoying new problem with rc0, and it's partly my
fault. Here's the issue: if you do a fresh build, and then clone, it's
going to do a sage -ba. The underlying problem is coming from the way
trac #4500 (which is a genuine bug) interacts with our new build
system. I'll fix i
mabshoff wrote:
> Hello folks,
>
> Sources and a sage.math only binary can be found at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/
>
On Fedora 8, 32 bits one test failure:
[EMAIL PROTECTED] sage-3.2.rc0]$ ./sage -t
devel/sage/sage/combinat/species/library.py
sage
I got the same matrix_double_dense failure as J. Palmieri on intel
macs running 10.4 and 10.5, plus this one which only occured on the
10.5 machine:
sage -t devel/sage/sage/calculus/wester.py
**
File "/Users/mh/sagestuff/sage-3.
mabshoff wrote:
>
> Sources and a sage.math only binary can be found at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/
>
On Fedora 9, 32 bits the one and only failure:
sage -t devel/sage/sage/combinat/root_system/weyl_characters.py*** *** Error:
TIMED OUT! *** ***
**
> Expect some numerical noise doctest failures and some other related
> known issues. Please report issues here and check trac for existing
> tickets.
On an intel mac running 10.5 (after changing my stone-age shell :),
sage -testall has two or three problems:
the known numerical noise problem in
On Nov 11, 12:07 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> On Nov 11, 12:02 pm, John H Palmieri <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Nov 11, 11:57 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> > > John H Palmieri wrote:
> > > > On Nov 11, 4:24 am, mabshoff <[EMAIL PROTECTED]> wrote:
> > > >> He
On Nov 11, 12:02 pm, John H Palmieri <[EMAIL PROTECTED]> wrote:
> On Nov 11, 11:57 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
>
>
> > John H Palmieri wrote:
> > > On Nov 11, 4:24 am, mabshoff <[EMAIL PROTECTED]> wrote:
> > >> Hello folks,
>
> > >> here is 3.2.rc0 and I have to confess that I ch
Jaap Spies wrote:
> John H Palmieri wrote:
>> On Nov 11, 4:24 am, mabshoff <[EMAIL PROTECTED]> wrote:
>>> Hello folks,
>>>
>>> here is 3.2.rc0 and I have to confess that I cheated: I did build this
>>> on numerous platforms before announcing here (if you hung out in IRC
>>> you knew about this rel
On Nov 11, 11:57 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
> John H Palmieri wrote:
> > On Nov 11, 4:24 am, mabshoff <[EMAIL PROTECTED]> wrote:
> >> Hello folks,
>
> >> here is 3.2.rc0 and I have to confess that I cheated: I did build this
> >> on numerous platforms before announcing here (if you
John H Palmieri wrote:
> On Nov 11, 4:24 am, mabshoff <[EMAIL PROTECTED]> wrote:
>> Hello folks,
>>
>> here is 3.2.rc0 and I have to confess that I cheated: I did build this
>> on numerous platforms before announcing here (if you hung out in IRC
>> you knew about this release for about 6 hours now
On Nov 11, 11:27 am, John H Palmieri <[EMAIL PROTECTED]> wrote:
> On Nov 11, 4:24 am, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > Hello folks,
>
> > here is 3.2.rc0 and I have to confess that I cheated: I did build this
> > on numerous platforms before announcing here (if you hung out in IRC
> > y
On Nov 11, 4:24 am, mabshoff <[EMAIL PROTECTED]> wrote:
> Hello folks,
>
> here is 3.2.rc0 and I have to confess that I cheated: I did build this
> on numerous platforms before announcing here (if you hung out in IRC
> you knew about this release for about 6 hours now) and as it turns out
> my cau
26 matches
Mail list logo
