Hi Phil.
On Sun, 05 Apr 2015 13:25:02 -0700, Phil Steitz wrote:
Thanks for the feedback and contributions!
I added a disclaimer making it clear that the challenges / lessons
learned stuff was just one contributor's view. The content is now
pretty much complete (unless someone has some awesome better example
I can swap in). I would appreciate a review of the completed
optimization slides and both the final challenges and lessons
learned slides. I will wait a few days to upload the slides so I
can clean them up some more and incorporate any feedback I get.
Anyone who wants to review but does not want to fuss with
tex/beamer, shoot me a note and I will cut a pdf based on master
when I get the request.
After this:
---CUT---
public PAIR optimize(OptimizationData... optData)
---CUT---
you could perhaps add one or two slides (to indicate the current
state of affairs and what remains to be implemented for the next
major release); something along the following lines:
---CUT---
Decision: Refactor of all classes in "o.a.c.m.optim"
* Phase out "OptimizationData"
* Use "fluent" API
* Separate optimization problem from optimization procedure
New ideas (brought forward by our most recent committer, Evan Ward)
experimented on least-squares optimizers:
* LevenbergMarquardtOptimizer
* GaussNewtonOptimizer
New classes/interfaces in "o.a.c.m.fitting.leastsquares":
* LeastSquaresProblem and LeastSquaresProblem.Evaluation
* LeastSquaresOptimizer and LeastSquaresOptimizer.Optimum
* LeastSquaresFactory
* LeastSquaresBuilder
* LevenbergMarquardtOptimizer
* GaussNewtonOptimizer
* AbstractEvaluation
* ...
Usage:
final LeastSquaresProblem problem = LeastSquaresFactory.create( /* ...
*/ );
final LeastSquaresOptimizer optim = new LevenbergMarquardtOptimizer( /*
... */ );
final Optimum result = optim.optimize(problem);
Yet to be done (before next major release?): Refactor all the other
optimizers.
---CUT---
Regards,
Gilles
Phil
On 4/1/15 10:27 AM, Phil Steitz wrote:
Starting with Thomas and Gilles' tex setup from FOSDEM 2013, I have
started creating slides for my talk in a couple of weeks at
Apachecon NA [1]. The basic idea is to combine an overview and
quick examples with some discussion of the many design and
implementation challenges that we have faced. I have put the tex
sources on github [2] and would appreciate any comments or just PRs
there. There is a make file (thanks, Thomas!) that creates a pdf
from the sources and also has a clean target to clean up cruft. You
need to have beamer installed for the build to work.
The content looks like too much for 50 mins, but I can fly through
most of it, so don't be discouraged to provide more examples. I can
also swap out some of the ones that are there. I have also
obviously not made it look pretty yet. Patches of all kinds welcome
:) My goal is to have the slides complete and uploaded to LF by the
end of this weekend.
Thanks in advance for review / feedback. Its probably best to
provide the feedback on github. If we get into any code
discussions, we can take things back here.
Phil
[1] http://sched.co/2P9O
[2] https://github.com/psteitz/apachecon-2015-commons-math.git
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
