Hi Evan,
Possibly a small jitter of initial guess would solve this issue. But it is hard
to tell if this method guaranties convergence in all problematic cases.
Normalization approach already works and allows to converge in those cases.
Thanks,
Olexiy
-Original Message-
From: Evan
Hi Gilles,
Looks good to me. It is the explicit update now. I would like to propose
different names for the new function:
applyConstraints() or renormalize()
Thanks,
Olexiy
-Original Message-
From: Gilles [mailto:gil...@harfang.homelinux.org]
Sent: Monday, September 08, 2014 3:11
On Mon, 8 Sep 2014 08:57:18 +, Olexiy Movchan wrote:
Hi Gilles,
Looks good to me. It is the explicit update now. I would like to
propose different names for the new function:
applyConstraints() or renormalize()
I had thought about the second one.
But, IMO, the (cosmetic) problem would
On 09/08/2014 04:50 AM, Olexiy Movchan wrote:
Hi Evan,
Possibly a small jitter of initial guess would solve this issue. But it is
hard to tell if this method guaranties convergence in all problematic cases.
Normalization approach already works and allows to converge in those cases.
For
Gilles,
I like this approach. My only thought is that a separate interface for
the validate method would be nicer for our Java 8 users. Then the
implementation could be a lambda: (p) - p.unitVector()
Best Regards,
Evan
On 09/07/2014 08:11 PM, Gilles wrote:
On Thu, 4 Sep 2014 12:52:24 -0400,
Please provide feedback as you see fit. I'll send this out in 24 hours.
[DRAFT] Apache Commons Board Report, September 9 2014
The Apache Commons project focuses on all aspects of reusable Java
components.
The Apache Commons components are widely used in many projects, both within
Apache and
Hello.
On Mon, 8 Sep 2014 08:56:36 -0400, Evan Ward wrote:
Gilles,
I like this approach. My only thought is that a separate interface
for
the validate method would be nicer for our Java 8 users. Then the
implementation could be a lambda: (p) - p.unitVector()
Do you mean define an
I was suggesting (though not clearly :) keeping the
MultivariateJacobianFunction interface as is and adding a new interface
for any post processing of the evaluated point. Something like:
interface StepFinalizer {
RealVector apply(RealVector point);
}
Then we would add another getter/setter
On Mon, 8 Sep 2014 11:50:43 -0400, Evan Ward wrote:
I was suggesting (though not clearly :) keeping the
MultivariateJacobianFunction interface as is and adding a new
interface
for any post processing of the evaluated point.
Isn't it rather pre-processing (the point is changed before
On 09/08/2014 12:06 PM, Gilles wrote:
On Mon, 8 Sep 2014 11:50:43 -0400, Evan Ward wrote:
I was suggesting (though not clearly :) keeping the
MultivariateJacobianFunction interface as is and adding a new interface
for any post processing of the evaluated point.
Isn't it rather
10 matches
Mail list logo
