From h.wickham at gmail.com  Tue Aug  7 14:34:07 2007
From: h.wickham at gmail.com (hadley wickham)
Date: Tue, 7 Aug 2007 07:34:07 -0500
Subject: [Rd] Optimization in R
In-Reply-To: <46B84A8B.1070601@stats.uwo.ca>
References: <46B47E53.2040801@stats.uwo.ca>
	<971536df0708041005h55c2488by76709cf4fb989690@mail.gmail.com>
	<46B4C2B2.3030109@stats.uwo.ca>
	<971536df0708041123n5d59b1ebw18618d6340b76300@mail.gmail.com>
	<46B4C56D.8020408@stats.uwo.ca>
	<971536df0708041153o174d73f5vd2c28f483a6bf6b6@mail.gmail.com>
	<46B4CFCD.2000202@stats.uwo.ca>
	<f8e6ff050708061955q4b0cba9fmda8b0df99f3c0173@mail.gmail.com>
	<20070807031813.GA1530@ms.unimelb.edu.au>
	<46B84A8B.1070601@stats.uwo.ca>
Message-ID: <f8e6ff050708070534v5aa973b5rd8bc46bf4d4ab334@mail.gmail.com>

On 8/7/07, Duncan Murdoch <murdoch at stats.uwo.ca> wrote:
> Those are small parts of the calculation, not the whole thing.  The
> original point was that optim() is a very thin wrapper around the code
> to do the optimization.  I just don't see a need to make it more
> complicated so it can be used to wrap other methods.  Authors of new
> optimization methods can just create new functions, following the
> pattern set by optim(), and it will be easier for almost everyone.

Another alternative would be to describe a common interface to
optimisation functions (like the modelling functions).  Otherwise it
becomes a hassle to switch in and out different functions because they
each have slightly different interfaces (eg. clustering and
classification algorithms).

Hadley



[Rd] Optimization in R
hadley wickham