Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 25 Apr 2017 22:32:04 +0000 (UTC)
From: "Eric Barnhill (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.13065067.1492604649000.49405.1493159524244@Atlassian.JIRA>
In-Reply-To: <JIRA.13065067.1492604649000@Atlassian.JIRA>
References: <JIRA.13065067.1492604649000@Atlassian.JIRA> <JIRA.13065067.1492604649062@jira-lw-us.apache.org>
Subject: [jira] [Commented] (NUMBERS-22) Method reciprocal() in Complex for
 complex numbers with parts very close to 0.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 25 Apr 2017 22:32:09 -0000


    [ https://issues.apache.org/jira/browse/NUMBERS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983762#comment-15983762 ] 

Eric Barnhill commented on NUMBERS-22:
--------------------------------------

I am indeed in the middle of coding a large test class that will enforce all the ISO C standards on the complex number trigonometric operations. 

Thank you for bringing this to my attention and I will make sure it is enforced in testing as well. This can be assigned to me.

> Method reciprocal() in Complex for complex numbers with parts very close to 0.0
> -------------------------------------------------------------------------------
>
>                 Key: NUMBERS-22
>                 URL: https://issues.apache.org/jira/browse/NUMBERS-22
>             Project: Commons Numbers
>          Issue Type: Improvement
>            Reporter: Gunel Jahangirova
>            Priority: Minor
>
> I have been redirected here from the issue repository of Apache Commons Math, as the Complex class will likely be deprecated in favour of its equivalent in "Commons Numbers".
> In class Complex method reciprocal() returns INF only if the real and imaginary parts are exactly equal to 0.0. In the cases when real and imaginary parts are double numbers very close to 0.0, it does not hold. For example, if we run this code
> {code}
> Complex complex0 = new Complex((-2.44242319E-315));
> Complex complex1 = complex0.reciprocal();
> {code}
> the value of complex1.getReal() will be -Infinity and the value of complex1.getImaginary() will be NaN, instead of complex1 being equal to INF.
> The suggested solutions after the discussion are either checking the equality to ZERO with some tolerance or to detect if one of the real or imaginary parts is going to be infinite or NaN and then return the proper result. 


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)