[sage-devel] Re: We need better counting of doctest failures.

2009/8/11 Minh Nguyen : > > Hi David, > > On Tue, Aug 11, 2009 at 6:49 AM, Dr. David > Kirkby wrote: >> >> >> test.log ends somthing like this. >> >> The following tests failed: >> >> >>         sage -t  "devel/sage/doc/en/constructions/calculus.rst" >>         sage -t  "devel/sage/doc/en/construc

[sage-devel] Re: We need better counting of doctest failures.

Hi David, On Tue, Aug 11, 2009 at 6:49 AM, Dr. David Kirkby wrote: > > > test.log ends somthing like this. > > The following tests failed: > > > sage -t "devel/sage/doc/en/constructions/calculus.rst" > sage -t "devel/sage/doc/en/constructions/linear_algebra.rst" > sage -

[sage-devel] Re: elliptic_e(0.5, 0.1) differs from Mathematica 7 by about 0.04%.

On Mon, Aug 10, 2009 at 10:09 PM, rjf wrote: > > > > On Aug 10, 2:00 pm, William Stein wrote: > > On Mon, Aug 10, 2009 at 12:51 PM, rjf wrote: > > > > > > > > > (RJF) Could you perhaps quote for us the DoD requirements? (and who > in DoD > > > requires them). > > > >(William) No, I definitel

[sage-devel] Re: elliptic_e(0.5, 0.1) differs from Mathematica 7 by about 0.04%.

On Aug 10, 2:00 pm, William Stein wrote: > On Mon, Aug 10, 2009 at 12:51 PM, rjf wrote: > > > > > (RJF) Could you perhaps quote for us the DoD requirements?  (and who in DoD > > requires them). > >(William) No, I definitely can't.   Sorry I can't go into any further details. > > Fascinating

Re: [codenode-devel] Re: [sage-devel] Indents in notebook cells

On Mon, Aug 10, 2009 at 11:08 AM, Dorian Raymer wrote: > Evaluating Kiran's CELL 1 in a codenode python notebook returns a similar > error: > > File "", line 1 > u = 2+3 >^ > IndentationError: unexpected indent > > I don't think this is a sign of any bug, it is simply bad Python syntax.

[sage-devel] Re: Some of the latest (5.19.0) Maxima tests look a lot 'cleaner'

On Mon, Aug 10, 2009 at 3:40 PM, Dr. David Kirkby wrote: > > I'm in the process of running the test suite after patching ECL 9.8.1 to > hopefully get rid of those elliptic integral bugs. > > > Some of the failures in the doc tests seem a result of what appears to > me at least to be a 'cleaner' ou

[sage-devel] Some of the latest (5.19.0) Maxima tests look a lot 'cleaner'

I'm in the process of running the test suite after patching ECL 9.8.1 to hopefully get rid of those elliptic integral bugs. Some of the failures in the doc tests seem a result of what appears to me at least to be a 'cleaner' output. File "/export/home/drkirkby/sage/sage-4.1.1.rc0/devel/sage

[sage-devel] We need better counting of doctest failures.

test.log ends somthing like this. The following tests failed: sage -t "devel/sage/doc/en/constructions/calculus.rst" sage -t "devel/sage/doc/en/constructions/linear_algebra.rst" sage -t "devel/sage/doc/en/constructions/plotting.rst" sage -t "devel/sage/d

[sage-devel] Re: elliptic_e(0.5, 0.1) differs from Mathematica 7 by about 0.04%.

On Mon, Aug 10, 2009 at 12:51 PM, rjf wrote: > > > > On Aug 9, 11:15 pm, William Stein wrote: > . > > > > ECL is massively better than CLISP, and is also the *only* other lisp > that > > is currently supported and builds 100% from source code. Both CMUCL and > > SBCL are immediately ruled

[sage-devel] Re: sage-4.1 on FreeBSD-7.2/i386

