[MATH-926] Refactor the "o.a.c.m.optim" package

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1
• Fix Version/s: 3.3
• Labels: api-change
• Assignee: Unassigned
• Reporter: Gilles Sadowski
• Created: 01/Jan/13 01:56
• Updated: 29/May/16 23:59
• Resolved: 29/May/16 23:59

Description

The "optim" package should only refer to the strict definition of an optimization problem: minimizing a cost function.

The non-linear least-squares "optimizers" should be considered as "fitting" algorithms and moved to the "o.a.c.m.fitting" package.

Issue Links

• supercedes: MATH-874 New API for optimizers

Sub-Tasks

• Move the contents of "o.a.c.m.nonlinear.vector.jacobian" to the "o.a.c.m.fitting" package: Closed
• Implement a "fluent" API: Resolved