[jira] [Created] (MATH-716) BracketingNthOrderBrentSolver exceeds maxIterationCount while updating always the same boundary

2011-12-01 Thread Pascal Parraud (Created) (JIRA) 
BracketingNthOrderBrentSolver exceeds maxIterationCount while updating always 
the same boundary
---

 Key: MATH-716
 URL: https://issues.apache.org/jira/browse/MATH-716
 Project: Commons Math
  Issue Type: Bug
Affects Versions: 3.0
Reporter: Pascal Parraud
Priority: Minor


In some cases, the aging feature in BracketingNthOrderBrentSolver fails.
It attempts to balance the bracketing points by targeting a non-zero value 
instead of the real root. However, the chosen target is too close too zero, and 
the inverse polynomial approximation is always on the same side, thus always 
updates the same bracket.
In the real used case for a large program, I had a bracket point xA = 12500.0, 
yA = 3.7e-16, agingA = 0, which is the (really good) estimate of the zero on 
one side of the root and xB = 12500.03, yB = -7.0e-5, agingB = 97. This shows 
that the bracketing interval is completely unbalanced, and we never succeed to 
rebalance it as we always updates (xA, yA) and never updates (xB, yB).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MATH-695) Incomplete reinitialization with some events handling

2011-10-25 Thread Pascal Parraud (Created) (JIRA) 
Incomplete reinitialization with some events handling
-

 Key: MATH-695
 URL: https://issues.apache.org/jira/browse/MATH-695
 Project: Commons Math
  Issue Type: Bug
Affects Versions: 3.0
Reporter: Pascal Parraud


I get a bug with event handling: I track 2 events that occur in the same step, 
when the first one is accepted, it resets the state but the reinitialization is 
not complete and the second one becomes unable to find its way.
I can't give my context, which is rather large, but I tried a patch that works 
for me, unfortunately it breaks the unit tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira