[
https://issues.apache.org/jira/browse/MATH-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812500#comment-13812500
]
Thomas Neidhart commented on MATH-1057:
---------------------------------------
Ok I understand now.
The difference was happening before, when we used Math.xxx calls, which
returned different results for different jdk versions.
Now, when using FastMath, the result is of course consistent with all jdks, as
FastMath is a pure java implementation. The result for this test has change
slightly and a epsilon of 1e-7 should be used to compensate the for change imho.
@Gilles: in case you read here, as you have done most of the work on this
optimizer, do you think that the switch from Math to FastMath is ok, or was
there a specific reason why Math was used in this case?
> BOBYQAOptimizerTest has two failing tests
> -----------------------------------------
>
> Key: MATH-1057
> URL: https://issues.apache.org/jira/browse/MATH-1057
> Project: Commons Math
> Issue Type: Bug
> Affects Versions: 3.2
> Environment: Mac OS X 10.9 and also Linux 3.4 kernel; Java 7; Maven
> 3.1.1
> Reporter: Sean Owen
> Priority: Minor
> Attachments: MATH-1057.patch
>
>
> I see two test failures, in both the copies of BOBYQAOptimizerTest:
> {code}
> Failed tests:
> BOBYQAOptimizerTest.testAckley:209->doTest:282->doTest:338 expected:<0.0>
> but was:<1.047765607609108E-8>
> BOBYQAOptimizerTest.testAckley:208->doTest:281->doTest:336 expected:<0.0>
> but was:<1.047765607609108E-8>
> Tests in error:
> BOBYQAOptimizerTest.testDiffPow:187->doTest:282->doTest:322 »
> TooManyEvaluations
> BOBYQAOptimizerTest.testDiffPow:186->doTest:281->doTest:326 »
> TooManyEvaluations
> {code}
> (This predated the patches I've worked on so I don't think it's me!)
> I tried on Mac OS X and Linux and see the same, so don't think it is an
> environment issue. I'll see if a little digging can uncover the issue from a
> recent commit.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
