Here's some code I put together for checkpointing a function being
optimized. Hooking directly into optim would require modifying its C
code, so this seemed the easiest route. I've wanted more information on
the iterations than is currently provided, so this stuff some info back
in the calling env
On Tue, Jan 03, 2006 at 01:26:39PM +, Prof Brian Ripley wrote:
> On Tue, 3 Jan 2006, Kasper Daniel Hansen wrote:
>
> >On Jan 3, 2006, at 9:36 AM, Brian D Ripley wrote:
> >
> >>I use save.image() or save(), which seem exactly what you are asking for.
> >
> >I have the (perhaps unsupported) impr
On Jan 3, 2006, at 2:26 PM, Prof Brian Ripley wrote:
> On Tue, 3 Jan 2006, Kasper Daniel Hansen wrote:
>
>> On Jan 3, 2006, at 9:36 AM, Brian D Ripley wrote:
>>
>>> I use save.image() or save(), which seem exactly what you are
>>> asking for.
>>
>> I have the (perhaps unsupported) impression th
Roger D. Peng wrote:
> One possibility is to write in some checkpointing into your objective
> function,
> such as saving the current parameter values via 'save()' or 'dput()'.
Has anyone successfully checkpointed and restarted R using any of the
linux process checkpointing solutions I find w
One possibility is to write in some checkpointing into your objective function,
such as saving the current parameter values via 'save()' or 'dput()'.
-roger
Ross Boylan wrote:
> I would like to checkpoint some of my calculations in R, specifically
> those using optim. As far as I can tell, R do
On Tue, 3 Jan 2006, Kasper Daniel Hansen wrote:
> On Jan 3, 2006, at 9:36 AM, Brian D Ripley wrote:
>
>> I use save.image() or save(), which seem exactly what you are asking for.
>
> I have the (perhaps unsupported) impression that Ross wanted to save the
> progress during the optim run. Since it
One possibility for overcoming this problem might be to divide the
variables being optimized over into two sets using a grid over one
set (which should probably consist of only one or two variables) and then
fixing the gridded variables use optim over the rest. In many problems its
really just one
On Jan 3, 2006, at 9:36 AM, Brian D Ripley wrote:
> I use save.image() or save(), which seem exactly what you are
> asking for.
I have the (perhaps unsupported) impression that Ross wanted to save
the progress during the optim run. Since it spends most of its time
in the .Internal(optim(***
I use save.image() or save(), which seem exactly what you are asking for.
On Mon, 2 Jan 2006, Ross Boylan wrote:
> I would like to checkpoint some of my calculations in R, specifically
> those using optim. As far as I can tell, R doesn't have this facility,
> and there seems to have been little
