On Feb 18, 2008 8:29 PM, Ben Goodrich <[EMAIL PROTECTED]> wrote: > > On Feb 18, 3:58 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: > > I believe Sage simply calls Maxima for the solution. Since you > > obviously know the > > most about the problem, perhaps the easiest thing to do would be to > > determine > > that it is Sage and not Maxima that is at fault. Perhaps you could see if > > the solution is obtained in Maxima? (On the command line of Sage, you > > can simply type "maxima_colsole()"; in the notebook I believe there is > > a drop down > > menu for maxima mode.) > > > > I tried running it via maxima mode under the Online Notebook, but it > ran for about an hour without producing any output. In SAGE mode, it
To me that suggests a Maxima bug. > (now) produces something in a few seconds. So, I think I would be okay Something *correct*? > if I knew how to interpret the output. For example, what does the r35 > mean in "lambda_42: r35"? This syntax does not seem to appear in the I don't see how that contains debugging info. I thin it means it is the 35th R-expression that Sage has had to keep track of to run that particular session. > documentation. > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
