Okay.  The program I have is called "Delaunay" and is available for
anonymous FTP from photon.utah.edu.  It's in ~ftp/pub/Delaunay.tar.Z.
(Don't forget to use binary mode.)

It is based on a program by the same name that Ken Sloan wrote some
time ago.  I hacked it to do several things:

   1) Accept the output of Durer when Durer is used with the -aL switch

   2) Maintain both the triangulation and the sampling kD-tree so that
      the user can view either one.

   3) Call a set of device dependent animation routines so that the user
      can view the triangulation (or kDtree) as it is constructed.


There are two devices currently supported:  "null" which does nothing but
compiles on anything and  "iris" which is for the SGI 4D series and uses the
GL library.

The null device is a good place to start from for a new port since it
has all the stubs in place.  You can look at iris.c to figure out what
each stub is supposed to do.  There is a function called
"AnimateDoEvent" that lets the user interact with the animation by
pressing function keys or doing things with the mouse.  For example,
they can choose whether they want to see the triangulation or the
kDtree cells.  You can leave that as a stub if you really don't care
about interaction and just want to watch the animation.


Oh yeah, Delaunay can accept output from Durer in either of two forms:
BINARY or ASCII.  You select which form at compile time.  The compile
switch is "-DBINARY" for binary mode.  Durer should have the same
makefile option.  BINARY is faster but requires that Durer and
Delaunay run on machines that share the same floating point format.


Generally, I hook Durer and Delaunay together like this:

Durer -x 128 -y 128 -m 3 -aL -ar 1 -aR 256 < some_object.wd  | \
Delaunay -

I forget what the "-" means in the Delaunay command line but I think it means
to do online animation rather than running in batch mode.  The Durer options
should be document in the "Durer -help" message.

Of course, for best performance you may want to run Durer on a different
processor than the machine running Delaunay and doing the animation.
Durer tends to be the bottleneck rather than Delaunay but its still worthwhile
to run them on different machines if possible.