Re: [OctDev] convhulln options.

[Paul K. <pki...@us...>]

On Dec 9, 2003, at 8:21 AM, Rafael Laboissiere wrote:

> * Simon Cross <si...@li...> [2003-11-25 14:48]:
>
>> I think convhulln() should remain compatible with the Matlab version 
>> but
>> it would be nice to have another function (called qhull?) which allows
>> one to pass options through to the qhull library.
>
> How is convhulln defined in Matlab?

K = convhulln(X)

>
>> Another route would be to have some way of setting the options which
>> convhulln() passes to the qhull library.
>>
>> Perhaps it would be best to implement both these options.  Then one
>> could easily modify the behaviour of convhulln() for a particular
>> program. The function convhulln() could then be implemented as a call 
>> to
>> qhull().
>
> Currently, the delaunay* functions of octave-forge have definitions 
> similar
> to this:
>
>     T = delaunayn (P[, OPT])
>
> where OPT is a string of options to be passed to the underlying qhull
> command.  I was thinking about extending the above to the voronoi* and
> convhull* functions.  Would it be okay?

Okay, but I would prefer 'standard' option handling.  Problem is, I
don't like the matlab standard: f(...,'option',val).  Passing a 
structure
x with fields option=value would be okay if octave had a syntax for
structure constants.

Paul Kienzle
pki...@us...