Two options spring to mind; the first is to dig through the Apache
Incubator and look for a project that piques your interest. You can
quite quickly have a strong impact on a project there. Your interest
can be fairly vague; it might be that the language is one you want to
learn, it might be that
On Wed, Nov 24, 2010 at 3:51 AM, sebb seb...@gmail.com wrote:
On 24 November 2010 11:02, Stefan Bodewig bode...@apache.org wrote:
On 2010-11-24, sebb wrote:
On 24 November 2010 09:46, Stefan Bodewig bode...@apache.org wrote:
On 2010-11-22, Jörg Schaible wrote:
Stefan Bodewig wrote:
The
There is another topic worth mentioning:
Multi-start using MultiStartMultivariateRealOptimizer.
In http://www.lri.fr/~hansen/cec2005.html an algo
called G-CMA-ES performed very well:
A CMA evolution strategy restarted with increasing population size.
Is there a general need beside CMA-ES to
Le 26/11/2010 11:58, Dr. Dietmar Wolz a écrit :
There is another topic worth mentioning:
Multi-start using MultiStartMultivariateRealOptimizer.
In http://www.lri.fr/~hansen/cec2005.html an algo
called G-CMA-ES performed very well:
A CMA evolution strategy restarted with increasing
Should we simply allow user to register an instance of some optimizer
reconfigurator interface in the constructor ? Something like:
public MultiStartDifferentiableMultivariateVectorialOptimizer(
DifferentiableMultivariateVectorialOptimizer optimizer,
int starts,
Le 26/11/2010 13:34, Dr. Dietmar Wolz a écrit :
Should we simply allow user to register an instance of some optimizer
reconfigurator interface in the constructor ? Something like:
public MultiStartDifferentiableMultivariateVectorialOptimizer(
Hello.
Should we simply allow user to register an instance of some optimizer
reconfigurator interface in the constructor ? Something like:
public MultiStartDifferentiableMultivariateVectorialOptimizer(
DifferentiableMultivariateVectorialOptimizer optimizer,
int starts,
[...]
Question is how reconfigure() is configured?
It is entirely up to the user who implements it, and it depends on the
algorithm he chose. If the algorithm does have some setXxx() setter, he
could do:
public DifferentiableMultivariateVectorialOptimizer
However, can we slow down on the new features? (Am I saying this? ;-)) [We
previously agreed that the main algorithm code should be put in place before
any other bells and whistles.]
We didn't discuss when a possible enhancement of
MultiStartMultivariateRealOptimizer
will be implemented, just
Le 26/11/2010 14:14, Gilles Sadowski a écrit :
Hello.
Should we simply allow user to register an instance of some optimizer
reconfigurator interface in the constructor ? Something like:
public MultiStartDifferentiableMultivariateVectorialOptimizer(
Hi,
Le 26/11/2010 14:23, Gilles Sadowski a écrit :
[...]
Question is how reconfigure() is configured?
It is entirely up to the user who implements it, and it depends on the
algorithm he chose. If the algorithm does have some setXxx() setter, he
could do:
public
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-jelly-tags-quartz has an issue affecting its community
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
The deprecations below are in the wrong source tree. They need to be
applied to the 2.x branch and unless it is just as a signal to those
building (dangerously) from trunk, I do not see the point of deprecating in
the 3.0 branch.
I am -0 on applying these to the 3.0 branch, since the code
On Fri, Nov 26, 2010 at 12:14:33PM -0500, Phil Steitz wrote:
The deprecations below are in the wrong source tree. They need to be
applied to the 2.x branch and unless it is just as a signal to those
building (dangerously) from trunk, I do not see the point of deprecating in
the 3.0 branch.
Hi,
I'm having a problem in my scxml project :
state id=STATE_START
onentry
send target=test targettype='x-csta' xmlns:csta=
http://www.ecma.ch/standards/ecma-323/csta;
EVENT TARGET=test TAG=EVENT_HELLO
![CDATA[
This is a post for the user list, but please see below first ...
On Fri, Nov 26, 2010 at 1:03 PM, Michael musset mickamus...@gmail.com wrote:
Hi,
I'm having a problem in my scxml project :
state id=STATE_START
onentry
send target=test targettype='x-csta' xmlns:csta=
On Fri, Nov 26, 2010 at 12:49 PM, Gilles Sadowski
gil...@harfang.homelinux.org wrote:
On Fri, Nov 26, 2010 at 12:14:33PM -0500, Phil Steitz wrote:
The deprecations below are in the wrong source tree. They need to be
applied to the 2.x branch and unless it is just as a signal to those
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=1857projectId=97
Build statistics:
State: Failed
Previous State: Ok
Started at: Fri 26 Nov 2010 18:23:11 +
Finished at: Fri 26 Nov 2010 18:24:44 +
Total time: 1m 32s
Build Trigger: Schedule
Build
The deprecations below are in the wrong source tree. They need to be
applied to the 2.x branch and unless it is just as a signal to those
building (dangerously) from trunk, I do not see the point of deprecating
in
the 3.0 branch.
This was done on purpose, in order to have one
On Fri, Nov 26, 2010 at 4:38 PM, Gilles Sadowski
gil...@harfang.homelinux.org wrote:
The deprecations below are in the wrong source tree. They need to
be
applied to the 2.x branch and unless it is just as a signal to those
building (dangerously) from trunk, I do not see the point
[...]
Think about users reading the changelog, which is the source of the release
notes, or developers tracing the provencance or change history of code.
This, along with making it tractable for reviewers to review commits, is the
reason that we favor smaller, atomic commits and fully
22 matches
Mail list logo