On 2009-Aug-10 06:53:38 -0700, William Stein wrote: >On Mon, Aug 10, 2009 at 4:55 AM, Peter Jeremy >wrote: > >> (I realise sage-4.1 has been superseded but it seemed less effort to >> complete the porting work on a single release and forward-port the >> patches in one step rather than continuously

[sage-devel] Re: elliptic_e(0.5, 0.1) differs from Mathematica 7 by about 0.04%.

On Aug 9, 11:15 pm, William Stein wrote: . > > ECL is massively better than CLISP, and is also the *only* other lisp that > is currently supported and builds 100% from source code.   Both CMUCL and > SBCL are immediately ruled out just because of that reason.  This is one of > the DoD requi

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

On Mon, Aug 10, 2009 at 7:29 PM, David Kirkby wrote: > Was this bit of code executed only on Solaris, and not linux or OS X? No, the problem must have been universal. It was located in ecl/src/cmp/sysfun.lsp, a list of translations from lisp forms to C equivalents. I was working on that some days

[sage-devel] Re: Top 10: Sage-4.1 valgrind report

On Mon, Aug 10, 2009 at 11:58 AM, Robert Miller wrote: > Hello all, > > I am going through the results for a valgrind run I did on the full > (long) test suite for Sage-4.1. ... > ... I see five new trac tickets that need to be made I should say *six* new tickets, including the stuff from ell_mod

[sage-devel] Re: [sage-release] Top 10: Sage-4.1 valgrind report

Hi Robert, On Tue, Aug 11, 2009 at 4:58 AM, Robert Miller wrote: > > Hello all, > > I am going through the results for a valgrind run I did on the full > (long) test suite for Sage-4.1. You posted this topic at the right moment. The release management wiki page http://wiki.sagemath.org/release

[sage-devel] Top 10: Sage-4.1 valgrind report

Hello all, I am going through the results for a valgrind run I did on the full (long) test suite for Sage-4.1. Here are the top ten "definitely lost" doctests, along with some explanation when I was able. As I have organized the leaks, I see five new trac tickets that need to be made blockers for

[sage-devel] Re: How might this elliptic_e issue on SPARC hardware with ECL be debugged?

On Aug 10, 11:29 am, David Kirkby wrote: > Is there a test-suite of some sort for Maxima (outside that in Sage of > course)? run_testsuite(); runs Maxima's collection of tests. run_testsuite(tests = [rtest1, rtest2, ...]); runs a subset of the tests. ? run_testsuite says more about options. H

Re: [codenode-devel] Re: [sage-devel] Indents in notebook cells

Evaluating Kiran's CELL 1 in a codenode python notebook returns a similar error: File "", line 1 u = 2+3 ^ IndentationError: unexpected indent I don't think this is a sign of any bug, it is simply bad Python syntax. It doesn't make sense to exec something with leading white space with no

[sage-devel] Re: Fwd: NetworkX licensing change

On Mon, Aug 10, 2009 at 10:19 AM, Minh Nguyen wrote: > > Hi folks, > > FYI: The upcoming NetworkX 1.0 will be licensed under the BSD. > Yeah. I'm really glad they aren't switching to GPLv3! I'm a little surprised by "If after 10 days I get no reply I will consider all of the current NetworkX c

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

2009/8/10 Juan Jose Garcia-Ripoll : > On Mon, Aug 10, 2009 at 6:16 PM, Robert Dodier wrote: >> >> The code in question is function ELLIPTIC-E in maxima/src/ellipt.lisp. >> (Note that there are several similarly-named functions in there, >> so be careful.) > > I have spotted a problem in the inline

[sage-devel] Fwd: NetworkX licensing change

Hi folks, FYI: The upcoming NetworkX 1.0 will be licensed under the BSD. -- Regards Minh Van Nguyen -- Forwarded message -- From: Aric Hagberg Date: Tue, Aug 11, 2009 at 3:15 AM Subject: NetworkX licensing change To: networkx-disc...@googlegroups.com Hi Everyone, For the n

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

William Stein wrote: > > > On Mon, Aug 10, 2009 at 9:20 AM, Juan Jose Garcia-Ripoll > > wrote: > > > On Mon, Aug 10, 2009 at 6:16 PM, Robert > Dodiermailto:robert.dod...@gmail.com>> wrote: > > > > The code in question is function

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

On Mon, Aug 10, 2009 at 9:20 AM, Juan Jose Garcia-Ripoll < juanjose.garciarip...@googlemail.com> wrote: > > On Mon, Aug 10, 2009 at 6:16 PM, Robert Dodier > wrote: > > > > The code in question is function ELLIPTIC-E in maxima/src/ellipt.lisp. > > (Note that there are several similarly-named functi

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

On Mon, Aug 10, 2009 at 6:16 PM, Robert Dodier wrote: > > The code in question is function ELLIPTIC-E in maxima/src/ellipt.lisp. > (Note that there are several similarly-named functions in there, > so be careful.) I have spotted a problem in the inline code generated by ECL at the lowest safety l

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

On Mon, Aug 10, 2009 at 2:22 AM, Juan Jose Garcia-Ripoll wrote: > The way to determine whether it is the compiled code that is > responsible is to execute the same function interpreted and compiled. > But of course, for that we need the particular expression that Maxima > is using. The code in q

[sage-devel] Re: Indents in notebook cells

On Mon, Aug 10, 2009 at 8:43 AM, Kiran Kedlaya wrote: > > What would you expect from the following input into the notebook? > > CELL 1: >u = 2+2 >u = 2+3 > > CELL 2: > print u > > If you try something like this at a command line, the first line gives > an error due to the spaces in front.

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

2009/8/10 John Cremona : > > Surely one option would be to implement elliptic_e ourselves in Sage; > or use the pari library, if it is there?  Some elliptic functions are > there.  If elliptic_e is one of the ones which can be computed > efficiently usn the AGM it should not be hard. > > John IMH

[sage-devel] Indents in notebook cells

What would you expect from the following input into the notebook? CELL 1: u = 2+2 u = 2+3 CELL 2: print u If you try something like this at a command line, the first line gives an error due to the spaces in front. But on my notebook server (running 4.1), the first cell evaluates without

[sage-devel] Re: C++ on Solaris in the matplotlib spkg

On Mon, Aug 10, 2009 at 7:28 AM, Jason Grout wrote: > > I just submitted most of our patches to matplotlib upstream and most > were incorporated into the main matplotlib trunk. One patch remains, > which is applied only when `uname`="SunOS" and applies to a C++ file. > In response to this patch (

[sage-devel] C++ on Solaris in the matplotlib spkg

I just submitted most of our patches to matplotlib upstream and most were incorporated into the main matplotlib trunk. One patch remains, which is applied only when `uname`="SunOS" and applies to a C++ file. In response to this patch (below), the main developer of matplotlib sent the followin

Re: [Maxima] [sage-devel] elliptic_e(0.5, 0.1) differs from Mathematica 7 by about 0.04%.

On Mon, Aug 10, 2009 at 1:02 AM, Dr. David Kirkby wrote: > > Valery Pipin wrote: > > William Stein wrote: > > < > > > > >>> I've no idea how the Sage group would feel about switches lisps. Given > >>> they have just recently done that (I forgot what was used before), > there > >>> might not be too

[sage-devel] Re: Sage benchmark

On Mon, Aug 10, 2009 at 4:39 AM, ggrafendorfer wrote: > > Hi All, > > concerning general benchmarks, here is a site where are plenty of > languages compared to each other (time, memory usage, source code > size): > > http://shootout.alioth.debian.org/gp4/index.php > > if you click on one language

[sage-devel] Re: sage-4.1 on FreeBSD-7.2/i386

On Mon, Aug 10, 2009 at 4:55 AM, Peter Jeremy wrote: > (I realise sage-4.1 has been superseded but it seemed less effort to > complete the porting work on a single release and forward-port the > patches in one step rather than continuously forward-porting bits. I > have an equivalent 4.1.1.rc2 pa

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

On Mon, Aug 10, 2009 at 5:59 AM, John Cremona wrote: > > Surely one option would be to implement elliptic_e ourselves in Sage; > or use the pari library, if it is there? Some elliptic functions are > there. If elliptic_e is one of the ones which can be computed > efficiently usn the AGM it shoul

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

Surely one option would be to implement elliptic_e ourselves in Sage; or use the pari library, if it is there? Some elliptic functions are there. If elliptic_e is one of the ones which can be computed efficiently usn the AGM it should not be hard. John 2009/8/10 Juan Jose Garcia-Ripoll : > > O

[sage-devel] sage-4.1 on FreeBSD-7.2/i386

(I realise sage-4.1 has been superseded but it seemed less effort to complete the porting work on a single release and forward-port the patches in one step rather than continuously forward-porting bits. I have an equivalent 4.1.1.rc2 patchset in boxen:~peter/sage-4.1.1.rc2.patch The "make test" is

[sage-devel] Re: Sage benchmark

Hi All, concerning general benchmarks, here is a site where are plenty of languages compared to each other (time, memory usage, source code size): http://shootout.alioth.debian.org/gp4/index.php if you click on one language, you can easily choose the other one to compare with, etc..., Georg

[sage-devel] Re: [Ecls-list] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

On Mon, Aug 10, 2009 at 9:42 AM, Dr. David Kirkby wrote: > You probably see my previous posts on the fact that elliptic_e is giving > incorrect results on SPARC hardware using ECL. If not, > http://sagetrac.org/sage_trac/ticket/6716 > has the details. I will remove maxima mailing list from this a

[sage-devel] Re: pictures in the reference manual?

John H Palmieri wrote: > On Aug 5, 4:29 pm, John H Palmieri wrote: >> Should we allow the inclusion of pictures in the reference manual? We >> could have a directory >> >> SAGE_ROOT/devel/sage/doc/en/reference/pictures >> >> and then in docstrings in the Sage library code, a line like >> >> .

Re: [Maxima] [sage-devel] elliptic_e(0.5, 0.1) differs from Mathematica 7 by about 0.04%.

Valery Pipin wrote: > William Stein wrote: > < > > >>> I've no idea how the Sage group would feel about switches lisps. Given >>> they have just recently done that (I forgot what was used before), there >>> might not be too much enthusiasm for it. >> Since you have no idea, perhaps I should clari

[sage-devel] Re: Sage benchmark

On Aug 8, 12:44 pm, "Dr. David Kirkby" wrote: > Has anyone ever thought of developing a Sage benchmark... I was thinking about a benchmark website, presenting some tasks and their timings. I've never finished it but it would still be nice if there is something as part of the sage-tour. What co

[sage-devel] How might this elliptic_e issue on SPARC hardware with ECL be debugged?

You probably see my previous posts on the fact that elliptic_e is giving incorrect results on SPARC hardware using ECL. If not, http://sagetrac.org/sage_trac/ticket/6716 has the details. Can anyone who knows the internals of Maxima tell me what standard libraries supplied with Solaris the fun