You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Alex Herbert (Jira)" <ji...@apache.org> on 2022/10/14 11:32:00 UTC

[jira] [Updated] (NUMBERS-4) Complex.ZERO.pow(2.0) is NaN

     [ https://issues.apache.org/jira/browse/NUMBERS-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Herbert updated NUMBERS-4:
-------------------------------
    Component/s: complex

> Complex.ZERO.pow(2.0) is NaN
> ----------------------------
>
>                 Key: NUMBERS-4
>                 URL: https://issues.apache.org/jira/browse/NUMBERS-4
>             Project: Commons Numbers
>          Issue Type: Bug
>          Components: complex
>         Environment: Linux, Java1.7/Java1.8
>            Reporter: Raymond DeCampo
>            Priority: Minor
>             Fix For: 1.0-beta1
>
>
> Description copied from MATH-1397 as reported by Mario Wenzel:
> {quote}
> ```
> package complextest;
> import org.apache.commons.math3.complex.Complex;
> public class T \{
> public static void main(String[] args)
> \{ System.out.println(Complex.ZERO.pow(2.0)); }
> }
> ```
> This is the code and the readout is `(NaN, NaN)`. This surely isn't right. For one, it should actually be zero (https://www.wolframalpha.com/input/?i=(0%2B0i)%5E2) and second of all, the documentation doesn't state that anything could go wrong from a Complex number that has no NaNs and Infs.
> The other definition states that it doesn't work when the base is Zero, but it surely should. This strange corner case destroys any naive implementation of stuff wrt the mandelbrot set.
> It would be nice to not have to implement this exception myself.
> {quote}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)