Actually, only the default algorithm is supported: algorithm="plinear" is
broken too. I've just added a check for the default algorithm in
R-patched, as the fix is better done on the R-devel code base (which
supports weights).
On Thu, 22 Dec 2005 [EMAIL PROTECTED] wrote:
> I've found the prob
You don't actually need Ben's example. The problem occurs
also for the first example in ?nls if algorithm = "port" is
used.
Peter Ehlers
[EMAIL PROTECTED] wrote:
> Duncan Murdoch wrote:
>
>>I've found the problem, but someone who knows more about nls() will have
>>to fix it.
>>
>>The problem i
Duncan Murdoch wrote:
> I've found the problem, but someone who knows more about nls() will have
> to fix it.
>
> The problem is that in the demo code below, n1 ends up being an nls
> object, but n1$call$control is NULL. profiler.nls() assumed that the
> nls object passed to it has a non-NULL
I've found the problem, but someone who knows more about nls() will have
to fix it.
The problem is that in the demo code below, n1 ends up being an nls
object, but n1$call$control is NULL. profiler.nls() assumed that the
nls object passed to it has a non-NULL element there, and doesn't check.
On 12/22/2005 1:23 PM, [EMAIL PROTECTED] wrote:
> Full_Name: Ben Bolker
> Version: 2.2.1
> OS: Windows XP and 2000
> Submission from: (NULL) (128.227.60.124)
>
>
> The following code, using confint() to try
> to get confidence intervals on an nls object
> that has been fitted with algorithm="po
Full_Name: Ben Bolker
Version: 2.2.1
OS: Windows XP and 2000
Submission from: (NULL) (128.227.60.124)
The following code, using confint() to try
to get confidence intervals on an nls object
that has been fitted with algorithm="port"
reliably crashes R 2.2.0 and 2.2.1 with the
latest version of
