-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
symbolic Laguerre / associated Laguerre polynomials #17151
Comments
This comment has been minimized.
This comment has been minimized.
New commits:
|
Commit: |
Author: Ralf Stephan |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
For some reason this branch is red. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
|
Changed branch from u/rws/symbolic_laguerre___associated_laguerre_polynomials to u/rws/17151 |
comment:12
|
comment:27
Not a bug, but would be nice to have: the implementation doesn't seem to know that L(n, 0) = 1 and more generally L(n, α, 0) = binomial(n+α,n). |
comment:29
Replying to @mezzarobba:
Equivalently to #16813 this behaviour can only be changed when we have #18832. EDIT: |
Changed branch from u/rws/17151-1 to u/rws/17151-2 |
comment:31
With the new branch all other comments were addressed. New commits:
|
comment:32
needs rebase, does not apply |
comment:33
rebased New commits:
|
Changed branch from u/rws/17151-2 to public/ticket/17151 |
comment:34
As explained in one of my previous comments, I still don't understand why you don't like the idea of using Thanks for working on it! |
Reviewer: Marc Mezzarobba |
comment:35
Thanks for the review. |
Changed branch from public/ticket/17151 to |
Not only is
laguerre(n,x)
not symbolic, a naive implementation is already 2x as fast atn=100
and 10x atn=1000
:Depends on #17953
Component: symbolics
Keywords: special, function, holonomic, orthogonal
Author: Ralf Stephan
Branch/Commit:
f0d809f
Reviewer: Marc Mezzarobba
Issue created by migration from https://trac.sagemath.org/ticket/17151
The text was updated successfully, but these errors were encountered: