With good starting values it often won't need to try anything outside
feasible region.
If after trying better starting values you find that that it is still
attempting to move outsie the feasible region then another approach is
to use the boundary value plus some monotonic function of the distance
Thanks Gabor, but my problem isn't finding reasonable starting parameter
values, it's preventing nls "giving up" when it tries parameter values
resulting in NA or Inf.
I know queries are often over-specific and the appropriate response is
"don't start there", so I'm trying to balance between si
With a small number of parameters just use brute force on grid
to calculate starting values. See nls2 package.
On Mon, Sep 21, 2009 at 12:17 PM, Keith Jewell wrote:
> Hi Everyone,
>
> I posted this a couple of weeks ago with no responses. My interface (via
> gmane) seemed a bit flakey at the tim
Hi Everyone,
I posted this a couple of weeks ago with no responses. My interface (via
gmane) seemed a bit flakey at the time, so I'm venturing to repost with some
additional information.
I'm trying to write selfStart non-linear models for use with nls. In these
models some combinations of para
4 matches
Mail list logo