Hi.
Yes, indeed, great idea!
A good way to do this is probably to build a wrapper (instead of a
class the inherit ConvergenceChecker) ConvergenceTracker implemented
very much like your proposal, except that can be wrapped around any
ConvergenceChecker with a constructor like
ct = new DebugConvergenceTracker(new SimpleValueChecker(...) )
You'd still need the "DebugConvergenceTracker" to implement the
"ConvergenceChecker" interface.
So that later on (after optim has been called), it is possible to get
the trajectory, with something like
List<PointValuePair> path = ct.getTrajectory() ;
The same wrapper principle may be applied to count the number of time
the objective function "value" is invoqued during the optimisation
process.
You can already get it with "getEvaluations()". :-)
Regards,
Gilles
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
