I'm getting a strange error with the following command:
find_maximum_on_interval(-x^2 + 9*x, 4.4, 8)
this returns the error:
RuntimeError: ECL says: THROW: The catch MACSYMA-QUIT is undefined.
I tried this on 4.7.2, 4.7.1, and on the single-cell server, and the same
thing occurs.
--
To pos
On Sun, Nov 13, 2011 at 8:10 PM, Dima Pasechnik wrote:
>
>
> On Thursday, 15 September 2011 05:16:38 UTC+8, R. Andrew Ohana wrote:
>>
>> sqrt5.cs should back up now.
>
> seems to be down again...
Thanks for the report. I'm guessing it is some kind of power or
dynamic ip issue. I might be able t
On Thursday, 15 September 2011 05:16:38 UTC+8, R. Andrew Ohana wrote:
>
> sqrt5.cs should back up now.
seems to be down again...
> On Sun, Sep 11, 2011 at 10:15, William Stein wrote:
> > On Sun, Sep 11, 2011 at 10:05 AM, R. Andrew Ohana
> > wrote:
> >> I'm not in Seattle currently, so I ca
Seems to be down again...
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
On Sun, Nov 13, 2011 at 6:19 PM, William Stein wrote:
> On Sun, Nov 13, 2011 at 5:48 PM, Adrian Seyboldt
> wrote:
>> Hello,
>>
>> I think I found a bug in the eigenvalues method of Matrices over
>> QQbar:
>
> This is definitely a serious bug. Thanks for reporting it! Basically
> root finding of
On Sun, Nov 13, 2011 at 5:48 PM, Adrian Seyboldt
wrote:
> Hello,
>
> I think I found a bug in the eigenvalues method of Matrices over
> QQbar:
This is definitely a serious bug. Thanks for reporting it! Basically
root finding of a polynomial over QQbar is failing.
I've opened a ticket:http:
Hello,
I think I found a bug in the eigenvalues method of Matrices over
QQbar:
Eigenvalues that are found over AA are not found when using QQbar.
H_AA = Matrix(AA, 8, lambda i, j: 1/(i + j + 1))
H_QQbar = Matrix(QQbar, 8, lambda i, j: 1/(i + j + 1))
E_AA = H_AA.eigenvalues()
E_QQbar = H_QQbar.ei
Hello. Here are some 2011 website stats:
Today marks the day when the number of page visits equals all the
visits from 2010.
2010: Jan 1st until Dec 31st:
1,030,456 Visits
607,883 Unique Visitors
2,735,611 Pageviews
2011: Jan 1st until Nov 13th:
1,028,793 Visits668,738 Unique Visitors2,548,789 P
Thanks, I missed the Xcode 4 part. I'll check it out.
On Nov 13, 1:34 pm, William Stein wrote:
> On Sun, Nov 13, 2011 at 1:27 PM, john.hoebing wrote:
> > I've reviewed those two tickets and I see some
> > discussion about the combo of Lion/Xcode4 but
> > I don't see a pointer to either a tar ba
On Sun, Nov 13, 2011 at 1:27 PM, john.hoebing wrote:
> I've reviewed those two tickets and I see some
> discussion about the combo of Lion/Xcode4 but
> I don't see a pointer to either a tar ball or patches
> to get an alpha 4.8 sage that will (start to) build
> on OS 10.7.x.
One of John Palmierri
I've reviewed those two tickets and I see some
discussion about the combo of Lion/Xcode4 but
I don't see a pointer to either a tar ball or patches
to get an alpha 4.8 sage that will (start to) build
on OS 10.7.x.
My build system is a new mac mini with
Lion/Xcode4 installed by default, and I'm not
Hi Sage Developers,
After deleting the server directory we need to add doctests to
about588 more functions to get coverage to 90%, which is a major goal
forsage-5.0, which we've been working on getting to for over a year
now.I did an audit and came up with about 350 functions in 18 files
forwhich a
> Anything that makes the doctests scream qualifies as a bug. Anything
> that is not even a bug but that is not the behaviour you expected also
> qualifies as a bug, even though it may just mean rewriting some
> documentation :-)
Ok I created some tickets:
doctest failure in linear_programming.rst
Hello !!
> seriously. But to go into the details with each failing test takes
> time and is tedious, so I think it is better to avoid possible
> problems (like those with the multible solutions) whenever possible.
Yepyep. All that needs to be fixed :-)
> I fully agree - is it okay if I crea
On Nov 13, 4:53 pm, Nathann Cohen wrote:
> Helloo Emil !
>
> Well, it looks like I am to blame for most of these errors :-/
Hi Nathan, thanks for quick response!
I am not sure if those are errors, but when I, as a non export, try to
build sage then I take failing doctests
seriously
Helloo Emil !
Well, it looks like I am to blame for most of these errors :-/
The first one is about a matching in Petersen's Graph. Then the error in
the gale_ryser theorem function. Both codes are calling GLPK (I assume that
you have not installed the CBC package ? Or CPLEX ?), and
I compiled sage 4.7.2 (and eventually use the new make micro_install
option) on my Live CD base distro. But I got some doctest failures.
With two of them I get different correct solutions compared to the
solutions in the doctests. Other failures seem specific for my setup.
Could you give me advice
Strangely, that piece of code works here when run manually:
...allations/sage-4.7 [130] > ./sage -python
Python 2.6.4 (r264:75706, Jul 17 2011, 20:26:56)
[GCC 4.4.5] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import subprocess
>>> P = subprocess.Popen("./
18 matches
Mail list logo
