Hi
Yes, ticket at http://trac.sagemath.org/sage_trac/ticket/14209 .
Maxima does call defint if you specify limits.
This problem is inside the ECL call (maxima_ecal) in maxima_lib.py. I tried
not sending the stdout to dev null, and in the same place setting
debugmode=true, but then got dropped in a shell whose syntax I don't know
at all.
Changes to get stdout and to turn on debugmode:
1
jan@tunis:/srv/local/Disk_Space/sage-5.7/devel/sage-maximabug/sage/interfaces$diff
-ruN maxima_lib_orig.py maxima_lib.py
--- maxima_lib_orig.py 2013-03-01 16:01:14.000000000 +0200
+++ maxima_lib.py 2013-03-01 16:06:58.000000000 +0200
@@ -132,7 +132,8 @@
ecl_eval(r"""(defparameter *dev-null* (make-two-way-stream
(make-concatenated-stream) (make-broadcast-stream)))""")
ecl_eval("(setf original-standard-output *standard-output*)")
-ecl_eval("(setf *standard-output* *dev-null*)")
+ecl_eval("#$debugmode(true)$")
+#ecl_eval("(setf *standard-output* *dev-null*)")
#ecl_eval("(setf *error-output* *dev-null*)")
## Default options set in Maxima
1
jan@tunis:/srv/local/Disk_Space/sage-5.7/devel/sage-maximabug/sage/interfaces$mysage
-b maximabug
That got me this far:
0 jan@tunis
:/srv/local/Disk_Space/sage-5.7/devel/sage-maximabug/sage/interfaces$mysage
----------------------------------------------------------------------
| Sage Version 5.7, Release Date: 2013-02-19 |
| Type "notebook()" for the browser-based notebook interface. |
| Type "help()" for help. |
----------------------------------------------------------------------
sage: from sage.interfaces.maxima_lib import sr_to_max
Loading maxima-grobner $Revision: 1.6 $ $Date: 2009-06-02 07:49:49 $
sage: integral(e^(-abs(x))/cosh(x),x,-infinity,infinity)ax
2*log(2)
sage: integral(e^(-abs(x))/cosh(x),x,-infinity,infinity)
-- an error. Entering the Maxima debugger.
Enter ':h' for help.
(dbm:1) :h
Break commands start with ':'. Any unique substring may be used,
eg :r :re :res all work for :resume.
Command Description
----------- --------------------------------------
:break Set a breakpoint in the specified FUNCTION at the
specified LINE offset from the beginning of the function.
If FUNCTION is given as a string, then it is presumed to be
a FILE and LINE is the offset from the beginning of the file.
:bt Print a backtrace of the stack frames
:continue Continue the computation.
:delete Delete all breakpoints, or if arguments are supplied delete the
specified breakpoints
:disable Disable the specified breakpoints, or all if none are specified
:enable Enable the specified breakpoints, or all if none are specified
:frame With an argument print the selected stack frame.
Otherwise the current frame.
:help Print help on a break command or with no arguments on
all break commands
:info Print information about item
:lisp Evaluate the lisp form following on the line
:lisp-quiet Evaluate the lisp form without printing a prompt
:next Like :step, except that subroutine calls are stepped over
:quit Quit this level
:resume Continue the computation.
:step Step program until it reaches a new source line
:top Throw to top level
:_none Undocumented
I've yet to dig into this. And here in Cape Town it is late Friday
afternoon ;)
Regards,
Jan
On 1 March 2013 15:54, kcrisman <kcris...@gmail.com> wrote:
>
>
> On Friday, March 1, 2013 7:52:12 AM UTC-5, Jan Groenewald wrote:
>>
>> This reproduces the error:
>>
>> sage: from sage.interfaces.maxima_lib import sr_to_max
>> sage: sr_to_max(integral(e^(-abs(x))**/cosh(x),x,-infinity,infinity)**)
>> <ECL: ((MTIMES) ((%LOG) 2) 2)>
>> sage: sr_to_max(integral(e^(-abs(x))**/cosh(x),x,-infinity,infinity)**)
>> ------------------------------**------------------------------**
>> ---------------
>> ValueError ** Traceback (most recent call
>> last)
>>
>>
>>
> Jan, can you open a ticket for this? I may have time to look into it this
> weekend. It does seem quite odd; maybe there is something we are not
> parsing as output.
>
> That said, the relevant Maxima command wouldn't be defint - I believe we
> just use "integrate(...,x,a,b)", though perhaps internally in Maxima that
> calls defint, I wouldn't be surprised. But that could be our problem, too.
>
> - kcrisman
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
.~.
/V\ Jan Groenewald
/( )\ www.aims.ac.za
^^-^^
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
