It appears that Sage defaults symbolic variables to the complex field. This is passed along to Maxima, eventually triggering segfaults. Given that all of my variables are real, is it possible to default the symbolic domain to the real field BEFORE asking any calculations of Maxima?
[Related to my thread on the Development mailing list.]
Nils Bruin provided the answer over on sage-devel. It is to insert
maxima_calculus.eval("domain:real;")before the variable declarations.
and it's a hack. Other parts of sage probably expect domain: complex to be active when maxima code is expected, so you may find failures in other areas. This is definitely in the "warranty voided if opened" category. Sage doesn't come with warranty, so you don't lose much ...
You can use the assume function (which is not alwys reliable, so you shoud test it):
sage: var('t')
t
sage: assume(t,'real')
sage: assumptions()
[t is real]Thanks,but that does not work. Sage will send to Maxima something like:
domain: complex;
declare( t, real );Alas, certain expressions involving t will now fail. What I'm looking for is a way to cause Maxima to execute "domain:real;".
You may try to wrap your computation in a try...except...finally structure, starting with maxima_calculus("domain:real") and maxima_calculus("domain:complex") in the finally clause. or, even better, define a decorator or a context.
Asked: 6 years ago
Seen: 322 times
Last updated: Jun 20 '18
Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
