[sage-devel] Re: Sage Integral Test Suite

2008-11-26 Thread Bill Page
On Wed, Nov 26, 2008 at 12:28 AM, Tim Lahey wrote: On Nov 26, 2008, at 12:25 AM, Bill Page wrote: That magic worked. 'integral_test1.sage' runs as expected. Now I'm happy. :-) Thanks! Great. If you have any suggestions (or code), I'd be happy to hear them. One thing that I wanted to

[sage-devel] Re: Sage Integral Test Suite

2008-11-26 Thread mabshoff
On Nov 26, 4:54 pm, Bill Page [EMAIL PROTECTED] wrote: On Wed, Nov 26, 2008 at 12:28 AM, Tim Lahey wrote: SNIP Hi Bill, In order to run these tests, it is also necessary to make some simple additions to the 'axiom.py' interface: [EMAIL

[sage-devel] Re: Sage Integral Test Suite

2008-11-26 Thread Tim Lahey
On Nov 26, 2008, at 7:54 PM, Bill Page wrote: One thing that I wanted to do with your code is to include comparisons of the answers produced by both Maxima and FriCAS as well as the comparison to the Schaum's tabulated value. Here is a small patch to 'integral_test1.sage' (changes to other

[sage-devel] Re: Sage Integral Test Suite

2008-11-26 Thread mabshoff
On Nov 26, 5:13 pm, Tim Lahey [EMAIL PROTECTED] wrote: On Nov 26, 2008, at 7:54 PM, Bill Page wrote: Hi Tim, One thing that I wanted to do with your code is to include comparisons of the answers produced by both Maxima and FriCAS as well as the comparison to the Schaum's tabulated

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Bill Page
Tim, What version of sage is required to run this? I get the following error: [EMAIL PROTECTED]:~$ ./sage*/sage -- | SAGE Version 3.1.4, Release Date: 2008-10-20 | | Type notebook() for the GUI, and

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Bill Page
On Tue, Nov 25, 2008 at 7:58 PM, Tim Lahey wrote: As Mike said, it requires Sage 3.2. After an apparently sucessful 'sage -upgrade': [EMAIL PROTECTED]:~$ sage -- | Sage Version 3.2, Release Date: 2008-11-20

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Tim Lahey
On Nov 25, 2008, at 10:16 PM, Bill Page wrote: [EMAIL PROTECTED]:~$ ./integral_test1.sage Test 1 : Test Passed. Maxima Time: Traceback (most recent call last): File ./integral_test1.py, line 96, in module time_Maxima_friCAS(integrand) File ./integral_test1.py, line 81, in

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Bill Page
On Tue, Nov 25, 2008 at 10:32 PM, Tim Lahey wrote: Strange, The timeit code is in sage/misc/sage_timeit.py and sage/misc/sage_timeit_class.py so I'd check to see if the code there has the stats attribute. If it does, I'd assume that somehow Sage didn't pick up the change. I do not have

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Mike Hansen
Hi Bill, On Tue, Nov 25, 2008 at 8:00 PM, Bill Page [EMAIL PROTECTED] wrote: It seems that none of these files has anything named 'stats': It appears that 'sage_timeit.py' was not updated by '-upgrade'. Note: Directory sage-3.1.4 is where I previously built sage from source. I did not

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Tim Lahey
On Nov 25, 2008, at 11:00 PM, Bill Page wrote: I do not have any file named 'sage/misc/sage_timeit_class.py', instead there is 'sage/misc/sage_timeit_class.c' and 'sage/misc/sage_timeit_class.pyx' [EMAIL PROTECTED]:~/sage-3.1.4$ find . -name sage_timeit.py

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Bill Page
On Tue, Nov 25, 2008 at 11:05 PM, Mike Hansen wrote: On Tue, Nov 25, 2008 at 8:00 PM, Bill Page wrote: It seems that none of these files has anything named 'stats': It appears that 'sage_timeit.py' was not updated by '-upgrade'. Note: Directory sage-3.1.4 is where I previously built sage

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Mike Hansen
On Tue, Nov 25, 2008 at 8:38 PM, Bill Page [EMAIL PROTECTED] wrote: Still unhappy. Did it really mean 'don't forget to commit'? Where? Regards, Bill Page. You just run hg ci to commit the merge. Then to make the changes active, you have to start sage with sage -br. --Mike

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Bill Page
On Tue, Nov 25, 2008 at 11:10 PM, Tim Lahey wrote: ... However, it sage_timeit.py there should be the class, class SageTimeitResult(): r I represent the statistics of a timeit() command. I print as a string so that I can be easily returned to a user. def

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread William Stein
On Tue, Nov 25, 2008 at 8:44 PM, Bill Page [EMAIL PROTECTED] wrote: On Tue, Nov 25, 2008 at 11:10 PM, Tim Lahey wrote: ... However, it sage_timeit.py there should be the class, class SageTimeitResult(): r I represent the statistics of a timeit() command. I print as a string so

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Bill Page
On Tue, Nov 25, 2008 at 11:42 PM, Mike Hansen wrote: On Tue, Nov 25, 2008 at 8:38 PM, Bill Page wrote: Still unhappy. Did it really mean 'don't forget to commit'? Where? You just run hg ci to commit the merge. Then to make the changes active, you have to start sage with sage -br. That

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Tim Lahey
On Nov 26, 2008, at 12:25 AM, Bill Page wrote: That magic worked. 'integral_test1.sage' runs as expected. Now I'm happy. :-) Thanks! Great. If you have any suggestions (or code), I'd be happy to hear them. Cheers, Tim. --- Tim Lahey PhD Candidate, Systems Design Engineering

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread Bill Page
On Wed, Nov 26, 2008 at 12:14 AM, William Stein wrote: Bill Page wrote: After the merge the dates on the 'sage_timeit.py' file did not change and there is no 'class SageTimeitResult' in that file. You definitely haven't upgraded to sage-3.2 then. Try this from sage: sage: hg_sage.ci()

[sage-devel] Re: Sage Integral Test Suite

2008-11-25 Thread William Stein
On Tue, Nov 25, 2008 at 9:28 PM, Bill Page [EMAIL PROTECTED] wrote: On Wed, Nov 26, 2008 at 12:14 AM, William Stein wrote: Bill Page wrote: After the merge the dates on the 'sage_timeit.py' file did not change and there is no 'class SageTimeitResult' in that file. You definitely haven't