- definition of RealVectorChangingVisitor,
- various methods to visit the entries of a RealVector (entries are possibly modified),
- default implementation in RealVector abstract class,
- unit tests in abstract RealVectorAbstractClass.
git-svn-id: https://svn.apache.org/repos/asf/commons/proper/math/trunk@1343342 13f79535-47bb-0310-9956-ffa450edef68
FastMath uses very large tables which are located at end of class for
better readability. this is not a standard layout, but is well suited
for this case, hence we explicitly suppress checkstyle warning for these
tables.
git-svn-id: https://svn.apache.org/repos/asf/commons/proper/math/trunk@1179948 13f79535-47bb-0310-9956-ffa450edef68
These catch occur in multi-start optimizers. The exceptions are caught
and stored, and if all restarts fail, then one of the stored
RuntimeException is rethrown. The purpose of multi-start is both to
allow some trials to fail and to avoid being trapped in a local
extremum. Catching RuntimeException is therefore mandatory here, and not
dangerous since we rethrow them as needed.
git-svn-id: https://svn.apache.org/repos/asf/commons/proper/math/trunk@1179947 13f79535-47bb-0310-9956-ffa450edef68
Using maven chekstyle plugin up to version 2.7, this property is not set
by default and should be set explicitely in the checkstyle configuration
file to prevent the report generation from failing.
git-svn-id: https://svn.apache.org/repos/asf/commons/proper/math/trunk@1178196 13f79535-47bb-0310-9956-ffa450edef68
- pom's need to use ${basedir} for configuration files as the multi-module profile is run from commons-parent, so if not specified it can't find those files
- the checkstyle configuration file needs to use ${checkstyle.header.file} for the headerFile property and <headerFile> element added to the plugin config in the pom.xml
- fix m1 checkstyle config to reflect the above where appropriate (specify header file property)
git-svn-id: https://svn.apache.org/repos/asf/commons/proper/math/branches/MATH_2_0@659441 13f79535-47bb-0310-9956-ffa450edef68
This problem has been discussed previously here:
http://markmail.org/message/pmbiyiqssjesq7tm
The solution implemented with this modification is to configure checkstyle
in such a way the errors can be filtered out using dedicated comments in the
source code:
// CHECKSTYLE: stop JavadocMethodCheck
// a bunch of functions known to trigger warnings
// that we explicitly REFUSE to fix
// CHECKSTYLE: resume JavadocMethodCheck
The checks are still performed normally in file parts not bracketed by
these comments. Hence the first few methods in o.a.c.m.stat.inference.TestUtils are
still checked for correct javadoc, and only for the last ones in the same files
are the checks relaxed.
git-svn-id: https://svn.apache.org/repos/asf/commons/proper/math/branches/MATH_2_0@658671 13f79535-47bb-0310-9956-ffa450edef68
Sebastien Brisard
Luc Maisonobe
Phil Steitz
Niall Pemberton
Henri Yandell
Brent Worden
Mark R. Diggory
Tim O'Brien