| Re: CONSTRAINED_MIN [message #12812] |
Tue, 08 September 1998 00:00 |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
Colin Rosenthal (rosentha@asp.hao.ucar.edu) writes:
> Has anyone had much joy using CONSTRAINED_MIN in idl 5.1?
> First the obvious. The calling sequence in the documentation is
>
> CONSTRAINED_MIN, Xbnd, Gbnd, Nobj, Gcomp, X, Inform
>
> while that in the example code is
>
> CONSTRAINED_MIN, x, xbnd, gbnd, nobj, gcomp, inform
>
> The latter is correct.
>
> Now the less obvious. On my first run it returns a value of the
> keyword INFORM of 7, although it only documents values between -1
> and 6 ! On the other hand, it apparently has found a better solution
> than POWELL (my problem is currently unconstrained) in many fewer function
> calls so I'm not ready to abandon ship just yet. Has anybody else
> experienced anything similar?
I'm not sure what version of IDL docs you have Colin,
but here is a post from not too long ago:
*******************************************************
Just to put everyone on the same page about this, the
correct sequence of arguments in the Constrained_Min
command is this:
CONSTRAINED_MIN, X, Xbnd, Gbnd, Nobj, Gcomp, Inform
The documentation incorrectly shows the command sequence as this:
CONSTRAINED_MIN, Xbnd, Gbnd, Nobj, Gcomp, X, Inform
Moreover, the Nobj argument is shown with a value of -4. It
should have a value of 3 to make the example work correctly.
********************************************************
I see the IDL 5.2 beta documentation has the problems
sorted out. :-)
Cheers,
David
----------------------------------------------------------
David Fanning, Ph.D.
Fanning Software Consulting
E-Mail: davidf@dfanning.com
Phone: 970-221-0438, Toll-Free Book Orders: 1-888-461-0155
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
