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

Bessel functions only support BigFloat arguments for integer orders #241

Open
Ceboc opened this issue Sep 24, 2020 · 1 comment
Open

Bessel functions only support BigFloat arguments for integer orders #241

Ceboc opened this issue Sep 24, 2020 · 1 comment

Comments

@Ceboc
Copy link

Ceboc commented Sep 24, 2020

Hi! I'm using the besselj and bessely ( )functions on a function to solve their zeros, as is shown in the source code of boostlibrary (https://github.com/Ceboc/BesselZeros). As i want to resolve roots with large values in certain x's interval, x_min < x_roots < x_max, where with .

The problem that i found is that is not consistent how bessely works.
imagen
imagen
imagen
imagen
imagen

That it's, if i use a i must give an bigfloat argument, but if i want to use a non entire value for , doesn't works.

I was using a wrap of the equivalent boost functions on CxxWrap, but i have problems with the parallelization, so i wrote my own functions to find the zeros of bessels.

@PaulXiCao
Copy link
Contributor

The problem that i found is that is not consistent how bessely works.

There is only a BigFloat implementation of bessely(nu, x) for integer values of nu. This explains why you get the MethodErrors. Thus, it is not inconsistent but rather just not implemented.

@stevengj stevengj changed the title Weird behaviour of bessel functions. Non regular results with BigFloat Bessel functions only support BigFloat arguments for integer orders Feb 2, 2021
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