-
-
Notifications
You must be signed in to change notification settings - Fork 561
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
add a free_variables() method? #20179
Comments
comment:1
These are practically all variables, minus the one(s) the limit is over? |
comment:2
The free variables in an expression are all its variables excluding any that are bound, for example, in limits, sums, products, or integrals. See for example https://en.wikipedia.org/wiki/Free_variables_and_bound_variables for a definition. |
comment:3
Implemented in pynac git master. Will be in the upcoming Pynac-0.7.6. |
comment:5
This is not ready for review because it doesn't work as expected but at least the interface is there now. New commits:
|
Commit: |
Author: Ralf Stephan |
Dependencies: #22844 |
comment:8
The problems seem resolved, now that there is a symbolic limit, and code in Pynac master that recognizes it and its bound symbols. |
comment:10
Is this ready for review? If so, then you can set it to positive review on my behalf. |
Reviewer: Travis Scrimshaw |
comment:11
Yes, I usually wait until the merge of the Pynac upgrade because not all reviewers want to go through the hassle of manual Pynac install. Thanks. |
Changed branch from u/rws/add_a_free_variables___method_ to |
It can be useful to query the free variables in an expression. SR's
variables()
andarguments()
return all variables in an expression, whether free or bound. For example:I would like to have a
free_variables()
method that returns onlyy
in this case. Is there a recommended way to get this information from an expression?Depends on #22844
Depends on #23134
CC: @EmmanuelCharpentier
Component: symbolics
Author: Ralf Stephan
Branch/Commit:
5b93a06
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/20179
The text was updated successfully, but these errors were encountered: