-----Original Message----- From: Al Chou [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 2:14 PM To: Jakarta Commons Developers List Subject: Re: [math] proposed ordering for task list, scope of initial release
--- Phil Steitz <[EMAIL PROTECTED]> wrote:
Brent Worden wrote:
I've used a default error constant several places.
It would be nice to come
up with a central location for such values.
I get the first 3, but what exactly do you mean by the default error constant?
I read that to mean the accuracy requested (aka allowable error) of a given algorithm invocation.
That's right. Certain routines perform their iterative computations until a desired accuracy is achieved. If the user doesn't explicitly state this accuracy, what should it be? A default error/accuracy constant would answer that and provide uniform level of accuracy throughout the library.
Now I get it. But I am not comfortable with the scope. I could see this defined for RootFinding or Distributions, etc, but not in general. In general, the constant would have no meaning (to me, at least). I would prefer to let individual implementations define their own defaults (specified in the javadoc of course) and allow users to override. A single default "max iterations" for both rootfinding and, e.g. numerical integration, makes no sense. Better to have the defaults scoped at the algorithm/implementation level.
Brent Worden http://www.brent.worden.org
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
