Dear DXplorers,
I have had no messages from the list since (and including) my last post (1
week ago), so please excuse me if you replied and something went wrong at
my end.
I am struggling to render a tricky, irregular, 3-D surface that the
{Connect} module does not fully cope with. The surface has saddle points;
only those facing +Z get connected properly. Below the 'good' part,
erroneous connections form across voids adjacent to saddle points.
Actually, on a closed surface, it makes no sense to define a single, global
normal for {Connect} because the surface will always contain faces that are
parallel to such a normal, and, thus, won't get connected.
I could modify my software to output a normal for every point on the
surface. Could I put these into something like {Connect}? or to take as
input a set of normals (i.e. 1 for each position on my surface) to
{Connect} instead of a single, global normal?
I have also tried {Grid} (hoping to invoke {ReGrid} & {Isosurface} after
fiddling the data component) but I can't get {Grid} to accept the
"positions" component as input for the <point> parameter. How does one
convert a field of positions to a list of vectors?
Thanks!
Allen H. Nugent
Graduate School of Biomedical Engineering
University of New South Wales
Sydney NSW 2052 Australia
Tel: +61 2 9385 3916 Fax: +61 2 9663 2108
