-
-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
desolve_system unable to interpret ilt and Maxima's temporary variables #9825
Comments
comment:1
On [ this Maxima list thread] we get the original system in Maxima notation - thanks to Stavros Macrackis:
He also provides a simpler example which does this:
The suggestion is that the ilt should be replacing the |
comment:2
Replying to @kcrisman:
Meaning this thread. |
comment:3
I've followed up again at this new thread - apparently it never actually made it to their bug tracker? |
comment:4
See also this ask.sagemath question. |
comment:5
And this ask.sagemath question, though here Maxima is actually asking a question about these variables! |
Upstream: Reported upstream. No feedback yet. |
comment:10
Did you report it upstream to their bug tracker? I never heard on either of these emails, so I think this is how it will have to be reported. |
comment:11
I took your repeated mail to the list as report. |
comment:12
Sadly, that isn't always enough :( Reported upstream here, however, just now. There was internal discussion in the original Maxima thread so I took it that the experts had several possible resolutions. |
Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, in a later stable release. |
comment:14
Upstream seems to have made a change that would do something about this. Anyone want to give it a whirl? |
comment:15
This now returns |
comment:16
Replying to @rwst:
According to the documentation of |
comment:17
This is now fixed (probably due to upstream upgrade) :
==> invalidation of the bug and review query in order to get this bug closed. HTH, |
comment:18
I guess as usual doctest needed? Looks like it was a combination of their upstream fix and something we did to parse it right. |
Commit: |
comment:20
Doctest added. HTH, New commits:
|
Reviewer: Karl-Dieter Crisman |
comment:21
Thanks, this is great. Despite patchbot not yet reporting and my own Sage install being too brittle to test, Cell server says it's fine so let's do it. |
Author: Emmanuel Charpentier |
Changed branch from u/charpent/desolve_system_unable_to_interpret_ilt_and_maxima_s_temporary_variables to |
desolve_system sometimes generates a Maxima result that includes temporary variables that Sage does not parse correctly.
Upstream: Fixed upstream, in a later stable release.
CC: @robert-marik
Component: calculus
Keywords: maxima, symbolics
Author: Emmanuel Charpentier
Branch/Commit:
74d88f4
Reviewer: Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/9825
The text was updated successfully, but these errors were encountered: