-
-
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
maxima sum returns hypergeometric function #9908
Comments
comment:1
one additional example by omologos on irc:
but i get this error:
|
comment:2
This should be
If I'm not mistaken, this might be related to #2516, in the sense that we should be parsing hypergeometric functions correctly and that would be part of that ticket. |
comment:4
This also causes a similar problem in #4102:
In that case, Maxima is returning |
comment:6
See also http://ask.sagemath.org/question/3091 for another example. |
Changed keywords from none to hypergeometric |
comment:9
And see this sage-support thread for possibly another example. |
comment:11
#2516 has all the examples above in it, with the exception of the ones mentioned in the comments.
without using W|A; apparently
would also be doable with hypergeometrics. |
comment:12
Replying to @kcrisman:
What I get with #2516 is
|
comment:13
Not really worth keeping open, as even Maxima does this.
Interestingly, this works in vanilla Sage as well. Maybe there weren't any hg functions to begin with there. I assume it was fixed with #16224 - earlier it gave yet another (wrong) answer. So I nominate to close this ticket. |
Reviewer: Karl-Dieter Crisman, Ralf Stephan |
comment:14
Even more interestingly, this is not as simple as just |
comment:15
Practically a duplicate of #2516 |
The parsing of Maxima's output is not good enough to handle this:
gives an exception
which is - i think - a f_43 hypergeometric function.
CC: @eviatarbach
Component: symbolics
Keywords: hypergeometric
Reviewer: Karl-Dieter Crisman, Ralf Stephan
Issue created by migration from https://trac.sagemath.org/ticket/9908
The text was updated successfully, but these errors were encountered: