Hi Gilles,
We also do not have a clear separation between algorithms that take a
bracket (e.g. BrentSolver) and those that don't (e.g. NewtonSolver).
If the solve methods called by the user contains more parameters than
needed by the algorithm implemented in the instance, they will be
Le 07/07/2011 09:35, Dennis Hendriks a écrit :
Hi Gilles,
We also do not have a clear separation between algorithms that take a
bracket (e.g. BrentSolver) and those that don't (e.g. NewtonSolver).
If the solve methods called by the user contains more parameters than
needed by the
Hi,
in Blas, the method DAXPY can lead to very compact code. As far as I know, it
has no equivalent in RealVector. There are a few method called ToSelf,
which modify the calling vector, instead of returning a new one, but these are
restricted to scalars operating on vectors.
In other words,
On 7 July 2011 00:57, Jörg Schaible joerg.schai...@gmx.de wrote:
Proposed changes done. Please review, especially also Javadoc as I'm a non-
native speaker.
Done. I think you could remove the add/set methods taking a Pair. The
other add/set methods taking two arguments is sufficient, and I
Hi Stephen,
Stephen Colebourne wrote:
On 7 July 2011 00:57, Jörg Schaible joerg.schai...@gmx.de wrote:
Proposed changes done. Please review, especially also Javadoc as I'm a
non- native speaker.
Done. I think you could remove the add/set methods taking a Pair. The
other add/set methods
On 7 July 2011 11:48, Jörg Schaible joerg.schai...@scalaris.com wrote:
One last opinion about the output? Originally we had e.g.:
[Handler = PersonConverter]
[Current Element = Person]
[Role = COO]
[Handler[1] = CompanyConverter]
[Current Element[1] = Company]
The current output does
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
Hi.
We also do not have a clear separation between algorithms that take a
bracket (e.g. BrentSolver) and those that don't (e.g. NewtonSolver).
If the solve methods called by the user contains more parameters than
needed by the algorithm implemented in the instance, they will be
ignored.
Le 07/07/2011 10:31, Sebastien Brisard a écrit :
Hi,
Hi Sébastien,
in Blas, the method DAXPY can lead to very compact code. As far as I know, it
has no equivalent in RealVector. There are a few method called ToSelf,
which modify the calling vector, instead of returning a new one, but
Le 07/07/2011 14:41, Gilles Sadowski a écrit :
Hi.
We also do not have a clear separation between algorithms that take a
bracket (e.g. BrentSolver) and those that don't (e.g. NewtonSolver).
If the solve methods called by the user contains more parameters than
needed by the algorithm
Hello.
in Blas, the method DAXPY can lead to very compact code. As far as I know, it
has no equivalent in RealVector. There are a few method called ToSelf,
which modify the calling vector, instead of returning a new one, but these are
restricted to scalars operating on vectors.
In other
On Thu, Jul 07, 2011 at 03:40:19PM +0200, Luc Maisonobe wrote:
Le 07/07/2011 14:41, Gilles Sadowski a écrit :
Hi.
We also do not have a clear separation between algorithms that take a
bracket (e.g. BrentSolver) and those that don't (e.g. NewtonSolver).
If the solve methods called by the
Hi All:
I do like using NullArgumentException, but I find writing this over and over
tedious:
if (arg == null) {
thrown new NullArgumentException(argName);
}
something(arg);
How about this instead:
NullArgumentException.check(arg, argName);
something(arg);
or:
On Thu, Jul 7, 2011 at 11:56 AM, Gary Gregory garydgreg...@gmail.com wrote:
Hi All:
I do like using NullArgumentException, but I find writing this over and over
tedious:
if (arg == null) {
thrown new NullArgumentException(argName);
}
something(arg);
How about this instead:
I use an Assert class (similar to commons Validate):
Assert.notNull(argName, arg);
http://ci.apache.org/projects/ofbiz/site/javadocs/org/ofbiz/base/util/Assert.html
The difference is it throws IllegalArgumentException.
-Adrian
On 7/7/2011 5:56 PM, Gary Gregory wrote:
Hi All:
I do like
On Thu, Jul 7, 2011 at 1:11 PM, Matt Benson gudnabr...@gmail.com wrote:
On Thu, Jul 7, 2011 at 11:56 AM, Gary Gregory garydgreg...@gmail.com
wrote:
Hi All:
I do like using NullArgumentException, but I find writing this over and
over
tedious:
if (arg == null) {
thrown new
Hey,
On Thu, Jul 7, 2011 at 9:56 AM, Gary Gregory garydgreg...@gmail.com wrote:
Hi All:
I do like using NullArgumentException, but I find writing this over and over
tedious:
if (arg == null) {
thrown new NullArgumentException(argName);
}
something(arg);
How about this instead:
The Colt package used a functional style to implement what you suggest.
This approach has been inherited by Mahout.
The basic idea is that there is an assign method that takes other arguments
and a function for combining the arguments. The function allows great
amounts of flexibility and
That sounds interesting. I was thinking of something like mapping a bivariate
function to two vectors, but was afraid of performance issues. Your feedback
on this is encouraging!
As for the approach used in Mahout, is it similar to the Procedures in GNU
Trove? It takes a little bit of time to
It sounds similar to the trove approach, but I couldn't say with certainty.
On Thu, Jul 7, 2011 at 11:10 AM, Sebastien Brisard
sebastien.bris...@polytechnique.org wrote:
That sounds interesting. I was thinking of something like mapping a
bivariate
function to two vectors, but was afraid of
On 03/07/2011 22:43, Phil Steitz wrote:
On 7/3/11 12:32 PM, Mark Thomas wrote:
On 26/06/2011 01:05, Phil Steitz wrote:
On 6/25/11 4:28 PM, Mark Thomas wrote:
On 17/06/2011 09:02, Mark Thomas wrote:
On 17/06/2011 00:32, Gary Gregory wrote:
I think 2.0 is the opportunity to do this right.
Stephen Colebourne wrote:
On 7 July 2011 11:48, Jörg Schaible joerg.schai...@scalaris.com wrote:
One last opinion about the output? Originally we had e.g.:
[Handler = PersonConverter]
[Current Element = Person]
[Role = COO]
[Handler[1] = CompanyConverter]
[Current Element[1] = Company]
Hi Hen,
Henri Yandell wrote:
I think we're ready for another release candidate.
Does anyone know of any remaining items? JIRA is clean, and I don't
see anything in the email threads that implies more work needs to be
done.
We have two failing unit tests with Java 7. At least one is due to
Hi,
It is probably a bit late, but it is only these days I've checked
javadoc of the commons-lang ver. 3 on the web, and found contexted
exceptions. I found the context info useful already some time ago, so
I've implemented my own classes, which you can find at
Hi
GUI code is out of scope IMO.
Gary
On Jul 7, 2011, at 17:17, Marko Klopcic markok3...@gmail.com wrote:
Hi,
It is probably a bit late, but it is only these days I've checked
javadoc of the commons-lang ver. 3 on the web, and found contexted
exceptions. I found the context info useful
Ted,
Mahout seems to be fairly large (!). What classes should I look at more
specifically?
Thanks!
Sebastien
The Colt package used a functional style to implement what you suggest.
This approach has been inherited by Mahout.
The basic idea is that there is an assign method that takes other
AbstractMatrix
On Thu, Jul 7, 2011 at 8:06 PM, Sebastien Brisard sebastien.bris...@m4x.org
wrote:
Ted,
Mahout seems to be fairly large (!). What classes should I look at more
specifically?
Thanks!
Sebastien
The Colt package used a functional style to implement what you suggest.
This
27 matches
Mail list logo
