I am ok with option 2.
I guess my issue goes to my problem with the general API. The number
of iterations is a stopping condition, as well as all the other
conditions that are for some reason called convergence conditions. The
number of iterations condition is singled out as bad, hence it
throws
On Tue, Nov 20, 2012 at 05:08:23AM -0500, Konstantin Berlin wrote:
I am ok with option 2.
Thanks. I'll add new constructors if nobody has objections. Please note that
by using custom checkers (even those defined in CM), you make some
algorithms deviate from their standard behaviour.
I guess
On Nov 20, 2012, at 7:56 AM, Gilles Sadowski gil...@harfang.homelinux.org
wrote:
On Tue, Nov 20, 2012 at 05:08:23AM -0500, Konstantin Berlin wrote:
I am ok with option 2.
Thanks. I'll add new constructors if nobody has objections. Please note that
by using custom checkers (even those
On Tue, Nov 20, 2012 at 11:59:07AM -0500, Konstantin Berlin wrote:
On Nov 20, 2012, at 7:56 AM, Gilles Sadowski gil...@harfang.homelinux.org
wrote:
On Tue, Nov 20, 2012 at 05:08:23AM -0500, Konstantin Berlin wrote:
I am ok with option 2.
Thanks. I'll add new constructors if nobody
There are numerous examples when the optimization might not have
converged to the stopping condition, but the minimum discovered point
is better than the starting point that was initially provided. The
user should have the ability to at least decide if it is good enough,
or use it as a starting
On Nov 17, 2012, at 6:57 PM, Konstantin Berlin wrote:
There are numerous examples when the optimization might not have
converged to the stopping condition, but the minimum discovered point
is better than the starting point that was initially provided. The
user should have the ability to at
On 19 November 2012 21:47, Bruce A Johnson johns...@umbc.edu wrote:
On Nov 17, 2012, at 6:57 PM, Konstantin Berlin wrote:
There are numerous examples when the optimization might not have
converged to the stopping condition, but the minimum discovered point
is better than the starting point
Hello.
On Mon, Nov 19, 2012 at 04:47:08PM -0500, Bruce A Johnson wrote:
On Nov 17, 2012, at 6:57 PM, Konstantin Berlin wrote:
There are numerous examples when the optimization might not have
converged to the stopping condition, but the minimum discovered point
is better than the starting
That would solve the problem. Seems a bit messy though, since you now have two
conflicting stopping conditions, one you provide in the checker implementation,
the other in the function call. I am not clear why if you are throwing an
exception you don't provide more information inside it, so the
Hi.
[Please do not top-post.]
On Mon, Nov 19, 2012 at 09:17:39PM -0500, Konstantin Berlin wrote:
That would solve the problem. Seems a bit messy though, since you now have
two conflicting stopping conditions, one you provide in the checker
implementation, the other in the function call. I
10 matches
Mail list logo
