>
> Dunno what's going on here, but when I try this in Maxima 5.19.2
> it works OK (I get a list of values from ufourn).
> I can post a session log later if there is interest.
>
Robert et al.,
Yes, please do post a log - there may some additional Maxima commands
called by Sage that trigger this than you use in your session.
>From a 2007 Maxima list thread about exactly this kind of situation:
>The "Too many contexts" is a side effect of some logic
>in the integration code. $INTEGRATE eventually calls the aptly-named
>MONSTERTRIG which calls $INTEGRATE as a special case,
>and then it just goes round and round. See src/sin.lisp.
>
>The call to trigreduce is the key point here. It modifies the
>integrand so as to avoid triggering the MONSTERTRIG bug.
Did this bug ever get fixed (I ask out of ignorance)? Could this be
related, assuming it did get fixed? After looking at this and
db.lisp, it seems that perhaps Sage wasn't the culprit (this time!
many other times it is). But maybe Sage is setting more contexts
somehow (I am not exactly sure how Sage sets contexts, though).
- kcrisman
PS, not necessarily relevant: On the Maxima lists, it seems this is
set at 50 at compile time. Can one do the following suggestion (taken
from the list) later? It may not help, of course, if there really is
a horrible loop.
The default number of contexts allowed is 50. You can change that by
setting the internal parameter ?connumber (the question mark indicates
that
it is internal), e.g.
?connumber : 500 $
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
