On Dec 13, 8:27 pm, Nils Bruin <nbr...@sfu.ca> wrote: > On Dec 13, 11:07 am, kcrisman <kcris...@gmail.com> wrote: > > > Yes, we try to turn it off as much as possible - > > seehttp://hg.sagemath.org/sage-main/file/9e29a3d84c48/sage/interfaces/ma... > > and the keepfloat:true. What an unhelpful error message, then! > > I think the error is triggered by an actual bug in "rationalize" > somewhere, so it might be worth reporting the error upstream. There is > no reason why "replace a float by a nearby rational number" should > ever fail. > > Workaround: > > sage: integrate(f(1.5,1,t), (t,0,2*pi)) > sage: M=sage.calculus.calculus.maxima > sage: M.eval("keepfloat: false;") > 'false' > sage: integrate(f(1.5,1,t), (t,0,2*pi)) > -2*pi > sage: M.eval("keepfloat: true;") # this is the default > 'true' > sage: integrate(f(1.5,1,t), (t,0,2*pi)) > RuntimeError
The workaround should give a correct answer with newer maxima. (As I have noticed) with the present maxima version the result -2*pi is wrong -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
