yes: From "?optim", I get the following:
optim(par, fn, gr = NULL,
method = c("Nelder-Mead", "BFGS",
"CG", "L-BFGS-B", "SANN"),
lower = -Inf, upper = Inf,
control = list(), hessian = FALSE, ...)
By "fn", I meant the function you supply for that argument.
spencer graves
Hae-Kyung Im wrote:> Hi,
> Thanks for your reply.
>
> I did search in google but I couldn't really find a list of error
codes.
> Although you're right, that wouldn't probably help me much.
>
> What do you mean by using "fn" as a stand-alone function? Do you
mean the
> function I'm maximizing?
>
> Haky
>
>
>
> On Thu, 4 Sep 2003, Spencer Graves wrote:
>
>
>> I just did a Google search for "lapack error codes" and got
several
>>hits. However, I don't know if a translation of "error code
17" would
>>really help you.
>>
>> Have you tried "fn" as a stand-alone function? If yes,
have you
>>tried including a "cat" or "print" statement in it,
so it prints the
>>value (and maybe the arguments) before it actually returns it? If optim
>>is going to run more than a few seconds, I have "fn" print the
value it
>>returns. If it returns NA. I see that, etc.
>>
>>hope this helps.
>>spencer graves
>>
>>Hae-Kyung Im wrote:
>>
>>>Does any of you know where I can find an explanation of lapack
errors codes?
>>>I get error code 17 when using optim().
>>>
>>>Is there a way to handle errors in R such that depending on the type
of
>>>error I can decide what to do next?
>>>
>>>Thanks,
>>>Haky
>>>
>>>______________________________________________
>>>R-help at stat.math.ethz.ch mailing list
>>>https://www.stat.math.ethz.ch/mailman/listinfo/r-help
>>
>>
>