| Re: mpfit: meaning of status flag [message #53645] |
Fri, 27 April 2007 11:32  |
Craig Markwardt
Messages: 1869
Registered: November 1996
|
Senior Member |
|
|
Maarten <maarten.sneep@knmi.nl> writes:
> Hi,
>
> I'm using mpfit (actually mpfitfun) to do some fitting. Even though
> the fit seems to converge properly, for all fits I get the message:
> improper input perameters. Is this a problem? I must admit that I
> thoughly abuse the X variable, to pass some extra information around,
> but as far as I know, mpfit does not touch this variable. On the other
> hand, looking at the list of possible status values, I wouldn't know
> exactly what's good, and what isn't.
As you suspect, neither MPFIT nor MPFITFUN touches the "X" values. As
I note on my FAQ, check the ERRMSG keyword for a text description of
the problem. Usually you have specified a model parameter outside of
its limits or something like that.
Craig
--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@REMOVEcow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------
|
|
|
|
| Re: mpfit: meaning of status flag [message #53679 is a reply to message #53645] |
Thu, 26 April 2007 07:55  |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Apr 26, 4:32 am, Maarten <maarten.sn...@knmi.nl> wrote:
> Hi,
>
> I'm using mpfit (actually mpfitfun) to do some fitting. Even though
> the fit seems to converge properly, for all fits I get the message:
> improper input perameters. Is this a problem? I must admit that I
> thoughly abuse the X variable, to pass some extra information around,
> but as far as I know, mpfit does not touch this variable. On the other
> hand, looking at the list of possible status values, I wouldn't know
> exactly what's good, and what isn't.
>
> Maarten
Another thing... to "pass extra information around" look at the
FUNCTARGS keyword in mpfitfun.
|
|
|
|
| Re: mpfit: meaning of status flag [message #53680 is a reply to message #53679] |
Thu, 26 April 2007 07:50 |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Apr 26, 4:32 am, Maarten <maarten.sn...@knmi.nl> wrote:
> Hi,
>
> I'm using mpfit (actually mpfitfun) to do some fitting. Even though
> the fit seems to converge properly, for all fits I get the message:
> improper input perameters. Is this a problem? I must admit that I
> thoughly abuse the X variable, to pass some extra information around,
> but as far as I know, mpfit does not touch this variable. On the other
> hand, looking at the list of possible status values, I wouldn't know
> exactly what's good, and what isn't.
>
> Maarten
Read the header of the mpfit.pro file - it's all in there.
|
|
|
|
| Re: mpfit: meaning of status flag [message #53774 is a reply to message #53645] |
Tue, 01 May 2007 03:03 |
Maarten[1]
Messages: 176
Registered: November 2005
|
Senior Member |
|
|
On Apr 27, 6:32 pm, Craig Markwardt wrote:
> As you suspect, neither MPFIT nor MPFITFUN touches the "X" values. As
> I note on my FAQ, check the ERRMSG keyword for a text description of
> the problem. Usually you have specified a model parameter outside of
> its limits or something like that.
the errmsg string is empty, at least on the output that I've managed
to generate. All I have is the status variable equal to 1, and the
model parameters are within the limits, I checked that first.
A plot of the fit looks OK, and the residuals seem to be fine, so I
suspect it is OK, but the documentation is a bit vague: "STATUS: an
integer status code is returned. All values other than zero can
represent success." So I might be successful, but I'm certainly a bit
uncertain right now ;)
Maarten
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
