Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <43010AAB.3090803@yahoo.de>
Date: Mon, 15 Aug 2005 23:35:39 +0200
From: "J.Pietschmann" <j3322ptm@yahoo.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7.6) Gecko/20050317 Thunderbird/1.0.2 Mnenhy/0.7.2.0
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: DO NOT REPLY [Bug 36060] New: - [math][patch] Integration Source
 Files
References: <20050806181356.98653E0@ajax.apache.org>
	 <42FE9A86.7000802@yahoo.de> <8a81b4af05081400226293acd0@mail.gmail.com>
In-Reply-To: <8a81b4af05081400226293acd0@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Phil Steitz wrote:
> Great!!  I created a release branch for 1.1 and updated the POM in
> trunk to 1.2, so there will be no contention with the release.  I also
> committed the sources in what I think is the latest version to trunk. 
> Pls check out and make any changes you see fit.
> 
Now that's convenient! Thank you!

BTW I'd rather created a new "Integration" or "SoC" entry in
bugzilla and declared the existing bugs as blockers rather
than mark them as duplicate. This way, reports from others
could be easily tracked too without mixing them with Zhang's
contribution. New, exiting bugzilla feature.
(Another BTW: also a neat way to track release blocking bugs
and feature requests).

> I think one could argue for including both kinds of things, similiar
> to other places in [math].  Provide users with the choice to select an
> algorithm or use a default or "adaptive" selection.

The problem is that making a reasonable choice about which
algorithm to use requires months, if not years of education
and experience. I'd say if we require this, a lot of people
will be dissapointed. As I said, the holy grail is an algorithm
which is consistently performance-wise within a factor of two
(or five) of a carefully picked, perhaps customized algorithm,
and either gives the correct answer or bails out for 99.99% of
the cases anybody wants to throw at it. Including functions like
1/(x^3), x*sin(1/x) or 1E+6*exp(-((x-0.55555)/1E-6)^100).
Unfortunately, unpleasant things like singularities in the
integration interval are uncomfortably common in real world
problems.

J.Pietschmann

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org