-
-
Notifications
You must be signed in to change notification settings - Fork 558
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 Stieltjes constants #19834
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:5
For the sake of representation: should there be two separate functions, say Of course, like |
comment:6
... or just |
Author: Ralf Stephan |
comment:8
This is what Sage needs to use the current pynac git master implementation of Stieltjes constants (not generalized). New commits:
|
Commit: |
Dependencies: pynac-0.6.1 |
comment:9
Why are you making |
comment:10
Ho I see. This is actually needed for the array of functions. |
comment:11
Yes, everything symbolic is rooted through Pynac, so |
Changed dependencies from pynac-0.6.1 to #19448 |
comment:14
I just resolved the merge conflict with New commits:
|
Changed branch from u/rws/implement_symbolic_stieltjes_constants to u/behackl/symbolics/stieltjes-constants |
Reviewer: Benjamin Hackl |
comment:15
Implementation looks fine to me; doctests pass. I'd still like to see if the patchbot is satisfied, too. I'll set this to |
comment:17
Thanks! |
Changed branch from u/behackl/symbolics/stieltjes-constants to |
Probably just another symbolic function would suffice. This would be needed for zeta expansion and special values. The Sage side would be a new
GinacFunction
and numeric evaluation.Depends on pynac/pynac#120
See also #18141.
Depends on #19948
CC: @behackl
Component: symbolics
Author: Ralf Stephan
Branch/Commit:
0e1162b
Reviewer: Benjamin Hackl
Issue created by migration from https://trac.sagemath.org/ticket/19834
The text was updated successfully, but these errors were encountered: