[
https://issues.apache.org/jira/browse/MATH-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590632#comment-13590632
]
Christoph Höger commented on MATH-937:
--------------------------------------
Hey,
thanks for the response and the in-depth explanation. I think the changed
javadoc is fine, except I would mention @{link: NoBracketingException}
explicitly, as people will probably google first before reading the docs (sad
but true).
I tried to workaround the issue by adding an explicit check in the solver code.
Unfortunately it failed a test, but what speaks against testing the bracketing
or even catching the exception and just go on without detecting an event? I
would be willing to implement it if someone would be willing to review my
implementation ;).
> NoBracketingException after event was found
> -------------------------------------------
>
> Key: MATH-937
> URL: https://issues.apache.org/jira/browse/MATH-937
> Project: Commons Math
> Issue Type: Bug
> Affects Versions: 3.1.1
> Reporter: Christoph Höger
> Attachments: ApacheCommonsBouncingBall.java,
> ApacheCommonsBouncingBallTest.java
>
>
> The BracketingNthOrderBrentSolver used by the EmbeddedRungeKuttaIntegrator
> fails, if an event is detected twice with a NoBracketingException.
> The problem lies in line EventState.java line 262 (version 3.1.1). Here the
> event detection function f is applied to an arbitrary choosen value of time.
> If the event detector crosses zero before this time, the solver throws the
> mentioned exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
