The bit_movie module is used to create and playback single bit black and white movie loops. It takes source images from any image source in AVS. The bit_movie module saves up movie loop sequences in "The X server" memory, and then allows for playback after storage. The motivation is to create the longest animation sequences possible, at the highest possible display rate, without going to disk.

The CREATE MINI DATA module is used in conjunction with the AVS module "write field", and other specially designed modules include "FIND MAP", "MULTI_extract", and "WRITE TIMESTAMP". The MCNC Environmental Programs Group has created this module as part of a suite of AVS demo modules, networks, and sample data sets to demonstrate the functionality of its visualization prototype for an Environmental Decision Support System (EDSS). You can download these modules individually from the IAC using anonymous ftp to the appropriate directories /avs_modules at avs.ncsc.org. If you would like to download the entire suite of modules, networks, and sample datasets at the same time, the IAC recommends that you use anonymous ftp to grab the following file from avs.ncsc.org ftp/avs/Data/avs_dataMCNC_Env_Pgms/MCNC_Env_Pgms.tar.Z This contains all source code to all local and remote modules, as well as all of the sample datasets, networks, documentation, installation, and usage notes.

CREATE USER MINI DATA -- creates a local data set from a remote data file and place it in the users own directory structure. The MCNC Environmental Programs Group has created this module as part of a suite of AVS demo modules, networks, and sample data sets to demonstrate the functionality of its visualization prototype for an Environmental Decision Support System (EDSS). You can download these modules individually from the IAC using anonymous ftp to the appropriate directories /avs_modules at avs.ncsc.org. If you would like to download the entire suite of modules, networks, and sample datasets at the same time, the IAC recommends that you use anonymous ftp to grab the following file from avs.ncsc.org ftp/avs/Data/avs_dataMCNC_Env_Pgms/MCNC_Env_Pgms.tar.Z This contains all source code to all local and remote modules, as well as all of the sample datasets, networks, documentation, installation, and usage notes.

Create MPEG is a subroutine module which will create MPEG movies from a series of AVS images. It uses Andy Hung's 'MPEG' which is available by anonymous ftp from Stanford. Because of the way MPEG movies are encoded by 'MPEG', many temporary files need to be stored, bear this in mind when choosing which directory to make your movie in. Version 2 fixes bugs.

This module allows users to draw the United States map with state boundary and county boundary. With the distribution of the module, two map data files are also included. "allcounty.txt" is ASCII data for boundaries of ALL counties in the United States, including Alaska, Hawaii and Perto Rico. "countryd.txt" is ASCII data for boundaries of the states. Users may construct their own boundary map according to the format. This is one of a suite of modules we used to plot the emission data for the state of North Carolina. This group of modules allows displaying points, lines and polygons over a map of the United States. The module suite is stored as a group in a compressed tar file at the International AVS Center, with some sample networks and datasets included. You may find it easier to access the modules this way. The compressed tar file is approximately 1.2MB in size, and can be found via anonymous ftp to avs.ncsc.org, in ftp/avs/Data/avs_dataWang_GIS_mods.tar.Z.

This module interprets AVS geometry data into Inventor format(V2.0 ascii) and writes it out to a new file.

"Geom to Wavefront" accepts as input an AVS GEOMedit_list struct which contains a pointer to a linked list of GEOMedit structs. The list is traversed and each element which is of type GEOM_EDIT_GEOMETRY is examined to determine its GEOMobj type--as opposed to GEOMedit type--where the possible types are mesh, polyhedron, polytriangle strip array, sphere, or label. An equivalent Wavefront .obj file is written to disk for each polyhedron and polytri in the edit list. Note that a single AVS geometry may map to multiple .obj files.

This product was developed for C3820, ConvexOS/10, Fortran Compiler 6.0. A so-called GEOM driver for the Application Visualization System (AVS) has been built into the classical RC-plotroutines (Calcomp), as an AVS course material spin-off. This means that AVS *.geom files can be produced by the plotroutines, which can be read in and visualized by the Geometry Viewer.

The Image to Postrscript module is a module that prints an Adobe Postscript file containing the image that is connected to the input port. It is designed to give the user a wide variety of image sizes, orientations, positions, and qualities. Note that the Dump to File button must be pressed to dump the image to the file, as the dump may take several seconds.

Used to record AVS animations to videotape or laserdisc, one frame at a time. It works by talking with either a Lyon-Lamb Minivas videotape controller, or a Sony Laser Videodisc recorder/player. Record Animation sends the appropriate commands to initialize the recording device, to tell the recording device when to record a frame, and to wait for the recording device to complete the frame record before continuing with the next frame. Usually, the Record Animation module is used in conjunction with an animation module of some sort which produces geometry for each frame of the animation. This geometry is then fed into the "render geom" module to be rendered as a pixmap output. The pixmap would then be connected to "display pixmap" and also to the pixmap input of the Record Animation module. The Record Animation module uses the pixmap to tell when the current scene has changed so that it will know to send the appropriate record command to the recording device.

Version 2.0 is basically just the text version (i.e. 1.0) with a Motif interface dropped on top. The goal is to provide easier script creation and adding, as well as a few new features. Interested users should consult the Instructions.ps file for a general guide on creating scripts with v2.0. Not covered in the instructions is the Convert script which is intended to allow v1.0 users to port their scripts to v2.0 format. The v2.0 format will be used in the final AVS/Motif version. The Convert script is simple to use - Convert source_file dest_file

This is a display module, it takes a 2D floating point field, treats each row as a 1D signal, and draws the signal traces next to each other. The offset, amplitude, signal spacing, etc. can be controlled for any range of data. The signals can be plotted vertically, horizontally, or in 180 degree polar configurations. Additional controls allow for Seismic moveout interpretation, given an Time Offset (T0) and a Velocity, linear or hyperbolic moveout functions may be overlayed and optionally applied to the trace data. The display is like wiggle trace, but the areas under the curve are not filled in. The module catches mouse events in the window, but these are currently commented out. One possibility is to provide dynamic pan and zoom under mouse control, or allow signal picking. If the input is 1D only, it will draw one signal line, and may be used like a real-time oscilliscope display.

Vector_Postscript - converts a Geometry Edit List to vector PostScript

This module writes an image from an AVS Network in a variety of formats. All formats which the San Diego Supercomputing Center's image tools support, this module supports. With this module you can write out an AVS image in MacPaint format for inclusion in a to-be published document !! Any of the following image file formats can be read in by this module eps Encapsulated PostScript file, gif Compuserve Graphics image file, hdf Hierarchical Data File, icon Sun Icon and Cursor file, iff Sun TAAC Image File Format, mpnt Apple Macintosh MacPaint file, pbm Portable Bit Map file, pcx ZSoft IBM PC Paintbrush file, pgm Portable Gray Map file, pic PIXAR picture file, pict Apple Macintosh QuickDraw/PICT file, pix Alias image file, pnm Portable aNy Map file, ppm Portable Pixel Map file, ps PostScript file, ras Sun Rasterfile, rgb SGI RGB image file, rla Wavefront raster image file, rle Utah Run length encoded image file, rpbm Raw Portable Bit Map file, rpgm Raw Portable Gray Map file, rpnm Raw Portable aNy Map file, rppm Raw Portable Pixel Map file, synu Synu image file, tiff Tagged image file, x Stardent AVS X image file, xbm X11 bitmap file, xwd X Window System window dump image file. Version 2.0 frees allocated memory after writing each image.

WRITE TIMESTAMP -- write into the specified file name the input timestamp string. The WRITE TIMESTAMP module creates an ASCII file and writes into it the set of timestamp labels input as one string. This file is needed to indicate the date and time represented by AVS data fields that have been created by extracting pieces from original model files of type ROM, RADM, UAM and ALPHA. The MCNC Environmental Programs Group has created this module as part of a suite of AVS demo modules, networks, and sample data sets to demonstrate the functionality of its visualization prototype for an Environmental Decision Support System (EDSS). You can download these modules individually from the IAC using anonymous ftp to the appropriate directories /avs_modules at avs.ncsc.org. If you would like to download the entire suite of modules, networks, and sample datasets at the same time, the IAC recommends that you use anonymous ftp to grab the following file from avs.ncsc.org - ftp/avs/Data/avs_dataMCNC_Env_Pgms/MCNC_Env_Pgms.tar.Z This contains all source code to all local and remote modules, as well as all of the sample datasets, networks, documentation, installation, and usage notes.

This DATA output module generates a sequence of UCD data time steps onto a (set of) file(s), which may then be read by the twin module, RdUcdAnim. For each time step, it can store node positions, node data, cell data, model data or a subset of these. It is fully compatible with the standard read ucd format, so the first time step may be read by read ucd.

The avs2vrml module saves an AVS geometry data structure as an equivalent VRML Version 1.0 compliant *.wrl file. Meshes, polyhedrons, spheres, and polytriangles are fully-supported. Labels don't quite work yet.

This module accepts a geometry object (mesh, polyhedron, polytriangle, or sphere type) and outputs the object's volume and surface area. The name of the object and its volume and area values are also printed to the terminal window in which AVS was started.

Keeps a running tally of the biggest and smallest numbers to come through its input ports. The text string parameters will update each time a smaller of larger value comes through one of its ports. If the reset button is turned on, then the running tally is reset to have to current minimum or maximum. For example, if on one execution the module received 0.020 and -0.020, and at the next execution the module receives 0.039 and -0.05, then the string parameters will display 0.039 and -0.020. If you have a time series of data and you want to find out the absolute minimum and maximum of the data values over time, this module allows that capability.

This module creates and sets up a unix pipe file, for communication between an AVS module and an external application. It makes unix system calls to create the pipe file, based on a typein name. It helps manage the use of the pipe, with options to flush, etc. It outputs the full pathname of the pipe, once established, for downstream modules to use for the communication.

This module deletes objects from the geometry viewer on command, based on the name (alias) of the module that created the geometry.

Deletes a geometry object having a user supplied name.

Read data from ascii file, data may be integer or floating point numbers separated by spaces.

This AVS module is designed to provide access to the HP specific back-to-front Volume Rendering graphics functionality of the Starbase graphics API. This module can only be successfully built and executed on an HP700 workstation. There are actually two modules here, which have identical functionality. They both takes in a word/voxel dataset (with packed ARGB) and a transform matrix and renders a volume in a window. The only difference is that the first module uses the PRE_SCALED_ALPHA data form, while the second does not. For an explanation of this CUBIC_POLYPOINT option see the man page for the module.

This AVS module is designed to provide access to the HP specific back-to-front Volume Rendering graphics functionality of the Starbase graphics API. This module can only be successfully built and executed on an HP700 workstation. This module takes in a byte/voxel dataset, a colormap, and a transform matrix and renders a volume in a window. The difference with this module is that it implements a form of gradient shading. For coding convenience and speed the light source direction has been limited to one of the 26 vectors which pass directly through an adjacent voxel. The gradient magnitude is approximated as the magnituded difference of voxel under computation and the adjacent voxel along the light source vector. This magnitude is store in a second byte (per voxel) along with the original voxel scalar magnitude byte. This 2 byte per voxel field is fed to the CUBIC_POLYPOINT gescape along with a table which contains a lighting model applied to the original colormap supplied to the model. This lighting model is driven by ambient, diffuse, and specular weighting and theta/phi light source angles supplied as input parameters.

Track 2D cursor motion over displayed image. This module takes an input image and displays it in an X-window. Inputs an image and allows the user create mouse clicks and moves in the image window, with event information passed to other AVS modules using the "upstream data" concept. This module acts similarly to "display image" or "display tracker" in that it accepts an input image and displays this in an X-window. It also then accepts asynchronous mouse events in the window, and passes these mouse events ( in an upstream transform structure ) to an output port. This allows applications to be built using this module to do all the X dependent code, leaving the actual operation (such as pan, draw, etc.) to an upstream module, with no concern of X events.

This AVS module is designed to provide access to the HP specific back-to-front Volume Rendering graphics functionality of the Starbase graphics API. This module can only be successfully built and executed on an HP700 workstation. This module takes in a byte/voxel dataset, a colormap, and a transform matrix and renders a volume in a window.

This module converts an input pixmap to the so-called ICC format. This image format is used by local device drivers which communicate with the Kodak XL7700 printer. The single parameter is a file browser that allows you to specify the name of the ICC file to be created. After the file is written, the filename is reset to null. This prevents subsequent changes upstream in the network from automatically triggering the rewriting of the file. A new file is written only after the user has entered a filename.

This module converts a pixmap to the PostScript page description language and stores it in a file. After the file is written, the filename is reset to NULL. This prevents subsequent changes upstream in the network from automatically triggering the rewriting of the file. A new file is written only after the user has entered a filename. Two types of PostScript output are supported, PostScript-compatible monochrome laser printer and PostScript-compatible color laser printer.

This module produces a sun rasterfile from an input AVS format pixmap. This module is familiar with 8,24 and 32-bit pixmaps. It will write an 8-bit rasterfile when presented an 8-bit pixmap as input, otherwise a 24-bit BGR ("RT_STANDARD") rasterfile is produced.

The "field2 to Math" module allows a two-dimensional scalar field to be imported into Mathematica from AVS. When the "field2 to Math" module is invoked an xterm is started running Mathematica with the input and output of the xterm directed to and from the Mathematica session main loop. Entering Mathematica commands into the window will result in the appropriate Mathematica results. The session is initialised with a package of Mathematica commands which have started a MathLink communication channel to AVS. Other initialisations are made so that the Mathematica command AVSReadField[ ] will read a two-dimensional scalar field from AVS. Please note that at the present time the IAC does not have Mathematica installed on a , Sun, or Kubota platforms. As a result this module was placed on the ftp site using the Makefiles provided by the author, without testing.

Calculates the maxima and minima of input field data and of the grids. If the field has more than three dimensions, grid information is obtained for only the first three. The information is used to produce GEOM text objects. The min/max parameters allow individual objects to be toggled on or off. The "Text Height" parameter sets the height of the GEOM text as a fraction of the window height.

ASCII Excel spreadsheet format files are produces containing field data in a table format. These files can be imported into a suitable excel format for analysis and plotting. Separator characters may be specified for differing output versions, three possible floating point output formats are selectable, and the maximum number of values per line is adjustable. The module only outputs the file if the file browser changes. This keeps the output file from beeing written too often.

"orthoslice" and "field to mesh" communicate through a secret code stored in the "points" array of the field structure. This will be an array of 6 floating point numbers representing [minx, maxx, miny, maxy, minz, maxz] for the 2D (3-space) field which orthoslice produces. FIELD TO MESH looks at these searching for when the min == max to determine which direction (I, J, or K) the slice was taken from. This is the means that FIELD TO MESH uses to orient and position the slices properly in the volume. The way to defeat this is to impose your own point information on the existing ones. For instance, you have a 64x64x64 volume and you're taking the 12th K slice. The points array will look like - [0, 63, 0, 63, 12, 12]. If you overwrite the Z mins/maxes with 0.0's, the slice will appear positioned on the XY plane (not 12 units above it). Similarly, the 23rd I slice points array looks like [23, 23, 0, 63, 0, 63] and will produce a slice parallel to the YZ plane at X=23. By overwriting the 23's with 0's, you will get it to lie right on the YZ plane. This should put between the orthoslice and the field_to_mesh modules in your network.

The geom parent module allows an interactive user to reparent any and all objects in the geometry viewer system. This is useful if you want some objects to move together, but not all. The "Group Name" parameter is used to define the group to add objects to. When the "Include Current Object" oneshot is pushed, the current object selected within the geometry viewer is reparented to the "Group Name".

To help place, size, and maintain user interface panels and widgets, this module gives dial and text parameter control over the "layout" of any item, without using the layout editor. Once an application is built, this module can will enable the layout to be dynamically changed by the end user, or used to prototype a layout, which can then be saved. Panel visibility can be controlled, as well as parent, place, and size. It used the CLI as the control path.

Converts its input image to the so-called ICC format. This image format is used by local device drivers which communicate with the Kodak XL7700 printer. The single parameter is a file browser that allows you to specify the name of the ICC file to be created. After the file is written, the filename is reset to NULL. This prevents subsequent changes upstream in the network from automatically triggering the rewriting of the file. A new file is written only when you enter a filename.

This is one of two modules written to translate AVS animations into mpeg format - image_to_YUV and image_to_PPM. Both formats can be read by mpeg encoder. A ppm image will have a memory size twice bigger than the yuv one, but it can be visualised by xv. You will need to make use of mpeg_encode and mpeg_play, both public domain utilities available via anonymous ftp from the University of California at Berkeley. These modules also make use of the San Diego Supercomputer Center's Image Tools, also available via anonymous ftp.

This is one of two modules written to translate AVS animations into mpeg format - image_to_YUV and image_to_PPM. Both formats can be read by mpeg encoder. A ppm image will have a memory size twice bigger than the yuv one, but it can be visualised by xv. You will need to make use of mpeg_encode and mpeg_play, both public domain utilities available via anonymous ftp from the University of California at Berkeley. These modules also make use of the San Diego Supercomputer Center's Image Tools, also available via anonymous ftp.

This module prints out an AVS image to a laser shot printer. You can specify the actual command to print in the parameter "Command". If you specify "cat > /tmp/filename" in "Command", you can save the image in the file in lbp format.

This coroutine takes upstream transform events from any geometry viewer scene, and outputs two transformation control ports, such that a small iconic scene can have remote control over two or more main geometry viewer windows. Once the position is defined from the icon window, pushing the "snap" button will send the transformation over to the other window.

Recreates the functionalities of some of the transformation options available in the geometry viewer. While this may seem redundant at first glance, it has proven to be a very useful module. The module is mainly used in networks where the Layout Editor is used to customize the user interface. The locations and appearances of this module's control widgets can be altered, while their corresponding widgets in the Geometry Viewer cannot. The module has no input or output ports. To include it in a network, simply drag it into the workspace.

This module creates a menu structure for all or part of the geometry viewer scene, and allows alteration of the object properties by simple color or transparency selection without going to the geometry viewer controls, for a simpler user interface.

This module takes input strings for the name of the object, the name of the view, and has a boolean toggle control to control the visible/invisible, or hide/show on that object in the view. It uses the CLI to perform the control, hence it has no output port.

Takes as input an AVS image field and creates a postscript file suitable for printing on a monochrome postscript printer. The postscript file contains a representation of the input color image using the "image" postscript command, using 8bits of gray. The color image is squashed down to 8 bits of gray by weighting each of the color channels in an attempt to approximate luminance. The postscript image is scaled so as to be centered on the page and to occupy as much area on the page as possible. The nice thing about the file produced is that it will work and produce similar results on, for example, a 200dpi device (like an Apple Laserwriter) or on a 600dpi device (like a Verityper). After executing, the module resets the filename parameter to NULL. This has the effect of requiring the user to enter a new filename for each subsequent invocation of this module before executing.

The output a60 module takes an AVS image data structure as input, converts it into Abekas YUV format and sends it to an Abekas a60 digital disk recorder. The user can specify the hostname of the a60 digital disk recorder on the network, the insert point and the number of times to repeat each frame. The insert point may be entered in any of four time formats (hh mm ss ff, mm ss ff, ss ff, or ff).

Takes as input an AVS image field and creates a postscript file suitable for printing on a color postscript printer. After executing, the module resets the filename parameter to NULL. This has the effect of requiring the user to enter a new filename for each subsequent invocation of this module before executing.

Extracts a single scalar value out of the input 2D scalar floating point field. The X and Y position parameters set the index point for the sample to be taken from the field. The numerical field value is then sent to stdout, usually into the window where avs was invoked. The one line message consist of the current X and Y sample index position, and the floating point value of the field at that point. The position values are clamped to the field dimensions internally, without regard to the dial min-max. This module does virtually no work, so "immediate" mode is recommended on the dials. The author has used this for debugging other networks and filters, by linking it in with a "t" junction to other more complex networks.

Print the contents of the "iv_pick" output port of the AVS4 image viewer module. This shows the results from picking on images with the left mouse button. It is a basic module showing the possibilities, and used for debugging of other image pick application modules. This module relies on features in AVS4, and will not function with earlier releases. This module will be useful for those building interactive image processing systems.

Print real creates a widget on the control panel that will contain the value of the module's input port. This module is part of the the Real Math module group, which is a single file, process-sharing set of modules that allow basic operations on and between integer and real AVS data types. They have been most useful in dealing with linkage of several AVS parameters. AVS has no simple way of performing math operations on reals, even though it does allow math operations on fields.

This module inputs any geometry, and outputs to the avs console window all of the vertices in the geometry objects present in the geometry edit list. This module initially can serve as a debugging tool for modules that output geometries. It also serves as an example module on how to process geometries on a module's input port. It most useful purpose however, is probably to extract quantitative information regarding surfaces, from visualization displays.

Is a diagnostic tool, used to show the contents of "upstream transform" data types, sent upstream for interactive control in AVS3. It uses "user defined data types".

Is a diagnostic tool, used to show the contents of "upstream geom" data types, sent upstream for interactive control in AVS3. It uses "user defined data types".

The "output 8bit ps" module takes as input a scalar (byte, single channel) field and creates a postscript file suitable for printing on a monochrom postscript printer. The postscript file contains a representation of the input color image using the "image" postscript command, using 8bits of gray. The postscript image is scaled so as to be centered on the page and to occupy as much area on the page as possible. The nice thing about the file produced is that it will work and produce similar results on, for example, a 200dpi device (like an Apple Laserwriter) or on a 600dpi device (like a Verityper).

This AVS module is designed to provide access to the HP specific back-to-front Volume Rendering graphics functionality of the Starbase graphics API. This module can only be successfully built and executed on an HP700 workstation. This module prototypes an ability to make use an HP graphics devices volume rendering capability remotely. The idea is to run AVS on the HP with the X display routed to a networked server, but make use of the HP workstation and one of the above listed display devices to render volume dataset on the HP then send the results (as AVS images) to the remote X display. To use this module you'll need to setup the environment variable COMPUTE_SERVER to point at the X server on the HP server that will be performing the rendering. This includes the same gradient lighting model described for the disp_lit_vol module.

This AVS module is designed to provide access to the HP specific back-to-front Volume Rendering graphics functionality of the Starbase graphics API. This module can only be successfully built and executed on an HP700 workstation. This module prototypes an ability to make use an HP graphics devices volume rendering capability remotely. The idea is to run AVS on the HP with the X display routed to a networked server, but make use of the HP workstation and one of the above listed display devices to render volume dataset on the HP then send the results (as AVS images) to the remote X display. To use this module you'll need to setup the environment variable COMPUTE_SERVER to point at the X server on the HP server that will be performing the rendering.

Is a field diagnostic and analysis module, similar to VOLSTAT, used to obtain global statistical information about field data. This module scans the data in the volume, and produces a small table, sent to stdout, usually into the window where avs was invoked, unless redirected. The table includes the following information about a field- Dimensions, Min/Max, Mean, Median, Standard Deviation, Skewness, and Kurtosis.

This AVS module is designed to provide access to the HP specific back-to-front Volume Rendering graphics functionality of the Starbase graphics API. This module can only be successfully built and executed on an HP700 workstation. This module assumes that a stereo ready monitor and viewing system (i.e. StereoGraphics' Crystal Eyes) are available. It will render a stereoscopic version of the disp_lit_vol module. This module make use of a similar environment variable as the COMPUTE_SERVER variable used by the remote_volume module. This module uses the environment variable STEREO_SERVER. Set this variable to point at the stereo-ready device. [In order to use this module well it is required that a second X display of some kind is available.] Run AVS with the DISPLAY set to the non-stereo screen or server. This module will open a full screen window on the display pointed to by STEREO_SERVER and will place the display in stereo mode (via the Starbase STEREO gescape). Stereo mode can be toggled off and on with the "Stereo" control button. (Turn off the stereo mode before deleting this module or exiting AVS, or your stereo display will be left in stereo mode.)

Sends the contents of the string input port to an output file, opened with a file browser. The string can replace the current contents of the file, or be appended to the file since opened during the session, as a log of strings in the network, controlled by a mode toggle. This is designed to be used to send command strings via a named pipe (see mknod pipe.file p) to another application program, where command input has been redirected to the same pipe. This allows an AVS user interface modules to control an external command-line driven application.

Ucd statistics is a diagnostic and analysis module, similar to the field module statistics, used to obtain statistical information about field data. This module scans the data in the volume, and produces a small table, sent to a scrollable text window in the module control panel. The table contains the statistics for each data component calculated separately. Then if there was more than one component, the table contains the statistics for all of the data components grouped together. It will create statistics for both node and cell data. It will also generate overall statistics for node data and cell data separately.

The ucd to wave module writes a ucd structure to disk, in wavefront format, which is supported by Data Visualizer. Ucd to wave works only with node data, therefore if you have cell data, you have to transform the cell data to node data using the cell to node module. Because Data Visulizer doesn't use mid-edge nodes, at this version, the ucd to wave module generally doesn't use the mid-edge nodes. One exception has been made - if the ucd cell is triangle with all mid-edge nodes present, ucd to wave module will split the triangle in 4 triangles. The user can change the module to support another ucd type which use mid-edge nodes. The wavefront file that will be written to disk is an ASCII file.

Often there will be a need to convert a string in AVS to a command or argument in unix to be performed at the command line. This module allows the user to output strings and integers to the command line for execution by the shell in the directory that AVS was run from.

Is a diagnostic and analysis module, used to obtain global statistical information about scalar volume data. Often the result of numerical analysis and visualization leads to an interest in just a few numbers such as the average value in the field. This "volume statistics" module scans the data in the volume, and produces a small table, sent to stdout, usually into the window where avs was invoked, unless redirected. The table shows the dimensional size of the field, total number of data points, the minimum and maximum scalar values, and the mean. This is a very simple module, and could be extended to measure other parameters such as standard deviation, median, etc. This module does virtually no computationally intensive work, has no parameters. The author has used this for debugging other networks and filters, by linking it in with a "t" junction to other more complex networks. In particular, when using "interpolate", it is nice to know the resulting volume dimensions.

Intended to be used with the AVS Animator application. The module hooks right up to the Animator module or the read_frame_seq module. This module accepts images, one at a time. The image is then converted into the Abekas A60 yuv format - with the same dimensions of the Abekas A60 yuv format - and output to a file in the Frame directory with a name corresponding to the frame number. ( i.e. Frame Number 20 -- Filename - 20 ) If the image is not the same size as the A60 image standard, then the AVS image is centered within the view of the Abekas. This works well when you consider the degradation of the image borders on its path to NCSC. This module was adapted from Ian Currington's write_abekas module and Abekas Inc.'s sample to_yuv program in their manual. It writes out a temporary file in between conversions. The module works fine - but it isn't pretty. Version 3 update provided by the UCLA School of Medicine's Andy Jacobson. The update includes bug fixes, and features wherein the user can name the file as with the animate_filename module, but with a fixed .yuv siffix. The user also has the choice of compressing the (huge!) output files. In some nets it may be desireable to allow or prevent overwriting of files, so a switch is now provided for this. Also you can supply your favorite compression program to this module, if desired.

Interprets AVS image data into Dore format and writes it out to a new file.

Interprets AVS image data into KSWAD format and writes it out to a new file.

This module is a first shot at incorporating QuickTime(tm) into AVS as a method for producing convenient, compact, and high quality video segments. QuickTime(tm) is rather convenient since there is likely to be more support on other systems, and there is a growing base of QuickTime(tm) cheaply available for the Macintosh. This code currently requires, the QuickTime Movie Exchange Toolkit, which is available from Apple, Inc, and a C++ compiler (you also need the C++ compiler to build the QuickTime(tm) libraries. Please note - since the IAC doesn't have the Exchange Toolkit, we weren't able to test this module out here.

This module provides I/O capability to images in the native machine format used by the abekas A60 digital video disk recording system. The image file specification is for the PAL (50 Hz, 625 line) version, but can easily be modified to support the NTSC version, or both. The abekas A60 holds 750 frames, or 30 seconds of live broadcast standard video imagery in the digital storage format dictated by the CCIR-601 specification. Although the disk format is Y-uv, the disk has firmware processing to encode/decode to 3-byte Red-Green-Blue images on-the-fly during tcp/ip file transfers.

The "write compressed image" module provides the same functionality as the AVS-supplied "write image" module, with the added twist that the image is in a "compressed" format. An AVS image may be compressed using the UNIX(tm) compress utility, or by using the sibling module "write compressed image." Compression ratios of 1 to 10 are easily achieved using this compression scheme.

This module writes an image in the eps format from an AVS Network. Encapsulated PostScript color, grayscale, and black-and- white image files are used by a variety of PostScript tools in order to include PostScript diagrams and images within other documents. Encapsulated PostScript files are recognized by the follow- ing filename suffixes .eps, .epi, .epsi, and .epsf.

This is yet another module to write a Compuserve GIF image file.

The write_geom module saves the geometry in a file. Currently there is a choice of three formats - avs-text, avs-binary, dxf (drawing exchange format by AUTODESK). The dxf-routines supply a rudimentary header, every object is placed on a single layer (PRISMS converts every layer in an object). The dxf-output is at last readable by PRISMS, ALIAS and of course AutoCAD.

This module writes an image in the gif format from an AVS Network. GIF (Graphics Interchange Format) is CompuServe's standard for generalized color raster images. This standard is a mechanism to exchange and display high-quality, high- resolution graphics images. CompuServe gif files are recognized by the filename suf- fixes .gif and .giff.

This module writes an image in the hdf format from an AVS Network. hdf is a generic, tagged Hierarchical Data File format developed by the National Center for Supercomputing Applica- tions (NCSA). hdf files may contain images, scientific data sets, and miscellaneous data items. Such files may be created by several NCSA tools. See the NCSA documentation for details on how to use these tools. hdf format handling within the SDSC image library is limited to images of certain depths and storage methods. hdf files are recognized by these filename suffixes .hdf, .df, and .ncsa.

This module writes an image in the icon format from an AVS Network. icon image files are used by Sun Microsystem's SunView win- dow system, NeWS window system, OpenWindows NeWS tool set, and X11 XView tool set for the storage of icons, cursors, fill patterns, and pieces of widgets (like button check- marks). Sun icon files can be most easily generated using Sun's iconedit(1) icon and cursor editor. The Sun operating sys- tem release includes a directory of standard icons, cursors, background patterns, and widget pieces in icon format in the directory /usr/include/images. See the Sun documentation set for details on how to use the tools dealing with Sun icon files. Sun icon files are recognized by these filename suffixes .icon, .cursor, and .pr.

This module writes an image in the iff format from an AVS Network. iff image files are generated by Sun Microsystems TAAC software such as voxvu(1) and cloudvu(1). See the TAAC-1 Application Accelerator Software Reference Manual for information on how to use these programs. Note that image files compressed with the Sun-TAAC utility make_movie(1) cannot be read by the SDSC image library. iff files are recognized by the following filename suffix .iff.

Writes an ASCII representation of an input irregular field to a file. The file format is the "LBL" irregular field file format, and is readable by the "read irreg" input module. This module is useful for looking at irregular fields, for example, after some processing step in a data flow network. A browser is supplied to let the user specify the filename to which the ascii representation will be written.

Compresses an image with the JPEG compression standard and writes to a file.The best and most readily available introduction to the JPEG compression algorithm is Wallace's article in the April '91 CACM- Wallace, Gregory K. "The JPEG Still Picture Compression Standard", Communications of the ACM, April 1991 (v. 34 no. 4), pp. 30-44. (Adjacent articles in that issue discuss MPEG motion picture compression, applications of JPEG, and related topics.) I highly recommend reading that article before looking at any of the JPEG code. For more detail about the JPEG standard you pretty much have to go to the draft standard, which is not nearly as intelligible as Wallace's article. The current version is ISO/IEC Committee Draft CD 10918-1 dated 1991-03-15.

This module writes an image in the mpnt format from an AVS Network. The MacPaint mpnt file is the standard Apple Macintosh mono- chrome bitmap image file format. It can be read by many Macintosh graphics applications, and many Macintosh applica- tions that can export bitmap graphics do so in the MacPaint mpnt file format. mpnt files are recognized by these filename suffixes .mpnt, .macp, and .pntg.

Writes a PC Paintbrush PCX image file. Note that a PCX file can contain a maximum of 256 colors. For maximum flexibility, a separate module is used to pick those colors.

This module writes an image in the pbm format from an AVS Network. pbm image files are used by various tools in Jef Poskanzer's PBM+ tool suite. See the PBM documentation set for details on how to use these tools. pbm files are recognized by the filename suffix .pbm.

This module writes an image in the pcx format from an AVS Network. The pcx image file format was invented by ZSoft for use in its IBM PC PC Paintbrush tool series. It has become a defacto standard in the IBM PC world and is regularly used for the storage of monochrome and color pixel information by paint-type tools. See the documentation for each of the IBM PC tools for details on how to use them. ZSoft pcx files are recognized by these filename suffixes .pcx and .pcc.

This module writes an image in the pgm format from an AVS Network. pgm image files are used by various tools in Jef Poskanzer's PBM+ tool suite. See the PBM documentation set for details on how to use these tools. pgm files are recognized by the filename suffix .pgm.

This module writes an image in the pic format from an AVS Network. pic image files are generated by PIXAR programming software, such as ChapVolumes and ChapReyes, the PIXAR Image Runtime Library called Pirl, and the PIXAR rendering tool RenderMan. See the PIXAR documentation set for details on how to use these applications and tools. PIXAR's pic file format is sometimes referred to as PICIO in PIXAR documentation. pic and PICIO mean the same thing. PIXAR's xpic is not the same as pic and is not supported by the SDSC image library. Note PIXAR's RenderMan always saves its image files with .pic filename suffixes. However, depending upon output defaults, RenderMan can generate .pic files with PICIO (same as pic) data or TIFF data. .pic files with TIFF data will confuse the SDSC image library. For you to avoid generating this type of file, we recommend that you configure RenderMan defaults to generate .pic files with PICIO data. PIXAR pic files are recognized by the following filename SDSC Last change March 4, 1991 1 IMPIC(3IM) SDSC IMAGE LIBRARY IMPIC(3IM) suffixes .pic, .picio, and .pixar.

This module writes an image in the pict format from an AVS Network. The PICT file is the standard Apple Macintosh image file format. It can be read by almost any Macintosh graphics application. Most Macintosh applications that can export graphics do so in the PICT file format. pict files are recognized by these filename suffixes .pict and .pict2.

This module writes a series of images in the pict format from an AVS Network. The file names are constructed from the base file name and the frame number as such ..pict The frame number is padded to the left with "0" to allow proper sequencing of frames. The intent of this is to allow conversion of a sequence of images into the pict format for video production.

This module writes an image in the pix format from an AVS Network. pix image files are generated by the rendering and painting tools of Alias Research, Inc., such as renderer, raytracer, and paint. See the Alias documentation set for details on how to use these tools. _N_o_t_e Alias quickpaint, available on Silicon Graphics, Inc., IRIS workstations, uses Silicon Graphic's rgb image file format rather than the Alias pix image file format. See the imrgb(3IM) man page for details on the rgb format. Alias pix files are recognized by these following filename suffixes .alias and .pix.

This module writes an image in the pnm format from an AVS Network. pnm image files are used by various tools in Jef Poskanzer's PBM+ tool suite. See the PBM documentation set for details on how to use these tools. pnm files are recognized by the filename suffix .pnm.

This module writes an image in the ps format from an AVS Network. PostScript color, grayscale, and black-and-white image files are used by a variety of PostScript laser printers and win- dowing system tools. PostScript files are recognized by the following filename suffixes .ps and .postscript.

This module writes an image in the ras format from an AVS Network. ras image files are used by various Sun Microsystems Inc. tools, such as screendump(1) and screenload(1). See the Sun documentation set for details on how to use these tools. Sun ras files are recognized by any of the following filename suffixes .ras, .scr, .sr, and .sun.

This module write data in ascii format from a "rectilinear field" data structure. The disk file is structured to contain information about the field at the beginning of the file, followed by the data.

Writes an ASCII representation of an input uniform field to a file. The file format is the "LBL" uniform field file format, and is readable by the "read uniform" input module. This module is useful for looking at uniform fields, for example, after some processing step in a data flow network. The uniform input field can be any type, size, and dimensionality. A browser is supplied to let the user specify the filename to which the ascii representation will be written.

This module writes an image in the rgb format from an AVS Network. rgb image files are generated by Silicon Graphics, Inc., software such as icut(1) and snapshot(1). See the Silicon Graphics documentation for information on how to use these and other Silicon Graphics programs. Silicon Graphics rgb files are recognized by the following filename suffixes .rgb, .iris, and .sgi.

This module writes a series of images in the rgb format from an AVS Network. The file names are constructed from the base file name and the frame number as such ..rgb The frame number is padded to the left with "0" to allow proper sequencing of frames. The intent of this is to allow conversion of a sequence of images into the rgb format for video production.

This module writes an image in the rla format from an AVS Network. rla image files are generated by Wavefront Technologies, Inc., software such as image and tdv. See the Wavefront documentation for information on how to use these and other Wavefront programs. rla is a subset of the newer Wavefront rlb specification. Programs that can read and write rlb files can also read and write rla files. The SDSC image library reader/writer is written to accommodate both types of files. Wavefront rla files are recognized by the following filename suffixes .rla and .rlb.

This module writes an image in the rle format from an AVS Network. rle image files are generated by the tools of Utah's Raster Toolkit. See the Utah documentation set for details on how to use these tools. Utah rle files are only recognized by the following filename suffix .rle

This module writes an image in the rpbm format from an AVS Network. rpbm image files are used by various tools in Jef Poskanzer's PBM+ tool suite. See the PBM documentation set for details on how to use these tools. rpbm files are recognized by the filename suffix .rpbm.

This module writes an image in the rpgm format from an AVS Network. rpgm image files are used by various tools in Jef Poskanzer's PBM+ tool suite. See the PBM documentation set for details on how to use these tools. rpgm files are recognized by the filename suffix .rpgm.

This module writes an image in the rpnm format from an AVS Network. rpnm image files are used by various tools in Jef Poskanzer's PBM+ tool suite. See the PBM documentation set for details on how to use these tools. rpnm files are recognized by the filename suffix .rpnm.

This module writes an image in the rppm format from an AVS Network. rppm image files are used by various tools in Jef Poskanzer's PBM+ tool suite. See the PBM documentation set for details on how to use these tools. rppm files are recognized by the filename suffix .rppm.

This module writes an image in the synu format from an AVS Network. synu is the image file format output by SDSC's synu (Syn- thetic Universe) portable renderer. synu files are recognized only by the following filename suffix

This module writes an image in the tiff format from an AVS Network. tiff is a generic Tagged Image File Format developed by Aldus and Microsoft in conjunction with leading scanner and printer manufacturers. tiff files may contain images and miscellaneous other image-related items. Such files may be created and manipulated by a variety of Tagged Image File Format tools. See the Tagged Image File Format documenta- tion for details on how to use these tools. tiff support within the SDSC image library is limited to images of certain depths and storage methods. tiff files are recognized by the following filename suf- fixes .tiff and .tif.

This module writes an image in the xbm format from an AVS Network. xbm bitmap image files are generated by MIT's X Window Sys- tem, version 11 (hereafter referred to as X11). xbm files are generated by the X11 bitmap(1) bitmap editor and used by most X11 tools to define cursors, icons, and other mono- chrome glyphs. See the X11 documentation set for details on how to use tools and subroutines dealing with X11 bitmaps. X11 xbm files are recognized by the following filename suf- fixes .xbm and .bm.

This module writes an image in the xwd format from an AVS Network. xwd window dump image files are used by the xwd(1) and xwud(1) tools of MIT's X Window System, version 11 (hereafter referred to as X11). See the X11 documentation set for details on how to use these tools. X11 xwd files are recognized by the following filename suffixes .xwd and .x11.