You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Gilles (JIRA)" <ji...@apache.org> on 2016/05/29 23:59:12 UTC

[jira] [Resolved] (MATH-926) Refactor the "o.a.c.m.optim" package

     [ https://issues.apache.org/jira/browse/MATH-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilles resolved MATH-926.
-------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 4.0)
                   3.3

Some of the changes were performed a long time ago (v3.3) with the creation of package {{o.a.c.m.fitting.leastsquares}}.

Further work (MATH-1013) is unlikely to happen.

> Refactor the "o.a.c.m.optim" package
> ------------------------------------
>
>                 Key: MATH-926
>                 URL: https://issues.apache.org/jira/browse/MATH-926
>             Project: Commons Math
>          Issue Type: Improvement
>    Affects Versions: 3.1
>            Reporter: Gilles
>              Labels: api-change
>             Fix For: 3.3
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)