of the base constraints imposed by a particular model. e.g. I may want to
bounds. This points to an additional public interface.
p.s. I owe(?) some code for G2++ and simulated annealing. Apologies, but other
things have taken precedence. Are there any deadlines coming up?
>
> Hi,
>
> On 2004.06.15 02:16,
[hidden email] wrote:
> > I'm still leaning towards requiring some public constraint interface.
>
> You mean, other than the one provided for passing an additional
> constraint to calibrate?
>
> > The contraints are hidden at the moment + it is difficult to add
> > multiple constraints (my 2 australs).
>
> Well, the intrinsic constraints are hidden because they're not supposed
> to be tampered with. When calling calibrate(), you can add an
> additional constraint; multiple constraints can be collapsed into one
> by using CompositeConstraint.
>
> > A model would have a list of constraints. A constraint would have a
> > constraint type (boundary, positive, none, addition, subtraction,
> > multiplication etc.) and a parameter list (unary, binary).
> > Please let me know if I'm talking trash.
>
> No, it's not trash---but you can do it already.
>
> Later,
> Luigi
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Quantlib-users mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/quantlib-users>