octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #62321] Wrong result for Airy funtion


From: anonymous
Subject: [Octave-bug-tracker] [bug #62321] Wrong result for Airy funtion
Date: Mon, 18 Apr 2022 13:20:16 -0400 (EDT)

Follow-up Comment #18, bug #62321 (project octave):

[comment #15] Thank you for all you did.

[comment #16] Hum that weird, can we contact the author of that change ?

I look around to see how other code do it. Both _SciPy_ and
_SpecialFunctions.jl_ call the scaling from the FORTRAN amos.
*
[https://github.com/scipy/scipy/blob/main/scipy/special/amos_wrappers.c#L180]
*
[https://github.com/JuliaMath/SpecialFunctions.jl/blob/6b686c0d6544a1e0ca59b627f22ea5559ba03e40/src/bessel.jl#L14]
Which does not make it right but increase my trust in it.

Additionally, from the ChangeLog you link, it says that the scaling for the
Bessel function was also done in octave part. But, if you look how it is done
now, for example for `besselj`, if you follow the argument `scaling/kode` in
*
[https://hg.savannah.gnu.org/hgweb/octave/file/30f7f409861a/libinterp/corefcn/besselj.cc#l109]
*
[https://hg.savannah.gnu.org/hgweb/octave/file/30f7f409861a/liboctave/numeric/lo-specfun.cc#l866]
the scaling version is call from the FORTRAN amos part. Maybe, if we find the
ChangeLog of the Bessel change, we might find some information.

[comment #17] Yes, that would make it more homogeneous.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62321>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]