[jira] [Updated] (MATH-768) org.apache.commons.math3.analysis.solvers.LaguerreSolver.ComplexSolver is private
[ https://issues.apache.org/jira/browse/MATH-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-768: Priority: Minor (was: Major) Fix Version/s: 3.1 Issue Type: Wish (was: Bug) As I've explained on the "user" ML, the removal was intentional. It would be helpful if you would open a discussion on the "dev" ML, that would lead to adopting a design for the complex solvers (such as what should be the API, how to name the interface and classes, in which those should belong, ...) > org.apache.commons.math3.analysis.solvers.LaguerreSolver.ComplexSolver is > private > - > > Key: MATH-768 > URL: https://issues.apache.org/jira/browse/MATH-768 > Project: Commons Math > Issue Type: Wish >Affects Versions: 3.0 >Reporter: Lance Finney >Priority: Minor > Fix For: 3.1 > > > We used LaguerreSolver.solveAll() in version 2.1, but we never upgraded to > 2.2. As such, we didn't notice that it was deprecated in that release. > Now that 3.0 is out, we want to upgrade, but that method has been completely > removed. > Interestingly, the logic is still there in the library in an inner class: > org.apache.commons.math3.analysis.solvers.LaguerreSolver.ComplexSolver. > Unfortunately for us, though, ComplexSolver is now private. So, for us as > users, we've lost access to a useful algorithm that is still in the library. > Please re-enable access to this useful algorithm that proves complex roots of > polynomial formulae. The simplest approach might be to make > LaguerreSolver.ComplexSolver public, but perhaps another approach would be > considered better design. -- 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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features (/) (r1292318)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}} (/) (cf. MATH-763)
* Remove class {{PivotingQRDecomposition}} (/) (cf. MATH-763)
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
** org.apache.commons.math3.distribution.TriangularDistribution (/) (r1292572)
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251 and
r1292270)
* Check the user guide (/) (no negative comments)
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features (/) (r1292318)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
** org.apache.commons.math3.distribution.TriangularDistribution (/) (r1292572)
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251 and
r1292270)
* Check the user guide
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
> (r1291896)
> ** List of new features (/) (r1292318)
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
> * Remove unit test class {{BatteryNISTTest}} (/) (cf. MATH-763)
> * Remove class {{PivotingQRDecomposition}} (/) (cf. MATH-763)
> * Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
> r1244996)
> * Findbugs:
> ** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
> ** org.apache.commons.math3.distribution.TriangularDistribution (/) (r1292572)
> ** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
> corrected before release)
> ** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251
> and r1292270)
> * Check the user guide (/) (no negative comments)
--
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] [Updated] (MATH-759) ListUnivariateImpl does not always access windowSize using synch.
[ https://issues.apache.org/jira/browse/MATH-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-759: Priority: Minor (was: Major) This is class is defined in the "test" part of the source tree. > ListUnivariateImpl does not always access windowSize using synch. > - > > Key: MATH-759 > URL: https://issues.apache.org/jira/browse/MATH-759 > Project: Commons Math > Issue Type: Bug >Reporter: Sebb >Priority: Minor > > ListUnivariateImpl has two synch. methods: > getWindowSize > setWindowSize > However, windowSize is frequently referenced elsewhere without synch. > It's not clear why the methods need synch., but if there is a need, then > windowSize should always be read using synch. > The code should use the super-class getter and setter. -- 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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features (/) (r1292318)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
** org.apache.commons.math3.distribution.TriangularDistribution (/) (r1292572)
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251 and
r1292270)
* Check the user guide
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features (/) (r1292318)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251 and
r1292270)
* Check the user guide
Concerning the "FindBugs" warnings: Only those for "BOBYQAOptimizer" remain.
But I think that it is fine to leave them since it is advertised as "alpha
code".
Concerning the "CheckStyle" warnings: Only those for "PivotingQRDecomposition"
remain. But it will be removed from the release branch.
Is there something more to be done on the "trunk" before creating a release
branch?
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
> (r1291896)
> ** List of new features (/) (r1292318)
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
> * Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
> r1244996)
> * Findbugs:
> ** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
> ** org.apache.commons.math3.distribution.TriangularDistribution (/) (r1292572)
> ** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
> corrected before release)
> ** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251
> and r1292270)
> * Check the user guide
--
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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features (/) (r1292318)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251 and
r1292270)
* Check the user guide
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251 and
r1292270)
* Check the user guide
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
> (r1291896)
> ** List of new features (/) (r1292318)
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
> * Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
> r1244996)
> * Findbugs:
> ** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
> ** org.apache.commons.math3.distribution.TriangularDistribution
> ** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
> corrected before release)
> ** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251
> and r1292270)
> * Check the user guide
--
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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251 and
r1292270)
* Check the user guide
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
* Check the user guide
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
> (r1291896)
> ** List of new features
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
> * Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
> r1244996)
> * Findbugs:
> ** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
> ** org.apache.commons.math3.distribution.TriangularDistribution
> ** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
> corrected before release)
> ** org.apache.commons.math3.stat.regression.RegressionResults (/) (r1292251
> and r1292270)
> * Check the user guide
--
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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
* Check the user guide
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
* Check the user guide
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
> (r1291896)
> ** List of new features
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
> * Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
> r1244996)
> * Findbugs:
> ** org.apache.commons.math3.analysis.solvers.BaseSecantSolver (/) (r1292245)
> ** org.apache.commons.math3.distribution.TriangularDistribution
> ** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
> corrected before release)
> ** org.apache.commons.math3.stat.regression.RegressionResults
> * Check the user guide
--
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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
(r1291896)
** List of new features
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
r1244996)
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
* Check the user guide
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
** List of new features
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
in {{r1244996}})
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
* Check the user guide
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621) (/) (r1291896)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740) (/)
> (r1291896)
> ** List of new features
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) (r1244855)
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) (r1244975)
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
> * Comment out "print" statement in {{SymmLQTest}} (/) (r1244992, removed in
> r1244996)
> * Findbugs:
> ** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
> ** org.apache.commons.math3.distribution.TriangularDistribution
> ** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
> corrected before release)
> ** org.apache.commons.math3.stat.regression.RegressionResults
> * Check the user guide
--
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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
** List of new features
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
in {{r1244996}})
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
* Check the user guide
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
in {{r1244996}})
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
* Check the user guide
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
> ** List of new features
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
> * Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
> in {{r1244996}})
> * Findbugs:
> ** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
> ** org.apache.commons.math3.distribution.TriangularDistribution
> ** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
> corrected before release)
> ** org.apache.commons.math3.stat.regression.RegressionResults
> * Check the user guide
--
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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
in {{r1244996}})
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
* Check the user guide
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
in {{r1244996}})
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
> * Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
> in {{r1244996}})
> * Findbugs:
> ** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
> ** org.apache.commons.math3.distribution.TriangularDistribution
> ** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
> corrected before release)
> ** org.apache.commons.math3.stat.regression.RegressionResults
> * Check the user guide
--
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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
in {{r1244996}})
* Findbugs:
** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
** org.apache.commons.math3.distribution.TriangularDistribution
** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
corrected before release)
** org.apache.commons.math3.stat.regression.RegressionResults
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
in {{r1244996}})
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
> * Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}}) (removed
> in {{r1244996}})
> * Findbugs:
> ** org.apache.commons.math3.analysis.solvers.BaseSecantSolver
> ** org.apache.commons.math3.distribution.TriangularDistribution
> ** org.apache.commons.math3.optimization.direct.BOBYQAOptimizer (cannot be
> corrected before release)
> ** org.apache.commons.math3.stat.regression.RegressionResults
--
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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
* Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}})
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
> * Comment out "print" statement in {{SymmLQTest}} (/) ({{r1244992}})
--
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] [Updated] (MATH-746) Things to do before releasing 3.0
[
https://issues.apache.org/jira/browse/MATH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-746:
Description:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
* Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
was:
This issue is meant to contain a list of tasks to be completed before the
release.
* Remarks to be added to the *release notes*:
** Experimental code: {{BOBYQAOptimizer}}
*** Many code paths untested
*** Looking for volunteers to improve the code readability, robustness and
performance
*** Looking for volunteers to extend the test suite
** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
* Create a "release branch"
* Disable CheckStyle scanning of {{BOBYQAOptimizer}}: {color:green}done in
{{r1244855}}{color} (/)
* Remove unit test class {{BatteryNISTTest}}
* Remove class {{PivotingQRDecomposition}}
> Things to do before releasing 3.0
> -
>
> Key: MATH-746
> URL: https://issues.apache.org/jira/browse/MATH-746
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Blocker
> Fix For: 3.0
>
>
> This issue is meant to contain a list of tasks to be completed before the
> release.
> * Remarks to be added to the *release notes*:
> ** Experimental code: {{BOBYQAOptimizer}} (cf. MATH-621)
> *** Many code paths untested
> *** Looking for volunteers to improve the code readability, robustness and
> performance
> *** Looking for volunteers to extend the test suite
> ** {{FastMath}} is not always faster than {{Math}} (issue MATH-740)
> * Create a "release branch"
> * Disable CheckStyle scanning of {{BOBYQAOptimizer}} (/) ({{r1244855}})
> * Comment out "print" statements in {{BOBYQAOptimizerTest}} (/) ({{r1244975}})
> * Remove unit test class {{BatteryNISTTest}}
> * Remove class {{PivotingQRDecomposition}}
--
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] [Updated] (MATH-621) BOBYQA is missing in optimization
[
https://issues.apache.org/jira/browse/MATH-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-621:
Fix Version/s: (was: 3.0)
3.1
Remaining Estimate: (was: 8h)
Original Estimate: (was: 8h)
No further work will be achieved before release 3.0: Postponing.
> BOBYQA is missing in optimization
> -
>
> Key: MATH-621
> URL: https://issues.apache.org/jira/browse/MATH-621
> Project: Commons Math
> Issue Type: New Feature
>Affects Versions: 3.0
>Reporter: Dr. Dietmar Wolz
> Fix For: 3.1
>
> Attachments: BOBYQA.math.patch, BOBYQA.v02.math.patch,
> BOBYQAOptimizer.java.patch, BOBYQAOptimizer0.4.zip, bobyqa.zip,
> bobyqa_convert.pl, bobyqaoptimizer0.4.zip, bobyqav0.3.zip
>
>
> During experiments with space flight trajectory optimizations I recently
> observed, that the direct optimization algorithm BOBYQA
> http://plato.asu.edu/ftp/other_software/bobyqa.zip
> from Mike Powell is significantly better than the simple Powell algorithm
> already in commons.math. It uses significantly lower function calls and is
> more reliable for high dimensional problems. You can replace CMA-ES in many
> more application cases by BOBYQA than by the simple Powell optimizer.
> I would like to contribute a Java port of the algorithm.
> I maintained the structure of the original FORTRAN code, so the
> code is fast but not very nice.
> License status: Michael Powell has sent the agreement via snail mail
> - it hasn't arrived yet.
> Progress: The attached patch relative to the trunk contains both the
> optimizer and the related unit tests - which are all green now.
> Performance:
> Performance difference (number of function evaluations)
> PowellOptimizer / BOBYQA for different test functions (taken from
> the unit test of BOBYQA, dimension=13 for most of the
> tests.
> Rosen = 9350 / 1283
> MinusElli = 118 / 59
> Elli = 223 / 58
> ElliRotated = 8626 / 1379
> Cigar = 353 / 60
> TwoAxes = 223 / 66
> CigTab = 362 / 60
> Sphere = 223 / 58
> Tablet = 223 / 58
> DiffPow = 421 / 928
> SsDiffPow = 614 / 219
> Ackley = 757 / 97
> Rastrigin = 340 / 64
> The number for DiffPow should be discussed with Michael Powell,
> I will send him the details.
> h3. Open Problems
> * Checkstyle violations[1] because of the original Fortran source:
> ** Original method comments were copied: Javadoc standard documentation
> should be added, but the original documentation should stay (as a reference
> to what the original intended behaviour was) untouched until we are sure that
> the code behaves as expected.
> ** Multiple variable declarations per line.
> ** "goto" conversions:
> *** "goto"s not convertible in loops were translated into a finite automaton
> (switch statement)
> *** "no default in switch"
> *** "fall through from previous case in switch"
> * Unexplored code paths: "throw" statements have been introduced in the code.
> Each should be triggered by at least one unit test. They are currently
> commented out in provision of the 3.0 release (cf. MATH-712) but should be
> re-enabled afterwards.
> [1] Once the violations are solved, the following lines should be removed
> from the source file:
> * {{// CHECKSTYLE: stop all}}
> * {{//CHECKSTYLE: resume all}}
--
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] [Updated] (MATH-621) BOBYQA is missing in optimization
[
https://issues.apache.org/jira/browse/MATH-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-621:
Description:
During experiments with space flight trajectory optimizations I recently
observed, that the direct optimization algorithm BOBYQA
http://plato.asu.edu/ftp/other_software/bobyqa.zip
from Mike Powell is significantly better than the simple Powell algorithm
already in commons.math. It uses significantly lower function calls and is
more reliable for high dimensional problems. You can replace CMA-ES in many
more application cases by BOBYQA than by the simple Powell optimizer.
I would like to contribute a Java port of the algorithm.
I maintained the structure of the original FORTRAN code, so the
code is fast but not very nice.
License status: Michael Powell has sent the agreement via snail mail
- it hasn't arrived yet.
Progress: The attached patch relative to the trunk contains both the
optimizer and the related unit tests - which are all green now.
Performance:
Performance difference (number of function evaluations)
PowellOptimizer / BOBYQA for different test functions (taken from
the unit test of BOBYQA, dimension=13 for most of the
tests.
Rosen = 9350 / 1283
MinusElli = 118 / 59
Elli = 223 / 58
ElliRotated = 8626 / 1379
Cigar = 353 / 60
TwoAxes = 223 / 66
CigTab = 362 / 60
Sphere = 223 / 58
Tablet = 223 / 58
DiffPow = 421 / 928
SsDiffPow = 614 / 219
Ackley = 757 / 97
Rastrigin = 340 / 64
The number for DiffPow should be discussed with Michael Powell,
I will send him the details.
h3. Open Problems
* Checkstyle violations[1] because of the original Fortran source:
** Original method comments were copied: Javadoc standard documentation should
be added, but the original documentation should stay (as a reference to what
the original intended behaviour was) untouched until we are sure that the code
behaves as expected.
** Multiple variable declarations per line.
** "goto" conversions:
*** "goto"s not convertible in loops were translated into a finite automaton
(switch statement)
*** "no default in switch"
*** "fall through from previous case in switch"
* Unexplored code paths: "throw" statements have been introduced in the code.
Each should be triggered by at least one unit test. They are currently
commented out in provision of the 3.0 release (cf. MATH-712) but should be
re-enabled afterwards.
[1] Once the violations are solved, the following lines should be removed from
the source file:
* {{// CHECKSTYLE: stop all}}
* {{//CHECKSTYLE: resume all}}
was:
During experiments with space flight trajectory optimizations I recently
observed, that the direct optimization algorithm BOBYQA
http://plato.asu.edu/ftp/other_software/bobyqa.zip
from Mike Powell is significantly better than the simple Powell algorithm
already in commons.math. It uses significantly lower function calls and is
more reliable for high dimensional problems. You can replace CMA-ES in many
more application cases by BOBYQA than by the simple Powell optimizer.
I would like to contribute a Java port of the algorithm.
I maintained the structure of the original FORTRAN code, so the
code is fast but not very nice.
License status: Michael Powell has sent the agreement via snail mail
- it hasn't arrived yet.
Progress: The attached patch relative to the trunk contains both the
optimizer and the related unit tests - which are all green now.
Performance:
Performance difference (number of function evaluations)
PowellOptimizer / BOBYQA for different test functions (taken from
the unit test of BOBYQA, dimension=13 for most of the
tests.
Rosen = 9350 / 1283
MinusElli = 118 / 59
Elli = 223 / 58
ElliRotated = 8626 / 1379
Cigar = 353 / 60
TwoAxes = 223 / 66
CigTab = 362 / 60
Sphere = 223 / 58
Tablet = 223 / 58
DiffPow = 421 / 928
SsDiffPow = 614 / 219
Ackley = 757 / 97
Rastrigin = 340 / 64
The number for DiffPow should be dicussed with Michael Powell,
I will send him the details.
Open Problems:
Some checkstyle violations because of the original Fortran source:
- Original method comments were copied - doesn't follow javadoc standard
- Multiple variable declarations in one line as in the original source
- Problems related to "goto" conversions:
"gotos" not convertible in loops were transated into a finite automata
(switch statement)
"no default in switch"
"fall through from previos case in switch"
which usually are bad style make no sense here.
{color: red} Once these checkstyle violations are solved, the following lines
should be removed from the source file{color}
* {{// CHECKSTYLE: stop all}}
* {{//CHECKSTYLE: resume all}}
> BOBYQA is missing in optimization
> -
>
> Key: MATH-621
> URL: https://issues.apache.org/jira/browse/MATH-621
> Project: Commons Math
> Issue Type: New Feature
>Affects Versions: 3.0
>Repor
[jira] [Updated] (MATH-672) EmpiricalDistribution(Impl) should implement the Distribution interface
[ https://issues.apache.org/jira/browse/MATH-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-672: Fix Version/s: (was: 3.0) 3.1 It's not a bug and there is no patch: Postponed. > EmpiricalDistribution(Impl) should implement the Distribution interface > --- > > Key: MATH-672 > URL: https://issues.apache.org/jira/browse/MATH-672 > Project: Commons Math > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Phil Steitz > Fix For: 3.1 > > > To compute cumulative probability at a point x > if no data have been loaded, throw IllegalStateException > if x is below the global min, return 0 > if x is above the global max, return 1 > otherwise find the bin that x belongs to, sum the probabilities of the bins > below x's bin and use the configured kernel to compute how much of the > containing bin's mass should be added the total -- 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] [Updated] (MATH-449) Storeless covariance
[
https://issues.apache.org/jira/browse/MATH-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-449:
Assignee: Thomas Neidhart
> Storeless covariance
>
>
> Key: MATH-449
> URL: https://issues.apache.org/jira/browse/MATH-449
> Project: Commons Math
> Issue Type: Improvement
>Reporter: Patrick Meyer
>Assignee: Thomas Neidhart
> Fix For: 3.0
>
> Attachments: MATH-449.patch, MATH-449.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Currently there is no storeless version for computing the covariance.
> However, Pebay (2008) describes algorithms for on-line covariance
> computations, [http://infoserve.sandia.gov/sand_doc/2008/086212.pdf]. I have
> provided a simple class for implementing this algorithm. It would be nice to
> have this integrated into org.apache.commons.math.stat.correlation.Covariance.
> {code}
> //This code is granted for inclusion in the Apache Commons under the terms of
> the ASL.
> public class StorelessCovariance{
> private double deltaX = 0.0;
> private double deltaY = 0.0;
> private double meanX = 0.0;
> private double meanY = 0.0;
> private double N=0;
> private Double covarianceNumerator=0.0;
> private boolean unbiased=true;
> public Covariance(boolean unbiased){
> this.unbiased = unbiased;
> }
> public void increment(Double x, Double y){
> if(x!=null & y!=null){
> N++;
> deltaX = x - meanX;
> deltaY = y - meanY;
> meanX += deltaX/N;
> meanY += deltaY/N;
> covarianceNumerator += ((N-1.0)/N)*deltaX*deltaY;
> }
>
> }
> public Double getResult(){
> if(unbiased){
> return covarianceNumerator/(N-1.0);
> }else{
> return covarianceNumerator/N;
> }
> }
> }
> {code}
--
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] [Updated] (MATH-449) Storeless covariance
[
https://issues.apache.org/jira/browse/MATH-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-449:
Fix Version/s: (was: 3.1)
3.0
Waiting for an imminent patch by Patrick Meyer.
> Storeless covariance
>
>
> Key: MATH-449
> URL: https://issues.apache.org/jira/browse/MATH-449
> Project: Commons Math
> Issue Type: Improvement
>Reporter: Patrick Meyer
> Fix For: 3.0
>
> Attachments: MATH-449.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Currently there is no storeless version for computing the covariance.
> However, Pebay (2008) describes algorithms for on-line covariance
> computations, [http://infoserve.sandia.gov/sand_doc/2008/086212.pdf]. I have
> provided a simple class for implementing this algorithm. It would be nice to
> have this integrated into org.apache.commons.math.stat.correlation.Covariance.
> {code}
> //This code is granted for inclusion in the Apache Commons under the terms of
> the ASL.
> public class StorelessCovariance{
> private double deltaX = 0.0;
> private double deltaY = 0.0;
> private double meanX = 0.0;
> private double meanY = 0.0;
> private double N=0;
> private Double covarianceNumerator=0.0;
> private boolean unbiased=true;
> public Covariance(boolean unbiased){
> this.unbiased = unbiased;
> }
> public void increment(Double x, Double y){
> if(x!=null & y!=null){
> N++;
> deltaX = x - meanX;
> deltaY = y - meanY;
> meanX += deltaX/N;
> meanY += deltaY/N;
> covarianceNumerator += ((N-1.0)/N)*deltaX*deltaY;
> }
>
> }
> public Double getResult(){
> if(unbiased){
> return covarianceNumerator/(N-1.0);
> }else{
> return covarianceNumerator/N;
> }
> }
> }
> {code}
--
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] [Updated] (MATH-698) Bounds in "BOBYQAOptimizer" and "CMAESOptimizer"
[ https://issues.apache.org/jira/browse/MATH-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-698: Assignee: (was: Gilles) > Bounds in "BOBYQAOptimizer" and "CMAESOptimizer" > > > Key: MATH-698 > URL: https://issues.apache.org/jira/browse/MATH-698 > Project: Commons Math > Issue Type: Improvement >Reporter: Gilles >Priority: Minor > Labels: api-change > Fix For: 3.0 > > Attachments: CMAESOptimizer.java.NEW, CMAESOptimizerTest.java.NEW > > > The bounds should be passed as arguments to the "optimize" method, instead of > through the constructor. > This is now possible, following the resolution of MATH-697. -- 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] [Updated] (MATH-643) Rename RealVector.map* to RealVector.ebe* (mapAdd(...) to ebeAdd(...) and mapAddToSelf(...) to ebeAddToSelf(...) for instance
[ https://issues.apache.org/jira/browse/MATH-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-643: Fix Version/s: (was: 3.0) 4.0 > Rename RealVector.map* to RealVector.ebe* (mapAdd(...) to ebeAdd(...) and > mapAddToSelf(...) to ebeAddToSelf(...) for instance > - > > Key: MATH-643 > URL: https://issues.apache.org/jira/browse/MATH-643 > Project: Commons Math > Issue Type: Improvement >Reporter: Arne Plöse >Priority: Minor > Fix For: 4.0 > > > I think the map* methods have historical names. Today I would prefer ebe as > prefix like ebeMultiply(...). > This would describe the methods better from a users view. > If this is a valid issue, I could provide a patch. -- 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] [Updated] (MATH-473) Frequency: new option: NON-sorted
[ https://issues.apache.org/jira/browse/MATH-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-473: Fix Version/s: (was: 3.0) 3.1 Postponed due to the absence of an updated patch. > Frequency: new option: NON-sorted > - > > Key: MATH-473 > URL: https://issues.apache.org/jira/browse/MATH-473 > Project: Commons Math > Issue Type: Improvement >Affects Versions: 1.0, 1.1, 1.2, 2.0, 2.1 >Reporter: Dan Checkoway > Fix For: 3.1 > > Attachments: MATH-473.patch > > > I have a request for enhancement on org.apache.commons.math.stat.Frequency. > I would like to be able to specify that the the backing map NOT be sorted. > Right now it uses TreeMap. I would like to have the option of specifying > that sorting is not important, and would in fact hinder performance, and a > plain old HashMap should be used instead. > i.e. constructor such as: > public Frequency(boolean sorted); > If sorted is true, use a TreeMap. If sorted is false, use a HashMap. Is > this feasible? I'd be happy to contribute a patch if that would help. -- 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] [Updated] (MATH-474) Frequency: new method: merge(Frequency)
[ https://issues.apache.org/jira/browse/MATH-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-474: Fix Version/s: (was: 3.0) 3.1 Postponed due to the absence of an updated patch. > Frequency: new method: merge(Frequency) > --- > > Key: MATH-474 > URL: https://issues.apache.org/jira/browse/MATH-474 > Project: Commons Math > Issue Type: Improvement >Reporter: Dan Checkoway > Fix For: 3.1 > > Attachments: MATH-474.patch > > > I'd like to propose an enhancement to org.apache.commons.math.stat.Frequency. > I need to "merge" multiple Frequency objects, and it would be great if > Frequency had inherent support for this, such as: > public void merge(Frequency other); > public void merge(Collection others); > I'd be happy to submit a patch if that would help... -- 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] [Updated] (MATH-608) Remove methods from RealMatrix Interface
[ https://issues.apache.org/jira/browse/MATH-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-608: Fix Version/s: (was: 3.0) 4.0 Postponed. > Remove methods from RealMatrix Interface > > > Key: MATH-608 > URL: https://issues.apache.org/jira/browse/MATH-608 > Project: Commons Math > Issue Type: Improvement >Affects Versions: 1.0, 1.1, 1.2, 2.0, 2.1, 2.2 > Environment: Java >Reporter: greg sterijevski >Priority: Minor > Labels: Matrices > Fix For: 4.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > The RealMatrix interface describes several methods which take a RealMatrix > and yield a RealMatrix return. They are: > RealMatrix multiply(RealMatrix m); > RealMatrix preMultiply(RealMatrix m); > RealMatrix power(final int p); > RealMatrix add(RealMatrix m) > RealMatrix subtract(RealMatrix m) > There is nothing inherently wrong in making all subclasses of RealMatrix > implement these methods. However, as the number of subclasses of RealMatrix > increases, the complexity of these methods will also increase. I think these > methods should be part of a separate class of 'operators' which handle matrix > multiplication, addition, subtraction and exponentiation. > Say for example, I implement SymmetricRealMatrix. I would like to store the > data of a real symmetric in compressed form, so that I only consume (nrow + > 1)*nrow /2 space in memory. When it comes time to implement multiply (for > example), I must test to see if the RealMatrix given in the argument is also > of Type SymmetricRealMatrix, since that will affect the algorithm I use to do > the multiplication. I could access each element of the argument matrix via > its getter, but efficiency will suffer. One can think of cases where we might > have a DiagonalRealMatrix times a DiagonRealMatrix. One would not want to > store the resultant diagonal in a general matrix storage. Keeping track of > all of the permutations of Symmetrics, Diagonals,..., and their resultants > inside of the body of a function makes for very brittle code. Furthermore, > anytime a new type of matrix is defined all matrix multiplication routines > would have to be updated. > There are special types of operations which result in particular matrix > patterns. A matrix times its transpose is itself a symmetric. A general > matrix sandwiched between another general matrix and its transpose is a > symmetric. Cholesky decompositions form upper and lower triangular matrices. > These are common enough occurrences in statistical techniques that it makes > sense to put them in their own class (perhaps as static methods). It would > keep the contract of the RealMatrix classes very simple. The ReaMatrix would > be nothing more than: > 1. Marker (is the matrix General, Symmetric, Banded, Diagonal, > UpperTriangular..) > 2. Opaque data store (except for the operator classes, no one would need to > know how the data is actually stored). > 3. Indexing scheme. > The reason I bring this up, is that I am attempting to write a > SymmetricRealMatrix class to support variance-covariance matrices. I noticed > that there are relatively few subclasses of RealMatrix. While it would be > easy to hack it up for the handful of implementations that exist, that would > probably create more problems as the number of types of matrices increases. > Thank you, > -Greg -- 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] [Updated] (MATH-656) "isSparse()" method vs marker interfaces
[ https://issues.apache.org/jira/browse/MATH-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-656: Fix Version/s: (was: 3.0) 4.0 Postponing to next major version, as it is unlikely that a new discussion on these API issues will occur before the release of 3.0. > "isSparse()" method vs marker interfaces > > > Key: MATH-656 > URL: https://issues.apache.org/jira/browse/MATH-656 > Project: Commons Math > Issue Type: Improvement >Reporter: Gilles >Priority: Trivial > Fix For: 4.0 > > > From discussions on the "dev" ML, it seems that it would be advantageous to > introduce a method "isSparse()" in "RealVector" and in "RealMatrix". > For "RealVector", it will make sense to use it to select between "iterator()" > and "sparseIterator()" in methods implemented in that class. > We could then remove the "SparseRealVector" and "SparseRealMatrix" interfaces. -- 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] [Updated] (MATH-734) Code cleanup: "ISAACRandom"
[
https://issues.apache.org/jira/browse/MATH-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-734:
Fix Version/s: (was: 3.0)
3.1
Postponing. Some of the same (non-blocking) issues apply to other RNG
implementations; this can be discussed later.
> Code cleanup: "ISAACRandom"
> ---
>
> Key: MATH-734
> URL: https://issues.apache.org/jira/browse/MATH-734
> Project: Commons Math
> Issue Type: Improvement
>Reporter: Gilles
>Assignee: Gilles
>Priority: Minor
> Fix For: 3.1
>
>
> In revision 1232899, I started to clean up the code (mainly, removing the
> one-letter instance variables, that can easily be confused with local ones
> within methods, making the code harder to understand and maintain).
> Other points I'd want to handle:
> * Should "Serializable" be implemented for such classes? I think not;
> especially if it supposed to be used for "secure" applications.
> * (Related to the above) I'd remove the "transient" keyword.
> * The contents of method "allocArrays" should be moved to within the
> constructor.
> * It is not recommended to call non-final "public" methods ("setSeed") from
> within the constructor, because an overriding code could access a not fully
> initialized object.
> * All initializations should take place within a single, most general,
> constructor and the other constructors should call that one (using the
> {{this(...)}} statement).
> * This code (line 130)
> {code}
> if (seed == null) {
> setSeed(System.currentTimeMillis() + System.identityHashCode(this));
> return;
> }
> {code}
> should probably be removed: it is safer to consider passing a null reference
> as a user error.
> * I'd remove the constructor taking a {{long}} argument. It is not obvious
> how the code will use the argument. I'd rather offer that alternative, in the
> class documentation, as an example of how to initialize the "array of
> integers" argument.
--
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] [Updated] (MATH-622) Default number format does not show enough digits
[
https://issues.apache.org/jira/browse/MATH-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-622:
Fix Version/s: (was: 3.0)
3.1
This is annoying but not a blocking issue; postponing.
> Default number format does not show enough digits
> -
>
> Key: MATH-622
> URL: https://issues.apache.org/jira/browse/MATH-622
> Project: Commons Math
> Issue Type: Improvement
>Reporter: Gilles
>Priority: Minor
> Fix For: 3.1
>
>
> In {{CompositeFormat}}, the {{getDefaultNumberFormat(final Locale locale)}}
> method contains
> {code}
> nf.setMaximumFractionDigits(2);
> {code}
> This default is too small.
> Also, it would be better to output the number in scientific notation.
--
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] [Updated] (MATH-575) Exceptions in genetics package or not consistent with the rest of [math]
[ https://issues.apache.org/jira/browse/MATH-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-575: Assignee: Thomas Neidhart Thomas, Could please check whether this issue is resolved? And if it is, mark it so? Thanks. > Exceptions in genetics package or not consistent with the rest of [math] > > > Key: MATH-575 > URL: https://issues.apache.org/jira/browse/MATH-575 > Project: Commons Math > Issue Type: Bug >Affects Versions: 2.0, 2.1, 2.2 >Reporter: Phil Steitz >Assignee: Thomas Neidhart >Priority: Minor > Fix For: 3.0 > > > InvalidRepresentationException is checked and non-localized. This exception > should be placed in the [math] hierarchy. The AbstractListChromosome > constructor also throws a non-localised IAE, which should be replaced by an > appropriate [math] exception. -- 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] [Updated] (MATH-726) Ridders derivative
[
https://issues.apache.org/jira/browse/MATH-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-726:
Fix Version/s: (was: 3.0)
3.1
Postponed.
> Ridders derivative
> --
>
> Key: MATH-726
> URL: https://issues.apache.org/jira/browse/MATH-726
> Project: Commons Math
> Issue Type: New Feature
>Reporter: Gilles
>Assignee: Gilles
>Priority: Minor
> Labels: features
> Fix For: 3.1
>
> Attachments: RiddersFirstDerivative.java
>
>
> Implementation of the numerical first derivative, as described in:
> {noformat}
> Accurate computation of F'(x) and F'(x) F''(x)
> C. J. F. Ridders
> Adv. Eng. Software, 1982, Vol 4, No. 2
> {noformat}
--
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] [Updated] (MATH-734) Code cleanup: "ISAACRandom"
[
https://issues.apache.org/jira/browse/MATH-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-734:
Description:
In revision 1232899, I started to clean up the code (mainly, removing the
one-letter instance variables, that can easily be confused with local ones
within methods, making the code harder to understand and maintain).
Other points I'd want to handle:
* Should "Serializable" be implemented for such classes? I think not;
especially if it supposed to be used for "secure" applications.
* (Related to the above) I'd remove the "transient" keyword.
* The contents of method "allocArrays" should be moved to within the
constructor.
* It is not recommended to call non-final "public" methods ("setSeed") from
within the constructor, because an overriding code could access a not fully
initialized object.
* All initializations should take place within a single, most general,
constructor and the other constructors should call that one (using the
{{this(...)}} statement).
* This code (line 130)
{code}
if (seed == null) {
setSeed(System.currentTimeMillis() + System.identityHashCode(this));
return;
}
{code}
should probably be removed: it is safer to consider passing a null reference as
a user error.
* I'd remove the constructor taking a {{long}} argument. It is not obvious how
the code will use the argument. I'd rather offer that alternative, in the class
documentation, as an example of how to initialize the "array of integers"
argument.
was:
In revision 1232899, I started to clean up the code (mainly, removing the
one-letter instance variables, that can easily be confused with local ones
within methods, making the code harder to understand and maintain).
Other points I'd want to handle:
* Should "Serializable" be implemented for such classes? I think not;
especially if it supposed to be used for "secure" applications.
* (Related to the above) I'd remove the "transient" keyword.
* The contents of method "allocArrays" should be moved to within the
constructor.
* It is not recommended to call non-final "public" methods ("setSeed") from
within the constructor, because an overriding code could access a not fully
uninitialized object.
* All initialization should take place within a single, most general,
constructor and the other constructors should call that one (using the
{{this(...)}} statement).
* This code (line 130)
{code}
if (seed == null) {
setSeed(System.currentTimeMillis() + System.identityHashCode(this));
return;
}
{code}
should probably be removed: it is safer to consider passing a null reference as
a user error.
* I'd remove the constructor taking a {{long}} argument. It is not obvious how
the code will use the argument. I'd rather offer that alternative, in the class
documentation, as an example of how to initialize the "array of integers"
argument.
> Code cleanup: "ISAACRandom"
> ---
>
> Key: MATH-734
> URL: https://issues.apache.org/jira/browse/MATH-734
> Project: Commons Math
> Issue Type: Improvement
>Reporter: Gilles
>Assignee: Gilles
>Priority: Minor
> Fix For: 3.0
>
>
> In revision 1232899, I started to clean up the code (mainly, removing the
> one-letter instance variables, that can easily be confused with local ones
> within methods, making the code harder to understand and maintain).
> Other points I'd want to handle:
> * Should "Serializable" be implemented for such classes? I think not;
> especially if it supposed to be used for "secure" applications.
> * (Related to the above) I'd remove the "transient" keyword.
> * The contents of method "allocArrays" should be moved to within the
> constructor.
> * It is not recommended to call non-final "public" methods ("setSeed") from
> within the constructor, because an overriding code could access a not fully
> initialized object.
> * All initializations should take place within a single, most general,
> constructor and the other constructors should call that one (using the
> {{this(...)}} statement).
> * This code (line 130)
> {code}
> if (seed == null) {
> setSeed(System.currentTimeMillis() + System.identityHashCode(this));
> return;
> }
> {code}
> should probably be removed: it is safer to consider passing a null reference
> as a user error.
> * I'd remove the constructor taking a {{long}} argument. It is not obvious
> how the code will use the argument. I'd rather offer that alternative, in the
> class documentation, as an example of how to initialize the "array of
> integers" argument.
--
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] [Updated] (MATH-722) [math] Complex Tanh for "big" numbers
[
https://issues.apache.org/jira/browse/MATH-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-722:
Fix Version/s: 3.0
> [math] Complex Tanh for "big" numbers
> -
>
> Key: MATH-722
> URL: https://issues.apache.org/jira/browse/MATH-722
> Project: Commons Math
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: I'm working with Eclipse 3.6.2 on Windows XP, but the
> bug is Enviroment independent
>Reporter: Juan Barandiaran
>Assignee: Sébastien Brisard
>Priority: Minor
> Labels: patch
> Fix For: 3.0
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> Hi,
> In Complex.java the tanh is computed with the following formula:
> tanh(a + bi) = sinh(2a)/(cosh(2a)+cos(2b)) + [sin(2b)/(cosh(2a)+cos(2b))]i
> The problem that I'm finding is that as soon as "a" is a "big" number,
> both sinh(2a) and cosh(2a) are infinity and then the method tanh returns in
> the real part NaN (infinity/infinity) when it should return 1.0.
> Wouldn't it be appropiate to add something as in the FastMath library??:
> if (real>20.0){
> return createComplex(1.0, 0.0);
> }
> if (real<-20.0){
> return createComplex(-1.0, 0.0);
> }
> Best regards,
> JBB
--
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] [Updated] (MATH-725) use initialized static final arrays, instead of initializing it in constructors
[
https://issues.apache.org/jira/browse/MATH-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-725:
Fix Version/s: 3.0
> use initialized static final arrays, instead of initializing it in
> constructors
> ---
>
> Key: MATH-725
> URL: https://issues.apache.org/jira/browse/MATH-725
> Project: Commons Math
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Eldar Agalarov
>Priority: Minor
> Fix For: 3.0
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The Well PRNG's implementations have arrays iRm1, iRm2, iRm3, i1, i2, i3. All
> these arrays are unmodifiable, so we can replace this arrays initialization
> block
> final int w = 32;
> final int r = (k + w - 1) / w;
> this.v = new int[r];
> this.index = 0;
>
> // precompute indirection index tables. These tables are used for
> optimizing access
> // they allow saving computations like "(j + r - 2) % r" with costly
> modulo operations
> iRm1 = new int[r];
> iRm2 = new int[r];
> i1 = new int[r];
> i2 = new int[r];
> i3 = new int[r];
> for (int j = 0; j < r; ++j) {
> iRm1[j] = (j + r - 1) % r;
> iRm2[j] = (j + r - 2) % r;
> i1[j] = (j + m1) % r;
> i2[j] = (j + m2) % r;
> i3[j] = (j + m3) % r;
> }
> with inline initialized static final arrays.
> This is much better and faster implementation, freed from unnecessary costly
> calculations (such as %).
> Another solution: leave as is, but make all these arrays static.
--
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] [Updated] (MATH-460) Levy Distribution
[ https://issues.apache.org/jira/browse/MATH-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-460: Fix Version/s: (was: 3.0) 3.1 > Levy Distribution > - > > Key: MATH-460 > URL: https://issues.apache.org/jira/browse/MATH-460 > Project: Commons Math > Issue Type: New Feature >Reporter: Pavel Ryzhov >Priority: Minor > Fix For: 3.1 > > Attachments: levy_math_460.patch > > > Pretty straightforward implementation of Levy Distribution (not Levy > alpha-stable) according to http://en.wikipedia.org/wiki/Lévy_distribution. -- 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] [Updated] (MATH-610) [patch] objects that use compareTo should have equals as well
[ https://issues.apache.org/jira/browse/MATH-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-610: Affects Version/s: (was: 3.0) Fix Version/s: (was: 3.0) 3.1 > [patch] objects that use compareTo should have equals as well > - > > Key: MATH-610 > URL: https://issues.apache.org/jira/browse/MATH-610 > Project: Commons Math > Issue Type: Improvement >Reporter: Dave Brosius >Priority: Trivial > Fix For: 3.1 > > Attachments: equals.diff > > > NaturalRanking implements compareTo. Code that implements compareTo should > also implement equals, and those that implement equals should implement > hashCode. This patch does this. -- 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] [Updated] (MATH-602) Inverse condition number
[ https://issues.apache.org/jira/browse/MATH-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-602: Fix Version/s: (was: 3.0) 3.1 > Inverse condition number > > > Key: MATH-602 > URL: https://issues.apache.org/jira/browse/MATH-602 > Project: Commons Math > Issue Type: Improvement >Affects Versions: 2.2 > Environment: All >Reporter: greg sterijevski >Priority: Minor > Labels: Condition, Inverse, Number > Fix For: 3.1 > > Attachments: svdinvcond, tstsvd > > Original Estimate: 1h > Remaining Estimate: 1h > > In SingularValueDecompositionImpl, the condition number is given as the ratio > of the largest singular value to the smallest singular value. While this is > the correct calculation, because of concerns over rank deficiency, > researchers have traditionally used the inverse of the condition number as a > more stable indicator of rank deficiency. -- 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] [Updated] (MATH-607) Current Multiple Regression Object does calculations with all data incore. There are non incore techniques which would be useful with large datasets.
[ https://issues.apache.org/jira/browse/MATH-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-607: Fix Version/s: (was: 3.0) 3.1 > Current Multiple Regression Object does calculations with all data incore. > There are non incore techniques which would be useful with large datasets. > - > > Key: MATH-607 > URL: https://issues.apache.org/jira/browse/MATH-607 > Project: Commons Math > Issue Type: New Feature >Affects Versions: 3.0 > Environment: Java >Reporter: greg sterijevski > Labels: Gentleman's, QR, Regression, Updating, decomposition, > lemma > Fix For: 3.1 > > Attachments: RegressResults2, millerreg, millerreg_take2, > millerregtest, regres_change1, updating_reg_cut2, updating_reg_ifaces > > Original Estimate: 840h > Remaining Estimate: 840h > > The current multiple regression class does a QR decomposition on the complete > data set. This necessitates the loading incore of the complete dataset. For > large datasets, or large datasets and a requirement to do datamining or > stepwise regression this is not practical. There are techniques which form > the normal equations on the fly, as well as ones which form the QR > decomposition on an update basis. I am proposing, first, the specification of > an "UpdatingLinearRegression" interface which defines basic functionality all > such techniques must fulfill. > Related to this 'updating' regression, the results of running a regression on > some subset of the data should be encapsulated in an immutable object. This > is to ensure that subsequent additions of observations do not corrupt or > render inconsistent parameter estimates. I am calling this interface > "RegressionResults". > Once the community has reached a consensus on the interface, work on the > concrete implementation of these techniques will take place. > Thanks, > -Greg -- 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] [Updated] (MATH-729) Add an implementation for Holt-Winters triple exponential smoothing
[ https://issues.apache.org/jira/browse/MATH-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-729: Affects Version/s: (was: 3.1) Fix Version/s: 3.1 > Add an implementation for Holt-Winters triple exponential smoothing > --- > > Key: MATH-729 > URL: https://issues.apache.org/jira/browse/MATH-729 > Project: Commons Math > Issue Type: New Feature >Reporter: Nishant Chandra > Labels: exponential, smoothing, triple > Fix For: 3.1 > > > Add an implementation for Holt-Winters triple exponential smoothing -- 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] [Updated] (MATH-734) Code cleanup: "ISAACRandom"
[
https://issues.apache.org/jira/browse/MATH-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-734:
Description:
In revision 1232899, I started to clean up the code (mainly, removing the
one-letter instance variables, that can easily be confused with local ones
within methods, making the code harder to understand and maintain).
Other points I'd want to handle:
* Should "Serializable" be implemented for such classes? I think not;
especially if it supposed to be used for "secure" applications.
* (Related to the above) I'd remove the "transient" keyword.
* The contents of method "allocArrays" should be moved to within the
constructor.
* It is not recommended to call non-final "public" methods ("setSeed") from
within the constructor, because an overriding code could access a not fully
uninitialized object.
* All initialization should take place within a single, most general,
constructor and the other constructors should call that one (using the
{{this(...)}} statement).
* This code (line 130)
{code}
if (seed == null) {
setSeed(System.currentTimeMillis() + System.identityHashCode(this));
return;
}
{code}
should probably be removed: it is safer to consider passing a null reference as
a user error.
* I'd remove the constructor taking a {{long}} argument. It is not obvious how
the code will use the argument. I'd rather offer that alternative, in the class
documentation, as an example of how to initialize the "array of integers"
argument.
was:
In revision 1232899, I started to clean up the code (mainly, removing the
one-letter instance variables, that can easily be confused with local ones
within methods, making the code harder to understand and maintain).
Other points I'd want to handle:
* Should "Serializable" be implemented for such classes? I think not;
especially if it supposed to be used for "secure" applications.
* (Related to the above) I'd remove the "transient" keyword.
* The contents of method "allocArrays" should be moved to within the
constructor.
* It is not recommended to call non-final "public" methods ("setSeed") from
within the constructor, because an overriding code could access a not fully
uninitialized object.
* All initialization should take place within a single, most general,
constructor and the other constructors should call that one (using the
{{this(...)}} statement).
* This code (line 130)
{code}
if (seed == null) {
setSeed(System.currentTimeMillis() + System.identityHashCode(this));
return;
}
{code}
should probably be removed: it is safer to consider passing a null reference as
a user error.
> Code cleanup: "ISAACRandom"
> ---
>
> Key: MATH-734
> URL: https://issues.apache.org/jira/browse/MATH-734
> Project: Commons Math
> Issue Type: Improvement
>Reporter: Gilles
>Assignee: Gilles
>Priority: Minor
> Fix For: 3.0
>
>
> In revision 1232899, I started to clean up the code (mainly, removing the
> one-letter instance variables, that can easily be confused with local ones
> within methods, making the code harder to understand and maintain).
> Other points I'd want to handle:
> * Should "Serializable" be implemented for such classes? I think not;
> especially if it supposed to be used for "secure" applications.
> * (Related to the above) I'd remove the "transient" keyword.
> * The contents of method "allocArrays" should be moved to within the
> constructor.
> * It is not recommended to call non-final "public" methods ("setSeed") from
> within the constructor, because an overriding code could access a not fully
> uninitialized object.
> * All initialization should take place within a single, most general,
> constructor and the other constructors should call that one (using the
> {{this(...)}} statement).
> * This code (line 130)
> {code}
> if (seed == null) {
> setSeed(System.currentTimeMillis() + System.identityHashCode(this));
> return;
> }
> {code}
> should probably be removed: it is safer to consider passing a null reference
> as a user error.
> * I'd remove the constructor taking a {{long}} argument. It is not obvious
> how the code will use the argument. I'd rather offer that alternative, in the
> class documentation, as an example of how to initialize the "array of
> integers" argument.
--
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] [Updated] (MATH-734) Code cleanup: "ISAACRandom"
[
https://issues.apache.org/jira/browse/MATH-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-734:
Description:
In revision 1232899, I started to clean up the code (mainly, removing the
one-letter instance variables, that can easily be confused with local ones
within methods, making the code harder to understand and maintain).
Other points I'd want to handle:
* Should "Serializable" be implemented for such classes? I think not;
especially if it supposed to be used for "secure" applications.
* (Related to the above) I'd remove the "transient" keyword.
* The contents of method "allocArrays" should be moved to within the
constructor.
* It is not recommended to call non-final "public" methods ("setSeed") from
within the constructor, because an overriding code could access a not fully
uninitialized object.
* All initialization should take place within a single, most general,
constructor and the other constructors should call that one (using the
{{this(...)}} statement).
* This code (line 130)
{code}
if (seed == null) {
setSeed(System.currentTimeMillis() + System.identityHashCode(this));
return;
}
{code}
should probably be removed: it is safer to consider passing a null reference as
a user error.
was:
In revision 1232899, I started to clean up the code (mainly, removing the
one-letter instance variables, that can easily be confused with local ones
within methods, making the code harder to understand and maintain).
Other points I'd want to handle:
* Should "Serializable" be implemented for such classes? I think not;
especially if it supposed to be used for "secure" applications.
* (Related to the above) I'd remove the "transient" keyword.
* The contents of method "allocArrays" should be moved to within the
constructor.
* It is not recommended to call non-final "public" methods ("setSeed") from
within the constructor, because an overriding code could access a not fully
uninitialized object.
* All initialization should take place within a single, most general,
constructor and the other constructors should call that one (using the
{{this(...)}} statement).
> Code cleanup: "ISAACRandom"
> ---
>
> Key: MATH-734
> URL: https://issues.apache.org/jira/browse/MATH-734
> Project: Commons Math
> Issue Type: Improvement
>Reporter: Gilles
>Assignee: Gilles
>Priority: Minor
> Fix For: 3.0
>
>
> In revision 1232899, I started to clean up the code (mainly, removing the
> one-letter instance variables, that can easily be confused with local ones
> within methods, making the code harder to understand and maintain).
> Other points I'd want to handle:
> * Should "Serializable" be implemented for such classes? I think not;
> especially if it supposed to be used for "secure" applications.
> * (Related to the above) I'd remove the "transient" keyword.
> * The contents of method "allocArrays" should be moved to within the
> constructor.
> * It is not recommended to call non-final "public" methods ("setSeed") from
> within the constructor, because an overriding code could access a not fully
> uninitialized object.
> * All initialization should take place within a single, most general,
> constructor and the other constructors should call that one (using the
> {{this(...)}} statement).
> * This code (line 130)
> {code}
> if (seed == null) {
> setSeed(System.currentTimeMillis() + System.identityHashCode(this));
> return;
> }
> {code}
> should probably be removed: it is safer to consider passing a null reference
> as a user error.
--
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] [Updated] (MATH-726) Ridders derivative
[
https://issues.apache.org/jira/browse/MATH-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-726:
Attachment: RiddersFirstDerivative.java
Attached proposed implementation. OK to add?
> Ridders derivative
> --
>
> Key: MATH-726
> URL: https://issues.apache.org/jira/browse/MATH-726
> Project: Commons Math
> Issue Type: New Feature
>Reporter: Gilles
>Assignee: Gilles
>Priority: Minor
> Labels: features
> Fix For: 3.0
>
> Attachments: RiddersFirstDerivative.java
>
>
> Implementation of the numerical first derivative, as described in:
> {noformat}
> Accurate computation of F'(x) and F'(x) F''(x)
> C. J. F. Ridders
> Adv. Eng. Software, 1982, Vol 4, No. 2
> {noformat}
--
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] [Updated] (MATH-698) Bounds in "BOBYQAOptimizer" and "CMAESOptimizer"
[ https://issues.apache.org/jira/browse/MATH-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-698: Attachment: CMAESOptimizerTest.java.NEW CMAESOptimizer.java.NEW Attached modified version of "CMAESOptimizer" and "CMAESOptimizerTest" to take into account the new way to handle bounds (base class "BaseAbstractSimpleBoundsScalarOptimizer" contains the "boiler-plate" code). Unfortunately, the changes generate many test failures... > Bounds in "BOBYQAOptimizer" and "CMAESOptimizer" > > > Key: MATH-698 > URL: https://issues.apache.org/jira/browse/MATH-698 > Project: Commons Math > Issue Type: Improvement >Reporter: Gilles >Assignee: Gilles >Priority: Minor > Labels: api-change > Fix For: 3.0 > > Attachments: CMAESOptimizer.java.NEW, CMAESOptimizerTest.java.NEW > > > The bounds should be passed as arguments to the "optimize" method, instead of > through the constructor. > This is now possible, following the resolution of MATH-697. -- 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] [Updated] (MATH-689) Breaking up "MathUtils"
[
https://issues.apache.org/jira/browse/MATH-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles updated MATH-689:
Comment: was deleted
(was: Bonjour Sébastien.
[Je réponds en direct parce le site "issues.apache.org" semble inaccessible
pour le moment.]
Choisis celui qui te fait le plus plaisir ;-}. ["Precision" a été fait.]
Bonne journée,
Gilles
)
> Breaking up "MathUtils"
> ---
>
> Key: MATH-689
> URL: https://issues.apache.org/jira/browse/MATH-689
> Project: Commons Math
> Issue Type: Task
>Reporter: Gilles
>Priority: Trivial
> Labels: api-change
> Fix For: 3.0
>
>
> Issue related to this
> [proposal|http://www.mail-archive.com/dev@commons.apache.org/msg25617.html].
> There seemed to be a global agreement on the following break-up:
> * Arithmetics (for "addAndCheck", "factorial", "gcd", ...)
> * Precision (for "equals", "compare", ...)
> * Binomial (for "binomialCoefficient")
> * MathArrays (for "linearCombination", "distance", "safeNorm",
> "sortInPlace", "copyOf", ...)
> I think that "ordinary" mathematical functions ("pow", "cosh", ...) should go
> into "FastMath" (if not already available there).
> Those who are willing to work on this issue, please coordinate here.
--
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] [Updated] (MATH-688) "FastMath" contains fractions of constants
[ https://issues.apache.org/jira/browse/MATH-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-688: Description: Fractions such as 1.0 / 3.0, 1.0 / 5.0, ... could be replaced with static final constants. In "asinh", for example, the change can sometimes result in more than halving the computation time (when the argument is in the range of values where the constants are used). In absolute times, the gain is not huge, amounting (on my machine) to something like 370 ms for 10 million computations. And, of course, the downside will be that these constants will be computed at the loading of "FastMath", leading to an additional penalty of about 16 divisions at initialization... :) was: Fractions such as 1.0 / 3.0, 1.0 / 5.0, ... could be replaced with static final constants. In "asinh", for example, the change can sometimes result in more than halving the computation time (when the argument is in the range of values where the constants are used). In absolute times, the gain is not huge, amounting to something like 5 ms for 10 million computations. And, of course, the downside will be that these values will be computed at the loading of "FastMath", leading to an additional penalty of about 16 divisions at initialization... :) > "FastMath" contains fractions of constants > -- > > Key: MATH-688 > URL: https://issues.apache.org/jira/browse/MATH-688 > Project: Commons Math > Issue Type: Improvement >Reporter: Gilles >Assignee: Gilles >Priority: Trivial > Fix For: 3.0 > > > Fractions such as 1.0 / 3.0, 1.0 / 5.0, ... could be replaced with static > final constants. > In "asinh", for example, the change can sometimes result in more than halving > the computation time (when the argument is in the range of values where the > constants are used). > In absolute times, the gain is not huge, amounting (on my machine) to > something like 370 ms for 10 million computations. > And, of course, the downside will be that these constants will be computed at > the loading of "FastMath", leading to an additional penalty of about 16 > divisions at initialization... :) -- 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] [Updated] (MATH-676) More efficient multiplication of small matrices
[ https://issues.apache.org/jira/browse/MATH-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles updated MATH-676: Attachment: cm_issue.dat Benchmark (10 million multiplications) results: total time (in ms) vs matrix size. > More efficient multiplication of small matrices > --- > > Key: MATH-676 > URL: https://issues.apache.org/jira/browse/MATH-676 > Project: Commons Math > Issue Type: Improvement >Reporter: Gilles >Assignee: Gilles >Priority: Minor > Fix For: 3.0 > > Attachments: cm_issue.dat > > > A benchmark shows that the "multiply" method in "Array2DRowRealMatrix" could > be faster. -- 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
