[sage-support] Re: Memory issues with maxima in SAGE

2009-08-21 Thread Ondrej Certik
On Fri, Aug 21, 2009 at 8:22 AM, Mani chandra wrote: > Ondrej Certik wrote: >> On Mon, Aug 17, 2009 at 11:06 AM, William Stein wrote: >> >>> On Mon, Aug 17, 2009 at 6:27 AM, Mani chandra wrote: >>> William Stein wrote: > On Mon, Aug 17, 2009 at 2:26 AM, Juan Jose > Garcia-Ripoll

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-21 Thread Mani chandra
Ondrej Certik wrote: > On Mon, Aug 17, 2009 at 11:06 AM, William Stein wrote: > >> On Mon, Aug 17, 2009 at 6:27 AM, Mani chandra wrote: >> >>> William Stein wrote: >>> On Mon, Aug 17, 2009 at 2:26 AM, Juan Jose Garcia-Ripoll wrote: > On Mon, Aug 17, 2

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-19 Thread Ondrej Certik
On Mon, Aug 17, 2009 at 11:06 AM, William Stein wrote: > > On Mon, Aug 17, 2009 at 6:27 AM, Mani chandra wrote: >> >> William Stein wrote: >>> On Mon, Aug 17, 2009 at 2:26 AM, Juan Jose >>> Garcia-Ripoll wrote: >>> On Mon, Aug 17, 2009 at 10:57 AM, William Stein wrote: > Note that Sa

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-19 Thread Mani chandra
Hi, Sage now runs fine when recompiled with a much larger memory limit for maxima. (Passing the command through maxima() didn't work). Thanks to everybody for helping out. Regards, Mani chandra --~--~-~--~~~---~--~~ To post to this group, send email to sage

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-18 Thread Robert Bradshaw
On Aug 17, 2009, at 2:21 PM, Robert Dodier wrote: > On Aug 17, 12:06 pm, William Stein wrote: > >> My understanding is that one has to modify the maxima source code >> itself and recompile maxima. > > Not so -- EXT:SET-LIMIT can be called anytime after the > Maxima session is launched. > To eval

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-17 Thread Robert Dodier
On Aug 17, 12:06 pm, William Stein wrote: > My understanding is that one has to modify the maxima source code > itself and recompile maxima. Not so -- EXT:SET-LIMIT can be called anytime after the Maxima session is launched. To evaluate a single Lisp expression in Maxima: :lisp (ext:set-limit

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-17 Thread William Stein
On Mon, Aug 17, 2009 at 6:27 AM, Mani chandra wrote: > > William Stein wrote: >> On Mon, Aug 17, 2009 at 2:26 AM, Juan Jose >> Garcia-Ripoll wrote: >> >>> On Mon, Aug 17, 2009 at 10:57 AM, William Stein wrote: >>> Note that Sage's Maxima uses ECL.  So the basic question is, how can we in

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-17 Thread Mani chandra
William Stein wrote: > On Mon, Aug 17, 2009 at 2:26 AM, Juan Jose > Garcia-Ripoll wrote: > >> On Mon, Aug 17, 2009 at 10:57 AM, William Stein wrote: >> >>> Note that Sage's Maxima uses ECL. So the basic question is, how can >>> we increase the memory that Maxima + ECL can use? >>>

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-17 Thread William Stein
On Mon, Aug 17, 2009 at 2:56 AM, Dr. David Kirkby wrote: > > William Stein wrote: >> On Mon, Aug 17, 2009 at 2:26 AM, Juan Jose >> Garcia-Ripoll wrote: >>> On Mon, Aug 17, 2009 at 10:57 AM, William Stein wrote: Note that Sage's Maxima uses ECL.  So the basic question is, how can we incre

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-17 Thread Dr. David Kirkby
William Stein wrote: > On Mon, Aug 17, 2009 at 2:26 AM, Juan Jose > Garcia-Ripoll wrote: >> On Mon, Aug 17, 2009 at 10:57 AM, William Stein wrote: >>> Note that Sage's Maxima uses ECL. So the basic question is, how can >>> we increase the memory that Maxima + ECL can use? >> The limits ECL has ar

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-17 Thread William Stein
On Mon, Aug 17, 2009 at 2:26 AM, Juan Jose Garcia-Ripoll wrote: > On Mon, Aug 17, 2009 at 10:57 AM, William Stein wrote: >> Note that Sage's Maxima uses ECL.  So the basic question is, how can >> we increase the memory that Maxima + ECL can use? > > The limits ECL has are by default too small for

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-17 Thread William Stein
On Sat, Aug 15, 2009 at 5:44 AM, Mani chandra wrote: > Maxima encountered a Lisp error: > >  Memory limit reached. Please jump to an outer point or quit program. > > Automatically continuing. > To reenable the Lisp debugger set *debugger-hook* to nil. > Here's a simpler example to get this error:

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-16 Thread Robert Dodier
Mani chandra wrote: > SB-INT:SIMPLE-READER-PACKAGE-ERROR at 21 (line 1, column 21) on > #: >package "EXT" not found > I'm not sure what implementation of lisp is being used in my Maxima > build and in the one included in SAGE. >From the package names, looks like you have SBCL in the stand-

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-16 Thread Mani chandra
Robert Dodier wrote: > Mani chandra wrote: > > >> I've attached the value of a particular func where it fails. But >> this varies though. Also I restarted the code, making sure I evaluate >> only the problematic part and it works. So, it must be an internal >> memory limit for Maxima. Is th

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-16 Thread Robert Dodier
Mani chandra wrote: > I've attached the value of a particular func where it fails. But > this varies though. Also I restarted the code, making sure I evaluate > only the problematic part and it works. So, it must be an internal > memory limit for Maxima. Is there any way of increasing this?

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-16 Thread Mani chandra
Robert Dodier wrote: > Mani chandra wrote: > > >> Yes, the computation of the "select_mode" function does indeed >> succeed for simple expressions. But if you run the code, you will notice >> that it works for some modes which probably have more complicated >> expressions than the ones for w

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-15 Thread Robert Dodier
Mani chandra wrote: > Yes, the computation of the "select_mode" function does indeed > succeed for simple expressions. But if you run the code, you will notice > that it works for some modes which probably have more complicated > expressions than the ones for which it breaks. Also the modes f

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-15 Thread William Stein
On Sat, Aug 15, 2009 at 11:02 AM, Mani chandra wrote: > > William Stein wrote: >> On Sat, Aug 15, 2009 at 5:44 AM, Mani chandra wrote: >> >>> Hi, >>> >>>    I wrote a code in sage to construct a Low Dimensional model for the >>> Magnetohydrodynamic equations to study dynamos etc... But the program

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-15 Thread Mani chandra
William Stein wrote: > On Sat, Aug 15, 2009 at 5:44 AM, Mani chandra wrote: > >> Hi, >> >>I wrote a code in sage to construct a Low Dimensional model for the >> Magnetohydrodynamic equations to study dynamos etc... But the program >> crashes at different points on different machines with th

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-15 Thread Mani chandra
Robert Dodier wrote: > Mani chandra wrote: > > >> def select_mode(func,l,m,n): >> val = (func*exp(-I*(l*x + m*y + >> n*z))).integrate(x,0,2*pi).integrate(y,0,2*pi).integrate(z,0,2*pi) >> return val/(8*pi**3) >> > > I guess l, m, and n are some integers between -2 and 2. > What is f

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-15 Thread Robert Dodier
Mani chandra wrote: > def select_mode(func,l,m,n): > val = (func*exp(-I*(l*x + m*y + > n*z))).integrate(x,0,2*pi).integrate(y,0,2*pi).integrate(z,0,2*pi) > return val/(8*pi**3) I guess l, m, and n are some integers between -2 and 2. What is func? (I see the definition for it in the code

[sage-support] Re: Memory issues with maxima in SAGE

2009-08-15 Thread William Stein
On Sat, Aug 15, 2009 at 5:44 AM, Mani chandra wrote: > Hi, > >    I wrote a code in sage to construct a Low Dimensional model for the > Magnetohydrodynamic equations to study dynamos etc... But the program > crashes at different points on different machines with the following error: > > Traceback