Howdy, >4. Thinking of the developers who will use this stuff, I feel like we >need a way to insulate them from having to think about rootfinding >strategy choice. As Al has pointed out, we are not (at least yet ;-)) >in the AI business, so we can't automagically make the best choice for >them; but it might be a good idea to somehow specify a default strategy. > Unfortunately, the "safe" choice would likely be bisection. We >could obviously annoint bisection as the "default" by naming it >something like "Solver", but there might be simpler/better ways to do this. ><flame-invitation> I bet that in most real world applications the >difference in convergence speed is not a big deal and guaranteed >convergence/domain of application is more important than expected speed >of convergence. Consider, for example, our own use in CDF inversion to >get critical values for stat tests. </flame-invitation>.
As someone who plans to use commons-math but does not plan to contribute code to it (though I do plan on testing, commenting in this forum, and using in production), I definitely need guaranteed convergence more than convergence speed. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
