-
-
Notifications
You must be signed in to change notification settings - Fork 557
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
implement symbolic product #17505
Comments
This comment has been minimized.
This comment has been minimized.
comment:3
Note that if #20179 is implemented it has to be adapted when symbolic products are made available. |
This comment has been minimized.
This comment has been minimized.
comment:6
Replying to @EmmanuelCharpentier:
Yes, but as you can see with #22844 it may not work 100%. |
This comment has been minimized.
This comment has been minimized.
Branch: u/rws/implement_symbolic_product |
comment:9
do you mind adding since:
New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:11
This doesn't have the |
Author: Ralf Stephan |
comment:12
Replying to @rwst:
First of all, thank you very much for this addition, which should enhance Sage's usefulness fo high-school/undergrad levels. However,
The second and third ones have been reported for 8.0.beta4 and are seen again in 8.0beta5. Nothing new here, so probably not related. The third one is new :
The last one is identical to one already seen in 8.0.beta4 and 8.0.beta5 ; again, nothing new, else probably not related. The four first ones seem identical : aren't they related to an undeclared variable ?
==> |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:15
Ah sorry just a moment, I'll address your other issues ASAP. |
comment:30
Replying to @EmmanuelCharpentier:
However, isn't it the duty of power to make the braces? |
comment:31
Replying to @rwst:
Not necessarily. There is still an ambiguity, that does not concern us there : tensors. But that's another whole can of worms. Your patch looks good. |
comment:32
Two new failures :
It seems that you forgot to upate your doctests... ;-) ==> |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:34
Hopefully my reviewers keep their patience. Thanks. |
comment:35
Replying to @rwst:
|
comment:36
==> Since this was tested on top of #22937, the latter is also ready for re-review. Would you mind ? |
comment:37
|
comment:38
The ticket was merged up to a point. I'll close it and put the branch with the remaining issues in another ticket. See #22989. |
comment:39
Replying to @rwst:
You mean in #22937, I suppose ?
Hmm... Unles I'm mistaken, there are two consequences :
|
comment:40
Sorry, forgot to close this ticket. Move your new commits to a new ticket. |
The symbolic product is currently broken in Sage :
At the moment anonymous functions named
product
can be created via the Maximapexpect
interface and they even behave as products in specific cases:The present ticket aims at creating a Sage function/method either evaluating the sum, or correctly creating a unevaluted symbolic product object.
For evaluation the ticket would have to decide which of (Maxima,SymPy) would be used as default for this.
Creating products by casting a Maxima expression via the library interface gives nonsense, see #17502.
CC: @EmmanuelCharpentier
Component: symbolics
Author: Ralf Stephan
Branch/Commit: u/rws/implement_symbolic_product @
5779423
Reviewer: Emmanuel Charpentier
Issue created by migration from https://trac.sagemath.org/ticket/17505
The text was updated successfully, but these errors were encountered: