Skip to content
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 Nielsen Generalized Polylogarithm #10050

Open
burcin opened this issue Oct 1, 2010 · 8 comments
Open

implement Nielsen Generalized Polylogarithm #10050

burcin opened this issue Oct 1, 2010 · 8 comments

Comments

@burcin
Copy link

burcin commented Oct 1, 2010

Numeric evaluation methods for the Nielsen Generalized Polylogarithm are commented out in the pynac source since it tries to call the CLN library directly. The calls to CLN should be replaced with their MPFR, etc. equivalents and the function made available symbolically in Sage. The Pynac part is pynac/pynac#3

Component: symbolics

Issue created by migration from https://trac.sagemath.org/ticket/10050

@burcin burcin self-assigned this Oct 1, 2010
@zimmermann6
Copy link

comment:1

note that there are issues with the current polylog function:

sage: polylog(2,1.0)
1/6*pi^2
sage: polylog(2,0.9)
polylog(2, 0.900000000000000)

The first command should not evaluate symbolically, since the input 1.0 is a floating-point.
The second command should evaluate numerically, like for example bessel_J(2,0.9).

Should I open a separate ticket?

Paul

@burcin
Copy link
Author

burcin commented Jan 3, 2012

comment:2

Replying to @zimmermann6:

note that there are issues with the current polylog function:

sage: polylog(2,1.0)
1/6*pi^2
sage: polylog(2,0.9)
polylog(2, 0.900000000000000)

The first command should not evaluate symbolically, since the input 1.0 is a floating-point.
The second command should evaluate numerically, like for example bessel_J(2,0.9).

Should I open a separate ticket?

I was thinking of the other polylog like functions from ginac/inifcns_nstdsums.cpp when I created this ticket. It seems even the symbolic evaluation code for these is commented out, so this would require quite a bit more work than I thought. I am removing the beginner keyword and changing this ticket to only mention numeric evaluation of polylogs.

@burcin

This comment has been minimized.

@burcin burcin changed the title wrap the polylogarithm functions from pynac numeric evaluation of polylog Jan 3, 2012
@rwst

This comment has been minimized.

@rwst
Copy link

rwst commented May 9, 2015

comment:4

At the moment Pynac calls symbolic/pynac.pyx:py_li() which calls mpmath. It is not clear to me why the outcommented pynac code would be needed, to remove the call overhead? If you replace the CLN dependency, with what MPFR?, how would this be better or faster than mpmath?

Proposed to be invalid. If you agree I would reword this ticket to fix the mentioned bugs only.

@rwst rwst removed the wishlist item label May 9, 2015
@rwst
Copy link

rwst commented May 9, 2015

comment:5

Ah okay, what was meant in this ticket's description is GiNaC's implementation of the Nielsen Generalized Polylogarithm which is not in mpmath. I have changed the description accordingly.

@rwst

This comment has been minimized.

@rwst rwst changed the title numeric evaluation of polylog implement Nielsen Generalized Polylogarithm May 9, 2015
@rwst
Copy link

rwst commented May 9, 2015

comment:6

Replying to @zimmermann6:

note that there are issues with the current polylog function:

sage: polylog(2,1.0)
1/6*pi^2
sage: polylog(2,0.9)
polylog(2, 0.900000000000000)

The first command should not evaluate symbolically, since the input 1.0 is a floating-point.
The second command should evaluate numerically, like for example bessel_J(2,0.9).

Should I open a separate ticket?

Better late than never. This is now #18386.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants