-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
give solution constants of ODEs unique names #16007
Comments
comment:2
Actually, these variables are very easy to recognize any way:
As you can see, maxima creates these constants as |
Branch: u/rws/ticket/16007 |
comment:4
Indeed, many thanks. With this easy patch the output is now
Any more variables? New commits:
|
Commit: |
Changed dependencies from #8734 to none |
Author: Ralf Stephan |
comment:5
seems to be a duplicate of #9421. Paul |
comment:6
Yes. So, are you okay with this solution applied to #9421, instead of the warning? If so, then I will make a reviewer's patch there and invalid this ticket. |
comment:7
yes I agree with this solution, but I won't have time quite soon to check the doctests still pass. Paul |
comment:8
It might be worth doing a few things. First, you must have documentation testing this fix - especially since people will be confused by underscore variables without some documentation! Also, how many different things can show up? Just But I agree it's very unlikely for anyone to have an underscore variable, so this could be a good compromise... there remains the issue of substituting in for non-Sageified variables. |
comment:11
Deleted misplaced comment. |
comment:12
Maxima-discuss list mail:
I take it then the ticket is complete for review. |
comment:13
Thanks for doing that due diligence. Yes, I believe these only arise from a contrib package in Maxima.
Well... see in comment:8
It's really unfortunate with the underscores. But I hate to think of checking whether
then as I said, this is definitely much better than leaving it 'as is'. |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:15
Merged in #8734. Thanks for the doctest reminder. |
comment:16
No problem. Do you think it's useful to add an example where there might have otherwise been a collision of names, or is that superfluous? Also, why is the doctest
and not
I'm not sure what the |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:35
Well, now there is a code point where the behaviour can be changed. So, again, is there anything missing? |
comment:36
Turns out it currently just keeps the underscore. This change could minutely slow down latex for variables that start with underscores, or if the symtable gets huge... but that is probably silly to worry about for now, neither are likely in the near future. Also may help with #6882. So I'm happy with this commit.
Doctest (presumably just in |
comment:38
Replying to @kcrisman:
I appreciate your thoroughness, and thanks for the review! |
comment:39
Okay, if doctests pass (currently attempting to build the branch but it will take a while) then I'm happy with this. Thanks for working on so many symbolics/calculus things recently. |
comment:41
Doctests don't pass (try
|
comment:42
Nuts!!! I could have sworn I checked everything... and now I see why long tests on #8734 are taking so long too, I did |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:44
Not all of #8734 was merged. Sorry for the inconvenience. |
comment:45
So has the code from #8734 been reviewed? If not make it a dependency here so I don't accidentally merge it. |
Dependencies: #8734 |
comment:48
I am not going to check whether this passes tests, but at any rate the changes most recent seem fine, although I don't know why the non-doctest pieces had to have the constant |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:50
Thanks. Pulled in changes from dependencies. I'll run a patchbot on this now. |
Changed branch from u/rws/ticket/16007 to |
Changed commit from |
(this was reported as part of #6882)
... solving of ode y'=c*x is not correct, the free variable is messed up with a parameter, see sage-devel - thanks for Yuri Karadzhov
the answer should be something like 1/2cx2 + c1
The fix depends on closing #8734. The
c
variable that comes from Sage can then be easily recognized, and the constantc
should then be renamed toc1
or_C1
.Depends on #8734
CC: @kcrisman
Component: calculus
Author: Ralf Stephan
Branch:
a8df107
Reviewer: Nils Bruin, Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/16007
The text was updated successfully, but these errors were encountered: