Khoros, like AVS, is a dataflow oriented application.  Prior to
this port, Khoros and AVS focused on two mututally exclusive
areas, Khoros on 1D digitial signal processing(DSP) and 2D image
processing (IP), and AVS on 3D volume visualization.  

Soon the Khoros group at the University of New Mexico will
release Khoros Version 2.0, which will support volume visualization,
and with this port of 235 khoros DSP and IP routines, AVS now
supports the 1D and 2D realms quite well.

For the AVS port, we used the code of Khoros V1.0 Patch 5.  So
in most respects, the algortithm code in the new AVS modules
is well debugged.

However, in the immediate short term, these AVS modules may
exhibit some eradic behavior.  If this is the case, there
is probably a trivial coding error in the wrapper around
the khoros algorithm.  Please let the IAC know whenever these
are encountered so that they may be rectified quickly, and
an updated version returned to you.

The goal is to test each and every module thoroughly by 
January 1, 1993.

On a technical note, for each module, vabs, there is a library
routine lvabs.  The source code to the vabs wrapper would
be in the conglomerate avs wrapper file, arith_unary.  The source
code to the khoros algorithm, or library routine would be in
the file lvabs.c

The motivation for conglomerating multiple module source codes
into one file was to limit the disk space requirement for the
complete khoros module suite.  Separately, the complete suite
might have occupied over 300 Mb for just the compiled binaries !

The khoros algorithms make references to functions in the khoros
libraries.  Thus, before the avs-khoros modules can be compiled
for a given platform, these libraries must be ported.  Currently,
we only have libraries for the DEC and the Sun platforms.  
However, please feel free to port these libraries to your own
platforms.  The khoros source code is available from pprg.eece.unm.edu.

Please let me know what gaps I have left out in this brain dump-

Terry

