In sage 6.5beta2, I find the following incoherence between Sage's Maxima called from its own command line and from Sage's interface :
Maxima CL : charpent@asus16-ec:~$ sage -maxima ;;; Loading #P"/usr/local/sage-6.5/local/lib/ecl/sb-bsd-sockets.fas" ;;; Loading #P"/usr/local/sage-6.5/local/lib/ecl/sockets.fas" ;;; Loading #P"/usr/local/sage-6.5/local/lib/ecl/defsystem.fas" ;;; Loading #P"/usr/local/sage-6.5/local/lib/ecl/cmp.fas" Maxima 5.34.1 http://maxima.sourceforge.net using Lisp ECL 13.5.1 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. (%i1) ratsimp(integrate(%e^-x*sinh(sqrt(x)),x,0,inf)), gamma_expand:super; 1/4 %e sqrt(%pi) (%o1) --------------- 2 In Sage : sage: maxima("ratsimp(integrate(%e^-x*sinh(sqrt(x)),x,0,inf)), gamma_expand:super;") (%e^(1/4)*sqrt(%pi)-2*('limit(%e^(-x-sqrt(x))*(sqrt(4*x+4*sqrt(x)+1)*(2*sqrt(%pi)*sqrt(x)*%e^(x+sqrt(x)+1/4)*erfc(sqrt((4*x+4*sqrt(x)+1)/4))-sqrt(%pi)*%e^(x+sqrt(x)+1/4)*erfc(sqrt((4*x+4*sqrt(x)+1)/4)))+sqrt(4*x-4*sqrt(x)+1)*(sqrt(%pi)*erfc(sqrt(-(-4*x+4*sqrt(x)-1)/4))*%e^(x+sqrt(x)+1/4)+2*%e^(1/4)*sqrt(%pi)*erfc(sqrt(-(-4*x+4*sqrt(x)-1)/4))*sqrt(x)*%e^(x+sqrt(x)))+(8*x-2)*%e^(2*sqrt(x))-8*x+2)/(16*x-4),x,inf,minus)))/2 Sage's notion of Maxima's "domain" f*cking things up *again* ? Or something more subtle ? The former seems likely : Maxima's default for domain is "real" (and in turns out that my example runs under this assumption). In sage, immediatly after the horror reported above : sage: maxima("domain") complex sage: maxima("domain:real;") real sage: maxima("ratsimp(integrate(%e^-x*sinh(sqrt(x)),x,0,inf)), gamma_expand:super;") %e^(1/4)*sqrt(%pi)/2 This problem happens often enough to make me wonder if integrate, limit and analytical friends shouldn't deserve a "maxima_domain" option, set to "complex" by default but settable as "real for one-shots. <PipeDream> Similarly, an easy shortcut such as analytical_domain (or maxima.domain ?) could be introduced and widely publicized... </PipeDream> Wups : it happens that maxima.domain() exists, and the doc asserts that it's default is ... "real". So why did I get the "complex" behaviour ? It seems that trying to set Maxima's working value of domain via this interface is ... ineffective ... Is that a known problem ? HTH, -- Emmanuel Charpentier HTH, -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
