There should be nothing in the algorithms that depend on the parameters being Float64:

<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clip

Remove hard coded Float64 about fastgaussquadrature.jl HOT 5 OPEN

juliaapproximation commented on September 25, 2024 3

Remove hard coded Float64

from fastgaussquadrature.jl.

Comments (5)

ajt60gaibb commented on September 25, 2024 3

I agree. It would also be exciting to add BigFloat versions of all the algorithms too.

from fastgaussquadrature.jl.

ajt60gaibb commented on September 25, 2024

I would need to think very carefully about this. I agree that there is in principle nothing in the algorithm that requires Float64, but there are some algorithmic parameters that do...

from fastgaussquadrature.jl.

dlfivefifty commented on September 25, 2024

We could have the routines allow for general choices of the parameters.  In the case of Float64 it uses the current defaults, otherwise, users have to specify their own.

On 28 Mar 2016, at 3:00 AM, Alex Townsend [email protected] wrote:

I would need to think very carefully about this. I agree that there is in principle nothing in the algorithm that requires Float64, but there are some algorithmic parameters that do...

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #22 (comment)

from fastgaussquadrature.jl.

sflammia commented on September 25, 2024

I am working on a problem that would benefit from a BigFloat implementation of both gausslegendre and gausslaguerre. I hope this comment will bump this issue up the priority queue!

from fastgaussquadrature.jl.

dlfivefifty commented on September 25, 2024

I have proposed it as an undergrad summer project so hopefully it can come together.

from fastgaussquadrature.jl.

Recommend Projects