X/ARM64 will be another difficult one).
>
>
>
> This advice is moot if you have a precise bound for the error.
>
>
>
> Kevin
>
>
>
>
>
> From: Ralf Gommers <mailto:ralf.gomm...@gmail.com>
> Sent: Wednesday, February 24, 2021 12:25 PM
e another difficult one).
>
>
>
> This advice is moot if you have a precise bound for the error.
>
>
>
> Kevin
>
>
>
>
>
> *From: *Ralf Gommers
> *Sent: *Wednesday, February 24, 2021 12:25 PM
> *To: *Discussion of Numerical Python
> *Subject: *Re:
OSX/ARM64 will be another difficult one). This advice is moot if you have a precise bound for the error. Kevin From: Ralf GommersSent: Wednesday, February 24, 2021 12:25 PMTo: Discussion of Numerical PythonSubject: Re: [Numpy-discussion] Guidelines for floating point comparison On Wed, Feb 24
On Wed, Feb 24, 2021 at 11:29 AM Bernard Knaepen wrote:
> Hi all,
>
> We are developing a code that heavily relies on NumPy. Some of our
> regression tests rely on floating point number comparisons and we are a bit
> lost in determining how to choose atol and rtol (we are trying to do all
> opera
Hi all,
We are developing a code that heavily relies on NumPy. Some of our regression
tests rely on floating point number comparisons and we are a bit lost in
determining how to choose atol and rtol (we are trying to do all operations in
double precision). We would like to set atol and rtol as
