Re: [Rd] Seeking opinions on possible change to nls() code

2021-08-20 Thread Martin Maechler
> J C Nash > on Fri, 20 Aug 2021 11:41:26 -0400 writes: > Thanks Martin. I'd missed the intention of that option, > but re-reading it now it is obvious. > FWIW, this problem is quite nasty, and so far I've found > no method that reveals the underlying dangers well.

Re: [Rd] Seeking opinions on possible change to nls() code

2021-08-20 Thread J C Nash
Thanks Martin. I'd missed the intention of that option, but re-reading it now it is obvious. FWIW, this problem is quite nasty, and so far I've found no method that reveals the underlying dangers well. And one of the issues with nonlinear models is that they reveal how slippery the concept of

Re: [Rd] Seeking opinions on possible change to nls() code

2021-08-20 Thread Martin Maechler
> J C Nash > on Fri, 20 Aug 2021 11:06:25 -0400 writes: > In our work on a Google Summer of Code project > "Improvements to nls()", the code has proved sufficiently > entangled that we have found (so far!) few > straightforward changes that would not break legacy

[Rd] Seeking opinions on possible change to nls() code

2021-08-20 Thread J C Nash
In our work on a Google Summer of Code project "Improvements to nls()", the code has proved sufficiently entangled that we have found (so far!) few straightforward changes that would not break legacy behaviour. One issue that might be fixable is that nls() returns no result if it encounters some