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:19:00 UTC

[jira] [Updated] (NUMBERS-16) Set tolerances in ComplexTest to zero?

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

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

> Set tolerances in ComplexTest to zero?
> --------------------------------------
>
>                 Key: NUMBERS-16
>                 URL: https://issues.apache.org/jira/browse/NUMBERS-16
>             Project: Commons Numbers
>          Issue Type: Improvement
>          Components: complex
>            Reporter: Eric Barnhill
>            Priority: Minor
>             Fix For: 1.0-beta1
>
>
> Considering the following JUnit test:
>     public void testConstructor() {
>         Complex z = new Complex(3.0, 4.0);
>         Assert.assertEquals(3.0, z.getReal(), 1.0e-5);
>         Assert.assertEquals(4.0, z.getImaginary(), 1.0e-5);
>     }
> That tolerance seems pretty high to me -- I sure would not want to work with a method that was not stabler than that, nor can I see a reason that the numbers would be exactly the same to the last place.
> Any reason not to set these tolerances to zero?



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