From lake@cwjcc.INS.CWRU.Edu (Dr. Robin Lake)
Newsgroups: comp.graphics.avs
Subject: Re: Viewing Topography Data
Message-ID: <1992Aug1.191931.24373@usenet.ins.cwru.edu>
Date: 1 Aug 92 19:19:31 GMT
References: <1992Jul30.213040.1082@netnews.whoi.edu>
Sender: news@usenet.ins.cwru.edu
Reply-To: lake@po.CWRU.Edu
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 40
Nntp-Posting-Host: cwjcc.ins.cwru.edu

In article <1992Jul30.213040.1082@netnews.whoi.edu> rsignell@crusty.er.usgs.gov (Richard P. Signell) writes:
>I have lots of topography data that is convenient to read in as a 2D
>rectilinear field, where the data variable is elevation, and the
>coordinate variables are latitude and longitude.
>
>To render this data usefully with field-to-mesh, it seems I need to convert  
>this to a 3D irregular field, where the data variable elevation is
>combined with the latitude and longitude to give each elevation point
>a 3rd coordinate.
>
>I checked the AVS center, but didn't see anything obvious that would 
>do the trick.  Did I miss something there, or does anyone have a unsubmitted
>module that would work?
>
>Thanks,
>--
>Rich Signell               |  rsignell@crusty.er.usgs.gov
>U.S. Geological Survey     |  (508) 457-2229  |  FAX (508) 457-2310
>Quissett Campus            |  "George promised to be good... 
>Woods Hole, MA  02543      |  ... but it is easy for little monkeys to forget."


As mentioned previously in this newsgroup, we used the undocumented 'sphere'
capability to visualize topographic data.  This was in AVS 3.0, left over from
an earlier AVS release.  We had to append 3 or 4 integers to each line of data
to represent sphere color and perhaps sphere size.  I'm not in the lab, so
I can't check this out right now.

Someone suggested another way to do this, but we've just installed AVS 4.0
and time doesn't yet permit looking at alternatives.  The MAIN problem we had
was that the data set we were provided did not completely fill a rectalinear
area, so some of the conversion and filter routines would not work.  I am
committed to solving this problem, rendering a surface of this topo data with
an aerial photo before the end of the year.  Will be happy to share what we
learn along the way!

Rob Lake
BP Research
lake@rcwcl1.dnet.bp.com


From davidb@doppler.ncsc.org (David Bennett)
Subject: AVS/Khoros
Message-ID: <BsE2wz.AqI@doppler.ncsc.org>
Sender: news@doppler.ncsc.org
Nntp-Posting-Host: doppler
Organization: North Carolina Supercomputing Center
Date: Mon, 3 Aug 1992 03:55:47 GMT

I wanted to let the AVS user community know that the
International AVS Center announced at SIGGRAPH '92 our
intention to join as a khoros affiliate and port their
modules to the AVS public domain site.  There are over
200 imaging modules and khoros has done an excellent job
with all areas.  Image processing, signal processing, GIS,
remote sensing and much more.  It is our intention to
have at least 75% percent of these available on the site
by October 1st of this year.  This is a weak area for our 
users and taking this step should help us all.  We will be
posting information about khoros as things progress.

If any of you have suggestions for other public domain packages
or tools that you would like to see ported to the International
AVS Center public domain site, please send me email.

Also, I would like to encourage you to take the time to
document your modules and submit them to the site.  As for those
with proprietary modules through your companies, please make
an additional effort to convince your companies that it is the
data that is usually of most importance and perhaps some of 
your modules could be submitted to help others.

As a SIGGRAPH '92 update, we are very pleased with the results of
the first IAC exhibit.  The Vision Dome booth had lines for
the entire conference, never had an empty seat and had rave reviews.
Our purpose was both to gain exposure and promote scientific 
visualization.  I think we accomplished both and learned a lot in
the process.

We are considering a smaller exhibit at Supercomputing '92 and
Technology 2002 this year.  If anyone is interested in joining
us we will use the same criteria.  Cost sharing for profit organizations
involved and module donations for non-profit and university
organizations.  I do not expect either of these to cost as much
as SIGGRAPH, although I am being asked to do something equally as
big for Technology 2002 and am considering.  Those at SIGGRAPH have
a better understanding of what I mean by doing a big exhibit.  Those
interested in joining if we decide to pursue this further, please send
email to be at avs@ncsc.org or call me, David Bennett, at 919-248-1182
for further discussion and information (FAX is 919 248 1101).

David Bennett
IAC Director


From i6040504@rz1strm1.rz.tu-bs.de (Holthoff)
Newsgroups: comp.graphics.avs
Subject: UCDnode_get_information
Message-ID: <1992Aug3.144715.19627@ibr.cs.tu-bs.de>
Date: 3 Aug 92 14:47:15 GMT
Sender: postnntp@ibr.cs.tu-bs.de (nntp inews entry)
Organization: Univ. Braunschweig
Lines: 6

Using the UCD structure routine UCDnode_get_information I always get 
the output zero for the parameter 'number of cells'. This value is
set in the routine read_ucd of the example directory. Is this a bug?


holger holthoff 


From dgs@draco.larc.nasa.gov (Dave G Shively)
Subject: hidden lines
Message-ID: <BsEy1w.9tJ@news.larc.nasa.gov>
Originator: dgs@draco.larc.nasa.gov
Sender: news@news.larc.nasa.gov (USENET Network News)
Organization: NASA Langley Research Center, Hampton, VA  USA
Date: Mon, 3 Aug 1992 15:08:19 GMT
Lines: 13


I an viewing some field data with the field-to-mesh module and the 
geometry viewer.  I would like to view it using the "lines" mode in the
geometry viewer menu but I can't seem to figure out how to get rid of
line segments which are behind other parts of the surface.  I guess 
this would be called "hidden line removal".

Does anyone have any suggestions???
Thanks,

Dave Shively
dgs@draco.larc.nasa.gov



From larryg@avs.com (Larry Gelberg)
Newsgroups: comp.graphics.avs
Subject: Trying to find Mike...
Message-ID: <1992Aug3.175933.4856@ctr.columbia.edu>
Date: 3 Aug 1992 17:59:33 GMT
Sender: news@ctr.columbia.edu (The Daily Lose)
Organization: Advanced Visual Systems Inc.
Lines: 13
X-Newsreader: Tin 1.1 PL4
X-Posted-From: phobos.avs.com
X-Posted-Through: sol.ctr.columbia.edu

This message is for 'Mike (French?)' who sent me a question regarding 
UCD and colormaps from FORTRAN:  Mike, your return address on the 
email got messed up and I cannot mail back directly to you.  
Please send me another message and I will try to respond.  

To the rest of you, I'm sorry for the wasted bandwidth.
larryg

--
=== Larry Gelberg ============================ larryg@avs.com =======
      Advanced Visual Systems Inc. (AVS Inc.)
      300 Fifth Ave, Waltham, MA 02154
===== Tel: 617-890-4300 = Fax: 617-890-8287 =========================


From larryg@avs.com (Larry Gelberg)
Subject: Re: hidden lines
Organization: Advanced Visual Systems Inc.
References: <BsEy1w.9tJ@news.larc.nasa.gov>
Message-ID: <1992Aug3.182059.5309@ctr.columbia.edu>
Sender: news@ctr.columbia.edu (The Daily Lose)
X-Newsreader: Tin 1.1 PL4
Date: Mon, 3 Aug 1992 18:20:59 GMT
X-Posted-From: phobos.avs.com
X-Posted-Through: sol.ctr.columbia.edu

dgs@draco.larc.nasa.gov (Dave G Shively) writes:
: 
: I an viewing some field data with the field-to-mesh module and the 
: geometry viewer.  I would like to view it using the "lines" mode in the
: geometry viewer menu but I can't seem to figure out how to get rid of
: line segments which are behind other parts of the surface.  I guess 
: this would be called "hidden line removal".
: 
: Does anyone have any suggestions???
: Thanks,
: 
: Dave Shively
: dgs@draco.larc.nasa.gov
: 

Here's a real hack:  turn on "Outline Gouraud" mode (you need to be 
in the software renderer for this to work) and set the object color
to be the same as the background.  This will create an image with 
"hidden lines" the expensive way. 

On a distantly related note, I was introduced to Henri Gouraud at
SIGGRAPH last week and when asked "Do you know Henri Gouraud?", I was
so overwhelmed by being in the presence of greatness that all I 
could figure out to say was "No, but I've used your interpolation
method!"  

I don't think he was impressed.

--
=== Larry Gelberg ============================ larryg@avs.com =======
      Advanced Visual Systems Inc. (AVS Inc.)
      300 Fifth Ave, Waltham, MA 02154
===== Tel: 617-890-4300 = Fax: 617-890-8287 =========================


From yeidel@tomar.accs.wsu.edu (Joshua Yeidel)
Subject: Re: FAQ and FTP query
Message-ID: <1992Aug3.183433.24154@serval.net.wsu.edu>
Keywords: FAQ FTP
Lines: 28
Sender: news@serval.net.wsu.edu (USENET News System)
Reply-To: yeidel@tomar.accs.wsu.edu (Joshua Yeidel)
Organization: Academic Computing Services, Washington State University
References:  <BsA2KK.CFq@world.std.com>
Date: Mon, 3 Aug 92 18:34:33 GMT


In article <BsA2KK.CFq@world.std.com>, spenderg@world.std.com (Stephen L Pendergast) writes:
|>From: spenderg@world.std.com (Stephen L Pendergast)
|>Subject: FAQ and FTP query
|>Organization: Hughes Aircraft Co GSG
|>Lines: 18
|>
|>I am just in the process of investigating AVS for its potential application
|>to our programs. Can some kind person please direct me to (or send) a FAQ
|>for this group. Is there an ftp archive.
|>
|>Thanks
|>Steve
|>------------------------------------------------------------------------
|>Stephen L Pendergast, Senior Scientist/Engineer, Hughes Aircraft Company 
|>Ground Systems Group, PO Box 3310 Bldg 604/MS B152, Fullerton, CA 92634
|>Voice: (714)732-2579  Personal - No Company/Official Responsibility
|>Email: penderga@hac2arpa.hac.com           Fax: (714)732-0242
|>------------------------------------------------------------------------

FTP site is avs.ncsc.org (128.109.178.23)

--
Joshua Yeidel               | yeidel@tomar.accs.wsu.edu
Academic Computing Services | All standard disclaimers apply
Washington State University |   "Believe it if you need it, 
Pullman, WA 99164-1226      |     or leave it if you dare..."
509/335-0441                |         -- Robert Hunter


From thorpe@doppler.ncsc.org (Steve Thorpe)
Subject: International AVS Center
Message-ID: <BsFv3o.B5u@doppler.ncsc.org>
Organization: North Carolina Supercomputing Center
Date: Tue, 4 Aug 1992 03:02:11 GMT

Hi Folks,

For those of you who are newcomers to comp.graphics.avs, I'm
enclosing a copy of AVS_README.  This file is available at the
International AVS Center's anonymous ftp site (avs.ncsc.org).
It tells about the IAC and the services it offers to the AVS
user community.

Enjoy!

-Steve
----------------------------------------------------------------
   Steve Thorpe, Application Visualization System Specialist
International AVS Center, North Carolina Supercomputing Center
PO Box 12889   3021 Cornwallis Rd, RTP, NC 27709   avs@ncsc.org
----------------------------------------------------------------

		Welcome to the International AVS Center


YOU MUST DOWNLOAD AND READ THE AVS_LICENSE FILE BEFORE MAKING USE OF THIS
ANONYMOUS FTP SITE OR ANY OF THE INTERNATIONAL AVS CENTER EMAIL FACILITIES!

****************************************************************************

	  INTERNATIONAL AVS CENTER OPENED OCTOBER 1, 1991 AT NCSC

    
    The AVS Consortium announced the opening of the new International
AVS Center at North Carolina Supercomputing Center in Research Triangle
Park, North Carolina.  The AVS Consortium is made up of seven AVS vendors
who are funding and providing direction for the International AVS Center.
The seven vendors are Advanced Visual Systems Inc., CONVEX Computer 
Corporation, Digital Equipment Corporation, IBM, Hewlett Packard Company, 
Sun Microsystems, and Wavetracer, Inc.  

    Non-consortium vendors who have AVS ported to their platforms are 
Cray, Evans and Sutherland, Kubota Pacific Computer Inc., Set Technology 
Corporation, and SGI.  Many of these are still in beta and will be made 
available in the future.

    The full functionality of the International AVS Center was not
available until January 1, 1992.  The Center was opened in several phases.
Phase I, which opened first, provides for ftp and email access to modules and
is primarily for submission of modules from the AVS Users.  There are several
hundred modules currently available and more will be added daily.  There
is construction for the porting facilities currently underway.  Initially
modules are available for CONVEX, Digital Equipment Corporation, IBM, Sun
Microsystems, and the Stardent Titan P3G3 (through 12/31/91).  As the 
hardware goes online, more ports are becoming available.  Rather than 
delay AVS User access to sharable code until porting was completed, it was 
decided to let them have access to what was available and let them do their 
own porting as needed until porting was completed on all platforms.

****************************************************************************

	        	     QUESTIONS AND ANSWERS

    If you ever have any questions,  please forward them to avs@ncsc.org.
The staff of the International AVS Center is here to support the AVS user
community as best we can.  

****************************************************************************

                              INTERNET NEWS GROUP

    AVS users should also be aware of the Internet news group 
comp.graphics.avs .  This news group provides a forum for general 
collaboration on all AVS topics between the entire AVS user community.

****************************************************************************

                                 AVS MAGAZINE

    The International AVS Center is publishing a quarterly magazine titled "AVS
Network News." This magazine discusses AVS related issues, has user articles, 
general information, etc.  These can be ordered from your AVS Vendor or by 
sending a check or money order to the Internation AVS Center.  The check should
be in the amount of $12.00 for an annual subscription, or $3.00 for a single 
issue.  Please add $0.75 per issue if outside of Continental USA.

        The International AVS Center
        PO Box 12889
        3021 Cornwallis Road
        RTP, NC 27709

****************************************************************************

                         INTERNATIONAL AVS USERS GROUP

     You can join the International AVS Users Group for a yearly fee of
$30.00 which includes subscription to the AVS magazine, the yearly AVS catalog
of modules ( user donated and commercial), a $50.00 reduction on attending the
yearly International AVS Users Group conference and have special rates for
additional services as they become available.  To join, send check or money
order for $30.00 ( add $5.00 if out of continental USA) to:

        The International AVS Center
        PO Box 12889
        3021 Cornwallis Road
        RTP, NC 27709

     The interim President of the AVS Users Group is Stephen Franklin
from the University of California at Irvine.  Stephen will be posting
notes to the AVS newsgroup comp.graphics.avs as well as provide guidance to
organizing local groups.  More information is forthcoming.

     There will be an additional fee for local user group memberships.

****************************************************************************

                   INTERNATIONAL AVS USERS GROUP CONFERENCE

    The 1st Annual International AVS Users Group Conference was held
February 11-13,1992 at the site of the International AVS Center : 
the North Carolina Supercomputing Center, Research Triangle Park, 
North Carolina.  The conference was titled : AVS '92 and is sponsored by the
AVS Consortium : AVS Incorporated, CONVEX Computer Corporation, Digital 
Equipment Corporation, Hewlett Packard Company, IBM, North Carolina 
Supercomputing Center, SET Technology, and Wavetracer, Inc.

Conference Overview :
	
        First International Users Group Conference
	          February 11 - 13, 1992

	Summary of events:

Keynote address:
	Attentive and Preattentive Processing in Visualization
	Richard Mark Friedhoff, Author of "Visualization:  The
	Second Computer Revolution"

Lectures:
	#1 - Fundamentals of Scientific Visualization by Jim
	Thomas, SIGGRAPH Chair, Battelle Pacific Labs

	#2 - Directions AVS Might Take:  A User Perspective by
	Richard Feldmann, NIH, Division of Computer Research
	and Technology.

	#3 - Tips and Tricks with AVS and Areas that are not
	documented by Larry Gelberg, AVS Inc.

	#4 - The AVS Module Generator by Larry Gelberg, AVS Inc.

	#5 - Future Plans for AVS and the International AVS
	Center by Ray Idaszek, NCSC and Dave Kamins, AVS Inc.

	#6 - Wide Area Information Servers: A Supercomputer on
	Every Desk by Brewster Kahle, Thinking Machines.

	#7 - The AVS Data Viewer by Larry Gelberg, AVS, Inc.

	#8 - The GenTools Distributed Computational-Genetics
	Program Suite by Jesse Driver, University of Texas,
	CHPC, Balcones Research Center.

	#9 - Full Motion Video over ETHERNET in an AVS Environment
	by Dan Winkelstein, MCNC Communications Division.

	#10 - The AVS Animation Application in AVS 3.5 by Ham
	Lord, AVS Inc.

	#11 - Distributed Visualization by Rick Franklin and Wade
	Smith, CONVEX Computer Corporation.

	#12 - Video Production in AVS by John Sheehan, AVS Inc.

	#13 - Overview of Implementing AVS on a Massively
	Parallel Machine by Edward Zyszkowski, Wavetracer Inc.

	#14 - The AVS Geometry Viewer Using AVS 3.5 by Jeff 
	Vroom, AVS Inc.

	#15 - VBASE:  Vector Database in AVS by Dennis Colomb.

	#16 - Chaotic System Tools in AVS by Mike Neacsu, NCSC.

	#17 - The Visualization Revolution by Wes Bethal, 
	Lawrence Berkeley Laboratory.

	#18 - Network Synamation:  An Integrated Environment for
	Distributed Computing by Meng H. Lean, Xerox Corporation,
	Webster Research Center.

Tutorials:

	#1 - Getting Started with AVS and Creating Networks

	#2 - Getting Started with the Geometry Viewer (AVS3.5)

	#3 - The Data Viewer

	#4 - The AVS Animation Application

	#5 - How to Write a Module in C using the Module Generator

Workshops:

	#1 - Chemistry using AVS by Richard Hedges, Polygen/MSI
	and Dave Kamins, AVS Inc.

	#2 - Visualizing Crystals with AVS by Don R. Jones, Erin
	N. Thornton, and Anthony Ness, Battelle Pacific Labs.

	#3 - Animation in AVS by Brian Kaplan, Indiana University
	and Ham Lord, AVS Inc.

	#4 - Imaging and GIS in AVS, Dennis Colomb.

	#5 - Crystal Viewer with AVS by Steve Bong, Crystal Imaging.

	#6 - Maple V Supporting AVS by Benton Leong, Waterloo Maple.

Panels:

	#1 - AVS as an Educational and Instructional Tool by Stephen
	Franklin, University of California, Irvine.

	#2 - AVS Developers and Porters Panel, led by David Bennett,
	International AVS Center and NCSC.

	#3 - Applications Panel led by Dennis Colomb.

	#4 - Virtual Reality by John Sheehan, AVS Inc.

	#5 - Distributed Computing Group led by Ray Idaszak, NCSC.

Videotapes:

	Videotapes of many of the presentations at AVS `92 will be
available from the International AVS Center after the final editing 
is completed.

****************************************************************************

                             GETTING MODULES

    There are currently two ways to obtain modules:

    	1.	Using standard ftp protocol.
	2.	Using the AVSemail request system

****************************************************************************

                              ANONYMOUS FTP

     The International AVS Center anonymous ftp site is located on the Internet 
at 128.109.178.23 .  If a name server is running, the server can be located 
as avs.ncsc.org .  When connected to the avs server, login as anonymous and 
provide your email address as the password.


WHAT YOU WILL FIND WHEN YOU LOG IN TO THE AVS SITE:

     When you login you will get a banner message that will provide some
basic information.  If you type ls -CF, you will then see the following:

.login                  COMP.GRAPHICS.AVS/      WHAT_IS_AVS
AVS                     DATA/                   WHAT_IS_WAIS
AVS_CATALOG             FAQ                     bin/
AVS_CATALOG.dvi         FILTERS/                dev/
AVS_CATALOG.ps          MAPPERS/                etc/
AVS_FLATLINE            RENDERERS/              pub/
AVS_LICENSE             SAMPLE_DATA/            usr/
AVS_README              SUBMIT/
AVS_USER_REG            SUBMIT_RELEASE


     THE INTERNATIONAL AVS CENTER GIVES NO WARRANTY, EXPRESSED OR
IMPLIED, FOR ANY SOFTWARE AND/OR DOCUMENTATION PROVIDED, INCLUDING,
WITHOUT LIMITATION, WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE.

     AVS is an Archie place holder.

     The AVS_CATALOG provides a complete listing of current module holdings 
at the International AVS Center.  Its general format is as follows:


Name        : animate_file    Version      : 1.000     Mod Number : 1135
Author      : Terry Myerson, International AVS Center (NCSC)
Submitted   : 02/24/92        Last Updated : 02/24/92  Language   : C
Ported to   : DEC Kubota IBM Sun Convex
Description : anim_fname is used to output a series of filenames for input
              into a reader module. The module inputs an integer and a
              filename base, and output a filename in the form "$base.%3d".
              This module is very useful for a series of files containing a
              time series of data.

     AVS_CATALOG, AVS_CATALOG.dvi, and AVS_CATALOG.ps are three versions
of the module catalog maintained at this site.  All three files are 
continuously updated as new modules are added to the ftp site.  The ASCII 
version of the module catalog (AVS_CATALOG) can be retrieved at any time 
by mailing any message to an automatic response script at avsemail@ncsc.org
The AVS_CATALOG.ps and AVS_CATALOG files should be printable on any standard
postscript printing device.  The AVS_CATALOG.dvi file requires a dvi2ps 
utility to be of any use, but provides a much more portable compact format 
for the postscript catalog for those who have this utility available.
NOTE: The AWAIS module, available in the DATA directory on the ftp site,
provides interactive browsing of the module catalog.

     AVS_FLATLINE provides the same information in a format suitable for
some database programs.  The general format for the AVS_FLATLINE file is 
as follows:

animate_file:data_input:anim_fname is used to output a series of filenames for 
input into a reader module. The module inputs an integer and a filename base, 
and output a filename in the form "$base.%3d". This module is very useful for 
a series of files containing a time series of data.:Terry Myerson:International
AVS Center (NCSC):16:C:02/24/92: Kubota Convex DEC IBM Sun:02/24/92:1:1135

     The AVS_LICENSE is a file that provides the conditions under which
modules may be obtained and your agreements to share code with others.  You
must agree to the terms in order to use the International AVS Center repository
and all that it contains.  Its purpose is to ensure the sharing of everything
that has been donated and prohibit misuse of code that has been so generously
donated by others.  If you need a "special" arrangement, you must have a
release in writing from the International AVS Center.  We will contact the
donors and obtain their approval for special cases.  

     You are reading the AVS_README file.

     AVS_USER_REG is a form that can be filled in and sent electronically to
the International AVS Center for registration to various mailing lists,
including AVS User Groups, AVS Special Interest Groups, and a list that
automatically sends you all postings to the comp.graphics.avs newsgroup.
AVS_USER_REG contains detailed instructions on the lists available and where
to send it.

     If you know of anyone, whom does not have news access, they can
download the files in the COMP.GRAPHICS.AVS directory.  These files
are in the standard mailbox format so that anybody can peruse these
files using any mail utility with the -f command.

For example :

  Mail -f May_92

If a "message" in this mailbox is replied to, then a message is sent back
to the poster of the article - but it is not replied to the newsgroup.
The files will be stored in a separate mailbox for each month : May_92 June_92

     The SAMPLE_DATA directory is for data that has no associated
modules.  Many individuals have requested new or interesting sample data
and are also donating it.  It does not fit with the standard module
directories and so has its own directory.

     The FAQ, or Frequently Asked Questions file answers common 
questions about the International AVS Center and AVS in general.

     There are four main directories of modules: DATA, FILTERS, MAPPERS 
and RENDERERS.  These directories correspond to the four columns of modules 
within AVS.

     The SUBMIT directory is for module submissions.  This directory has
write permission and will be explained below in the submission section.
	
     The SUBMIT_RELEASE form is explained in more detail in the submission
section below.  Basically, we want you to agree to certain terms before 
making your submissions available to the public.  

     WHAT_IS_AVS is a several page overview of the AVS system.  
 
     WHAT_IS_WAIS is a several page overview of the Wide Area Information
Server system, and how you might want to use it to peruse through our
anonymous ftp site.

     Your first step, after reading this AVS_README file is to download
the AVS_LICENSE file and read it.  If you have any problem abiding by the
AVS Licensing Agreement, please send email to avs@ncsc.org or US mail to the
International AVS Center, po Box 12889, 3021 Cornwallis road, RTP, NC 27709.
We will try to deal with special circumstances as they arise on a one on one
basis.

USING STANDARD FTP PROTOCOL:

     There are only a few basic commands you will need to move around 
in the AVS directories and download or submit files.  Additional information
is available in your local man pages on ftp.  The first step is to "cd" to
the directory you are interested in such as "cd DATA".  You will receive a
message on how to proceed.  You should then "cd" to the module directory you
want such as "cd abekas".  You should change your settings as follows:  type 
"bin" at the prompt to change to binary mode; type "hash" at the prompt, this 
gives a # sign on your home device that shows you that things are working; type
"prompt" to get multiple files at one time.  There are only a few other 
commands that are general. You should know get and mget.  Typing "get filename" 
at the prompt will download any one file.  Typing "mget filenames" (or with 
wildcards *,?,etc) will get you several files at one time.  If you did not type 
the prompt command you will be asked yes/no for each file.  If you did type 
prompt you will not be prompted, ftp will just continue to download all files 
requested.  The reverse procedure is true when you want to submit modules using 
the put and mput commands ( more on submission later).  
                                            
     In this directory, you will find all of the files for a module.
These include the source code, scripts, networks, helpfiles, and makefiles. 
The Makefiles are named make.platform ( i.e. make.Convex, make.DEC )

     There is another ftp option available for getting a module that
you may find easier.  Suppose you want the module read_tiff, which is
located in the subdirectory DATA/read_tiff.  If you do the following
sequence of steps, you will wind up with a tar file containing all of
read_tiff's files in it:

	ftp avs.ncsc.org
	use anonymous for the userid
	use your userid for the password
	cd DATA
	binary
	get read_tiff.tar
	bye

Then on your local machine, use "tar -xvf read_tiff.tar" to restore
the files from the archive.  This method may take a while due to
the potentially large size of the tar file.  If you use
"get read_tiff.tar.Z" instead, you will get a compressed version of
the tar file, which should come over significantly faster due to
the smaller size.  Then on your local machine, use 
"uncompress read_tiff.tar.Z", followed by "tar -xvf read_tiff.tar"
to restore the files.

****************************************************************************

                               EMAIL FACILITIES

    It was determined that there were many users who did not have ftp
protocol on their system.  For those individuals an email procedure has
been set up.  There are three email addresses associated with the International
AVS Center.  These are avs@ncsc.org for questions/module submission, 
avsemail@ncsc.org for an automated information request, and avsorder@ncsc.org 
for automated module requests.  avsorder and avsemail are both explained below.
                   
   Mailing to avsemail@ncsc.org will automatically retrieve a response which 
includes this AVS_README file and also a current module catalog.

   Mailing to avsorder@ncsc.org will automatically retrieve module source codes.
Since some mail handlers have restrictions on the maximum size of 
a mail message, the modules that are requested will arrive in several
messages - one message per file per module.  Some modules that could be 
requested may also not be deliverable by email because of the size of 
individual files in that module.  These cases will be noted in the return 
email you receive.  Phase II will offer you option of receiving these files 
or any others via tape.  Construction is currently underway of porting 
facilities and as soon as hardware is installed, we will update this notice 
and provide instructions on how to request modules, data, etc. via tape.

    Note that you will need to remove the mail header lines after saving the 
files from within your mail system.  The title for each of a module
file's mail message will be of the form <module name>/<file name>, in
order to facilitate easier saving of these files.

HOW TO ORDER:

1.      First, review the modules available in the AVS_CATALOG

2.      Decide which modules you want.  Add a pound sign (#)
	to the beginning of each module number and make sure it is
	on a separate line of its own for each module ordered.

3.      Submit the order form.  The #module_number and name ( the # 
	is necessary in front of each module ordered with no spaces, 
	as #1037 ).

4.	When your order is filled out send it to "avsorder@ncsc.org",
	it will be processed immediately.  DO NOT send orders to 
	avsemail@ncsc.org or avs@ncsc.org.


        SAMPLE ORDER FORM:

*******************************************************************************
        I would like to order the following modules:

#1005 ( these lines are the module numbers)
#1023 ( NOTE that each entry must be on a separate line, this is required)
#1029 
#1130
..............You may order as many modules as you like as long as each is
..............on a separate line.


Thanks
John Doe
Smurfville, USA  (Full name and address is not required, just requested)

*******************************************************************************

        WHAT THIS ORDER FORM DID FOR YOU:
        
The #numbers order modules 1005, 1023 1129 and 1130 from the module list.
Each number told the automatic ordering service what you wanted in addition 
to the module source code.  Everything is automatic.  If you did not receive 
what you ordered, send email to avs@ncsc.org and we will correct the problem 
quickly. 

*******************************************************************************

BATCH TAPE REQUESTS:

	There is a $5.00 dollar shipping and handling fee for tapes ( $10.00
for shipping out of country and no insurance).  If you send your own tape
this is the only cost incurred.  If you wish us to use one of our tapes we
will charge you cost plus 15% for our ordering, stocking, etc costs.  This 
is still less than retail and is designed only as a cost recovery.  We are
not responsible for items damaged in transit.  Exact costs for tapes and 
handling will be determined when hardware is delivered and set up.  We will
post information as soon as it becomes available

*******************************************************************************

HOW TO SUBMIT MODULES:

	Donating a module to the International AVS Center benefits 
the entire AVS user community by facilitating further use of AVS to 
visualize complex scientific phenomena.  Any module that is not 
donated may be rewritten elsewhere - wasting someone's 
valuble time - hindering further development of other module 
capabilities for everyone's benefit.  

	There are three ways to submit modules:

	1.	Standard ftp protocol
	2.	email ( no binaries)
	3.	Sending tapes to:	The International AVS Center
					P.O. Box 12889              
					3021 Cornwallis Road
					RTP, NC 27709  
	
	There is a SUBMIT_RELEASE file that can be found when you login. 
It has the terms you agree to by submitting a module to the International 
AVS Center.  It tells us that we have permission to share these modules 
and associated files with others and that there are no known viruses in 
the code.  This will ensure that the there are no other claims from 
universities, individuals, companies, etc.  If you cannot meet these 
conditions because of special circumstances ( e.g. government lab, etc.,
please email to avs@ncsc.org and we will make special arrangements on an      
individual basis).  
                                                                           
	Several individuals have said they would contribute, but from 
past experience they knew they would be bombarded with questions about the 
code and did not have the time to spend replying to these questions.  If 
you are in this situation, we will put a unique control number in the code 
and the International AVS Center will act as the only contact between you 
and the world.  Many of the questions will be fielded by the AVS staff, 
but if a question cannot be answered internally, you will only be contacted 
by the center and not hundreds of individuals.    
                                                                             

*******************************************************************************

STANDARD FTP SUBMISSION:


	 If you have arrived at this point it is assumed that you know the
ftp site name (avs.ncsc.org).  The IPnumber will be changing shortly as
we move to a larger server, so be prepared for this number to change in the
near future.  We will post it later.

        When you login you will get a banner message that will provide some
basic information.  You will then see the following:

.login                  COMP.GRAPHICS.AVS/      WHAT_IS_AVS
AVS                     DATA/                   WHAT_IS_WAIS
AVS_CATALOG             FAQ                     bin/
AVS_CATALOG.dvi         FILTERS/                dev/
AVS_CATALOG.ps          MAPPERS/                etc/
AVS_FLATLINE            RENDERERS/              pub/
AVS_LICENSE             SAMPLE_DATA/            usr/
AVS_README              SUBMIT/
AVS_USER_REG            SUBMIT_RELEASE


	Most of the files and directories have been explained above, except
the SUBMIT directory.  The SUBMIT directory is the only one that has write
permission.  In order to provide a minimum level of security to those who
donate modules, and try to make sure others do not accidentally copy over their
files, and to streamline the process of adding your module to the catalog,
we ask you to follow the following procedures.

	Please prepare your submission to conform to the following guidelines
as closely as you can:
	1.	all C source code should have a .c suffix
	2.	all FORTRAN source code should have a .f suffix
	3.	all C header files should have a .h suffix
	4.	all FORTRAN header files should have a .inc suffix
	5.	provide one file with a .txt suffix for each AVS
		module, in plain text format, which provides complete
		documentation for the module
	6.	provide a sample AVS network file, with a .net suffix
	7.	do not include assembly language code

	When you "cd" to the SUBMIT" directory, a banner message will appear
that will prompt you with instructions.  You will be asked to create a
directory using mkdir as in "mkdir myname".  This directory will be  invisible 
and entry into this directory can only be achieved by typing "cd myname".
When someone else logs in, they will see nothing, unless they know the name and
unique number identifier.  After you "cd" to your new directory you will be able
to donate modules using standard ftp protocol.  Detailed information is 
available in the ftp man pages, but you will only need to know a few basic
commands such as bin, hash, prompt, put and mput. to donate your modules.

	You should create additional directories for each module using "mkdir".
If you are submitting multiple modules, please use "mkdir mynameN", where
N would be a unique number for each module being submitted.
You should type "bin" at the command line to change to binary format, then
type "hash" at the command line to show a # sign on your local machine that 
tells you things are working.  You should then type prompt if you have 
more than one file as this lets you download multiple files at one time
using mput without waiting for the prompt yes/no command.  Then type the
command "put myfile" or "mput myfiles" at the command line and they will
download to the new directory you have created.  We prefer and recommend
that all files submitted are only straight ASCII files, although if your 
files are in tar or tar.Z format, we will accept them.

	If you logout and wish to make a change, you must remember the 
unique name for the invisible directory you were given or else start all
over again.


*******************************************************************************

EMAIL SUBMISSION:

	We will accept email submissions to avs@ncsc.org, but ask you follow
these guidelines.

	Do not include any binaries.  If data files are large, put in uucp
format or provide a smaller data file with a note that larger files are 
available.  We will contact you to try to arrange obtaining these larger
files through other methods.  Please do not send data files over 200K.
Separate all files by a line of at least twenty (20) asterisk marks (*) so 
we can search for these easily.  

	Your first lines should describe the module, the platform it has
been ported to and special notes such as large data size, followed by *'s.


*******************************************************************************


BATCH TAPE SUBMISSION:

	To submit a module via tape, put it onto a tape
using "tar -cvf tapedrive filename[s]".  Label the tape with the
appropriate platform the module runs on (and the platform the tape
was made on, if different), and mail it to us at:

        The International AVS Center
        PO Box 12889
        3021 Cornwallis Road
        RTP, NC 27709

*******************************************************************************


A COPY OF THE FREQUENTLY ASKED QUESTIONS (FAQ) FILE:


       ___________________________________________________________________
                                       FAQ
                        Frequently Asked Questions of the
                            International AVS Center
                      North Carolina Supercomputing Center
       ___________________________________________________________________

	Questions answered in this file :
	---------------------------------

1.	 What is the International AVS Center ?
2.	 Where is the International AVS Center ?
3.	 What is AVS ?
4.	 Where can I get more information on AVS ?
5.	 What are the system requirements to run AVS ?
6.	 How do I download modules from the International AVS Center,
	 or submit modules, or get a list of the currently available
	 modules ?
7.	 When I try to run AVS on a remote machine and display the output
	 on an X server, I get a message saying Client unauthorized to
	 connect to server. How do I fix this ?
8.	 Is there sample AVS data available ?
9.	 When I try to ftp to avs.ncsc.org, I get terminated before I get
	 connected. What am I doing wrong ?
10.	 What is the procedure to add a question to this FAQ file ?
11.	 Why should I submit a module to the International AVS Center ?
12.	 Where can I find more information on AVS in published
	 literature ?
13.	 What is WAIS and how can I use it at the International AVS Center ?

What is the International AVS Center:what_is_iac:
 ___________________________________________________________________ 

1.	 What is the International AVS Center ?

        The International AVS Center serves as a catalyst
for expanding the AVS user base and for increasing AVS
functionality by fostering discipline-specific module
development and new AVS uses.  Located at the North Carolina
Supercomputing Center, the worldwide clearinghouse collects,
ports, and distributes user-contributed, public-domain
modules and acts as liason between users and vendors.
The International AVS Center also publishes a quarterly
magazine called AVS Network News and a yearly module
catalog.  It also hosts the yearly International AVS
User Group conference and coordinates User Group activities.

        The AVS Consortium is made up of seven AVS vendors
who are funding and providing direction for the International
AVS Center.  The seven vendors are Advanced Visual Systems Inc.,
CONVEX Computer Corporation, Digital Equipment Corporation,
IBM, Hewlett Packard Company, Sun Microsystems, and Wavetracer, Inc.
Where is the International AVS Center:where_is_iac:
 ___________________________________________________________________ 

2.	 Where is the International AVS Center ?

        The International AVS Center is located at the
North Carolina Supercomputing Center.  The anonymous ftp
site for the center is located on the internet at avs.ncscs.org
with an IP address of 128.109.178.23 .  The main email alias
for the center is avs@ncsc.org .
What is AVS:what_is_avs:
 ___________________________________________________________________ 

3.	 What is AVS ?

        Using anonymous ftp to avs.ncsc.org, you can then
get the file What_is_AVS.  Take a look at this file
for a good summary of what AVS does.
Where can I get more information on AVS:where_info_avsinc:
 ___________________________________________________________________ 

4.	 Where can I get more information on AVS ?

        If this file and other files available via anonymous
ftp to avs.ncsc.org do not answer your questions, you can
send mail to avs@ncsc.org.  The International AVS Center
will do its best to help you out.  You also may want to
monitor and/or post articles to the Internet newsgroup
comp.graphics.avs, which has an ongoing dialog between
various AVS users.  Or you can contact AVS Inc. directly at:

        Advanced Visual Systems Inc.
        300 Fifth Ave.
        Waltham, MA  02154
        USA

        Tel: 617-890-4300
        Fax: 617-890-8287
What are the system requirements to run AVS:sys_req:
 ___________________________________________________________________ 

5.	 What are the system requirements to run AVS ?

Numerous people have requested AVS configuration information.
This information changes regularly and you should contact either
AVS Inc at 617-890-4300, your local vendor reps or AVS Inc reps
for additional information.

CONVEX - Available now - CONVEX OSV9.1 or later release, CONVEX
OS Utilities 9.1 or later, CONVEX OS Internet Services V9.1 or
later, IEEE floating point hardware.  Requires approximately
90MB disk space, and a color display device networked to your
CONVEX system supporting X window System Version 11 Release 4
color server, which supports either a PSEUDOCOLOR or TRUECOLOR
visual type, or a Silicon Graphics workstation running IRIX 4.0
or a workstation or terminal with a PEX server.

DEC - Available now - DEC AVS V3.0 generates PEX V4.0 protocol
(when displaying to a PEX V4.0 cpable display server), and is
compatible with ULTRIX V4.2 which includes a PEX V4.0 server.
ULTRIX V4.2A includes a PEX V5.0 server.  For compatiblitiy with
that server, DEC AVS V3.0A has been released.  Note that
PEX V5.0 provides (two pass) transparency.  Also note that
the ULTRIX V4.2A distribution does include a PEX compatibility
kit which is essentially a PEX V4.0 server.  There is no support
for runing both PEX V4.0 and PEX V5.0 servers concurrently.  Only
one such server can be run at any one time.

Hewlett-Packard - Available now - HP 9000 series 700,
CRX graphics (call for information on other graphic configurations),
OS release 8.01 or later ( 'uname -r' to get OS level), Phigs runtime
will be required for systems using H/W rendering, 16 MB memory
minimum, 32 MB recommended, installation uses about 40 MB disk,
CRX will use the S/W renderer ( others will support H/W rendering
when appropriate), monochrome is not supported.

IBM - Available now - RS6000 workstations, models 3xx, 5xx or
7xx, 8-bit Color Graphics Display adapter, High Performance 3D
24-bit Color Graphics Processor with Z buffer option, GTO 3D 24-bit
Graphics adapter with Z buffer (a.k.a. Supergraphics Subsystem),
(call for information on other graphic configurations), AIX release
3.1.5 w/2006 patch tape and APAR#: a19758 (X server), use
command 'lslpp -h bos.obj' which should show release
03.01.0006.0008 as active, use command 'lsdev -C -c adapter' to see
graphics configuration, 16 MB memory minimum, 32 MB
recommended, installation uses about 40 MB disk, hardware
rendering is only on 24-bit Z buffered systems, specify SW
renderer on all systems without 24-bit Z buffering, AIX 3.1.5
X server is limited to 8-bit pseudocolor visuals, images are then dithered.

SUN - Available now - Sun SPARC workstations 1, 1+, 2 supporting
the sun4/sun4c applications architecture, 8-bit frame buffers (GX,
CG3, etc), GS and GT graphics after OpenWindows version 3 is
available from Sun ( first quarter 92), Sun OS 4.1.1 w/ 100299-01
patch or later, use command /usr/etc/showrev to get revision
levels, 8-bit frame buffers require OpenWindows version 2 with
X server installed, 16 MB minimum, 24 or 32 MB recommended,
installation uses about 38 MB disk, strongly recommend
increasing shared memory segment and swap space size per
release notes, 8-bit graphics boards ( GX, CG3, etc) always uses
S/W renderer, H/W rendering systems will use XGL graphics, S/W
render also available

Wavetracer - to provide users with logical and uniform access
to Wavetracer's three-dimensional and massively parallel Data
Transport Computer (DTC) and advanced software tools, AVS modules
are currently being ported to make use of the DTC.  The DTC
is a three dimensional, massively parallel computer.  It has
a 3D computing architecture, high data capacity and bandwidth,
high I/O bandwidth, ultra finegrained parallellism and low cost
of ownership.  It easily connects to a host UNIX workstation
via an industry-standard SCSI interface.  The processing
resources of the DTC are integrated into the host's software
and network environment by multiC, a powerful data-parallel
extension of ANSI C.
How do I download modules from the International AVS Center, or submit modules, or get a list of the currently available modules:how_download:
 ___________________________________________________________________ 

6.	 How do I download modules from the International AVS Center,
	 or submit modules, or get a list of the currently available
	 modules ?

        There is an AVS_README file which should answer
these and many other questions for you.  To obtain a
copy of this file, there are two methods currently
available and a third method under development.  Mail
sent to avsemail@ncsc.org will automatically retrieve
a response which includes the AVS_README file and
also a current module catalog.  Or you can ftp to
avs.ncsc.org, login with anonymous as your userid and
your own userid as the password, and get the AVS_README
file and the AVS_CATALOG file from there.  For those users
without ftp capability, there is a tape ordering system
being developed at the International AVS Center.
When I try to run AVS on a remote machine and display the output on an X server, I get a message saying Client unauthorized to connect to server.  How do I fix this:x_help:
 ___________________________________________________________________ 

7.	 When I try to run AVS on a remote machine and display the output
	 on an X server, I get a message saying Client unauthorized to
	 connect to server. How do I fix this ?

        The xhost command will let your server know its
OK for your remote machine to display there.  In the
file read in when you boot up X (for example, on a Titan
.xsession, on a Sun .xinitrc), add the line:

        xhost <Client1 machine name> <Client2 machine name> ...
Is there sample AVS data available:sample_data:
 ___________________________________________________________________ 

8.	 Is there sample AVS data available ?

        Using anonymous ftp to avs.ncsc.org, you can then
cd to AVS_SAMP_DATA.  This directory is for sample data that
has been donated without any modules.  No tests have been made
on this data, so use it at your own risk.  This is simply to
allow you to get your hands on a variety of different data types
for experimentation purposes.
When I try to ftp to avs.ncsc.org, I get terminated before I get connected.  What am I doing wrong:ftp_help:
 ___________________________________________________________________ 

9.	 When I try to ftp to avs.ncsc.org, I get terminated before I get
	 connected. What am I doing wrong ?

        Possibly your host machine isn't a registered
internet site.  In such a case, the IP address can't be
mapped by our machine into a valid hostname.  Speak to the
person in charge of your network about making sure it is
correctly registered.
What is the procedure to add a question to this FAQ file:add_faq:
 ___________________________________________________________________ 

10.	 What is the procedure to add a question to this FAQ file ?

        Please submit your suggestion for this FAQ file via
email to avs@ncsc.org.  Your question and answer will quite possibly
show up in this file shortly thereafter.
Why should I submit a module to the International AVS Center:why_submit:
 ___________________________________________________________________ 

11.	 Why should I submit a module to the International AVS Center ?

        Donating a module to the International AVS Center benefits
the entire AVS user community by facilitating further use of AVS to
visualize complex scientific phenomena.  Any module that is not
donated may be rewritten elsewhere - wasting someone's
valuble time - hindering further development of other module
capabilities for everyone's benefit.
Where can I find more information on AVS in published literature:references:
 ___________________________________________________________________ 

12.	 Where can I find more information on AVS in published
	 literature ?

Here is a short (no doubt incomplete!) reference list:

Upson, Craig, Thomas Faulhaber, Jr., David Kamins, David Laidlaw,
David Schlegel, Jeffrey Vroom, Robert Gurwitz and Andries van Dam.
"The Application Visualization System:  A Computational Environment
for Scientific Visualization."  IEEE Computer Graphics and Applications
(July 1989), Vol.9, No.4, pp 30-42.

Currington, I., Coutant, M., "AVS - A Flexible Interactive Distributed
Environment for Scientific Visualisation Applications", Second
Eurographics Workshop on Visualization in Scientific Computing, April,
1991

VandeWettering, "The Application Visualization System - AVS 2.0",
PIXEL, July/August, 1990

Garrity, M., "Raytracing Irregular Volume Data", San Diego Workshop
on Volume Visualization, Dec, 1990

Gelberg, L., Kamins, D., Vroom, J., "VEX: A Volume Exploratorium",
Chapel Hill Workshop on Volume Visualization, May 1989

Gelberg, L., et al, "Visualization Techniques for Structured and
Unstructured Scientific Data", Course Notes, SIGGRAPH '90 Course
"State of the Art in Data Visualization"

Mathias, C., "Visualization Techniques Augment Research into Structure
of Adenovirus", Scientific Computing & Automation, April, 1991

Parker, D., Lin, Y., "The Application Visualization System for Finite
Element Analysis", Banff Conference on FEA, May, 1990

Upson, C., "Scientific Visualization Environments for the
Computational Sciences", Proceedings of the 34th IEEE Computer Society
International Conference - Spring, 1989

Craig Upson, "Tools for Creating Visions," UNIX REVIEW,
Vol.8, No.8, pp. 39-47.

Calvert, Brian "Interactive Analysis of Multidimensional Data", Masters Thesis
University of Illinois Department of Computer Science, 1991.
What is WAIS and how can I use it at the International AVS Center:what_is_wais
 ___________________________________________________________________ 

13.	 What is WAIS and how can I use it at the International AVS Center ?

There is now a WAIS (Wide Area Information Servers) server running
at the International AVS Center.  WAIS allows a user to ask
a question to a server, which provides a ranked list of documents
that may help answer that question.  The user can then peruse
through the documents that seem useful.  

All of the .txt files for AVS modules freely available on the 
International AVS Center's anonymous ftp site have been indexed, 
as well as informational files such as AVS_README and FAQ.  
WAIS should prove more and more useful as the AVS module repository
becomes larger.  It provides a convienient interface to large amounts
of data.

For a more thorough discussion of WAIS and how you can use it
to peruse the files at the International AVS Center, please check 
the file WHAT_IS_WAIS on avs.ncsc.org.
*******************************************************************************



From wes@maui.lbl.gov (Wes Bethel)
Subject: texture mesh is here
Message-ID: <1992Aug4.213657.5825@overload.lbl.gov>
Followup-To: comp.graphics.avs
Sender: usenet@overload.lbl.gov
Nntp-Posting-Host: maui.lbl.gov
Organization: Lawrence Berkeley Laboratory
Date: Tue, 4 Aug 92 21:36:57 GMT
Lines: 46


Hi Folks....

I have a way cool new module that I've put up at the IAC.  It's so
way cool that I thought I should say something to the net.

A few days ago, someone posted asking for a module that would produce
a mesh from a 2d rectilinear field.  This note is a follow-up to a 
previous post on that subject.

The new module, called "texture mesh", takes 2D data of any type and
creates a quad mesh.  If you have ever tried to make a height map of
a 2d rectilinear field using "field to mesh", you will like this module.

I'll try to be brief about what this module does:
	1. take a 2D field, create a quad mesh.  for uniform fields,
		the x,y coords come from the extent info, if present,
		or the size if not.  the z values come from the data.
		for 2D rectilinear fields, the x,y coords are specified
		in the field, the z- values come from the data.
		for 2D 3-space irregular fields, all of x,y,z are
		present in the field.  2D 2-space irregular fields are
		treated exactly like rectilinear fields.
	2. do something "intelligent" about texture mapping (I'll save
		you wise guys the effort of stating that intelligence
		is in the eyes of the beholder).  One can set the
		UV coordinates in the field, and subsequently use 
		dynamic texture mapping in the software renderer, or
		one can color the vertices of the mesh using an image.
		In either case, one can move the texture around and do
		texture scaling (no rotations or non-affine transforms)
		using the parameters provided for controlling the UV
		mapping of texture to mesh.

I have found a million and one uses for this module.  Don't know why I
didn't write it sooner.  Plus, if it breaks, or you don't like something
about it, you can do something about it (scream at me, or fix it yourself).

Now, isn't that SPECIAL!  ;-) ;-)

wes


ps- give the IAC a couple of days to unpack it, install, port and test it
on all AVS platforms.



From tvv@doppler.ncsc.org (Terry Myerson)
Subject: Datasets needed !!!
Message-ID: <BsIzox.8xo@doppler.ncsc.org>
Organization: North Carolina Supercomputing Center
Date: Wed, 5 Aug 1992 19:34:09 GMT

Hi folks -

    The Boston Workshop on Volume Visualization is looking for datasets for
their conference in October.  The International AVS Center at the North
Carolina Supercomputing Center will be collecting these datasets.

    Basically, we are looking for volume data sets for the biggest conference
on Volume Visualization in the world.  The data sets will be public domain after 
the conference.  The scientific visualization researchers at the conference,
will be attempting completely revolutionary volume visulization techniques on the 
data, and the results of their work will then be returned the data donaters.  

    If you are interested, could you please email the IAC at avs@ncsc.org with
some information on the data set which you could possibly submit to the conference
archive.  Any standard data format would be usable, as well as any uniform or non-
uniformly gridded data.  We are looking for data which covers a large number
of disciplines, so please submit.

Thank you -

Terry

---
Terry Myerson
International AVS Center
North Carolina Supercomputing Center
avs@ncsc.org

> 
> 	     1992 Boston Workshop on Volume Visualization
> 			 October 19-20, 1992
> 		     Park Plaza Hotel, Boston, MA
> 		   --------------------------------
> 
> As a follow-on to the successful Chapel Hill and San Diego Workshops
> on Volume Visualization, this third workshop will combine papers,
> poster sessions, and works-in-progress of new developments in this
> evolving area.  Scientists from all disciplines involved in the visual
> interpretation of volumetric data are invited to both submit and
> attend this exciting workshop.      
> 
> The Workshop is sponsored by ACM-SIGGRAPH in cooperation with the IEEE
> Computer Society Technical Committee on Computer Graphics. This
> Workshop will take place during the week of October 19-23, 1992 at the
> Park Plaza Hotel in Boston, MA in coordination with the Visualization
> 92 conference.       
> 
> 				Papers
> 			      ----------
> 	      Session 1: Parallel VolumeVisualization I
> "Volume Rendering on the MasPar MP-1", G. Vezina, P.A. Fletcher, P.K.
> Robertson, CSIRO Division of Information Technology, Australian
> National University
> 
> "Parallel Volume Visualization on a Hypercube Architecture", L.
> Misericordia, C. Montani, R. Perego, R. Scopigno, CNUCE C.N.R.
> 
> 	      Session 2: Parallel VolumeVisualization II
> "Volume Rendering on Scalable Shared-Memory MIMD Architectures", J.
> Nieh, M. Levoy, Stanford University
> 	
> "Data Parallel Volume Rendering as Line Drawing", P. Schroder, G.
> Stroll, Princeton University
> 
> 		   Session 3: Medical Applications
> "Supercomputer Assisted Brain Visualization with an Extended Ray
> Tracer", D. Stredney, R. Yagel, S. May, M. Torello, Ohio State
> University 
> 
> "Integrated Visualization of Brain Anatomy and Cerebral Blood
> Vessels", D. Vandermeulen, P. Plets, S. Ramkers, P. Suetens, G.
> Marchal, A. Baert, A. Oosterlinck Katholieke Unversiteit Leuven
> 
> 		    Session 4: Flow Visualization
> "Interactive Visualization of Flow Fields", A. van Gelder, J.
> Wilhelms, University of California at Santa Cruz
> 
> "Direct Volume Visualization of Three-Dimensional Vector Fields", R.
> Crawfis, N. Max, Lawrence Livermore National Lab. 
> 
> 			Session 5: Techniques
> "A Volume Density Optical Model", Peter L. Williams, Center for
> Supercomputing Research & Development, University of Illinois at
> Urbana-Champaign 
> 
> "Vector Quantization for Volume Rendering", Paul Ning, Stanford
> University 
> 
> "Three-dimensional Alpha Shapes", Herbert Edelsbrunner, Ernst P.
> Mucke, University of Illinois at Urbana-Champaign
> 
> 			Session 6: Algorithms
> "A Power Series Algorithm for Highly Accurate Volume Rendering", K.L.
> Novins, J.R. Arvo, Cornell University
> 
> "Fast Algorithms for Volume Ray Tracing", J. Danskin, P. Hanrahan,
> Princeton University 
> 
> 
> 			 Dataset Information
> 		       -----------------------
> For information on receiving or submitting sample datasets, please contact:
> 
> 	Terry Myerson
> 	North Carolina Supercomputing Center
> 	PO Box 12889
> 	3021 Cornwallis Road
> 	Research Triangle Park, NC
> 	27709-2889
> 
> 	Tel: 919-248-1186
> 	Fax: 919-248-1101
> 	email: tvv@ncsc.org
> 
> 		      Poster Session Information
> 		    ------------------------------
> For information on participating in the Poster Session, please contact:
> 
> 	Roni Yagel
> 	Department of Computer and Information Science
> 	The Ohio State University
> 	228 Bolz Hall
> 	2036 Neil Av. Mall
> 	Columbus, Ohio 43210-1277
> 
> 	Tel: (614) 292-0060
>         Fax: (614) 292-9021
> 	Email: yagel@cis.ohio-state.edu
> 
> 
> 			  Workshop Committee
> 			----------------------
> Workshop Co-Chairs:
> Larry Gelberg			Haim Levkowitz                
> Advanced Visual Systems Inc.	Computer ScienceDepartment    
> 300 Fifth Ave.			University of Mass. at Lowell 
> Waltham, MA 02154		Lowell, MA 01854              
> Tel: 617-890-4300		Tel: 508-934-3654             
> Fax: 617-890-8287		Fax: 508-452-4298             
> larryg@avs.com			haim@cs.ulowell.edu           
> 
> Treasurer: Jay Hersh - MIT X Consortium
> Registration: Edward Council - Timberfield Systems -	volvis92@cs.ulowell.edu
> Publicity: Ally Heim - Precision Visuals Inc.
> Local Arrangements: Ralph McNall - ACE Technology
> Student Volunteers: Roni Yagel - Ohio State University
> Poster Session: Roni Yagel - Ohio State University
> Datasets: Don Speray - The Computational Mechanics Compary
> Visualization '92 Liason: Georges Grinstein - University of Mass. at Lowell
> 
> 			  Program Committee
> 			---------------------
> Program Co-Chairs:
> Arie Kaufman			William Lorensen                   
> Computer Science Department	General Electric Co.               
> State University of New York	Bldg KW, Rm. C207A, PO Box 8       
> Stony Brook, NY 11794		Schenectady, NY                    
> Tel: 516-632-8441		Tel: 518-387-6744                  
> Fax: 516-632-8334		email: lorensen@dwaskill.crd.ge.com
> email: ari@cs.sunysb.edu
> 
> Program Committee:
> Nick England - SUN Microsystems
> Pat Hanrahan - Princeton University
> Wolfgang Krueger - GMD-HLRZ, Germany
> Marc Levoy - Stanford University
> Nelson Max - Lawrence Livermore National Lab
> Holly Rushmeir - National Institute of Standards & Technology
> Craig Upson - Silicon Graphics
> Sam Uselton - CS Corp - NASA Ames
> Jane Wilhelms - University of California at Santa Cruz
> 
> 
> 		       Registration Information
> 		     ----------------------------
> Conference Fees:
> 
> 		ACM/IEEE Members	Non-Members	Students
> Postmarked on or
> before Sept 30, 1992	$270		$300		$150
> after Sept. 30, 1992	$325		$375		$200
> 
> 	Conference Registration Fee				  $____________
> 	Additional Reception Tickets @ $30 each _________ X $30 = $____________
> 	Additional Vis92 Reception Tickets @ $30 each ___ X $30 = $____________
> 	Total Fees						  $____________
> 
> Please note:  Additional tickets for the Monday night reception at the
> Museum of Science are limited.  Please order addtional tickets in advance. 
> 
> Form:   					please print or type:
> Name	_____________________________________________________________
> Company	_____________________________________________________________
> Address	_____________________________________________________________
> City/State/Zip/Country 	_____________________________________________
> Daytime Phone	_____________________________________________________
> Fax:		_____________________________________________________
> Email Address	_____________________________________________________
> ACM/IEEE Member Number ______________________________________________
> 
> Payment:
> _______	Check is enclosed 
> 		(made out to 1992 Boston Workshop on Volume Visualization)
> _______	American Express		Card # 		_________________________
> _______	Mastercard			Name on Card	_________________________
> _______	Visa				Expiration Date _________________________
> 					Signature	_________________________
> 
> Complete this form and return with a check (in U.S. dollars) or credit
> card endorsement to:  
> 
> 		1992 Boston Workshop on Volume Visualization
> 		Edward Council
> 		PO Box 9296
> 		Lowell, MA 01853
> 
> 		email: volvis92@cs.ulowell.edu
> 		
> Registration will be accepted onsite during the following times:
> Sunday, October 18, 1992 (11:00 am - 6:30 pm), Monday, October 19
> (7:00 am-5:30 pm), Tuesday, October 20 (7:00 am - 5:30 pm).  Students
> attach a copy of your valid student picture ID card.  Member number
> (ACM or IEEE) must be included to receive member rate.  Requests for
> refunds must be received by September 30, 1992.  Refunds are subject
> to a $50 service charge.  Participants who fail to notify Edward
> Council prior to the the refund date are subject to the full fee.
> Substitutions are allowed at any time.         
> 
> 			  Hotel Information
> 			---------------------
> To make hotel reservations, please contact:
> 	
> 	The Park Plaza Hotel Reservations
> 	64 Arlington Street 
> 	Boston, MA  02117
> 	(617) 426-2000
> 	
> 
-- 
Terry Myerson
International AVS Center
North Carolina Supercomputing Center
avs@ncsc.org


From avs@ncsc.org (Terry Myerson)
Subject: Re: Help required in using upstream data
Message-ID: <BsJ04s.92o@doppler.ncsc.org>
Sender: news@doppler.ncsc.org
Nntp-Posting-Host: doppler
Reply-To: avsIn article <1992Jul20.172036.15106@menudo.uh.edu>, hsingh@Turing.chem.uh.edu (Harpreet Singh) writes:
Organization: North Carolina Supercomputing Center
References:  <1992Jul20.172036.15106@menudo.uh.edu>
Date: Wed, 5 Aug 1992 19:43:40 GMT

**** Begin included article

Hi Harpreet -

I am not exactly sure if this is the answer to you query, but I'll give
it a shot anyways...

The picking feature of AVS will only allow the selection of the nearest
vertice or object.  It does not support picking an arbitrary place in space -
as this would be truly arbitrary on a 2D display system.  A great example
of this feature is the awesome create_geom module which requires the
generate_grid
module to work ( if there is an empty scene )

Good Luck -

Terry

---
Terry Myerson
International AVS Center
North Carolina Supercomputing Center
avs@ncsc.org


Hi AVS users,
	I have a small problem. I am trying to use upstream data
in AVS so that the module is notified whenever the first button
of the mouse is pressed so that I can know the coordinates at
that point. The problem is that sometimes the coordinates 
returned by two or more consecuitive clicks at different places
return the same value of the coordinates. I am using the
same struct upstream_geom as is given in the example pic_cube.c.

Any help will be appreciated.

Thanks

Harpreet
--
~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'
~'  Harpreet Singh                      e-mail:hsingh@turing.chem.uh.edu  ~'
~'  @University Of Houston              v-mail:(713)743-3328,(713)748-7292~'
~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'
**** End included article

@ncsc.org 
Organization: North Carolina Supercomputing Center
Subject: Re: Help required in using upstream data
Keywords: 


Terry Myerson
International AVS Center
North Carolina Supercomputing Center
avs@ncsc.org


From ianh@resmel.bhp.com.au (Ian Hoyle)
Newsgroups: comp.graphics.avs
Subject: help needed for neophyte new user :)
Message-ID: <ianh.713082052@morgana>
Date: 6 Aug 92 06:20:52 GMT
Sender: usenet@resmel.bhp.com.au (network news)
Organization: BHP Research - Melbourne Laboratories, AUSTRALIA
Lines: 37

Well, I've been through the voluminous documentation for our new copy of
AVS 4.0 and couldn't really quite see what I needed so I thought I'd ask
you people out there for some guidance!! (it's like anything new .... you 
just need a bit of a kickstart to get going)

I have a bunch of 2-D seismic survey lines that are physically located on the 
survey area  in essentially orthogonal directions. Taken indivually they
constitute 2-D images but because they are located in 3-D space they are
a 3-D irregular field (ndim=2 & nspace=3) going by AVS data types.

Now what I would like to do is visualize multiple sesmic sections located
vertically in 3-D space, some of them intersecting, and apply different 
colourmaps/transparenies to the rendered image to hilite different horizons
in the seismic section.

My first guess was to convert the 2-D image (field) to a 3-D geometric
object where the image now becomes a 3-D surface (geometry?) that can then
be rotatedt. The field-to-mesh module doesn't look to be what
I want since really I am mapping (x,y,z) info to each of the pixels in the
original image.

Without belabouring the point, is there any direction I should be looking
at in attempting to get the image I am after??

thanx,

	ian
--
   /\/\     :  Ian Hoyle,  Senior Research Scientist
  / / /\    :  Image Analysis Group
 / / /  \   :  BHP Research - Melbourne Laboratories
/ / / /\ \  :  245 Wellington Rd, Mulgrave, 3170, AUSTRALIA
\ \/ / / /  :  Phone    +61-3-560-7066
 \  / / /   :  E-mail   ianh@resmel.bhp.com.au
  \/\/\/    :
            : "The kernel IS a continuously running random number
            :  generator" -- Larry Wall


From dna@math.psu.edu (Douglas N Arnold)
Subject: Anyone have an unformatted man page for AVS?
Message-ID: <BsJx6t.1sx@cs.psu.edu>
Sender: news@cs.psu.edu (Usenet)
Nntp-Posting-Host: fredholm.math.psu.edu
Organization: Department of Mathematics, The Pennsylvania State University
Date: Thu, 6 Aug 1992 07:37:40 GMT
Lines: 22

The lack of the unformatted source for the avs man page is a real
annoyance.  Has anyone decompiled the formatted page supplied
with the AVS distribution to create one?

In case you're wondering why this is bothering me here are the
details.  First, we don't keep the /usr/local/man/cat1 directory around
at all, since it consumes disk space and the formatting time is so
short, that there is little to be gained by keeping preformatted pages
about.  Second, without the unformatted page in
/usr/local/man/man1/avs.1, avs doesn't get entered into the whatis
database.  Of course we could add it there by hand, but then everytime
anyone adds a new piece of software and regenerates the whatis database
(a very frequent occurence) they need to remember to add this line by
hand.  Not very convenient.  Of the 430 or so executables we've
installed in our /usr/local, avs is the only one to supply a formatted
man page only.

If you have an unformatted man page, please send it to me by email.
Thanks.
--
Douglas N. Arnold                         dna@math.psu.edu
Dept. of Mathematics, Penn State Univ.    (814) 865-0246


From bonnett@seismo.CSS.GOV (H. David Bonnett)
Newsgroups: comp.graphics.avs
Subject: Looking for way to handle stream integer data
Message-ID: <51046@seismo.CSS.GOV>
Date: 6 Aug 92 15:04:28 GMT
Sender: usenet@seismo.CSS.GOV
Organization: Center for Seismic Studies, Arlington, VA
Lines: 23
Nntp-Posting-Host: bragi.css.gov


After looking through the AVS manuals (4.0) and through the IAC
archives, I now turn to the net for help..

I am looking for an input module that is a cross between Wes Bethel's
*Animate Inte(ger)* and the supported *Read Data*. I have a set of 
inputs that are integer values sampled from seismometers and I need to 
read them in one sample at a time for processing and display at a single
point (with changing color or something similar). Is there a way to do this,
without building a new module, that I have overlooked? 

It appears that I could add a browser and read routine to Wes' Animate
Integer to accomplish this, but I wanted to see if someone else had
met the same goal before I learn to write Modules. (given I have been
using AVS for almost a week now ;)

Any pointers or donations will be greatly appreciated... Either by post or
e-mail
--
-dave bonnett-   Center for Seismic Studies;  Arlington, VA 
      bonnett@seismo.css.gov :  (703) 276-7900 	Pop Kid Internationale
"Rec would be ridiculous, people would start posting stupid things."
(Stephanie da Silva on alt.folklore Straw Poll)


From lbm@avs.com (Linda B. Merims)
Subject: Re: Anyone have an unformatted man page for AVS?
Organization: Advanced Visual Systems Inc.
References: <BsJx6t.1sx@cs.psu.edu>
Message-ID: <1992Aug6.161835.20922@ctr.columbia.edu>
Sender: news@ctr.columbia.edu (The Daily Lose)
X-Newsreader: Tin 1.1 PL4
Date: Thu, 6 Aug 1992 16:18:35 GMT
X-Posted-From: phobos.avs.com
X-Posted-Through: sol.ctr.columbia.edu
Lines: 965


Here is the unformatted avs man page.  Some of the nroff/troff
macros are Advanced Visual Systems-specific and will not
format correctly (such as .eS and .pS R), but it does come
out reasonably well when run through straight nroff and -man.

We will include the source to this in the next release.

L. B. Merims
Advanced Visual Systems
---------------------------------------
\"	@(#)avs.6	7.6 Advanced Visual Systems 92/03/05
\"			Copyright (c) 1989 by
\"			Advanced Visual Systems Inc.
\"			All Rights Reserved
\"	
\"	This software comprises unpublished confidential information of
\"	Advanced Visual Systems Inc. and may not be used, copied or made
\"	available to anyone, except in accordance with the license
\"	under which it is furnished.
\"	
\"	This file is under sccs control at:
\"	
ds BU \s-2\(bu\s0
\"
TH avs 1 "Application Visualization System" "\&"
SH NAME
avs \- \c
Application Visualization System
SH SYNOPSIS
\f3avs\fP  \f2option(s)\fP
SH DESCRIPTION
The Application Visualization System (AVS) is an interactive
tool for scientific visualization. It includes the following
subsystems:
TP 18p
\*(BU
\f3Image Viewer.\fP
A high-level tool for manipulating and viewing images.
TP 18p
\*(BU
\f3Graph Viewer.\fP
A high-level tool for graphing data.
TP 18p
\*(BU
\f3Geometry Viewer.\fP
Allows you to compose "scenes"
that contain geometrically-defined objects. The objects must have
been created by programs or AVS modules that use AVS's GEOM
programming library. You can transform the objects themselves
(move, rotate, scale); you can change the viewing parameters
(e.g. move the eye point, perspective view, etc.); and you can
control the way in which the graphical images are rendered
(lighting and shading, Z-buffering, etc.).
TP 18p
\*(BU
\f3Network Editor.\fP
A visual programming interface for
connecting computational modules together into networks
that perform visualization functions.
PP
AVS also includes a sample application, the \f3AVS Data Viewer\f1.
The Data Viewer provides a simplified, pulldown menu interface
for building visualization networks.  It is a useful tool for
the novice user learning basic scientific visualization techniques.
PP
The command to start AVS is simple:
pS K
avs
pE
Use the \f2avs\f1 command to start AVS when your terminal or
workstation is directly-connected to the system that will run
AVS.  You should use the \f2avs\f1 command together with
the \f3-nohw\f1 option or \f3NoHW 1\f1 startup file
keyword when running
AVS as a remote X client on a different hardware platform, or
when you are displaying on an "X terminal."
AVS runs as an X Window System client, and thus requires that the
DISPLAY environment variable be set correctly.  These are usually
the only options necessary to start an AVS session.  However,
see the AVS release notes for your platform for additional
platform-specific information on which options, such as
\f3VisualType\f1, may be required
to start AVS correctly on your workstation.
SH CONTROLLING AVS STARTUP
Three entities can affect how AVS starts.  They are listed in
their order of precedence:
TP 1.5P
1.
Command line options.
TP 1.5P
2.
The \f2.avsrc\f1 startup file.  The startup file contains
keyword-value pairs.  AVS always reads the system default startup
file in \f2/usr/avs/runtime/avsrc\f1 first.  Users may override or
supplement these system default options with a personal \f2.avsrc\f1
file.  AVS will look for a personal startup file in \f2./.avsrc\f1
(in the current directory), then \f2$HOME/.avsrc\f1 (in your HOME directory).
It uses the first \f2.avsrc\f1 that it finds.
TP 1.5P
3.
Environment variables.
SH OPTIONS
All option keywords begin with a hyphen
(e.g. \f3\-data\fP). In many cases, the keyword is followed
by an additional word (e.g. a directory name). You must separate the
keyword and the additional word with whitespace (SPACE and/or TAB
characters).
PP
All options keywords can be abbreviated, as long as there is no ambiguity.
For example, \f3\-data\fP can be abbreviated to \f3\-da\fP. But you cannot
abbreviate it to \f3\-d\fP, since this might indicate either \f3\-data\fP or
\f3\-display\fP.
PP
In several cases, you can use an entry in the \f2AVS startup file\fP
as an alternative to a command line option. For example, a \f3DataDirectory\fP
entry in the startup file is equivalent to a \f3\-data\fP option.
See the next section for details on the startup file.
TP  4.5P
\f3\-class \f2string\f1
(startup file equivalent:  none)
This is the command line option equivalent of
the DISPLAYCLASS environment variable.  You can use
it to make AVS behave in different ways when it is started from
different types of display hardware.
\f3-class\f1 has two effects:
RS
TP 1.5P
1.  
An \f2Xdefaults\f1 file
specifies the "look" of the AVS interface; what shades of grey are
used for command buttons, what fonts to use, whether the background is
"stippled" or a flat color, etc.
When \f3-class \f2string\f1 is given, AVS does not use the default
\f2/usr/avs/runtime/avs.Xdefaults\f1 file.  Instead, it looks for
an Xdefaults.\f2string\f1
file in the \f2/usr/avs/runtime\f1 directory and uses it.
At present, the only
alternate X defaults file supplied is \f2Xdefaults.X\f1.
TP 1.5P
2.
If such a file is present, it will use an alternate startup file,
\f2/usr/avs/runtime/avsrc.string\f1.  Otherwise, it uses
\f2/usr/avs/runtime/avsrc\f1.
It will also look for a .avsrc.\f2string\f1 file in the current,
then HOME directory
and use it instead of your usual \f2.avsrc\f1 file.
eS
\f3-class\f1 is used
when running AVS from an "X terminal."  See the full discussion
in the "AVS on Color X Servers" appendix to the \f2AVS User's Guide\f1.
RE
PP
TP 4.5P
\f3\-cli\fP
(startup file equivalent:  none)
Run AVS with the Command Language Interpreter functioning in the
terminal emulator window from which AVS was invoked. This takes an optional
argument, which is a CLI command string, to be executed after
AVS starts up.  See the chapter on the "Command Language Interpreter" 
in the \f2AVS User's Guide\fP for details.
TP 4.5P
\f3-compile_library\f2 source_filespec compiled_filespec\f1
(startup file equivalent:  none)
This is a utility for maintaining module libraries whose component
modules are changing.  It follows a "source module library"
vs "compiled module library" paradigm.  Specifically, \f3-compile_library\f1
takes the \f2source_filespec\f1 to be an AVS module library file
containing a list of \f3file\f1 commands followed by the
name of a module binary file.  It executes each module listed in order
to extract the module description information.  From this, it generates
\f2compiled_filespec\f1 as an AVS module library file containing
the description information necessary to load the module into
the Network Editor's Palette quickly without actually executing
the module binary.  This option does not start a full AVS session.
eS
See the "Constructing a Module Library" discussion in the "Advanced Network
Editor" chapter for more information.
TP 4.5P
\f3\-data \f2directory\f1
(startup file equivalent: \f3DataDirectory\fP)
Specifies the directory in which all subsystem data input
file browsers, including the Image Viewer, the Graph Viewer,
the Geometry Viewer, and the data input modules in the
Network Editor, will
initially look for data files (files used an input to computational
modules).  This is the major tool for redirecting AVS's default
data input
focus off the sample data files provided in \f2/usr/avs/data\fP
and onto your own data files.
eS
The default data directory is \f2/usr/avs/data\fP.
TP 4.5P
\f3\-dials \f2devicefilespec\f1
(startup file equivalent: \f3DialDevice\fP)
Specifies the serial communications port to which a 
dialbox device is attached (e.g. \f2/dev/tty2\fP).  If
\f3-dials\fP is present, AVS automatically connects
the dialbox dials to the Geometry Viewer's rotation,
translation, and scaling transformations.  You must know
which serial communications port your dialbox is connected to.
This argument also corresponds to the environment variable DIALS.
Dialboxes are not supported on all platforms.
TP 4.5P
\f3\-display \f2display-name\f1
(startup file equivalent:  none)
Specifies the X Window System display on which AVS is to display.
This overrides the current setting of the DISPLAY environment variable.
TP 4.5P
\f3\-gamma \f2number\f1
(startup file equivalent: \f3Gamma\f1)
Controls the brightness of the display for all AVS windows except Geometry
Viewer output windows produced with a hardware renderer.  The default
varies from platform to platform.  Values between 1.7 to 2.2 are good
starting points for experimentation.  Higher real values produce
a lighter display.
TP 4.5P
\f3\-geometry \f2[ geom-option(s) ]\f1
(startup file equivalent:  none)
Automatically invokes the Geometry Viewer subsystem at startup.
There will be no \f3Data Viewers\f1 button to access other subsystems.
If you use this option, it must be the \f2last\f1 option on the
command line, followed only by the options listed below
that are specific to this subsystem.  All other options that
follow \f2-geometry\f1 will be ignored.
RS
TP 4.5P
\f3\-scene \f2scene-file.scene\f1 or \f2geomcli-file.scr\f1
(startup file equivalent:  none)
This option
executes the Geometry Viewer's \f3Read Scene\f1 function,
using the file \f2scene-file.scene\f1 or \f2geomcli-file.scr\f1,
depending upon the setting of the \f3AVS_GEOM_WRITE_V30\f1
environment variable.
TP 4.5P
\f3\-filter \f2pathname\f1
Specifies \f2pathname\f1 as the directory to search
for geometry conversion utilities, named \f2\&..._to_geom\f1.
See the "Importing Data Into AVS" chapter of the \f2User's Guide\f1.
eS
The default directory for these programs is \f2/usr/avs/bin\f1.
TP 4.5P
\f3\-defaults \f2filename\f1
Specifies a Geometry Viewer defaults file. The format of this file
is described in the "Geometry Viewer Script Language" appendix.
TP 4.5P
\f3\-geometry \f2Xgeometry\f1
Specifies an X Window System geometry (e.g. \f3500x500-5-5\fP)
for the initial window created by the Geometry Viewer.
TP 4.5P
\f3-noroll\f1
Turns off track rolling.  Track rolling occurs when you perform
a transformation and release the mouse button while the mouse is
still moving.  This "flings" the transformable, causing it to
continue in motion.
TP 4.5P
\f3\-usage\f1
Displays a list of Geometry Viewer startup options.
RE
TP 4.5P
\f3\-graph\fP
Automatically invokes the AVS Graph Viewer at system startup.  There
will be no \f3Data Viewers\f1 button to access other subsystems.
TP 4.5P
\f3\-image\fP
Automatically invokes the AVS Image Viewer at system startup.  There
will be no \f3Data Viewers\f1 button to access other subsystems.
TP 4.5P
\f3\-library \f2filespec\f1
(startup file equivalent: \f3ModuleLibraries\fP)
Specifies which AVS module library file to load into the Network
Editor at system startup.  Module library files are ASCII
files describing sets of modules.  \f2/usr/avs/avs_library/Supported\fP
is an example.  This is the major tool that allows
you to load your own sets of modules\(emeither modules you've
written yourself or subsets of the supplied modules that you
have customized to your needs\(eminstead of always relying
on the system default Supported and Unsupported module libraries
specified in the \f2/usr/avs/runtime/avsrc\fP file.
eS
To load more than one module library, use multiple pairs
of \f3-library \f2filespec\f1 options.
eS
It is equivalent to using the Network Editor's \f3Read Module Library\fP
function.
TP 4.5P
\f3\-modules \f2directory\f1 or \f2filename\f1
(startup file equivalent: none)
Specifies the directory or file in which the AVS Network Editor subsystem
initially will look for executable modules.  All executable
files in a directory are examined to determine whether they contain
one or more modules.
eS
\f3-modules\fP differs from \f3-library\fP above in that it
loads \f2binary\fP module files, not ASCII module \f2library\fP files.
It is slower to load modules as binary files rather than libraries.
\" For each module located in this search, an icon
\" is placed in one of the four columns of the \*(lqModule Palette\*(rq menu.
eS
You can use more than one \f3\-modules\fP options to specify
multiple individual module binaries, or to have AVS search
through multiple directories for modules.  This is the main tool
for loading individual modules (perhaps modules that you are debugging)
that you have not yet formalized into a module library.  It is
equivalent to the Network Editor's \f3Read Module(s)\fP
function.  It cannot be used to read remote modules.
eS
The default modules directory is \f2/usr/avs/avs_library\fP.
TP 4.5P
\f3\-netdir \f2directory\f1
(startup file equivalent: \f3NetworkDirectory\fP)
Specifies the directory in which the AVS Network Editor subsystem
initially will look for network files (\f3Read Network\fP and \f3Write Network\fP
functions).  This is the tool to use to redirect AVS's default network
focus away from the samples provided in \f2/usr/avs/networks\fP and
onto your own network files.
eS
The default network directory is \f2/usr/avs/networks\fP.
TP 4.5P
\f3\-network \f2network-file\f1
(startup file equivalent:  none)
Starts AVS and brings up the Network Editor's module control panel
with the controls for the network displayed.  The full Network Editor
subsystem is not displayed or accessible.  This is one way to make
an individual production network available to a user.
TP 4.5P
\f3-nodmc\f1
(startup file equivalent:  \f3DirectModuleCommunication 0\f1)
Turns off the default direct module-to-module communication.  This
is useful if you want to perform timing tests to compare network
execution speed with/without direct module-to-module communication.
TP 4.5P
\f3-nohw\f1
(startup file equivalent:  \f3NoHW 1\f1)
Tells the AVS Geometry Viewer to not initialize any hardware renderers.
Without a hardware renderer, the AVS Geometry Viewer will use a
software renderer to
create its 3D scenes instead of the platform's native graphics
facilities.  \f3-nohw\fP is used when you are running
AVS as a remote X client on a different hardware platform
or when you are using an "X terminal."
The software renderer creates an X image rendering of the
3D scene and ships only the image to the local X server
for display rather than a stream
rendering commands that may not be understood by the local system.
eS
\f2-nohw\f1 is equivalent to the obsolete \f2-swrender\f1.
TP 4.5P
\f3-parallel \f2n\f1
(startup file equivalent: none)
Sets the maximum number of module processes that will attempt to execute in
parallel at any one time.  The default is 1 (no parallelization.)
You should set this figure intelligently for the system(s) that
you are running on.  If two processors are available (a two-processor
system, or a local and a remote system) then this figure can reasonably
be set to 2.  If you give a value that exceeds the number of processors
available, the underlying operating systems will serialize the processes.
There is no inherent upper limit to the \f2n\f1 parameter.
eS
Modules
must be in separate processes to execute in parallel.  Most modules
supplied with AVS are combined into a single executable
that runs as a single process.  Thus, they will not run in
parallel unless they are divided into separate processes.  This may be
done wholesale with the \f3-separate\f1 option, or precisely using the
Network Editor's module group editing facility.  See the discussion
on parallel module execution in the "Advanced Network Editor"
chapter of the AVS \f2User's Guide\f1 for more information.
TP 4.5P
\f3\-path \f2directory\f1
(startup file equivalent: \f3Path\fP)
Specifies the directory tree in which AVS itself is installed.
eS
The default path is \f2/usr/avs\fP. If you specify another path, then
the default data directory and network directory are modified
accordingly. For example:
pS R
ta 4.5P 12P
\f3If:\fP	path	= \f2/usr/local/avs\fP
\f3Then:\fP	data directory	= \f2/usr/local/avs/data\fP
	network directory	= \f2/usr/local/avs/networks\fP
pE
sp .5
This option is also useful to switch between multiple
versions of AVS (for example, a test release
and a production release).
TP 4.5P
\f3\-reindex\f1
(startup file equivalent:  none)
This option creates AVS help system \f2.topics\fP files.  It does
not start an AVS session.  It is useful
if you are creating help files for applications that you want to
be accessible through the AVS help system.  See the appendix
on creating help files in the \f2AVS Developer's Guide\fP for
more information.
TP 4.5P
\f3-renderer \f2"string"\f1
(startup file equivalent:  \f3Renderer\f1)
Specifies which renderer will be the default selected in the
Geometry Viewer when a camera window is first created.  \f2"string"\f1 is
the literal name found on
the renderer buttons under the Geometry Viewer's \f3Cameras\f1
menu, usually either "Software Renderer" or "Hardware Renderer",
though other strings are possible.
It must match exactly, in spelling, case, and spacing.  The double
quote marks must be present.  Where
there is a hardware renderer available, \f3-renderer\f1
defaults to "Hardware Renderer".  If the user specified \f3-nohw\f1,
then only one renderer is available, the software renderer, and
this option is ignored.
TP 4.5P
\f3\-separate \fP
(startup file equivalent:  none)
This option disables AVS's multiple modules in one process feature.
It forces each module to execute as a separate process, whether
or not it is combined in an executable with other modules.  The option
is primarily useful for debugging, or when parallel module execution
is desired.  (In this last case, it is better to not use \f3-separate\f1,
since it usually increases memory utilization.  Instead, individually
divide modules into different executables using the Network Editor's
module process group editing facility.)
See the section on 
"Multiple Modules in a Single Process" in the \f2AVS Developer's Guide\fP.
TP 4.5P
\f3\-server \fP
(startup file equivalent: none)
This option opens a connection that an external process
can use to connect to AVS and exchange with it a
stream of Command Language Interpreter (CLI) commands
and their output.  See the chapter on the CLI in
the \f2AVS User's Guide\fP for details.
TP 4.5P
\f3\-shm/noshm \fP
(startup file equivalent:  \f3SharedMemory \f2on/off\f1)
This turns the AVS shared memory option on and off.  When shared memory
is on, AVS keeps only one copy of AVS field and UCD data that all
modules in a network share.  (GEOM-format data and pixmaps do not use
shared memory.)  This improves performance by
saving memory and processor time.  \f3-noshm\fP can disable shared memory
if, for example,
AVS's use of the finite shared memory area is interfering with other
applications.  On most systems shared memory is on by default.
TP 4.5P
\f3\-size \f2XDIM\f1x\f2YDIM\f1
(startup file equivalent: \f3ScreenSize\fP)
Specifies size, in pixels, to use for AVS's virtual display screen
size.  AVS will
automatically resize its interface to fit into the virtual screen.
You could use this to confine AVS to run within one section
of your screen instead of across the whole screen.
TP 4.5P
\f3\-spaceball \f2devicefilespec\f1
(startup file equivalent:  \f3SpaceballDevice\fP)
Specifies the serial communications port to which a 
Spaceball device is attached (e.g. \f2/dev/tty2\fP).  If
\f3-spaceball\fP is present, AVS automatically connects
the Spaceball device to the Geometry Viewer's rotation,
translation, and scaling transformations.  You must know
which serial communications port your spaceball is connected to.
This entry also corresponds to the environment variable SPACEBALL.
Spaceballs may not be supported on all platforms.
TP 4.5P
\f3\-timer\f1
(startup file equivalent: none)
Writes Geometry Viewer performance data to \f2stderr\f1.  This should be
used in conjunction with the \f3Object Info\f1 panel to display the
number of polygons being rendered.  To get the measurement, use
track rolling to set the object in continuous motion (middle mouse
button to rotate, release mouse button while mouse is still moving,
thereby "flinging" the object into continuous motion).  Wait several
seconds (the longer, the more accurate), then press any mouse button
in the window to stop the object.  Minimize mouse movements while the
measurement is being taken.  The measurement looks like:
eS
73 frames in 6.632989 seconds for 11.005596 FPS
eS
FPS stands for "frames per second."  By convention, the "standard unit"
is \f2/usr/avs/data/geometry/teapot.geom\f1, in the default-sized window, with
no additional rendering options (color, shading, etc.).  In this case,
FPS can be referred to as TPS ("teapots per second").
TP 4.5P
\f3\-version\fP
Displays the AVS version number. (Does not start an AVS session.)
TP 4.5P
\f3\-usage\fP
Displays a usage message for AVS.  No AVS session
is started.
SH AVS STARTUP FILE
When it begins execution, AVS uses a \f2startup file\fP, which
specifies such things as which module libraries to load,
the locations of various directories, where to
look for Help files, how big to make the AVS interface, etc.
PP
AVS always first reads the system default startup file in
\f2/usr/avs/runtime/avsrc\f1.  Users may override or supplement the
options in the system startup file with a personal \f2.avsrc\f1 file.
AVS looks user \f2.avsrc\f1 files in the order listed, using the first
that it finds:
pS 
\&./.avsrc                    \f1(current directory)\fP
\&$HOME/.avsrc                \f1(home directory)\fP
pE
PP
You can copy the system default
\f2/usr/avs/runtime/avsrc\fP file
to your HOME or other directory,
modify it according to your needs and preferences, and rename
it with the "." prefix.
PP
If you give the \f3-class X\fP command option, or set the
DISPLAYCLASS X environment variable, AVS will use a different startup
file:  \f2/usr/avs/runtime/avsrc.X\f1.  In the same manner as the
regular startup file, AVS will look for personal \f2.avsrc.X\f1 file
in the current directory, then your HOME directory.
This file
is used to customize AVS when you are running it from
an "X terminal."
SS .avsrc Startup File Format
Each line of the AVS startup file consists of keyword-value pair,
with whitespace separating the keyword and the value. For example:
pS
\s-1
ModuleLibraries       /usr/avs/avs_library/Supported  /usr/johnp/avs/modules/Modlib
NetworkWindow        867x567+407+2
NetworkDirectory     /usr/johnp/avs/nets
\" ModulesDirectory  /usr/johnp/avs/modules
DataDirectory        /usr/johnp/avs/data
DialDevice           /dev/tty02
\" Pat                 /usr/avs
\s+1
pE
PP
Often, the keyword corresponds to one of the command line options
described in the preceding section. If you use a command line option,
it overrides the specification, if any, in the startup file.
SS Startup File Keywords
The AVS startup file keywords are listed below.  
PP
\f3NOTE\f1:
Where
startup file keywords have command line equivalents, see the
command line description above for the most complete discussion of
the feature.
PP
TP 4.5P
\f3Applications  \f2filespec\f1
(command line equivalent:  none)
Causes AVS to use a file other than \f2/usr/avs/runtime/AVS.applns\f1
to build the large Applications menu.  This is how a user would
create their own set of application networks and have them
accessible from AVS's Applications menu without modifying the
central system file.  If a simple filename is given rather than
an absolute file and pathname, AVS will
look for the file in the directory defined by Path (by default,
\f2/usr/avs\f1).
TP 4.5P
\f3BoundingBox \f2switch\f1
(command line equivalent:  none)
If \f3BoundingBox on\fP is set, then the AVS Image Viewer and
Geometry Viewer will come up with their \f3Bounding Box\fP control
already turned on.  A "bounding box" is a less compute-intensive
style of moving geometric objects and Image Viewer subimages.
Instead of moving the object "real time," it only moves a
wirebox representation of the object.  Only when you release
the mouse button is the object/subimage rendered at its new
location.  \f3BoundingBox\f1 is most useful when you are using
AVS on lower performance graphics systems, with the software
renderer, or from an "X terminal."  \f3Bounding Box\f1 is usually
off by default.
TP 4.5P
\f3Colors \f2r g b gray\f1
(command line equivalent:  none)
This option controls how many cells of a \f2system\fP colormap
AVS will attempt to allocate to itself when it starts.  \f2r g b g\fP
represent numbers for red, green, blue, and gray.  This is primarily
intended for people who are using AVS from an "X terminal" or PseudoColor
workstation that objects to the number of colormap cells that
AVS tries to allocate for itself.  See the discussion on
"AVS on Color X Servers" in the AVS \f2User's Guide\f1.
TP 4.5P
\f3DataDirectory \f2directory\fP
(command line equivalent: \f3\-data\fP)
Specifies the directory in which the various AVS data
input file browsers used in the subsystems
(Image Viewer, Graph Viewer, and Geometry Viewer) and
Network Editor modules \*(lqread data\*(rq modules
(\f3read field\fP, \f3read geometry\fP, etc.)
initially will look for data files.  This is the
main tool to refocus AVS's data input attention off
the sample data files in \f2/usr/avs/data\fP and onto
your own data files.
TP 4.5P
\f3DialDevice \f2devicefilespec\f1
(command line equivalent:  \f3-dials\fP)
Specifies \f2devicefilespec\f1 as the serial communications
port to which a dialbox device
is attached (e.g. \f2/dev/tty1\fP).  If \f3DialDevice\fP is specified, AVS automatically
connects the dialbox dials to the Geometry Viewer's rotate, translate,
and scale transformations.
eS
This entry also corresponds to the environment variable DIALS. 
Dialboxes may not be supported on
all platforms.
TP 4.5P
\f3DirectModuleCommunication  \f2switch\f1
(command line equivalent:  \f3-nodmc\f1)
Turns direct module-to-module communication on and off.  This
is useful if you want to perform timing tests to compare network
execution speed with/without direct module-to-module communication.
Direct module-to-module communication is on by default.
TP 4.5P
\f3DisplayPixmapWindow \f2Xgeometry\f1
(command line equivalent:  none)
Controls the default X Window System geometry of
the \f3display pixmap\f1 module's window.
TP 4.5P
\f3Gamma \f2number\f1
(command line equivalent: \f3-gamma\f1)
Controls the brightness of the display for all AVS windows except Geometry
Viewer output windows produced with a hardware renderer.  The default
varies from platform to platform.  Values between 1.7 to 2.2 are good
starting points for experimentation.  Higher real values produce
a lighter display.
TP 4.5P
\f3GridSize \f2n\f1
(command line equivalent:  none)
Controls the size in pixels of the Layout Editor's alignment squares
when \f3Snap to Grid\f1 is switched on.  The
default is 10.
TP 4.5P
\f3HelpPath \f2directory ...\f1
(command line equivalent:  none)
Expands the list of directories that AVS will search to find a
module's documentation when you click \f3Show Module Documentation\fP
in the module's Module Editor window.  This is useful when you
are using modules other than the set provided with AVS. For the format
of the "Help" path, see Appendix D of the \f2AVS Developer's Guide\fP,
concerning "On-Line Help".
TP 4.5P
\f3Hosts \f2fullfilespec\f1
(command line equivalent: none)
Gives the name of a "Hosts" file that lists machines, access methods,
and directories of remote modules.  It provides a
personal override to the
system default \f2/usr/avs/runtime/hosts\fP file when you click on
the Network Editor's \f3Read Remote Module(s)\fP button under
\f3Module Tools\fP.  See the "Running Remote Modules" section
in the \f2AVS User's Guide\fP Network Editor chapter for details.
TP 4.5P
\f3ImageAutomagnify \f2switch\f1
(command line equivalent: none)
In AVS 3 and later releases, the display image window will not
rescale an image when the window is resized.  Turning this option
"on" will restore the AVS2 behavior of automatically magnifying the image.
TP 4.5P
\f3ImageScrollbars \f2switch\f1
(command line equivalent: none)
If set to the value \f3off\fP, suppresses the adding of scrollbars
to display windows that are too small for the image they are
currently displaying. (You can always see more of the image simply
by dragging it with the mouse.)
TP 4.5P
\f3ModuleLibraries\f2 filespec filespec ...\f1
(command line equivalent:  \f3-library\fP)
Specifies which libraries of modules will be loaded into the
Network Editor's module palette.  The \f2last\fP module library
listed will be the "default" library showing in the module
Palette when you enter
the Network Editor.  The other module libraries listed can
be called up by clicking on their iconic representation at the
top of the Network Editor's main panel.
There is no way to continue
the list of module libraries to a new line; the list must be on
one (perhaps very long) line.
TP 4.5P
\f3ModulePanelHeight \f2integer\f1
(command line equivalent:  none)
Controls the proportion of the Network Construction  window devoted to
the module Palette as opposed to the Workspace.
TP 4.5P
\f3NetworkDirectory \f2directory\f1
(command line equivalent: \f3\-netdir\f1)
Specifies the directory in which the AVS Network Editor subsystem
initially will look for network files (\f3Read Network\fP and 
\f3Write Network\fP functions).
TP 4.5P
\f3NetworkWindow \f2Xgeometry\f1
(command line equivalent: none)
Specifies the X Window system geometry of the Network Construction Window,
which includes the Network Editor menu, the Module Palette, and the Workspace
in which you construct networks of modules.  You may need this if
your display is substantially smaller than the usual 1280x1024 pixels.
TP 4.5P
\f3NoHW \f2switch\f1
(command line equivalent:  \f3-nohw\f1)
\f3NoHW 1\f1 tells the AVS Geometry Viewer to not initialize
any hardware renderer.
Without a hardware renderer, the AVS Geometry Viewer will use a
software renderer to
create its 3D scenes instead of the platform's native graphics
facilities.  \f3NoHW 1\fP is used when you are running
AVS as a remote X client on a different hardware platform
or when you are using an "X terminal."
The software renderer creates an X image rendering of the
3D scene and ships only the image to the local X server
for display rather than a stream of
rendering commands that the local display may not understand.
The default is \f3NoHW 0\f1 (do initialize
hardware renderers) on systems that support a hardware renderer.
eS
\f3NoHW 1\f1 is equivalent to the obsolete \f3SWRender 1\f1.
TP 4.5P
\f3NetWriteAllParams \f2switch\f1
(command line equivalent: none)
AVS saves only parameters that have been modified out to a network file.
Setting this option to \f3on\f1, will enable saving all parameters, as was the
default in AVS 2.  The default is \f3off\f1.
TP 4.5P
\f3Path\fP
(command line equivalent: \f3\-path\fP)
Specifies the directory tree in which AVS itself is installed.
TP 4.5P
\f3PrintNetwork \f2command\f1
(command line equivalent:  none)
The Network Editor's \f3Print Network\fP button normally sends
output to your default printer.  This lets you specify
an alternate print command to execute. The command should be a regular
shell command, such as:
pS
lpr -Plw2
pE
TP 4.5P
\f3ReadOnlySharedMemory \f2switch\f1
(command line equivalent:  none)
Shared memory is normally "read only."  Occasionally, the system
developer might wish to keep shared memory turned on, but allow
it to be written into.  Setting \f3ReadOnlySharedMemory 0\f1
accomplishes this.  The default is \f31\f1.
TP 4.5P
\f3Renderer "\f2string\f1"
(command line equivalent:  \f3-renderer "\f2string\f3"\f1)
Specifies which renderer will be the default selected in the
Geometry Viewer when the first camera window is created.  \f2"string"\f1 is
the literal name found on
the renderer buttons under the Geometry Viewer's \f3Cameras\f1
menu, usually either "Software Renderer" or "Hardware Renderer",
though other strings are possible.
It must match exactly, in spelling, case, and spacing.  The double
quote marks must be present.  Where
there is a hardware renderer available, \f3Renderer\f1
defaults to "Hardware Renderer".  If the user specified \f3NoHW 1\f1,
then only one renderer is available, the software renderer, and
this option is ignored.
TP 4.5P
\f3SaveMessageLog \f2switch\f1
(command line equivalent: none)
If set to the value \f3on\fP, causes the AVS message log
to be preserved when the AVS session ends normally.
By default, the message log (\f2/tmp/avs_message.log_\f(BIXXX\f1,
where \f(BIXXX\fP is the AVS process number) is deleted
automatically.
The log file is always preserved if AVS exits abnormally (e.g.
\f3Ctrl-C\fP interrupt, system crash).
TP 4.5P
\f3ScreenSize \f2XDIM\f1x\f2YDIM\f1
(command line equivalent: \f3size\f1)
Specifies the size of AVS's virtual display in pixels, confining
AVS to run within this area.  AVS scales its interface to fit
the virtual screen.
TP 4.5P
\f3SharedMemory \f2switch\f1
(command line equivalent:  \f3shm/noshm\fP)
Specifying \f3SharedMemory off\fP turns off AVS's shared memory
feature.
TP 4.5P
\f3SpaceballDevice \f2devicefilespec\f1
(command line equivalent:  \f3-spaceball\fP)
Indicates the serial communications port to which a Spaceball device
is attached (e.g. \f2/dev/tty1\fP).  If \f3Spaceball\fP is specified, AVS automatically
connects the Spaceball to the Geometry Viewer's rotate, translate,
and scale transformations.
eS
This entry also corresponds to the environment variable SPACEBALL.
Spaceballs may not be supported
on all platforms.
TP 4.5P
\f3StackSelector \f2option\f1
(command line equivalent:  none)
People who build very large networks sometimes find that the Network
Editor's control panel "overflows," making some of the module
buttons difficult to access, because the radio buttons take up too much
of the control panel.  Setting \f3StackSelector choice_browser\fP
displays the module names as a scrolling list similar to the
file browsers instead of as the default \f3radio_buttons\fP.
TP 4.5P
\f3VisualType \f2visualtype\f1
(command line equivalent:  none)
This command may be necessary when you are seeing less color rendition
than you know your display is capable of.
eS
AVS normally uses the X server's default visual.  Occasionally,
this is the wrong visual to use.  For example, the default may be set to
PseudoColor when there actually is a TrueColor visual available.
(The standard X Window System
command to list which
X visuals are available and which is being used as the default is
\f2xdpyinfo\f1.  This command may not be available on all platforms.)
eS
\f3VisualType\f1 lets you specify a \f2visualtype\f1, either
\f3PseudoColor\fP, \f3TrueColor\fP, or \f3DirectColor\f1.    AVS
will then search the X server's visual
list until it finds the first visual with the given visual type and
use it.
eS
You
can also specify an explicit visual using the string
\f3VisualID\f1 followed by a number \f2n\f1 that is the
decimal equivalent of the X server's hexadecimal visual id for the
visual you want to use.  For example:
pS K
VisualType  VisualID  41
pE
eS
This option may also be useful to people
using AVS from "X terminals."
eS
\f3Note:\f1  Poor color rendition may also be caused because your display is
using double buffering.  It may be using its 24 planes as two double-buffered
12 planes (or 12/6, or 8/4).  Turning off
double buffering on the Geometry Viewer's \f3Cameras\f1 submenu will
fix this, but you will see the object being drawn.
TP 4.5P
\f3WindowMgr \f2mgr\f1
(command line equivalent:  none)
This option ensures that the Network Editor's Layout Editor and
the X Window System window manager that you are using work
correctly together.  The default for this parameter is
specified in the \f2/usr/avs/runtime/avs.Xdefaults\f1 file.
The currently recognized values are:  \f3awm\f1, \f3mwm\f1 (Motif-style
window managers),
\f3twm\f1, \f3uwm\f1, \f3olwm\f1(Open Look), and \f3dxwm\f1(Dec XVI).  
TP 4.5P
\f3XWarpPtr \f2on\f1
(command line equivalent: none)
Causes the mouse cursor to be automatically moved ("warped") into
typein panels when they appear.  \f3XWarpPtr\f1 is off by
default.
SH AVS ENVIRONMENT VARIABLES
AVS uses the following environment variables.  Only DISPLAY
must be set correctly before AVS will work.
TP 6P
\f3AVS_ADAPT_TABLE \f2switch\f1
A block table is a data structure that maps field points' I, J, K
indicies
in an irregular field within a "block" of
X, Y, Z world space.  Modules such as \f3arbitrary slicer\f1 and
\f3probe\f1 use the block table to interpolate values at points
"on" their sampling surface, determining which  need to be mapped
as colored polygons.
eS
AVS normally builds a regular, evenly-dimensioned block table.  Where
data points are fairly uniformly spaced within the field, such a block
table provides efficient access to the I, J, K values in each block
of the grid\(emeach block has approximately the same number of points.
However, where data values are concentrated in some areas of the
field, but sparse elsewhere (e.g., the wing surface of the \f2bluntfin.fld\f1
dataset) search times in the dense blocks become much longer.
eS
An adaptive block table creates the block table as an octree.  Where
data values are dense, the block grid is divided and subdivided
again until each block contains only a short list of I, J, K values
to search through, improving performance.
eS
Adaptive block tables are slower to construct, but execute more rapidly
in the areas with dense grids.
People with irregular datasets where the distribution of data points
is uneven should try setting AVS_ADAPT_TABLE 1 to see if it improves
the performance of the \f3arbitrary slicer\f1, \f3threshold slicer\f1,
\f3streamline\f1, \f3particle advector\f1, \f3hedgehog\f1, \f3probe\f1, and 
\f3color geom\f1 modules.  AVS_ADAPT_TABLE is 0 (off) by default.
TP 6P
\f3AVS_GEOM_WRITE_V30 \f2switch\f1
A 1 value causes the Geometry Viewer's \f3Save Scene\f1 and
\f3Save Object\f1 functions
to save scenes and objects as Geometry Viewer Script Language \f2.scene\f1
and \f2.obj\f1 files, as occurred in AVS Release 3.0 and earlier,
rather than in a single CLI \f2.scr\f1 file.  It is provided for backward
compatibility.  It is 0 (off) by default.
TP 6P
\f3AVS_HELP_PATH\fP
Specifies one or more locations in the file system for AVS to use
when searching for on-line help files.
See Appendix D of the \f2AVS Developer's Guide\fP for more on this
variable.
TP 6P
\f3AVS_MEM_CHECK \f2switch\f1
sp 0
TP 6P
\f3AVS_MEM_HISTORY \f2switch\f1
sp 0
TP 6P
\f3AVS_MEM_VERBOSE \f2integer\f1
These three environment variables are all used by the alternate
memory allocation routines invoked with the include file
\f2/usr/avs/include/mem_defs.h\f1.  These routines replace the UNIX
standard memory allocation utilities such as \f2malloc\f1 with AVS
utilities that perform extensive dynamic memory allocation/deallocation
bug checking.  See the "Memory Allocation Debugging" section in the
"Advanced Topics" chapter of the AVS \f2Developer's Guide\f1 for
more information on these utilities.
TP 6P
\f3AVS_MG_TROFF \f2switch\f1
Causes the AVS Module Generator to generate its module man page
documentation templates in \f2troff\f1 format rather than the
default preformatted text man page using tabs and blanks.  This
option is 0 (off) by default.
TP 6P
\f3DIALS \f2devicefilespec\f1
Indicates the serial communications port to which a dialbox device
is attached.  Dialboxes may not be supported on all platforms.
TP 6P
\f3DISPLAY \f2host:server.screen\f1
(required)
Used by the X Window System to
indicate the display screen at which you're working.
TP 6P
\f3DISPLAYCLASS \f2string\f1
\f2string\f1 is used to specify an alternate
\f2/usr/avs/runtime/Xdefaults\f1 file, such as the supplied
\f2/usr/avs/runtime/Xdefaults.X\f1.  Also causes AVS to use
alternate \f2.avsrc.string\f1 startup files, both the default
in the \f2/usr/avs/runtime\f1 directory (no such alternative
is supplied with the release), and user \f2.avsrc\f1
files.  Both may be customized to make AVS behave differently
on different types of display hardware, such as an X terminal.
\f3-class\f1 is the command line equivalent.
TP 6P
\f3EDITOR\f1
The AVS Module Generator will use this common UNIX environment
variable's value as the default text editor that it will start
when you press the Module Generator's \f3Edit\f1 function.
TP 6P
\f3SPACEBALL \f2devicefilespec\fP
Indicates the serial communications port to which a Spaceball device
is attached.
Spaceballs may not be supported on all platforms.
\".TP 6P
\"\f3AVS_NUM_PROCS\f1
\"This environment variable only has meaning on Stardent ST3000VS
\"systems.  It controls how many of the system's parallel processors the
\"Dore graphics library will execute on.  (AVS uses Dore as its
\"underlying rendering package on Stardent "Titan" series
\"systems.)  The default is 1.
\".TP 6P
\"\f3DORE_ARGS\f1
\"(optional)
\"This environment variable only has meaning on Stardent "Titan" series
\"systems.  It controls some aspects of the Dore' graphics library
\"execution.  Specifically, it is the equivalent of the Dore' \f3DoDevice\f1
\"function call.  Its arguments are described in the "Device Driver"
\"appendix of the Stardent \f2Dore' Programmer's Guide\f1.  The
\"argument string should be enclosed in quotes with individual
\"arguments separated by semi-colons.
if n .Ee



From dlc@convex.com (Dominique Le Corre)
Subject: Re: Looking for way to handle stream integer data
Message-ID: <1992Aug07.081146.16693@convex.com>
Sender: usenet@convex.com (news access account)
Nntp-Posting-Host: convex1.convex.com
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
References: <51046@seismo.CSS.GOV>
Date: Fri, 07 Aug 1992 08:11:46 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.
Lines: 15

The easiest, though not most efficient way to do this is:
- Run avs -cli
- In the window where you started Avs, type script -o file_name
- Bring up your network and select any file name.
- In the window where you started Avs, type script -c
- Now, you just created an Ascii file (file_name) with a script
  of your session, and you will see a line which sets the filename parameter.
- Just duplicate the line (or have it done by a shell script) for all other
  files after having saved the template to avoid redoing the previous
  steps for any animation.
- In the window where you started Avs, type script -p file_name.

Hope this works.
D.LC
dlc@cvxfr.fr.convex.com


From lbm@avs.com (Linda B. Merims)
Subject: Re: Anyone have an unformatted man page for AVS?
Organization: Advanced Visual Systems Inc.
References: <BsJx6t.1sx@cs.psu.edu>
Message-ID: <1992Aug7.145937.10078@ctr.columbia.edu>
Sender: news@ctr.columbia.edu (The Daily Lose)
X-Newsreader: Tin 1.1 PL4
Date: Fri, 7 Aug 1992 14:59:37 GMT
X-Posted-From: phobos.avs.com
X-Posted-Through: sol.ctr.columbia.edu

OK, second try.  The mailer ate the leading "."s in the last
posting.  This is a "shar" version of the man page.  Follow
the instructions in the header to get rid of the "@"s.
------------------CUT HERE-------------------------------
# This is a shell archive.  Remove anything before this line,
# then unpack it by saving it in a file and typing "sh file".
#
# Wrapped by  <lbm@putty> on Fri Aug  7 10:44:06 1992
#
# This archive contains:
#	avs.6	
#

LANG=""; export LANG
PATH=/bin:/usr/bin:$PATH; export PATH

echo x - avs.6
sed 's/^@//' >avs.6 <<'@EOF'
@.\"	@(#)avs.6	7.6 Advanced Visual Systems 92/03/05
@.\"			Copyright (c) 1989 by
@.\"			Stardent Computer Inc.
@.\"			All Rights Reserved
@.\"	
@.\"	This software comprises unpublished confidential information of
@.\"	Advanced Visual Systems Inc. and may not be used, copied or made
@.\"	available to anyone, except in accordance with the license
@.\"	under which it is furnished.
@.\"	
@.\"	This file is under sccs control at Advanced Visual Systems in:
@.\"	
@.\"	
@.ds BU \s-2\(bu\s0
@.\"
@.TH avs 1 "Application Visualization System" "\&"
@.SH NAME
avs \- \c
Application Visualization System
@.SH SYNOPSIS
\f3avs\fP  \f2option(s)\fP
@.SH DESCRIPTION
The Application Visualization System (AVS) is an interactive
tool for scientific visualization. It includes the following
subsystems:
@.TP 18p
\*(BU
\f3Image Viewer.\fP
A high-level tool for manipulating and viewing images.
@.TP 18p
\*(BU
\f3Graph Viewer.\fP
A high-level tool for graphing data.
@.TP 18p
\*(BU
\f3Geometry Viewer.\fP
Allows you to compose "scenes"
that contain geometrically-defined objects. The objects must have
been created by programs or AVS modules that use AVS's GEOM
programming library. You can transform the objects themselves
(move, rotate, scale); you can change the viewing parameters
(e.g. move the eye point, perspective view, etc.); and you can
control the way in which the graphical images are rendered
(lighting and shading, Z-buffering, etc.).
@.TP 18p
\*(BU
\f3Network Editor.\fP
A visual programming interface for
connecting computational modules together into networks
that perform visualization functions.
@.PP
AVS also includes a sample application, the \f3AVS Data Viewer\f1.
The Data Viewer provides a simplified, pulldown menu interface
for building visualization networks.  It is a useful tool for
the novice user learning basic scientific visualization techniques.
@.PP
The command to start AVS is simple:
@.pS K
avs
@.pE
Use the \f2avs\f1 command to start AVS when your terminal or
workstation is directly-connected to the system that will run
AVS.  You should use the \f2avs\f1 command together with
the \f3-nohw\f1 option or \f3NoHW 1\f1 startup file
keyword when running
AVS as a remote X client on a different hardware platform, or
when you are displaying on an "X terminal."
AVS runs as an X Window System client, and thus requires that the
DISPLAY environment variable be set correctly.  These are usually
the only options necessary to start an AVS session.  However,
see the AVS release notes for your platform for additional
platform-specific information on which options, such as
\f3VisualType\f1, may be required
to start AVS correctly on your workstation.
@.SH CONTROLLING AVS STARTUP
Three entities can affect how AVS starts.  They are listed in
their order of precedence:
@.TP 1.5P
1.
Command line options.
@.TP 1.5P
2.
The \f2.avsrc\f1 startup file.  The startup file contains
keyword-value pairs.  AVS always reads the system default startup
file in \f2/usr/avs/runtime/avsrc\f1 first.  Users may override or
supplement these system default options with a personal \f2.avsrc\f1
file.  AVS will look for a personal startup file in \f2./.avsrc\f1
(in the current directory), then \f2$HOME/.avsrc\f1 (in your HOME directory).
It uses the first \f2.avsrc\f1 that it finds.
@.TP 1.5P
3.
Environment variables.
@.SH OPTIONS
All option keywords begin with a hyphen
(e.g. \f3\-data\fP). In many cases, the keyword is followed
by an additional word (e.g. a directory name). You must separate the
keyword and the additional word with whitespace (SPACE and/or TAB
characters).
@.PP
All options keywords can be abbreviated, as long as there is no ambiguity.
For example, \f3\-data\fP can be abbreviated to \f3\-da\fP. But you cannot
abbreviate it to \f3\-d\fP, since this might indicate either \f3\-data\fP or
\f3\-display\fP.
@.PP
In several cases, you can use an entry in the \f2AVS startup file\fP
as an alternative to a command line option. For example, a \f3DataDirectory\fP
entry in the startup file is equivalent to a \f3\-data\fP option.
See the next section for details on the startup file.
@.TP  4.5P
\f3\-class \f2string\f1
(startup file equivalent:  none)
This is the command line option equivalent of
the DISPLAYCLASS environment variable.  You can use
it to make AVS behave in different ways when it is started from
different types of display hardware.
\f3-class\f1 has two effects:
@.RS
@.TP 1.5P
1.  
An \f2Xdefaults\f1 file
specifies the "look" of the AVS interface; what shades of grey are
used for command buttons, what fonts to use, whether the background is
"stippled" or a flat color, etc.
When \f3-class \f2string\f1 is given, AVS does not use the default
\f2/usr/avs/runtime/avs.Xdefaults\f1 file.  Instead, it looks for
an Xdefaults.\f2string\f1
file in the \f2/usr/avs/runtime\f1 directory and uses it.
At present, the only
alternate X defaults file supplied is \f2Xdefaults.X\f1.
@.TP 1.5P
2.
If such a file is present, it will use an alternate startup file,
\f2/usr/avs/runtime/avsrc.string\f1.  Otherwise, it uses
\f2/usr/avs/runtime/avsrc\f1.
It will also look for a .avsrc.\f2string\f1 file in the current,
then HOME directory
and use it instead of your usual \f2.avsrc\f1 file.
@.eS
\f3-class\f1 is used
when running AVS from an "X terminal."  See the full discussion
in the "AVS on Color X Servers" appendix to the \f2AVS User's Guide\f1.
@.RE
@.PP
@.TP 4.5P
\f3\-cli\fP
(startup file equivalent:  none)
Run AVS with the Command Language Interpreter functioning in the
terminal emulator window from which AVS was invoked. This takes an optional
argument, which is a CLI command string, to be executed after
AVS starts up.  See the chapter on the "Command Language Interpreter" 
in the \f2AVS User's Guide\fP for details.
@.TP 4.5P
\f3-compile_library\f2 source_filespec compiled_filespec\f1
(startup file equivalent:  none)
This is a utility for maintaining module libraries whose component
modules are changing.  It follows a "source module library"
vs "compiled module library" paradigm.  Specifically, \f3-compile_library\f1
takes the \f2source_filespec\f1 to be an AVS module library file
containing a list of \f3file\f1 commands followed by the
name of a module binary file.  It executes each module listed in order
to extract the module description information.  From this, it generates
\f2compiled_filespec\f1 as an AVS module library file containing
the description information necessary to load the module into
the Network Editor's Palette quickly without actually executing
the module binary.  This option does not start a full AVS session.
@.eS
See the "Constructing a Module Library" discussion in the "Advanced Network
Editor" chapter for more information.
@.TP 4.5P
\f3\-data \f2directory\f1
(startup file equivalent: \f3DataDirectory\fP)
Specifies the directory in which all subsystem data input
file browsers, including the Image Viewer, the Graph Viewer,
the Geometry Viewer, and the data input modules in the
Network Editor, will
initially look for data files (files used an input to computational
modules).  This is the major tool for redirecting AVS's default
data input
focus off the sample data files provided in \f2/usr/avs/data\fP
and onto your own data files.
@.eS
The default data directory is \f2/usr/avs/data\fP.
@.TP 4.5P
\f3\-dials \f2devicefilespec\f1
(startup file equivalent: \f3DialDevice\fP)
Specifies the serial communications port to which a 
dialbox device is attached (e.g. \f2/dev/tty2\fP).  If
\f3-dials\fP is present, AVS automatically connects
the dialbox dials to the Geometry Viewer's rotation,
translation, and scaling transformations.  You must know
which serial communications port your dialbox is connected to.
This argument also corresponds to the environment variable DIALS.
Dialboxes are not supported on all platforms.
@.TP 4.5P
\f3\-display \f2display-name\f1
(startup file equivalent:  none)
Specifies the X Window System display on which AVS is to display.
This overrides the current setting of the DISPLAY environment variable.
@.TP 4.5P
\f3\-gamma \f2number\f1
(startup file equivalent: \f3Gamma\f1)
Controls the brightness of the display for all AVS windows except Geometry
Viewer output windows produced with a hardware renderer.  The default
varies from platform to platform.  Values between 1.7 to 2.2 are good
starting points for experimentation.  Higher real values produce
a lighter display.
@.TP 4.5P
\f3\-geometry \f2[ geom-option(s) ]\f1
(startup file equivalent:  none)
Automatically invokes the Geometry Viewer subsystem at startup.
There will be no \f3Data Viewers\f1 button to access other subsystems.
If you use this option, it must be the \f2last\f1 option on the
command line, followed only by the options listed below
that are specific to this subsystem.  All other options that
follow \f2-geometry\f1 will be ignored.
@.RS
@.TP 4.5P
\f3\-scene \f2scene-file.scene\f1 or \f2geomcli-file.scr\f1
(startup file equivalent:  none)
This option
executes the Geometry Viewer's \f3Read Scene\f1 function,
using the file \f2scene-file.scene\f1 or \f2geomcli-file.scr\f1,
depending upon the setting of the \f3AVS_GEOM_WRITE_V30\f1
environment variable.
@.TP 4.5P
\f3\-filter \f2pathname\f1
Specifies \f2pathname\f1 as the directory to search
for geometry conversion utilities, named \f2\&..._to_geom\f1.
See the "Importing Data Into AVS" chapter of the \f2User's Guide\f1.
@.eS
The default directory for these programs is \f2/usr/avs/bin\f1.
@.TP 4.5P
\f3\-defaults \f2filename\f1
Specifies a Geometry Viewer defaults file. The format of this file
is described in the "Geometry Viewer Script Language" appendix.
@.TP 4.5P
\f3\-geometry \f2Xgeometry\f1
Specifies an X Window System geometry (e.g. \f3500x500-5-5\fP)
for the initial window created by the Geometry Viewer.
@.TP 4.5P
\f3-noroll\f1
Turns off track rolling.  Track rolling occurs when you perform
a transformation and release the mouse button while the mouse is
still moving.  This "flings" the transformable, causing it to
continue in motion.
@.TP 4.5P
\f3\-usage\f1
Displays a list of Geometry Viewer startup options.
@.RE
@.TP 4.5P
\f3\-graph\fP
Automatically invokes the AVS Graph Viewer at system startup.  There
will be no \f3Data Viewers\f1 button to access other subsystems.
@.TP 4.5P
\f3\-image\fP
Automatically invokes the AVS Image Viewer at system startup.  There
will be no \f3Data Viewers\f1 button to access other subsystems.
@.TP 4.5P
\f3\-library \f2filespec\f1
(startup file equivalent: \f3ModuleLibraries\fP)
Specifies which AVS module library file to load into the Network
Editor at system startup.  Module library files are ASCII
files describing sets of modules.  \f2/usr/avs/avs_library/Supported\fP
is an example.  This is the major tool that allows
you to load your own sets of modules\(emeither modules you've
written yourself or subsets of the supplied modules that you
have customized to your needs\(eminstead of always relying
on the system default Supported and Unsupported module libraries
specified in the \f2/usr/avs/runtime/avsrc\fP file.
@.eS
To load more than one module library, use multiple pairs
of \f3-library \f2filespec\f1 options.
@.eS
It is equivalent to using the Network Editor's \f3Read Module Library\fP
function.
@.TP 4.5P
\f3\-modules \f2directory\f1 or \f2filename\f1
(startup file equivalent: none)
Specifies the directory or file in which the AVS Network Editor subsystem
initially will look for executable modules.  All executable
files in a directory are examined to determine whether they contain
one or more modules.
@.eS
\f3-modules\fP differs from \f3-library\fP above in that it
loads \f2binary\fP module files, not ASCII module \f2library\fP files.
It is slower to load modules as binary files rather than libraries.
@.\" For each module located in this search, an icon
@.\" is placed in one of the four columns of the \*(lqModule Palette\*(rq menu.
@.eS
You can use more than one \f3\-modules\fP options to specify
multiple individual module binaries, or to have AVS search
through multiple directories for modules.  This is the main tool
for loading individual modules (perhaps modules that you are debugging)
that you have not yet formalized into a module library.  It is
equivalent to the Network Editor's \f3Read Module(s)\fP
function.  It cannot be used to read remote modules.
@.eS
The default modules directory is \f2/usr/avs/avs_library\fP.
@.TP 4.5P
\f3\-netdir \f2directory\f1
(startup file equivalent: \f3NetworkDirectory\fP)
Specifies the directory in which the AVS Network Editor subsystem
initially will look for network files (\f3Read Network\fP and \f3Write Network\fP
functions).  This is the tool to use to redirect AVS's default network
focus away from the samples provided in \f2/usr/avs/networks\fP and
onto your own network files.
@.eS
The default network directory is \f2/usr/avs/networks\fP.
@.TP 4.5P
\f3\-network \f2network-file\f1
(startup file equivalent:  none)
Starts AVS and brings up the Network Editor's module control panel
with the controls for the network displayed.  The full Network Editor
subsystem is not displayed or accessible.  This is one way to make
an individual production network available to a user.
@.TP 4.5P
\f3-nodmc\f1
(startup file equivalent:  \f3DirectModuleCommunication 0\f1)
Turns off the default direct module-to-module communication.  This
is useful if you want to perform timing tests to compare network
execution speed with/without direct module-to-module communication.
@.TP 4.5P
\f3-nohw\f1
(startup file equivalent:  \f3NoHW 1\f1)
Tells the AVS Geometry Viewer to not initialize any hardware renderers.
Without a hardware renderer, the AVS Geometry Viewer will use a
software renderer to
create its 3D scenes instead of the platform's native graphics
facilities.  \f3-nohw\fP is used when you are running
AVS as a remote X client on a different hardware platform
or when you are using an "X terminal."
The software renderer creates an X image rendering of the
3D scene and ships only the image to the local X server
for display rather than a stream
rendering commands that may not be understood by the local system.
@.eS
\f2-nohw\f1 is equivalent to the obsolete \f2-swrender\f1.
@.TP 4.5P
\f3-parallel \f2n\f1
(startup file equivalent: none)
Sets the maximum number of module processes that will attempt to execute in
parallel at any one time.  The default is 1 (no parallelization.)
You should set this figure intelligently for the system(s) that
you are running on.  If two processors are available (a two-processor
system, or a local and a remote system) then this figure can reasonably
be set to 2.  If you give a value that exceeds the number of processors
available, the underlying operating systems will serialize the processes.
There is no inherent upper limit to the \f2n\f1 parameter.
@.eS
Modules
must be in separate processes to execute in parallel.  Most modules
supplied with AVS are combined into a single executable
that runs as a single process.  Thus, they will not run in
parallel unless they are divided into separate processes.  This may be
done wholesale with the \f3-separate\f1 option, or precisely using the
Network Editor's module group editing facility.  See the discussion
on parallel module execution in the "Advanced Network Editor"
chapter of the AVS \f2User's Guide\f1 for more information.
@.TP 4.5P
\f3\-path \f2directory\f1
(startup file equivalent: \f3Path\fP)
Specifies the directory tree in which AVS itself is installed.
@.eS
The default path is \f2/usr/avs\fP. If you specify another path, then
the default data directory and network directory are modified
accordingly. For example:
@.pS R
@.ta 4.5P 12P
\f3If:\fP	path	= \f2/usr/local/avs\fP
\f3Then:\fP	data directory	= \f2/usr/local/avs/data\fP
	network directory	= \f2/usr/local/avs/networks\fP
@.pE
@.sp .5
This option is also useful to switch between multiple
versions of AVS (for example, a test release
and a production release).
@.TP 4.5P
\f3\-reindex\f1
(startup file equivalent:  none)
This option creates AVS help system \f2.topics\fP files.  It does
not start an AVS session.  It is useful
if you are creating help files for applications that you want to
be accessible through the AVS help system.  See the appendix
on creating help files in the \f2AVS Developer's Guide\fP for
more information.
@.TP 4.5P
\f3-renderer \f2"string"\f1
(startup file equivalent:  \f3Renderer\f1)
Specifies which renderer will be the default selected in the
Geometry Viewer when a camera window is first created.  \f2"string"\f1 is
the literal name found on
the renderer buttons under the Geometry Viewer's \f3Cameras\f1
menu, usually either "Software Renderer" or "Hardware Renderer",
though other strings are possible.
It must match exactly, in spelling, case, and spacing.  The double
quote marks must be present.  Where
there is a hardware renderer available, \f3-renderer\f1
defaults to "Hardware Renderer".  If the user specified \f3-nohw\f1,
then only one renderer is available, the software renderer, and
this option is ignored.
@.TP 4.5P
\f3\-separate \fP
(startup file equivalent:  none)
This option disables AVS's multiple modules in one process feature.
It forces each module to execute as a separate process, whether
or not it is combined in an executable with other modules.  The option
is primarily useful for debugging, or when parallel module execution
is desired.  (In this last case, it is better to not use \f3-separate\f1,
since it usually increases memory utilization.  Instead, individually
divide modules into different executables using the Network Editor's
module process group editing facility.)
See the section on 
"Multiple Modules in a Single Process" in the \f2AVS Developer's Guide\fP.
@.TP 4.5P
\f3\-server \fP
(startup file equivalent: none)
This option opens a connection that an external process
can use to connect to AVS and exchange with it a
stream of Command Language Interpreter (CLI) commands
and their output.  See the chapter on the CLI in
the \f2AVS User's Guide\fP for details.
@.TP 4.5P
\f3\-shm/noshm \fP
(startup file equivalent:  \f3SharedMemory \f2on/off\f1)
This turns the AVS shared memory option on and off.  When shared memory
is on, AVS keeps only one copy of AVS field and UCD data that all
modules in a network share.  (GEOM-format data and pixmaps do not use
shared memory.)  This improves performance by
saving memory and processor time.  \f3-noshm\fP can disable shared memory
if, for example,
AVS's use of the finite shared memory area is interfering with other
applications.  On most systems shared memory is on by default.
@.TP 4.5P
\f3\-size \f2XDIM\f1x\f2YDIM\f1
(startup file equivalent: \f3ScreenSize\fP)
Specifies size, in pixels, to use for AVS's virtual display screen
size.  AVS will
automatically resize its interface to fit into the virtual screen.
You could use this to confine AVS to run within one section
of your screen instead of across the whole screen.
@.TP 4.5P
\f3\-spaceball \f2devicefilespec\f1
(startup file equivalent:  \f3SpaceballDevice\fP)
Specifies the serial communications port to which a 
Spaceball device is attached (e.g. \f2/dev/tty2\fP).  If
\f3-spaceball\fP is present, AVS automatically connects
the Spaceball device to the Geometry Viewer's rotation,
translation, and scaling transformations.  You must know
which serial communications port your spaceball is connected to.
This entry also corresponds to the environment variable SPACEBALL.
Spaceballs may not be supported on all platforms.
@.TP 4.5P
\f3\-timer\f1
(startup file equivalent: none)
Writes Geometry Viewer performance data to \f2stderr\f1.  This should be
used in conjunction with the \f3Object Info\f1 panel to display the
number of polygons being rendered.  To get the measurement, use
track rolling to set the object in continuous motion (middle mouse
button to rotate, release mouse button while mouse is still moving,
thereby "flinging" the object into continuous motion).  Wait several
seconds (the longer, the more accurate), then press any mouse button
in the window to stop the object.  Minimize mouse movements while the
measurement is being taken.  The measurement looks like:
@.eS
73 frames in 6.632989 seconds for 11.005596 FPS
@.eS
FPS stands for "frames per second."  By convention, the "standard unit"
is \f2/usr/avs/data/geometry/teapot.geom\f1, in the default-sized window, with
no additional rendering options (color, shading, etc.).  In this case,
FPS can be referred to as TPS ("teapots per second").
@.TP 4.5P
\f3\-version\fP
Displays the AVS version number. (Does not start an AVS session.)
@.TP 4.5P
\f3\-usage\fP
Displays a usage message for AVS.  No AVS session
is started.
@.SH AVS STARTUP FILE
When it begins execution, AVS uses a \f2startup file\fP, which
specifies such things as which module libraries to load,
the locations of various directories, where to
look for Help files, how big to make the AVS interface, etc.
@.PP
AVS always first reads the system default startup file in
\f2/usr/avs/runtime/avsrc\f1.  Users may override or supplement the
options in the system startup file with a personal \f2.avsrc\f1 file.
AVS looks user \f2.avsrc\f1 files in the order listed, using the first
that it finds:
@.pS 
\&./.avsrc                    \f1(current directory)\fP
\&$HOME/.avsrc                \f1(home directory)\fP
@.pE
@.PP
You can copy the system default
\f2/usr/avs/runtime/avsrc\fP file
to your HOME or other directory,
modify it according to your needs and preferences, and rename
it with the "." prefix.
@.PP
If you give the \f3-class X\fP command option, or set the
DISPLAYCLASS X environment variable, AVS will use a different startup
file:  \f2/usr/avs/runtime/avsrc.X\f1.  In the same manner as the
regular startup file, AVS will look for personal \f2.avsrc.X\f1 file
in the current directory, then your HOME directory.
This file
is used to customize AVS when you are running it from
an "X terminal."
@.SS .avsrc Startup File Format
Each line of the AVS startup file consists of keyword-value pair,
with whitespace separating the keyword and the value. For example:
@.pS
\s-1
ModuleLibraries       /usr/avs/avs_library/Supported  /usr/johnp/avs/modules/Modlib
NetworkWindow        867x567+407+2
NetworkDirectory     /usr/johnp/avs/nets
@.\" ModulesDirectory  /usr/johnp/avs/modules
DataDirectory        /usr/johnp/avs/data
DialDevice           /dev/tty02
@.\" Pat                 /usr/avs
\s+1
@.pE
@.PP
Often, the keyword corresponds to one of the command line options
described in the preceding section. If you use a command line option,
it overrides the specification, if any, in the startup file.
@.SS Startup File Keywords
The AVS startup file keywords are listed below.  
@.PP
\f3NOTE\f1:
Where
startup file keywords have command line equivalents, see the
command line description above for the most complete discussion of
the feature.
@.PP
@.TP 4.5P
\f3Applications  \f2filespec\f1
(command line equivalent:  none)
Causes AVS to use a file other than \f2/usr/avs/runtime/AVS.applns\f1
to build the large Applications menu.  This is how a user would
create their own set of application networks and have them
accessible from AVS's Applications menu without modifying the
central system file.  If a simple filename is given rather than
an absolute file and pathname, AVS will
look for the file in the directory defined by Path (by default,
\f2/usr/avs\f1).
@.TP 4.5P
\f3BoundingBox \f2switch\f1
(command line equivalent:  none)
If \f3BoundingBox on\fP is set, then the AVS Image Viewer and
Geometry Viewer will come up with their \f3Bounding Box\fP control
already turned on.  A "bounding box" is a less compute-intensive
style of moving geometric objects and Image Viewer subimages.
Instead of moving the object "real time," it only moves a
wirebox representation of the object.  Only when you release
the mouse button is the object/subimage rendered at its new
location.  \f3BoundingBox\f1 is most useful when you are using
AVS on lower performance graphics systems, with the software
renderer, or from an "X terminal."  \f3Bounding Box\f1 is usually
off by default.
@.TP 4.5P
\f3Colors \f2r g b gray\f1
(command line equivalent:  none)
This option controls how many cells of a \f2system\fP colormap
AVS will attempt to allocate to itself when it starts.  \f2r g b g\fP
represent numbers for red, green, blue, and gray.  This is primarily
intended for people who are using AVS from an "X terminal" or PseudoColor
workstation that objects to the number of colormap cells that
AVS tries to allocate for itself.  See the discussion on
"AVS on Color X Servers" in the AVS \f2User's Guide\f1.
@.TP 4.5P
\f3DataDirectory \f2directory\fP
(command line equivalent: \f3\-data\fP)
Specifies the directory in which the various AVS data
input file browsers used in the subsystems
(Image Viewer, Graph Viewer, and Geometry Viewer) and
Network Editor modules \*(lqread data\*(rq modules
(\f3read field\fP, \f3read geometry\fP, etc.)
initially will look for data files.  This is the
main tool to refocus AVS's data input attention off
the sample data files in \f2/usr/avs/data\fP and onto
your own data files.
@.TP 4.5P
\f3DialDevice \f2devicefilespec\f1
(command line equivalent:  \f3-dials\fP)
Specifies \f2devicefilespec\f1 as the serial communications
port to which a dialbox device
is attached (e.g. \f2/dev/tty1\fP).  If \f3DialDevice\fP is specified, AVS automatically
connects the dialbox dials to the Geometry Viewer's rotate, translate,
and scale transformations.
@.eS
This entry also corresponds to the environment variable DIALS. 
Dialboxes may not be supported on
all platforms.
@.TP 4.5P
\f3DirectModuleCommunication  \f2switch\f1
(command line equivalent:  \f3-nodmc\f1)
Turns direct module-to-module communication on and off.  This
is useful if you want to perform timing tests to compare network
execution speed with/without direct module-to-module communication.
Direct module-to-module communication is on by default.
@.TP 4.5P
\f3DisplayPixmapWindow \f2Xgeometry\f1
(command line equivalent:  none)
Controls the default X Window System geometry of
the \f3display pixmap\f1 module's window.
@.TP 4.5P
\f3Gamma \f2number\f1
(command line equivalent: \f3-gamma\f1)
Controls the brightness of the display for all AVS windows except Geometry
Viewer output windows produced with a hardware renderer.  The default
varies from platform to platform.  Values between 1.7 to 2.2 are good
starting points for experimentation.  Higher real values produce
a lighter display.
@.TP 4.5P
\f3GridSize \f2n\f1
(command line equivalent:  none)
Controls the size in pixels of the Layout Editor's alignment squares
when \f3Snap to Grid\f1 is switched on.  The
default is 10.
@.TP 4.5P
\f3HelpPath \f2directory ...\f1
(command line equivalent:  none)
Expands the list of directories that AVS will search to find a
module's documentation when you click \f3Show Module Documentation\fP
in the module's Module Editor window.  This is useful when you
are using modules other than the set provided with AVS. For the format
of the "Help" path, see Appendix D of the \f2AVS Developer's Guide\fP,
concerning "On-Line Help".
@.TP 4.5P
\f3Hosts \f2fullfilespec\f1
(command line equivalent: none)
Gives the name of a "Hosts" file that lists machines, access methods,
and directories of remote modules.  It provides a
personal override to the
system default \f2/usr/avs/runtime/hosts\fP file when you click on
the Network Editor's \f3Read Remote Module(s)\fP button under
\f3Module Tools\fP.  See the "Running Remote Modules" section
in the \f2AVS User's Guide\fP Network Editor chapter for details.
@.TP 4.5P
\f3ImageAutomagnify \f2switch\f1
(command line equivalent: none)
In AVS 3 and later releases, the display image window will not
rescale an image when the window is resized.  Turning this option
"on" will restore the AVS2 behavior of automatically magnifying the image.
@.TP 4.5P
\f3ImageScrollbars \f2switch\f1
(command line equivalent: none)
If set to the value \f3off\fP, suppresses the adding of scrollbars
to display windows that are too small for the image they are
currently displaying. (You can always see more of the image simply
by dragging it with the mouse.)
@.TP 4.5P
\f3ModuleLibraries\f2 filespec filespec ...\f1
(command line equivalent:  \f3-library\fP)
Specifies which libraries of modules will be loaded into the
Network Editor's module palette.  The \f2last\fP module library
listed will be the "default" library showing in the module
Palette when you enter
the Network Editor.  The other module libraries listed can
be called up by clicking on their iconic representation at the
top of the Network Editor's main panel.
There is no way to continue
the list of module libraries to a new line; the list must be on
one (perhaps very long) line.
@.TP 4.5P
\f3ModulePanelHeight \f2integer\f1
(command line equivalent:  none)
Controls the proportion of the Network Construction  window devoted to
the module Palette as opposed to the Workspace.
@.TP 4.5P
\f3NetworkDirectory \f2directory\f1
(command line equivalent: \f3\-netdir\f1)
Specifies the directory in which the AVS Network Editor subsystem
initially will look for network files (\f3Read Network\fP and 
\f3Write Network\fP functions).
@.TP 4.5P
\f3NetworkWindow \f2Xgeometry\f1
(command line equivalent: none)
Specifies the X Window system geometry of the Network Construction Window,
which includes the Network Editor menu, the Module Palette, and the Workspace
in which you construct networks of modules.  You may need this if
your display is substantially smaller than the usual 1280x1024 pixels.
@.TP 4.5P
\f3NoHW \f2switch\f1
(command line equivalent:  \f3-nohw\f1)
\f3NoHW 1\f1 tells the AVS Geometry Viewer to not initialize
any hardware renderer.
Without a hardware renderer, the AVS Geometry Viewer will use a
software renderer to
create its 3D scenes instead of the platform's native graphics
facilities.  \f3NoHW 1\fP is used when you are running
AVS as a remote X client on a different hardware platform
or when you are using an "X terminal."
The software renderer creates an X image rendering of the
3D scene and ships only the image to the local X server
for display rather than a stream of
rendering commands that the local display may not understand.
The default is \f3NoHW 0\f1 (do initialize
hardware renderers) on systems that support a hardware renderer.
@.eS
\f3NoHW 1\f1 is equivalent to the obsolete \f3SWRender 1\f1.
@.TP 4.5P
\f3NetWriteAllParams \f2switch\f1
(command line equivalent: none)
AVS saves only parameters that have been modified out to a network file.
Setting this option to \f3on\f1, will enable saving all parameters, as was the
default in AVS 2.  The default is \f3off\f1.
@.TP 4.5P
\f3Path\fP
(command line equivalent: \f3\-path\fP)
Specifies the directory tree in which AVS itself is installed.
@.TP 4.5P
\f3PrintNetwork \f2command\f1
(command line equivalent:  none)
The Network Editor's \f3Print Network\fP button normally sends
output to your default printer.  This lets you specify
an alternate print command to execute. The command should be a regular
shell command, such as:
@.pS
lpr -Plw2
@.pE
@.TP 4.5P
\f3ReadOnlySharedMemory \f2switch\f1
(command line equivalent:  none)
Shared memory is normally "read only."  Occasionally, the system
developer might wish to keep shared memory turned on, but allow
it to be written into.  Setting \f3ReadOnlySharedMemory 0\f1
accomplishes this.  The default is \f31\f1.
@.TP 4.5P
\f3Renderer "\f2string\f1"
(command line equivalent:  \f3-renderer "\f2string\f3"\f1)
Specifies which renderer will be the default selected in the
Geometry Viewer when the first camera window is created.  \f2"string"\f1 is
the literal name found on
the renderer buttons under the Geometry Viewer's \f3Cameras\f1
menu, usually either "Software Renderer" or "Hardware Renderer",
though other strings are possible.
It must match exactly, in spelling, case, and spacing.  The double
quote marks must be present.  Where
there is a hardware renderer available, \f3Renderer\f1
defaults to "Hardware Renderer".  If the user specified \f3NoHW 1\f1,
then only one renderer is available, the software renderer, and
this option is ignored.
@.TP 4.5P
\f3SaveMessageLog \f2switch\f1
(command line equivalent: none)
If set to the value \f3on\fP, causes the AVS message log
to be preserved when the AVS session ends normally.
By default, the message log (\f2/tmp/avs_message.log_\f(BIXXX\f1,
where \f(BIXXX\fP is the AVS process number) is deleted
automatically.
The log file is always preserved if AVS exits abnormally (e.g.
\f3Ctrl-C\fP interrupt, system crash).
@.TP 4.5P
\f3ScreenSize \f2XDIM\f1x\f2YDIM\f1
(command line equivalent: \f3size\f1)
Specifies the size of AVS's virtual display in pixels, confining
AVS to run within this area.  AVS scales its interface to fit
the virtual screen.
@.TP 4.5P
\f3SharedMemory \f2switch\f1
(command line equivalent:  \f3shm/noshm\fP)
Specifying \f3SharedMemory off\fP turns off AVS's shared memory
feature.
@.TP 4.5P
\f3SpaceballDevice \f2devicefilespec\f1
(command line equivalent:  \f3-spaceball\fP)
Indicates the serial communications port to which a Spaceball device
is attached (e.g. \f2/dev/tty1\fP).  If \f3Spaceball\fP is specified, AVS automatically
connects the Spaceball to the Geometry Viewer's rotate, translate,
and scale transformations.
@.eS
This entry also corresponds to the environment variable SPACEBALL.
Spaceballs may not be supported
on all platforms.
@.TP 4.5P
\f3StackSelector \f2option\f1
(command line equivalent:  none)
People who build very large networks sometimes find that the Network
Editor's control panel "overflows," making some of the module
buttons difficult to access, because the radio buttons take up too much
of the control panel.  Setting \f3StackSelector choice_browser\fP
displays the module names as a scrolling list similar to the
file browsers instead of as the default \f3radio_buttons\fP.
@.TP 4.5P
\f3VisualType \f2visualtype\f1
(command line equivalent:  none)
This command may be necessary when you are seeing less color rendition
than you know your display is capable of.
@.eS
AVS normally uses the X server's default visual.  Occasionally,
this is the wrong visual to use.  For example, the default may be set to
PseudoColor when there actually is a TrueColor visual available.
(The standard X Window System
command to list which
X visuals are available and which is being used as the default is
\f2xdpyinfo\f1.  This command may not be available on all platforms.)
@.eS
\f3VisualType\f1 lets you specify a \f2visualtype\f1, either
\f3PseudoColor\fP, \f3TrueColor\fP, or \f3DirectColor\f1.    AVS
will then search the X server's visual
list until it finds the first visual with the given visual type and
use it.
@.eS
You
can also specify an explicit visual using the string
\f3VisualID\f1 followed by a number \f2n\f1 that is the
decimal equivalent of the X server's hexadecimal visual id for the
visual you want to use.  For example:
@.pS K
VisualType  VisualID  41
@.pE
@.eS
This option may also be useful to people
using AVS from "X terminals."
@.eS
\f3Note:\f1  Poor color rendition may also be caused because your display is
using double buffering.  It may be using its 24 planes as two double-buffered
12 planes (or 12/6, or 8/4).  Turning off
double buffering on the Geometry Viewer's \f3Cameras\f1 submenu will
fix this, but you will see the object being drawn.
@.TP 4.5P
\f3WindowMgr \f2mgr\f1
(command line equivalent:  none)
This option ensures that the Network Editor's Layout Editor and
the X Window System window manager that you are using work
correctly together.  The default for this parameter is
specified in the \f2/usr/avs/runtime/avs.Xdefaults\f1 file.
The currently recognized values are:  \f3awm\f1, \f3mwm\f1 (Motif-style
window managers),
\f3twm\f1, \f3uwm\f1, \f3olwm\f1(Open Look), and \f3dxwm\f1(Dec XVI).  
@.TP 4.5P
\f3XWarpPtr \f2on\f1
(command line equivalent: none)
Causes the mouse cursor to be automatically moved ("warped") into
typein panels when they appear.  \f3XWarpPtr\f1 is off by
default.
@.SH AVS ENVIRONMENT VARIABLES
AVS uses the following environment variables.  Only DISPLAY
must be set correctly before AVS will work.
@.TP 6P
\f3AVS_ADAPT_TABLE \f2switch\f1
A block table is a data structure that maps field points' I, J, K
indicies
in an irregular field within a "block" of
X, Y, Z world space.  Modules such as \f3arbitrary slicer\f1 and
\f3probe\f1 use the block table to interpolate values at points
"on" their sampling surface, determining which  need to be mapped
as colored polygons.
@.eS
AVS normally builds a regular, evenly-dimensioned block table.  Where
data points are fairly uniformly spaced within the field, such a block
table provides efficient access to the I, J, K values in each block
of the grid\(emeach block has approximately the same number of points.
However, where data values are concentrated in some areas of the
field, but sparse elsewhere (e.g., the wing surface of the \f2bluntfin.fld\f1
dataset) search times in the dense blocks become much longer.
@.eS
An adaptive block table creates the block table as an octree.  Where
data values are dense, the block grid is divided and subdivided
again until each block contains only a short list of I, J, K values
to search through, improving performance.
@.eS
Adaptive block tables are slower to construct, but execute more rapidly
in the areas with dense grids.
People with irregular datasets where the distribution of data points
is uneven should try setting AVS_ADAPT_TABLE 1 to see if it improves
the performance of the \f3arbitrary slicer\f1, \f3threshold slicer\f1,
\f3streamline\f1, \f3particle advector\f1, \f3hedgehog\f1, \f3probe\f1, and 
\f3color geom\f1 modules.  AVS_ADAPT_TABLE is 0 (off) by default.
@.TP 6P
\f3AVS_GEOM_WRITE_V30 \f2switch\f1
A 1 value causes the Geometry Viewer's \f3Save Scene\f1 and
\f3Save Object\f1 functions
to save scenes and objects as Geometry Viewer Script Language \f2.scene\f1
and \f2.obj\f1 files, as occurred in AVS Release 3.0 and earlier,
rather than in a single CLI \f2.scr\f1 file.  It is provided for backward
compatibility.  It is 0 (off) by default.
@.TP 6P
\f3AVS_HELP_PATH\fP
Specifies one or more locations in the file system for AVS to use
when searching for on-line help files.
See Appendix D of the \f2AVS Developer's Guide\fP for more on this
variable.
@.TP 6P
\f3AVS_MEM_CHECK \f2switch\f1
@.sp 0
@.TP 6P
\f3AVS_MEM_HISTORY \f2switch\f1
@.sp 0
@.TP 6P
\f3AVS_MEM_VERBOSE \f2integer\f1
These three environment variables are all used by the alternate
memory allocation routines invoked with the include file
\f2/usr/avs/include/mem_defs.h\f1.  These routines replace the UNIX
standard memory allocation utilities such as \f2malloc\f1 with AVS
utilities that perform extensive dynamic memory allocation/deallocation
bug checking.  See the "Memory Allocation Debugging" section in the
"Advanced Topics" chapter of the AVS \f2Developer's Guide\f1 for
more information on these utilities.
@.TP 6P
\f3AVS_MG_TROFF \f2switch\f1
Causes the AVS Module Generator to generate its module man page
documentation templates in \f2troff\f1 format rather than the
default preformatted text man page using tabs and blanks.  This
option is 0 (off) by default.
@.TP 6P
\f3DIALS \f2devicefilespec\f1
Indicates the serial communications port to which a dialbox device
is attached.  Dialboxes may not be supported on all platforms.
@.TP 6P
\f3DISPLAY \f2host:server.screen\f1
(required)
Used by the X Window System to
indicate the display screen at which you're working.
@.TP 6P
\f3DISPLAYCLASS \f2string\f1
\f2string\f1 is used to specify an alternate
\f2/usr/avs/runtime/Xdefaults\f1 file, such as the supplied
\f2/usr/avs/runtime/Xdefaults.X\f1.  Also causes AVS to use
alternate \f2.avsrc.string\f1 startup files, both the default
in the \f2/usr/avs/runtime\f1 directory (no such alternative
is supplied with the release), and user \f2.avsrc\f1
files.  Both may be customized to make AVS behave differently
on different types of display hardware, such as an X terminal.
\f3-class\f1 is the command line equivalent.
@.TP 6P
\f3EDITOR\f1
The AVS Module Generator will use this common UNIX environment
variable's value as the default text editor that it will start
when you press the Module Generator's \f3Edit\f1 function.
@.TP 6P
\f3SPACEBALL \f2devicefilespec\fP
Indicates the serial communications port to which a Spaceball device
is attached.
Spaceballs may not be supported on all platforms.
\".TP 6P
@.\"\f3AVS_NUM_PROCS\f1
@.\"This environment variable only has meaning on Stardent ST3000VS
@.\"systems.  It controls how many of the system's parallel processors the
@.\"Dore graphics library will execute on.  (AVS uses Dore as its
@.\"underlying rendering package on Stardent "Titan" series
@.\"systems.)  The default is 1.
@.\".TP 6P
@.\"\f3DORE_ARGS\f1
@.\"(optional)
@.\"This environment variable only has meaning on Stardent "Titan" series
@.\"systems.  It controls some aspects of the Dore' graphics library
@.\"execution.  Specifically, it is the equivalent of the Dore' \f3DoDevice\f1
@.\"function call.  Its arguments are described in the "Device Driver"
@.\"appendix of the Stardent \f2Dore' Programmer's Guide\f1.  The
@.\"argument string should be enclosed in quotes with individual
@.\"arguments separated by semi-colons.
@.if n .Ee
@EOF

chmod 770 avs.6

exit 0



From gable@beta.lanl.gov (Carl W Gable)
Subject: field_math module for UCD data type
Message-ID: <1992Aug7.215021.13183@newshost.lanl.gov>
Keywords: field math UCD data 
Sender: gable@lanl.gov   
Organization: Los Alamos National Laboratory
Distribution: comp.graphics.avs
Date: Fri, 7 Aug 1992 21:50:21 GMT
Lines: 17

Has any one put togather a module which is like 
Field_Math that will work with UCD data type.
I want to be able to toggel between 
f(data) and f(log10(data)). Other mathematical operations
would be nice too.

Thanks for any help.
  
 
            Carl W. Gable
 
 E-mail  gable@lanl.gov
 Mail    MS F665, LANL, Los Alamos NM 87545
 Phone   505-665-3533
  




From gable@beta.lanl.gov (Carl W Gable)
Subject: UCD data, same structure different data 
Message-ID: <1992Aug7.215517.13851@newshost.lanl.gov>
Summary: UCD data, time dependent,  same structure different data
Keywords: field math UCD data 
Sender: gable@lanl.gov   
Organization: Los Alamos National Laboratory
Distribution: comp.graphics.avs
Date: Fri, 7 Aug 1992 21:55:17 GMT


I've been working with some UCD format files.  The UCD format first
contains information about the 'structure' of the data, that is the
node # associated with sets of x,y,z coordinates and then information
on connectivity of the nodes. The actual scalar or vector data
associated with each node comes last.

With the canned modules (read_ucd) every file has to have all the
structure information. Does anyone know of a module which allow one to
read new 'data' and associate it with a seperate 'structure' file. The
canned format results in excessive output when one has output at many
timesteps of a calculation and the structure information does not need
to be changed.


Thanks
Carl Gable

E-mail  gable@lanl.gov
Mail    MS F665, LANL, Los Alamos NM 87545
Phone   505-665-3533



From srinivas@lgc.com (Manapragada Srinivas)
Newsgroups: comp.graphics.avs
Subject: ANSI or C++ headers for AVS includes
Message-ID: <1992Aug8.173946.16813@lgc.com>
Date: 8 Aug 92 17:39:46 GMT
Sender: usenet@lgc.com
Organization: Landmark Graphics Corporation
Lines: 10
Nntp-Posting-Host: squirt.lgc.com


A while ago someone had posted about ANSI or C++ header version about the
avs include files, I would appreciate it very much if someone can direct me
to the ftp site where these may be available.

Thanks in adavnce,

Srinivas
--
Yonder, beyond the event horizon!


From dlc@convex.com (Dominique Le Corre)
Subject: New AVS module to read FITS files
Message-ID: <1992Aug10.125823.10989@convex.com>
Keywords: FITS, avs
 
Sender: usenet@convex.com (news access account)
Nntp-Posting-Host: convex1.convex.com
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
Date: Mon, 10 Aug 1992 12:58:23 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.
Lines: 11

Enjoy it.

D. LE CORRE
CONVEX S.A
9,Ave Ampere
78180 Montigny-le-Bx
France
E-mail : dlc@cvxfr.fr.convex.com (short term)





From dlc@convex.com (Dominique Le Corre)
Newsgroups: comp.graphics.avs
Subject: AVS module to read FITS files
Keywords: avs,fits
Message-ID: <1992Aug10.150426.16908@convex.com>
Date: 10 Aug 92 15:04:26 GMT
Sender: usenet@convex.com (news access account)
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
Lines: 20
Nntp-Posting-Host: convex1.convex.com
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

My last post got broken (sorry for the lost bandwith), so here
it goes again :

A new AVS module is available for astronomers at IAC (avs.ncsc.org).
This module, called read_fits, reads into an AVS field primary data,
image extensions, Ascii tables, fixed and variable length binary tables
from any HDU of a FITS formatted file. It can also display keywords
and table components in a text window. It handles byte, 16-bit integer,
32-bit integer, 32-bit real and 64-bit real data. It also supports complex
and double complex data for tables only in the text window.
It is based on the FITSIO package from W.D. Pence.

Enjoy it.

D. LE CORRE
CONVEX S.A
9,Ave Ampere
78180 Montigny-le-Bx
France
E-mail : dlc@cvxfr.fr.convex.com (short term)


From merritt@provolone.bchem.washington.edu (Ethan A Merritt)
Newsgroups: comp.graphics.avs
Subject: Problem with RGB byte ordering between AVS modules
Message-ID: <1992Aug10.195155.4648@u.washington.edu>
Date: 10 Aug 92 19:51:55 GMT
Sender: news@u.washington.edu (USENET News System)
Reply-To: merritt@u.washington.edu
Followup-To: comp.graphics.avs
Organization: University of Washington
Lines: 25


	I pulled the track_cursor module from avs.ncsc.org and modified 
it for use with a specific application.  However, I have the following
problem which I find very annoying.  I would greatly appreciate any
pointers from the net community.

	The area around the cursor is obtained using the call XGetImage(),
from which the (4 bytes per pixel) pixel array is copied to the data field
of the output (AVSfield_char) port.  All very well except that on my
DECstation this results in the RGB bytes being interpreted in reverse
order. It seems odd that copying from one window opened by AVS to another
window opened by AVS results in byte-inversion, but there you have it. I
know how I would fix this if it were going to be displayed in an X-window
which I opened myself, but I haven't a clue how to get AVS to stop
inverting the byte order when the "display image" module gets it. Anyone
have any ideas?

					    Ethan A Merritt
------------------------------------------------------------------------
---------
Dept of Biological Structure                H510 Health Sciences
University of Washington SM-20              (206)543-1421 or 543-8865
Seattle, WA 98195                           merritt@xray.bchem.washington.edu
------------------------------------------------------------------------
---------


From cohen@quartz.ciw.edu (Ronald Cohen)
Subject: non-cubic excavate_brick
Sender: usenet@granite.ciw.edu
Message-ID: <11Aug92.025755.7684@granite.ciw.edu>
Date: 11 Aug 92 02:57:55 GMT
Organization: Geophysical Laboratory, CIW
Lines: 9

I would like to do texture mapping like the excavate_brick module,
but onto a rhombus rather than a cube, i.e. a cube stretched along
one of its diagonals.  If I could strain the "brick" without
straining the field that would do the trick.  Any ideas or
modules out there that would do this?  Thanks,
-- 
Ronald Cohen
Geophysical Laboratory, Carnegie Institution of Washington
5251 Broad Branch Rd., N.W.,  Washington, D.C. 20015


From thorpe@doppler.ncsc.org (Steve Thorpe)
Subject: Archive of ftp site available
Message-ID: <BstpD4.9H6@doppler.ncsc.org>
Organization: North Carolina Supercomputing Center
Date: Tue, 11 Aug 1992 14:24:39 GMT

Hi AVSers,

Several people have been interested in downloading all the
modules on the International AVS Center's ftp site at once.
To make this easier, as of this morning there is a compressed 
archive of the entire site available for you to download, 
called ALL_OF_IT.tar.Z (see description below).  So for 
those of you hungry for modules, have fun!

Enclosed is a copy of AVS_README, a file describing the 
International AVS Center and how you can make use of it.

Take care,

-Steve
----------------------------------------------------------------
   Steve Thorpe, Application Visualization System Specialist
International AVS Center, North Carolina Supercomputing Center
PO Box 12889   3021 Cornwallis Rd, RTP, NC 27709   avs@ncsc.org
----------------------------------------------------------------
		Welcome to the International AVS Center


YOU MUST DOWNLOAD AND READ THE AVS_LICENSE FILE BEFORE MAKING USE OF THIS
ANONYMOUS FTP SITE OR ANY OF THE INTERNATIONAL AVS CENTER EMAIL FACILITIES!

****************************************************************************

	  INTERNATIONAL AVS CENTER OPENED OCTOBER 1, 1991 AT NCSC

    
    The AVS Consortium announced the opening of the new International
AVS Center at North Carolina Supercomputing Center in Research Triangle
Park, North Carolina.  The AVS Consortium is made up of seven AVS vendors
who are funding and providing direction for the International AVS Center.
The seven vendors are Advanced Visual Systems Inc., CONVEX Computer 
Corporation, Digital Equipment Corporation, IBM, Hewlett Packard Company, 
Sun Microsystems, and Wavetracer, Inc.  

    Non-consortium vendors who have AVS ported to their platforms are 
Cray, Evans and Sutherland, Kubota Pacific Computer Inc., Set Technology 
Corporation, and SGI.  Many of these are still in beta and will be made 
available in the future.

    The full functionality of the International AVS Center was not
available until January 1, 1992.  The Center was opened in several phases.
Phase I, which opened first, provides for ftp and email access to modules and
is primarily for submission of modules from the AVS Users.  There are several
hundred modules currently available and more will be added daily.  There
is construction for the porting facilities currently underway.  Initially
modules are available for CONVEX, Digital Equipment Corporation, IBM, Sun
Microsystems, and the Stardent Titan P3G3 (through 12/31/91).  As the 
hardware goes online, more ports are becoming available.  Rather than 
delay AVS User access to sharable code until porting was completed, it was 
decided to let them have access to what was available and let them do their 
own porting as needed until porting was completed on all platforms.

****************************************************************************

	        	     QUESTIONS AND ANSWERS

    If you ever have any questions,  please forward them to avs@ncsc.org.
The staff of the International AVS Center is here to support the AVS user
community as best we can.  

****************************************************************************

                              INTERNET NEWS GROUP

    AVS users should also be aware of the Internet news group 
comp.graphics.avs .  This news group provides a forum for general 
collaboration on all AVS topics between the entire AVS user community.

****************************************************************************

                                 AVS MAGAZINE

    The International AVS Center is publishing a quarterly magazine titled "AVS
Network News." This magazine discusses AVS related issues, has user articles, 
general information, etc.  These can be ordered from your AVS Vendor or by 
sending a check or money order to the Internation AVS Center.  The check should
be in the amount of $12.00 for an annual subscription, or $3.00 for a single 
issue.  Please add $0.75 per issue if outside of Continental USA.

        The International AVS Center
        PO Box 12889
        3021 Cornwallis Road
        RTP, NC 27709

****************************************************************************

                         INTERNATIONAL AVS USERS GROUP

     You can join the International AVS Users Group for a yearly fee of
$30.00 which includes subscription to the AVS magazine, the yearly AVS catalog
of modules ( user donated and commercial), a $50.00 reduction on attending the
yearly International AVS Users Group conference and have special rates for
additional services as they become available.  To join, send check or money
order for $30.00 ( add $5.00 if out of continental USA) to:

        The International AVS Center
        PO Box 12889
        3021 Cornwallis Road
        RTP, NC 27709

     The interim President of the AVS Users Group is Stephen Franklin
from the University of California at Irvine.  Stephen will be posting
notes to the AVS newsgroup comp.graphics.avs as well as provide guidance to
organizing local groups.  More information is forthcoming.

     There will be an additional fee for local user group memberships.

****************************************************************************

                   INTERNATIONAL AVS USERS GROUP CONFERENCE

    The 1st Annual International AVS Users Group Conference was held
February 11-13,1992 at the site of the International AVS Center : 
the North Carolina Supercomputing Center, Research Triangle Park, 
North Carolina.  The conference was titled : AVS '92 and is sponsored by the
AVS Consortium : AVS Incorporated, CONVEX Computer Corporation, Digital 
Equipment Corporation, Hewlett Packard Company, IBM, North Carolina 
Supercomputing Center, SET Technology, and Wavetracer, Inc.

Conference Overview :
	
        First International Users Group Conference
	          February 11 - 13, 1992

	Summary of events:

Keynote address:
	Attentive and Preattentive Processing in Visualization
	Richard Mark Friedhoff, Author of "Visualization:  The
	Second Computer Revolution"

Lectures:
	#1 - Fundamentals of Scientific Visualization by Jim
	Thomas, SIGGRAPH Chair, Battelle Pacific Labs

	#2 - Directions AVS Might Take:  A User Perspective by
	Richard Feldmann, NIH, Division of Computer Research
	and Technology.

	#3 - Tips and Tricks with AVS and Areas that are not
	documented by Larry Gelberg, AVS Inc.

	#4 - The AVS Module Generator by Larry Gelberg, AVS Inc.

	#5 - Future Plans for AVS and the International AVS
	Center by Ray Idaszek, NCSC and Dave Kamins, AVS Inc.

	#6 - Wide Area Information Servers: A Supercomputer on
	Every Desk by Brewster Kahle, Thinking Machines.

	#7 - The AVS Data Viewer by Larry Gelberg, AVS, Inc.

	#8 - The GenTools Distributed Computational-Genetics
	Program Suite by Jesse Driver, University of Texas,
	CHPC, Balcones Research Center.

	#9 - Full Motion Video over ETHERNET in an AVS Environment
	by Dan Winkelstein, MCNC Communications Division.

	#10 - The AVS Animation Application in AVS 3.5 by Ham
	Lord, AVS Inc.

	#11 - Distributed Visualization by Rick Franklin and Wade
	Smith, CONVEX Computer Corporation.

	#12 - Video Production in AVS by John Sheehan, AVS Inc.

	#13 - Overview of Implementing AVS on a Massively
	Parallel Machine by Edward Zyszkowski, Wavetracer Inc.

	#14 - The AVS Geometry Viewer Using AVS 3.5 by Jeff 
	Vroom, AVS Inc.

	#15 - VBASE:  Vector Database in AVS by Dennis Colomb.

	#16 - Chaotic System Tools in AVS by Mike Neacsu, NCSC.

	#17 - The Visualization Revolution by Wes Bethal, 
	Lawrence Berkeley Laboratory.

	#18 - Network Synamation:  An Integrated Environment for
	Distributed Computing by Meng H. Lean, Xerox Corporation,
	Webster Research Center.

Tutorials:

	#1 - Getting Started with AVS and Creating Networks

	#2 - Getting Started with the Geometry Viewer (AVS3.5)

	#3 - The Data Viewer

	#4 - The AVS Animation Application

	#5 - How to Write a Module in C using the Module Generator

Workshops:

	#1 - Chemistry using AVS by Richard Hedges, Polygen/MSI
	and Dave Kamins, AVS Inc.

	#2 - Visualizing Crystals with AVS by Don R. Jones, Erin
	N. Thornton, and Anthony Ness, Battelle Pacific Labs.

	#3 - Animation in AVS by Brian Kaplan, Indiana University
	and Ham Lord, AVS Inc.

	#4 - Imaging and GIS in AVS, Dennis Colomb.

	#5 - Crystal Viewer with AVS by Steve Bong, Crystal Imaging.

	#6 - Maple V Supporting AVS by Benton Leong, Waterloo Maple.

Panels:

	#1 - AVS as an Educational and Instructional Tool by Stephen
	Franklin, University of California, Irvine.

	#2 - AVS Developers and Porters Panel, led by David Bennett,
	International AVS Center and NCSC.

	#3 - Applications Panel led by Dennis Colomb.

	#4 - Virtual Reality by John Sheehan, AVS Inc.

	#5 - Distributed Computing Group led by Ray Idaszak, NCSC.

Videotapes:

	Videotapes of many of the presentations at AVS `92 will be
available from the International AVS Center after the final editing 
is completed.

****************************************************************************

                             GETTING MODULES

    There are currently two ways to obtain modules:

    	1.	Using standard ftp protocol.
	2.	Using the AVSemail request system

****************************************************************************

                              ANONYMOUS FTP

     The International AVS Center anonymous ftp site is located on the Internet 
at 128.109.178.23 .  If a name server is running, the server can be located 
as avs.ncsc.org .  When connected to the avs server, login as anonymous and 
provide your email address as the password.


WHAT YOU WILL FIND WHEN YOU LOG IN TO THE AVS SITE:

     When you login you will get a banner message that will provide some
basic information.  If you type ls -CF, you will then see the following:

ALL_OF_IT.tar.Z         COMP.GRAPHICS.AVS/      VolVis92/
AVS                     DATA/                   WHAT_IS_AVS
AVS_CATALOG             FAQ                     WHAT_IS_WAIS
AVS_CATALOG.dvi         FILTERS/                bin/
AVS_CATALOG.ps          MAPPERS/                dev/
AVS_FLATLINE            RENDERERS/              etc/
AVS_LICENSE             SAMPLE_DATA/            pub/
AVS_README              SUBMIT/                 usr/
AVS_USER_REG            SUBMIT_RELEASE

     THE INTERNATIONAL AVS CENTER GIVES NO WARRANTY, EXPRESSED OR
IMPLIED, FOR ANY SOFTWARE AND/OR DOCUMENTATION PROVIDED, INCLUDING,
WITHOUT LIMITATION, WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE.

     ALL_OF_IT.tar.Z is a compressed tar archive of the entire ftp
site.   It was approximately 20MB in size when initially created
(8/11/92), and will continue to grow.  If you want to grab all of the
modules from the ftp site at one time, download this file using binary
ftp.  Then use 'uncompress ALL_OF_IT.tar.Z', and 'tar xvf ALL_OF_IT.tar' 
to unpack all the files.  Keep in mind that after uncompressing, you
will be using about 3.5 times the disk space as when the file was
compressed.  

     AVS is an Archie place holder.

     The AVS_CATALOG provides a complete listing of current module holdings 
at the International AVS Center.  Its general format is as follows:


Name        : animate_file    Version      : 1.000     Mod Number : 1135
Author      : Terry Myerson, International AVS Center (NCSC)
Submitted   : 02/24/92        Last Updated : 02/24/92  Language   : C
Ported to   : DEC Kubota IBM Sun Convex
Description : anim_fname is used to output a series of filenames for input
              into a reader module. The module inputs an integer and a
              filename base, and output a filename in the form "$base.%3d".
              This module is very useful for a series of files containing a
              time series of data.

     AVS_CATALOG, AVS_CATALOG.dvi, and AVS_CATALOG.ps are three versions
of the module catalog maintained at this site.  All three files are 
continuously updated as new modules are added to the ftp site.  The ASCII 
version of the module catalog (AVS_CATALOG) can be retrieved at any time 
by mailing any message to an automatic response script at avsemail@ncsc.org
The AVS_CATALOG.ps and AVS_CATALOG files should be printable on any standard
postscript printing device.  The AVS_CATALOG.dvi file requires a dvi2ps 
utility to be of any use, but provides a much more portable compact format 
for the postscript catalog for those who have this utility available.
NOTE: The AWAIS module, available in the DATA directory on the ftp site,
provides interactive browsing of the module catalog.

     AVS_FLATLINE provides the same information in a format suitable for
some database programs.  The general format for the AVS_FLATLINE file is 
as follows:

animate_file:data_input:anim_fname is used to output a series of filenames for 
input into a reader module. The module inputs an integer and a filename base, 
and output a filename in the form "$base.%3d". This module is very useful for 
a series of files containing a time series of data.:Terry Myerson:International
AVS Center (NCSC):16:C:02/24/92: Kubota Convex DEC IBM Sun:02/24/92:1:1135

     The AVS_LICENSE is a file that provides the conditions under which
modules may be obtained and your agreements to share code with others.  You
must agree to the terms in order to use the International AVS Center repository
and all that it contains.  Its purpose is to ensure the sharing of everything
that has been donated and prohibit misuse of code that has been so generously
donated by others.  If you need a "special" arrangement, you must have a
release in writing from the International AVS Center.  We will contact the
donors and obtain their approval for special cases.  

     You are reading the AVS_README file.

     AVS_USER_REG is a form that can be filled in and sent electronically to
the International AVS Center for registration to various mailing lists,
including AVS User Groups, AVS Special Interest Groups, and a list that
automatically sends you all postings to the comp.graphics.avs newsgroup.
AVS_USER_REG contains detailed instructions on the lists available and where
to send it.

     If you know of anyone, whom does not have news access, they can
download the files in the COMP.GRAPHICS.AVS directory.  These files
are in the standard mailbox format so that anybody can peruse these
files using any mail utility with the -f command.

For example :

  Mail -f May_92

If a "message" in this mailbox is replied to, then a message is sent back
to the poster of the article - but it is not replied to the newsgroup.
The files will be stored in a separate mailbox for each month : May_92 June_92

     The SAMPLE_DATA directory is for data that has no associated
modules.  Many individuals have requested new or interesting sample data
and are also donating it.  It does not fit with the standard module
directories and so has its own directory.

     The FAQ, or Frequently Asked Questions file answers common 
questions about the International AVS Center and AVS in general.

     There are four main directories of modules: DATA, FILTERS, MAPPERS 
and RENDERERS.  These directories correspond to the four columns of modules 
within AVS.

     The SUBMIT directory is for module submissions.  This directory has
write permission and will be explained below in the submission section.
	
     The SUBMIT_RELEASE form is explained in more detail in the submission
section below.  Basically, we want you to agree to certain terms before 
making your submissions available to the public.  

     WHAT_IS_AVS is a several page overview of the AVS system.  
 
     WHAT_IS_WAIS is a several page overview of the Wide Area Information
Server system, and how you might want to use it to peruse through our
anonymous ftp site.

     Your first step, after reading this AVS_README file is to download
the AVS_LICENSE file and read it.  If you have any problem abiding by the
AVS Licensing Agreement, please send email to avs@ncsc.org or US mail to the
International AVS Center, po Box 12889, 3021 Cornwallis road, RTP, NC 27709.
We will try to deal with special circumstances as they arise on a one on one
basis.

USING STANDARD FTP PROTOCOL:

     There are only a few basic commands you will need to move around 
in the AVS directories and download or submit files.  Additional information
is available in your local man pages on ftp.  The first step is to "cd" to
the directory you are interested in such as "cd DATA".  You will receive a
message on how to proceed.  You should then "cd" to the module directory you
want such as "cd abekas".  You should change your settings as follows:  type 
"bin" at the prompt to change to binary mode; type "hash" at the prompt, this 
gives a # sign on your home device that shows you that things are working; type
"prompt" to get multiple files at one time.  There are only a few other 
commands that are general. You should know get and mget.  Typing "get filename" 
at the prompt will download any one file.  Typing "mget filenames" (or with 
wildcards *,?,etc) will get you several files at one time.  If you did not type 
the prompt command you will be asked yes/no for each file.  If you did type 
prompt you will not be prompted, ftp will just continue to download all files 
requested.  The reverse procedure is true when you want to submit modules using 
the put and mput commands ( more on submission later).  
                                            
     In this directory, you will find all of the files for a module.
These include the source code, scripts, networks, helpfiles, and makefiles. 
The Makefiles are named make.platform ( i.e. make.Convex, make.DEC )

     There is another ftp option available for getting a module that
you may find easier.  Suppose you want the module read_tiff, which is
located in the subdirectory DATA/read_tiff.  If you do the following
sequence of steps, you will wind up with a tar file containing all of
read_tiff's files in it:

	ftp avs.ncsc.org
	use anonymous for the userid
	use your userid for the password
	cd DATA
	binary
	get read_tiff.tar
	bye

Then on your local machine, use "tar -xvf read_tiff.tar" to restore
the files from the archive.  This method may take a while due to
the potentially large size of the tar file.  If you use
"get read_tiff.tar.Z" instead, you will get a compressed version of
the tar file, which should come over significantly faster due to
the smaller size.  Then on your local machine, use 
"uncompress read_tiff.tar.Z", followed by "tar -xvf read_tiff.tar"
to restore the files.

****************************************************************************

                               EMAIL FACILITIES

    It was determined that there were many users who did not have ftp
protocol on their system.  For those individuals an email procedure has
been set up.  There are three email addresses associated with the International
AVS Center.  These are avs@ncsc.org for questions/module submission, 
avsemail@ncsc.org for an automated information request, and avsorder@ncsc.org 
for automated module requests.  avsorder and avsemail are both explained below.
                   
   Mailing to avsemail@ncsc.org will automatically retrieve a response which 
includes this AVS_README file and also a current module catalog.

   Mailing to avsorder@ncsc.org will automatically retrieve module source codes.
Since some mail handlers have restrictions on the maximum size of 
a mail message, the modules that are requested will arrive in several
messages - one message per file per module.  Some modules that could be 
requested may also not be deliverable by email because of the size of 
individual files in that module.  These cases will be noted in the return 
email you receive.  Phase II will offer you option of receiving these files 
or any others via tape.  Construction is currently underway of porting 
facilities and as soon as hardware is installed, we will update this notice 
and provide instructions on how to request modules, data, etc. via tape.

    Note that you will need to remove the mail header lines after saving the 
files from within your mail system.  The title for each of a module
file's mail message will be of the form <module name>/<file name>, in
order to facilitate easier saving of these files.

HOW TO ORDER:

1.      First, review the modules available in the AVS_CATALOG

2.      Decide which modules you want.  Add a pound sign (#)
	to the beginning of each module number and make sure it is
	on a separate line of its own for each module ordered.

3.      Submit the order form.  The #module_number and name ( the # 
	is necessary in front of each module ordered with no spaces, 
	as #1037 ).

4.	When your order is filled out send it to "avsorder@ncsc.org",
	it will be processed immediately.  DO NOT send orders to 
	avsemail@ncsc.org or avs@ncsc.org.


        SAMPLE ORDER FORM:

*******************************************************************************
        I would like to order the following modules:

#1005 ( these lines are the module numbers)
#1023 ( NOTE that each entry must be on a separate line, this is required)
#1029 
#1130
..............You may order as many modules as you like as long as each is
..............on a separate line.


Thanks
John Doe
Smurfville, USA  (Full name and address is not required, just requested)

*******************************************************************************

        WHAT THIS ORDER FORM DID FOR YOU:
        
The #numbers order modules 1005, 1023 1129 and 1130 from the module list.
Each number told the automatic ordering service what you wanted in addition 
to the module source code.  Everything is automatic.  If you did not receive 
what you ordered, send email to avs@ncsc.org and we will correct the problem 
quickly. 

*******************************************************************************

BATCH TAPE REQUESTS:

	There is a $5.00 dollar shipping and handling fee for tapes ( $10.00
for shipping out of country and no insurance).  If you send your own tape
this is the only cost incurred.  If you wish us to use one of our tapes we
will charge you cost plus 15% for our ordering, stocking, etc costs.  This 
is still less than retail and is designed only as a cost recovery.  We are
not responsible for items damaged in transit.  Exact costs for tapes and 
handling will be determined when hardware is delivered and set up.  We will
post information as soon as it becomes available

*******************************************************************************

HOW TO SUBMIT MODULES:

	Donating a module to the International AVS Center benefits 
the entire AVS user community by facilitating further use of AVS to 
visualize complex scientific phenomena.  Any module that is not 
donated may be rewritten elsewhere - wasting someone's 
valuble time - hindering further development of other module 
capabilities for everyone's benefit.  

	There are three ways to submit modules:

	1.	Standard ftp protocol
	2.	email ( no binaries)
	3.	Sending tapes to:	The International AVS Center
					P.O. Box 12889              
					3021 Cornwallis Road
					RTP, NC 27709  
	
	There is a SUBMIT_RELEASE file that can be found when you login. 
It has the terms you agree to by submitting a module to the International 
AVS Center.  It tells us that we have permission to share these modules 
and associated files with others and that there are no known viruses in 
the code.  This will ensure that the there are no other claims from 
universities, individuals, companies, etc.  If you cannot meet these 
conditions because of special circumstances ( e.g. government lab, etc.,
please email to avs@ncsc.org and we will make special arrangements on an      
individual basis).  
                                                                           
	Several individuals have said they would contribute, but from 
past experience they knew they would be bombarded with questions about the 
code and did not have the time to spend replying to these questions.  If 
you are in this situation, we will put a unique control number in the code 
and the International AVS Center will act as the only contact between you 
and the world.  Many of the questions will be fielded by the AVS staff, 
but if a question cannot be answered internally, you will only be contacted 
by the center and not hundreds of individuals.    
                                                                             

*******************************************************************************

STANDARD FTP SUBMISSION:


	 If you have arrived at this point it is assumed that you know the
ftp site name (avs.ncsc.org).  The IPnumber will be changing shortly as
we move to a larger server, so be prepared for this number to change in the
near future.  We will post it later.

        When you login you will get a banner message that will provide some
basic information.  You will then see the following:

.login                  COMP.GRAPHICS.AVS/      WHAT_IS_AVS
AVS                     DATA/                   WHAT_IS_WAIS
AVS_CATALOG             FAQ                     bin/
AVS_CATALOG.dvi         FILTERS/                dev/
AVS_CATALOG.ps          MAPPERS/                etc/
AVS_FLATLINE            RENDERERS/              pub/
AVS_LICENSE             SAMPLE_DATA/            usr/
AVS_README              SUBMIT/
AVS_USER_REG            SUBMIT_RELEASE


	Most of the files and directories have been explained above, except
the SUBMIT directory.  The SUBMIT directory is the only one that has write
permission.  In order to provide a minimum level of security to those who
donate modules, and try to make sure others do not accidentally copy over their
files, and to streamline the process of adding your module to the catalog,
we ask you to follow the following procedures.

	Please prepare your submission to conform to the following guidelines
as closely as you can:
	1.	all C source code should have a .c suffix
	2.	all FORTRAN source code should have a .f suffix
	3.	all C header files should have a .h suffix
	4.	all FORTRAN header files should have a .inc suffix
	5.	provide one file with a .txt suffix for each AVS
		module, in plain text format, which provides complete
		documentation for the module
	6.	provide a sample AVS network file, with a .net suffix
	7.	do not include assembly language code

	When you "cd" to the SUBMIT" directory, a banner message will appear
that will prompt you with instructions.  You will be asked to create a
directory using mkdir as in "mkdir myname".  This directory will be  invisible 
and entry into this directory can only be achieved by typing "cd myname".
When someone else logs in, they will see nothing, unless they know the name and
unique number identifier.  After you "cd" to your new directory you will be able
to donate modules using standard ftp protocol.  Detailed information is 
available in the ftp man pages, but you will only need to know a few basic
commands such as bin, hash, prompt, put and mput. to donate your modules.

	You should create additional directories for each module using "mkdir".
If you are submitting multiple modules, please use "mkdir mynameN", where
N would be a unique number for each module being submitted.
You should type "bin" at the command line to change to binary format, then
type "hash" at the command line to show a # sign on your local machine that 
tells you things are working.  You should then type prompt if you have 
more than one file as this lets you download multiple files at one time
using mput without waiting for the prompt yes/no command.  Then type the
command "put myfile" or "mput myfiles" at the command line and they will
download to the new directory you have created.  We prefer and recommend
that all files submitted are only straight ASCII files, although if your 
files are in tar or tar.Z format, we will accept them.

	If you logout and wish to make a change, you must remember the 
unique name for the invisible directory you were given or else start all
over again.


*******************************************************************************

EMAIL SUBMISSION:

	We will accept email submissions to avs@ncsc.org, but ask you follow
these guidelines.

	Do not include any binaries.  If data files are large, put in uucp
format or provide a smaller data file with a note that larger files are 
available.  We will contact you to try to arrange obtaining these larger
files through other methods.  Please do not send data files over 200K.
Separate all files by a line of at least twenty (20) asterisk marks (*) so 
we can search for these easily.  

	Your first lines should describe the module, the platform it has
been ported to and special notes such as large data size, followed by *'s.


*******************************************************************************


BATCH TAPE SUBMISSION:

	To submit a module via tape, put it onto a tape
using "tar -cvf tapedrive filename[s]".  Label the tape with the
appropriate platform the module runs on (and the platform the tape
was made on, if different), and mail it to us at:

        The International AVS Center
        PO Box 12889
        3021 Cornwallis Road
        RTP, NC 27709

*******************************************************************************


A COPY OF THE FREQUENTLY ASKED QUESTIONS (FAQ) FILE:


       ___________________________________________________________________
                                       FAQ
                        Frequently Asked Questions of the
                            International AVS Center
                      North Carolina Supercomputing Center
       ___________________________________________________________________

	Questions answered in this file :
	---------------------------------

1.	 What is the International AVS Center ?
2.	 Where is the International AVS Center ?
3.	 What is AVS ?
4.	 Where can I get more information on AVS ?
5.	 What are the system requirements to run AVS ?
6.	 How do I download modules from the International AVS Center,
	 or submit modules, or get a list of the currently available
	 modules ?
7.	 When I try to run AVS on a remote machine and display the output
	 on an X server, I get a message saying Client unauthorized to
	 connect to server. How do I fix this ?
8.	 Is there sample AVS data available ?
9.	 When I try to ftp to avs.ncsc.org, I get terminated before I get
	 connected. What am I doing wrong ?
10.	 What is the procedure to add a question to this FAQ file ?
11.	 Why should I submit a module to the International AVS Center ?
12.	 Where can I find more information on AVS in published
	 literature ?
13.	 What is WAIS and how can I use it at the International AVS Center ?

What is the International AVS Center:what_is_iac:
 ___________________________________________________________________ 

1.	 What is the International AVS Center ?

        The International AVS Center serves as a catalyst
for expanding the AVS user base and for increasing AVS
functionality by fostering discipline-specific module
development and new AVS uses.  Located at the North Carolina
Supercomputing Center, the worldwide clearinghouse collects,
ports, and distributes user-contributed, public-domain
modules and acts as liason between users and vendors.
The International AVS Center also publishes a quarterly
magazine called AVS Network News and a yearly module
catalog.  It also hosts the yearly International AVS
User Group conference and coordinates User Group activities.

        The AVS Consortium is made up of seven AVS vendors
who are funding and providing direction for the International
AVS Center.  The seven vendors are Advanced Visual Systems Inc.,
CONVEX Computer Corporation, Digital Equipment Corporation,
IBM, Hewlett Packard Company, Sun Microsystems, and Wavetracer, Inc.
Where is the International AVS Center:where_is_iac:
 ___________________________________________________________________ 

2.	 Where is the International AVS Center ?

        The International AVS Center is located at the
North Carolina Supercomputing Center.  The anonymous ftp
site for the center is located on the internet at avs.ncscs.org
with an IP address of 128.109.178.23 .  The main email alias
for the center is avs@ncsc.org .
What is AVS:what_is_avs:
 ___________________________________________________________________ 

3.	 What is AVS ?

        Using anonymous ftp to avs.ncsc.org, you can then
get the file What_is_AVS.  Take a look at this file
for a good summary of what AVS does.
Where can I get more information on AVS:where_info_avsinc:
 ___________________________________________________________________ 

4.	 Where can I get more information on AVS ?

        If this file and other files available via anonymous
ftp to avs.ncsc.org do not answer your questions, you can
send mail to avs@ncsc.org.  The International AVS Center
will do its best to help you out.  You also may want to
monitor and/or post articles to the Internet newsgroup
comp.graphics.avs, which has an ongoing dialog between
various AVS users.  Or you can contact AVS Inc. directly at:

        Advanced Visual Systems Inc.
        300 Fifth Ave.
        Waltham, MA  02154
        USA

        Tel: 617-890-4300
        Fax: 617-890-8287
What are the system requirements to run AVS:sys_req:
 ___________________________________________________________________ 

5.	 What are the system requirements to run AVS ?

Numerous people have requested AVS configuration information.
This information changes regularly and you should contact either
AVS Inc at 617-890-4300, your local vendor reps or AVS Inc reps
for additional information.

CONVEX - Available now - CONVEX OSV9.1 or later release, CONVEX
OS Utilities 9.1 or later, CONVEX OS Internet Services V9.1 or
later, IEEE floating point hardware.  Requires approximately
90MB disk space, and a color display device networked to your
CONVEX system supporting X window System Version 11 Release 4
color server, which supports either a PSEUDOCOLOR or TRUECOLOR
visual type, or a Silicon Graphics workstation running IRIX 4.0
or a workstation or terminal with a PEX server.

DEC - Available now - DEC AVS V3.0 generates PEX V4.0 protocol
(when displaying to a PEX V4.0 cpable display server), and is
compatible with ULTRIX V4.2 which includes a PEX V4.0 server.
ULTRIX V4.2A includes a PEX V5.0 server.  For compatiblitiy with
that server, DEC AVS V3.0A has been released.  Note that
PEX V5.0 provides (two pass) transparency.  Also note that
the ULTRIX V4.2A distribution does include a PEX compatibility
kit which is essentially a PEX V4.0 server.  There is no support
for runing both PEX V4.0 and PEX V5.0 servers concurrently.  Only
one such server can be run at any one time.

Hewlett-Packard - Available now - HP 9000 series 700,
CRX graphics (call for information on other graphic configurations),
OS release 8.01 or later ( 'uname -r' to get OS level), Phigs runtime
will be required for systems using H/W rendering, 16 MB memory
minimum, 32 MB recommended, installation uses about 40 MB disk,
CRX will use the S/W renderer ( others will support H/W rendering
when appropriate), monochrome is not supported.

IBM - Available now - RS6000 workstations, models 3xx, 5xx or
7xx, 8-bit Color Graphics Display adapter, High Performance 3D
24-bit Color Graphics Processor with Z buffer option, GTO 3D 24-bit
Graphics adapter with Z buffer (a.k.a. Supergraphics Subsystem),
(call for information on other graphic configurations), AIX release
3.1.5 w/2006 patch tape and APAR#: a19758 (X server), use
command 'lslpp -h bos.obj' which should show release
03.01.0006.0008 as active, use command 'lsdev -C -c adapter' to see
graphics configuration, 16 MB memory minimum, 32 MB
recommended, installation uses about 40 MB disk, hardware
rendering is only on 24-bit Z buffered systems, specify SW
renderer on all systems without 24-bit Z buffering, AIX 3.1.5
X server is limited to 8-bit pseudocolor visuals, images are then dithered.

SUN - Available now - Sun SPARC workstations 1, 1+, 2 supporting
the sun4/sun4c applications architecture, 8-bit frame buffers (GX,
CG3, etc), GS and GT graphics after OpenWindows version 3 is
available from Sun ( first quarter 92), Sun OS 4.1.1 w/ 100299-01
patch or later, use command /usr/etc/showrev to get revision
levels, 8-bit frame buffers require OpenWindows version 2 with
X server installed, 16 MB minimum, 24 or 32 MB recommended,
installation uses about 38 MB disk, strongly recommend
increasing shared memory segment and swap space size per
release notes, 8-bit graphics boards ( GX, CG3, etc) always uses
S/W renderer, H/W rendering systems will use XGL graphics, S/W
render also available

Wavetracer - to provide users with logical and uniform access
to Wavetracer's three-dimensional and massively parallel Data
Transport Computer (DTC) and advanced software tools, AVS modules
are currently being ported to make use of the DTC.  The DTC
is a three dimensional, massively parallel computer.  It has
a 3D computing architecture, high data capacity and bandwidth,
high I/O bandwidth, ultra finegrained parallellism and low cost
of ownership.  It easily connects to a host UNIX workstation
via an industry-standard SCSI interface.  The processing
resources of the DTC are integrated into the host's software
and network environment by multiC, a powerful data-parallel
extension of ANSI C.
How do I download modules from the International AVS Center, or submit modules, or get a list of the currently available modules:how_download:
 ___________________________________________________________________ 

6.	 How do I download modules from the International AVS Center,
	 or submit modules, or get a list of the currently available
	 modules ?

        There is an AVS_README file which should answer
these and many other questions for you.  To obtain a
copy of this file, there are two methods currently
available and a third method under development.  Mail
sent to avsemail@ncsc.org will automatically retrieve
a response which includes the AVS_README file and
also a current module catalog.  Or you can ftp to
avs.ncsc.org, login with anonymous as your userid and
your own userid as the password, and get the AVS_README
file and the AVS_CATALOG file from there.  For those users
without ftp capability, there is a tape ordering system
being developed at the International AVS Center.
When I try to run AVS on a remote machine and display the output on an X server, I get a message saying Client unauthorized to connect to server.  How do I fix this:x_help:
 ___________________________________________________________________ 

7.	 When I try to run AVS on a remote machine and display the output
	 on an X server, I get a message saying Client unauthorized to
	 connect to server. How do I fix this ?

        The xhost command will let your server know its
OK for your remote machine to display there.  In the
file read in when you boot up X (for example, on a Titan
.xsession, on a Sun .xinitrc), add the line:

        xhost <Client1 machine name> <Client2 machine name> ...
Is there sample AVS data available:sample_data:
 ___________________________________________________________________ 

8.	 Is there sample AVS data available ?

        Using anonymous ftp to avs.ncsc.org, you can then
cd to AVS_SAMP_DATA.  This directory is for sample data that
has been donated without any modules.  No tests have been made
on this data, so use it at your own risk.  This is simply to
allow you to get your hands on a variety of different data types
for experimentation purposes.
When I try to ftp to avs.ncsc.org, I get terminated before I get connected.  What am I doing wrong:ftp_help:
 ___________________________________________________________________ 

9.	 When I try to ftp to avs.ncsc.org, I get terminated before I get
	 connected. What am I doing wrong ?

        Possibly your host machine isn't a registered
internet site.  In such a case, the IP address can't be
mapped by our machine into a valid hostname.  Speak to the
person in charge of your network about making sure it is
correctly registered.
What is the procedure to add a question to this FAQ file:add_faq:
 ___________________________________________________________________ 

10.	 What is the procedure to add a question to this FAQ file ?

        Please submit your suggestion for this FAQ file via
email to avs@ncsc.org.  Your question and answer will quite possibly
show up in this file shortly thereafter.
Why should I submit a module to the International AVS Center:why_submit:
 ___________________________________________________________________ 

11.	 Why should I submit a module to the International AVS Center ?

        Donating a module to the International AVS Center benefits
the entire AVS user community by facilitating further use of AVS to
visualize complex scientific phenomena.  Any module that is not
donated may be rewritten elsewhere - wasting someone's
valuble time - hindering further development of other module
capabilities for everyone's benefit.
Where can I find more information on AVS in published literature:references:
 ___________________________________________________________________ 

12.	 Where can I find more information on AVS in published
	 literature ?

Here is a short (no doubt incomplete!) reference list:

Upson, Craig, Thomas Faulhaber, Jr., David Kamins, David Laidlaw,
David Schlegel, Jeffrey Vroom, Robert Gurwitz and Andries van Dam.
"The Application Visualization System:  A Computational Environment
for Scientific Visualization."  IEEE Computer Graphics and Applications
(July 1989), Vol.9, No.4, pp 30-42.

Currington, I., Coutant, M., "AVS - A Flexible Interactive Distributed
Environment for Scientific Visualisation Applications", Second
Eurographics Workshop on Visualization in Scientific Computing, April,
1991

VandeWettering, "The Application Visualization System - AVS 2.0",
PIXEL, July/August, 1990

Garrity, M., "Raytracing Irregular Volume Data", San Diego Workshop
on Volume Visualization, Dec, 1990

Gelberg, L., Kamins, D., Vroom, J., "VEX: A Volume Exploratorium",
Chapel Hill Workshop on Volume Visualization, May 1989

Gelberg, L., et al, "Visualization Techniques for Structured and
Unstructured Scientific Data", Course Notes, SIGGRAPH '90 Course
"State of the Art in Data Visualization"

Mathias, C., "Visualization Techniques Augment Research into Structure
of Adenovirus", Scientific Computing & Automation, April, 1991

Parker, D., Lin, Y., "The Application Visualization System for Finite
Element Analysis", Banff Conference on FEA, May, 1990

Upson, C., "Scientific Visualization Environments for the
Computational Sciences", Proceedings of the 34th IEEE Computer Society
International Conference - Spring, 1989

Craig Upson, "Tools for Creating Visions," UNIX REVIEW,
Vol.8, No.8, pp. 39-47.

Calvert, Brian "Interactive Analysis of Multidimensional Data", Masters Thesis
University of Illinois Department of Computer Science, 1991.
What is WAIS and how can I use it at the International AVS Center:what_is_wais
 ___________________________________________________________________ 

13.	 What is WAIS and how can I use it at the International AVS Center ?

There is now a WAIS (Wide Area Information Servers) server running
at the International AVS Center.  WAIS allows a user to ask
a question to a server, which provides a ranked list of documents
that may help answer that question.  The user can then peruse
through the documents that seem useful.  

All of the .txt files for AVS modules freely available on the 
International AVS Center's anonymous ftp site have been indexed, 
as well as informational files such as AVS_README and FAQ.  
WAIS should prove more and more useful as the AVS module repository
becomes larger.  It provides a convienient interface to large amounts
of data.

For a more thorough discussion of WAIS and how you can use it
to peruse the files at the International AVS Center, please check 
the file WHAT_IS_WAIS on avs.ncsc.org.
*******************************************************************************



From dlc@convex.com (Dominique Le Corre)
Subject: Re: Problem with RGB byte ordering between AVS modules
Message-ID: <1992Aug11.143929.1993@convex.com>
Sender: usenet@convex.com (news access account)
Nntp-Posting-Host: convex1.convex.com
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
References: <1992Aug10.195155.4648@u.washington.edu>
Date: Tue, 11 Aug 1992 14:39:29 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.
Lines: 11

In article <1992Aug10.195155.4648@u.washington.edu> merritt@u.washington.edu writes:
>
>	The area around the cursor is obtained using the call XGetImage(),
>from which the (4 bytes per pixel) pixel array is copied to the data field
>of the output (AVSfield_char) port.  All very well except that on my
>DECstation this results in the RGB bytes being interpreted in reverse
>order.
I would suspect this has to do with little/big Indian.
Anyway, I've got no explanation, but a workaround:
Feed your image into 3 extract scalars (R,G,B), and then back into combine
scalars, crossing the R & B ports.


From merritt@provolone.bchem.washington.edu (Ethan A Merritt)
Subject: Re: Problem with RGB byte ordering between AVS modules
Message-ID: <1992Aug11.172034.23919@u.washington.edu>
Sender: news@u.washington.edu (USENET News System)
Reply-To: merritt@u.washington.edu
Organization: University of Washington
References: <1992Aug10.195155.4648@u.washington.edu> <1992Aug11.143929.1993@convex.com>
Date: Tue, 11 Aug 1992 17:20:34 GMT
Lines: 41


In article <1992Aug11.143929.1993@convex.com>, dlc@convex.com (Dominique
Le Corre) writes:
|> In article <1992Aug10.195155.4648@u.washington.edu> I wrote:
|> >
|> >	The area around the cursor is obtained using the call XGetImage(),
|> >from which the (4 bytes per pixel) pixel array is copied to the data field
|> >of the output (AVSfield_char) port.  All very well except that on my
|> >DECstation this results in the RGB bytes being interpreted in reverse
|> >order.
|> I would suspect this has to do with little/big Indian.
|> Anyway, I've got no explanation, but a workaround:
|> Feed your image into 3 extract scalars (R,G,B), and then back into combine
|> scalars, crossing the R & B ports.

	Ugh. The mind reels at the wasted CPU cycles and memory usage
(remember that the cursor tracker is in a for(1) {...} loop!). I can do
much better than that by simply inverting the bytes per brute force inside
the track_cursor module.  Even that is a distasteful waste of CPU cycles
though, especially since the image display module is apparently going to do
it all over again just to get back where I started.

        Perhaps I was too terse in my original complaint.  I know perfectly
well that the problem is in whether the byte order is little/big endian.  I
also know that there is a field in the XImage structure which describes this.
The problem is that the AVSfield_char structure _doesn't_ have such a field
(that I can see anyway) so I can't pass this information on with the data.
Others have suggested that I check the .../avs/port.h header for correctness,
but this is a red herring (I think).  The data is perfectly consistent inside
the module I'm compiling; it's after it goes out the output port that I'm
unhappy with its treatment!

Let me try again, with a more specific request:

Anyone know how to either (1) specify which endedness an XImage structure
will have upon return from XGetImage, or (2) persuade the internal AVS
display image modules to use a particular endedness, or (3) use some
entirely different mechanism for cursor_tracking?

					still head-scrathing,
					Ethan A Merritt


From larryg@avs.com (Larry Gelberg)
Subject: Re: Problem with RGB byte ordering between AVS modules
Organization: Advanced Visual Systems Inc.
References: <1992Aug11.172034.23919@u.washington.edu>
Message-ID: <1992Aug11.205505.24701@ctr.columbia.edu>
Sender: news@ctr.columbia.edu (The Daily Lose)
X-Newsreader: Tin 1.1 PL4
Date: Tue, 11 Aug 1992 20:55:05 GMT
X-Posted-From: phobos.avs.com
X-Posted-Through: sol.ctr.columbia.edu
Lines: 19

Here's an answer that you're probably not going to be happy with:
(This is verbatim from John Langner, who always speaks the truth)

"The "display image" module always expects images in the same order:
	4 bytes per pixel A, R, G, B

It does any necessay conversion from this standard order to 
whatever the particular X server requires."

AVS images are the same from machine to machine regardless of 
endieness.  This decision was made for compatibility reasons,
not (obviously) performance ones.

larryg
--
=== Larry Gelberg ============================ larryg@avs.com =======
      Advanced Visual Systems Inc. (AVS Inc.)
      300 Fifth Ave, Waltham, MA 02154
===== Tel: 617-890-4300 = Fax: 617-890-8287 =========================


From drj@lhdsy1.lahabra.chevron.com (Dave R. Jones)
Newsgroups: comp.graphics.avs
Subject: Developers AVS and DEC???
Keywords: Licensing, platforms
Message-ID: <5943@lhdsy1.lahabra.chevron.com>
Date: 11 Aug 92 22:54:35 GMT
Organization: Chevron, La Habra, CA
Lines: 30


              Developers AVS vs. DEC AVS
              --------------------------
I would like to pose a question to AVS Inc. and DEC.

Are there any plans to include DEC AVS in the plan for distributing
AVS as part of the Delopers AVS Licensing scheme???

Right now, AVS Inc is offering a developers package for AVS which allows
a developer to create runtime only licenses for AVS. The initial package
allows the creation of 5 licenses and additional licenses are $3000/ seat.

Unfortunately, DEC is NOT one of the platforms that these licenses can be
created for and we support several different type of platforms
in our organization including DEC.

Is this arrangement going to require us to make a separate arrangement with
DEC concerning licensing on their platforms. This situation will make AVS
cost prohibitive on platforms in the field and most likely, discourage
users from selecting the DEC platform in the field.

I have asked this question in this newsgroup before in a less direct manner
and got no response from either AVS or DEC in this newsgroup.

Is anyone listening???

-- 
  David R. Jones                                      drj@chevron.com
  Chevron Oil Field Research Co.                      (310) 694-7105
  SCUBA.... KAYAKING.... Parallel Processing....   What more is there?


From fredv@hydra.acs.uci.edu (Fred Velijanian)
Subject: Re: Developers AVS and DEC???
Nntp-Posting-Host: hydra.acs.uci.edu
Message-ID: <2A888F35.16791@noiro.acs.uci.edu>
Newsgroups: comp.graphics.avs
Organization: University of California, Irvine
Keywords: Licensing, platforms
Lines: 42
Date: 12 Aug 92 04:10:29 GMT
References: <5943@lhdsy1.lahabra.chevron.com>

In article <5943@lhdsy1.lahabra.chevron.com> drj@lhdsy1.lahabra.chevron.com (Dave R. Jones) writes:
>
>              Developers AVS vs. DEC AVS
>              --------------------------
>I would like to pose a question to AVS Inc. and DEC.
>
>Are there any plans to include DEC AVS in the plan for distributing
>AVS as part of the Delopers AVS Licensing scheme???
>
>Right now, AVS Inc is offering a developers package for AVS which allows
>a developer to create runtime only licenses for AVS. The initial package
>allows the creation of 5 licenses and additional licenses are $3000/ seat.
>
>Unfortunately, DEC is NOT one of the platforms that these licenses can be
>created for and we support several different type of platforms
>in our organization including DEC.
>
>Is this arrangement going to require us to make a separate arrangement with
>DEC concerning licensing on their platforms. This situation will make AVS
>cost prohibitive on platforms in the field and most likely, discourage
>users from selecting the DEC platform in the field.
>
>I have asked this question in this newsgroup before in a less direct manner
>and got no response from either AVS or DEC in this newsgroup.
>
>Is anyone listening???
>
>-- 
>  David R. Jones                                      drj@chevron.com
>  Chevron Oil Field Research Co.                      (310) 694-7105
>  SCUBA.... KAYAKING.... Parallel Processing....   What more is there?

Last week DEC announced that they are making DEC AVS available
from AVS Inc. I don't have the press release, but it sounded like
AVS Inc. will continue development of all versions (Ultrix, OSF/1 and
VMS) in the future. No idea if we can still buy it from DEC directly.
So if/when this goes through, I suppose, AVS Inc will provide the
same licensing scheme as other platforms.

Fred Velijanian
UC Irvine
fredv@uci.edu


From gzc@gserv1.dl.ac.uk (G. Coulter,office,extension,homephone)
Newsgroups: comp.graphics.avs
Subject: AVS Mesh.....
Message-ID: <1992Aug12.113714.8042@gserv1.dl.ac.uk>
Date: 12 Aug 92 11:37:14 GMT
Sender: news@gserv1.dl.ac.uk (netnews)
Reply-To: gzc@gserv1.dl.ac.uk
Organization: Daresbury Laboratory, UK
Lines: 18

Keywords:

I am trying to visualize a set of fluid dynamic data representing super-sonic airflow.
The problem that I have is how to generate a 3D representation of the data. The data format is (2D field irregular float). Now if I feed this into FIELD_TO_MESH I just
get a plane representing the data, with color coding representing the data points. 
What I really want is somehow to extrude the data values to represent the "Z" value
of the data. This can be done in a sort of round about way by first converting the
field from irregular to uniform using a module such as IRREG_2_REG by Wes Bethel.
Passing the result through FIELD_TO_MESH then produces a desirable result but means
that the resulting data has been stripped of the all important coordinate grid
information. 

Any help would be great, even if its a totally different way of doing the whole thing.
Overall result similar 3D representation as FIELD_TO_MESH on uniform 2D field but
using irregular data.

Thanks:   Gary Coulter..
Reply to: gzc@uk.ac.daresbury


From hsingh@Turing.chem.uh.edu (Harpreet Singh)
Newsgroups: comp.graphics.avs
Subject: Help required in getting a multiple selection file or text browser
Message-ID: <1992Aug12.195814.5682@menudo.uh.edu>
Date: 12 Aug 92 19:58:14 GMT
Sender: usenet@menudo.uh.edu (USENET News System)
Organization: Dept. of Chemistry
Lines: 19
Nntp-Posting-Host: turing.chem.uh.edu


Hi geniuses
	I wanted to know if there is any way in AVS that you can have
a string browser in which you can select multiple lines. (Eg. a 
file browser in which you can select multiple files at the same
time). 
	I want to have such a menu so that multiple displays can be 
displayed letting the user know which ones are being shown and which
are not.

Hope you get my problem.

Thanks
Harpreet
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%   Harpreet Singh                      e-mail: hsingh@hobbes.chem.uh.edu  %
%   @University Of Houston              v-mail: (713) 748-7292             %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


From aboulang@bbn.com (Albert Boulanger)
Newsgroups: comp.graphics.avs
Subject: Xnetlib idea for AVS
Message-ID: <ABOULANG.92Aug12163938@tiryns.bbn.com>
Date: 12 Aug 92 23:39:38 GMT
Reply-To: aboulanger@bbn.com
Organization: BBN, Cambridge MA
Lines: 269
NNTP-Posting-Host: tiryns.bbn.com


 
I thought the Xnetlib tool was really neat. Does anybody have a desire
to do something like that for the AVS archive? It would be neat to do
something like this in AVS itself!

Here is the readme for Xnetlib:




     xnetlib(2.0)               (11 Mar 92)               xnetlib(2.0)



     NAME
          xnetlib - an X interface to netlib

     DESCRIPTION
          Xnetlib is a new version of netlib recently developed at the
          University of Tennessee and Oak Ridge National Laboratory.
          Unlike netlib, which uses electronic mail to process
          requests for mathematical software, xnetlib uses an X Window
          graphical user interface and a socket-based connection
          between the user's machine and the xnetlib server machine to
          process software requests.  Xnetlib is available to anyone
          who has access to the TCP/IP Internet.

     INSTALLATION
          To install type:

          % xmkmf

          % make

          and

          % make install

          or, perhaps more likely

          % cp xnetlib ~/whereEverYou/Want/it/bin

          Xmkmf uses imake to create a makefile from the provided
          imakefile.  Both xmkmf and imake should be installed on your
          system as part of the X distribution, so if you get an error
          on the xmkmf command talk to your system manager or check
          your command search path.  As a last resort, you might also
          try editing Makefile.std as necessary and typing 'make -f
          Makefile.std'.

          The Xnetlib.res file contains some resources you may want to
          edit and include in your .Xdefaults or .Xresources file.
          See also the postscript map of xnetlib resources,
          resourcemap.ps.  (Note: there are reports that
          resourcemap.ps wont print on some older printers, we are
          working on a fix for this.)

          To run xnetlib type:  % xnetlib

          (The Athena Widget set is required to build xnetlib.)

     OPERATION
          Each time xnetlib starts up it contacts the netlib server at
          Oak Ridge National Laboratory, (surfer.epm.ornl.gov) to get
          the latest list of index files.  Any new or updated index
          files may then be downloaded as you wish. (When xnetlib is



     Page 1                                          (printed 3/13/92)






     xnetlib(2.0)               (11 Mar 92)               xnetlib(2.0)



          started for the first time you really ought to get them
          because xnetlib is not very useful otherwise.) At this time
          there are about 200 of these files, each about a page or two
          in size. By default, these files are placed in
          $HOME/xnlData. To begin the transfer of these files press
          the 'set up' button, then 'download new index files'. If you
          Cancel this process or if for some reason a file can't be
          transferred, xnetlib will forget it ever got any of the
          batch. The good files will still be used but they will be
          treated as out of date the next time you start xnetlib.

          If several people at the same site are using xnetlib, you
          may want to maintain one shared collection of index files
          instead of maintaining several separate collections. To do
          this set the resource to that directory. The effect of the
          'publicData' resource is that the xnlData directory and
          files in it are world writable so that anyone may update the
          indices. (You might even set this as the default in the
          source. See the fallback_resources in main.c.) To avoid
          problems the index directory is locked when someone is
          downloading index files.  If the lock gets stuck for some
          reason remove the xnlPath/LOCK file.

          To get files from xnetlib, click on 'library' (for example)
          and then select from the list of libraries. Click on the
          files you want and then click 'download'.

     INDEX FILES
          The index files are stored locally in your xnlPath directory
          under indexitems. They are written with the '.desc' suffix.
          These are the same files you might get by sending for the
          index by email from netlib.

     PLATFORMS
          Most development of xnetlib is being done on an IBM RS/6000
          running the X11R5 server and libraries. It has been tested
          on Sun, Decstation 5000, Sequent, NeXT (w/CoExist), HP9000,
          and Convex. It has been tested under these window managers:
          olwm, mwm, dxwm, twm.

          Please tell us about other environments it runs (or doesn't
          run) under.

     FUTURE DIRECTIONS
          The most important improvement in the next release of
          xnetlib will be index file caching.  This feature will give
          users the option of eliminating or reducing in size the
          local database of index files.  Requested indices not found
          in the local database will be retrieved on the fly from the
          xnetlib server.

          Multiserver support - perhaps you want to get files from



     Page 2                                          (printed 3/13/92)






     xnetlib(2.0)               (11 Mar 92)               xnetlib(2.0)



          other servers.

          General FTP support - with or without special index files on
          the remote machine.

          More.

          Please send us your comments. (xnetlib@cs.utk.edu)

     A ONE LINER
          We have included a command line interface to netlib. It was
          a last minute sort of thing and has not been well tested. To
          make it, type:

          cc -DSTANDALONE -o netlibget nl_access.c

          or your system's equivalent. Type 'netlibget' to see the
          usage line. Netlibget uses the same routines to talk to
          netlib that xnetlib does.

     X RESOURCES
          whoEntrySep: the separator displayed between entries in the
          NA-NET white pages database. The default is '-------'.

          whoPrintCommand: the format string for the print command of
          the NA-NET white pages database. The string must contain a
          %s which is replaced with the name of the file which is
          printed. The default is 'lpr %s'.

          showWhoInfo: whether to show instructions for adding your
          name to the NA-NET white pages database. The default is
          True.

          xnlPath: path to the local xnetlib database. The default is
          $HOME/xnlData.

          publicData: if True, save index files world writeable. The
          default is False.

          xnlDownloadPath: path to directory where the files you
          select are downloaded. The default is $HOME/xnlFiles

          depCheck: if True then any files required by the items you
          explicitly request are downloaded also. The default is True.

          showReceiveAnyway: if True then the receive button is not
          greyed out when there is nothing to download. The default is
          False.

          confirmQuit: if True you are asked if you truly want to exit
          when you press the Quit button. The default is True.




     Page 3                                          (printed 3/13/92)






     xnetlib(2.0)               (11 Mar 92)               xnetlib(2.0)



          dontWarp: sometimes xnetlib tries to help you out by placing
          the cursor where it thinks you may want it. Set to True if
          you don't care for this type of behavior. The default is
          False.

          These colors affect the status window background:

          okColor: the happy color, normally green

          badColor: the 'something's wrong' color, normally red

          cautionColor: the 'something's almost wrong' color, normally
          yellow

     BUGS
          On Ultrix, you MUST either have MIT X windows (not
          DECWindows) installed, OR have the "Unsupported X11
          Components" software subset loaded, in order to compile
          HeNCE.  The include files supplied with vanilla DECWindows
          are incompatible with those supplied by MIT and required by
          Xnetlib.

     AUTHORS
          This work is directed by Jack J. Dongarra, Univ. of
          Tennessee and Oak Ridge National Laboratory, and Tom Rowan,
          Oak Ridge National Laboratory, supported in part by the
          Applied Mathematical Sciences subprogram of the Office of
          Energy Research, U.S. Department of Energy, under contract
          DE-AC05-84OR21400, and in part by the National Science
          Foundation under contract NSF ASC-9103853.

          Xnetlib has evolved over a period of time between 1991 -
          1992 and has had help from: David Bolt, Univ. of Tennessee
          Jennifer Finger, Oak Ridge National Laboratory Andy Pearson,
          Univ. of Tennessee Bill Rosener, Univ. of Tennessee Jon
          Richardson, Univ. of Tennessee Andrea Van Hull, Northwestern
          Univ. and Oak Ridge National Laboratory

          Xnetlib 2.0 was written by:  Reed Wade, Univ. of Tennessee

          Fasthelp code from:  Ken Bateman, Virginia Tech and Oak
          Ridge National Laboratory

          A very special thanks to victims of the prerelease code.

          Convex fixes from:  salevin@drl.mobil.com









     Page 4                                          (printed 3/13/92)


From yeidel@tomar.accs.wsu.edu (Joshua Yeidel)
Newsgroups: comp.graphics.avs
Subject: Re: Xnetlib idea for AVS
Message-ID: <1992Aug13.165721.10773@serval.net.wsu.edu>
Date: 13 Aug 92 16:57:21 GMT
References: <ABOULANG.92Aug12163938@tiryns.bbn.com>
Sender: news@serval.net.wsu.edu (USENET News System)
Reply-To: yeidel@tomar.accs.wsu.edu (Joshua Yeidel)
Organization: Academic Computing Services, Washington State University
Lines: 12


I'm not an expert on this, but I understand that a more
general and standard solution is available -- Gopher.

What does the net think?

--
Joshua Yeidel               | yeidel@tomar.accs.wsu.edu
Academic Computing Services | All standard disclaimers apply
Washington State University |   "Believe it if you need it, 
Pullman, WA 99164-1226      |     or leave it if you dare..."
509/335-0441                |         -- Robert Hunter


From hampel@siemens.com. (Ken Hampel)
Newsgroups: comp.graphics.avs
Subject: Question about many objects in one geometry file
Message-ID: <100280@siemens.siemens.com>
Date: 13 Aug 92 18:02:57 GMT
Sender: news@siemens.siemens.com
Organization: Siemens Corporate Research, Inc., Princeton, NJ
Lines: 13


Can someone help me figure out how to have more than one object
in a geometry file. I'm trying to modify the byu.c filter which
converts byu format files to avs geometry files so that the
resulting .geom file contains many objects.
Then I came across something in a manual which lead me to believe
that the problem is in reading the geometry file. By default all
objects in a geometry file are read in as one big object? If so,
how can I read in each object separately.

Thanks in advance for any help.

-Ken


From d-lewart@uiuc.edu (Daniel S. Lewart)
Subject: Re: RFD: comp.graphics.gnuplot
References: <1992Aug7.232539.4927@uunet.uu.net>
Message-ID: <BszFpw.16G@news.cso.uiuc.edu>
Originator: dslg0849@uxa.cso.uiuc.edu
Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
Reply-To: d-lewart@uiuc.edu (Daniel S. Lewart)
Followup-To: news.groups
Organization: University of Illinois at Urbana
Date: Fri, 14 Aug 1992 16:41:55 GMT
Lines: 29

I have posted a `Request For Discussion' to news.groups for the creation
of a GNUPLOT newsgroup.  The charter is reproduced below.

Should the group be named `comp.apps.gnuplot' or `comp.graphics.gnuplot'?
Please follow-up to news.groups.  I strongly discourage email replies.

Thank you,
Daniel Lewart
d-lewart@uiuc.edu
-------------------------------------------------------------------------------
NAME:   comp.apps.gnuplot or comp.graphics.gnuplot

CHARTER:
1) This group is for the discussion of the GNUPLOT plotting program by
   developers and users.
2) This group will be gatewayed with a mailing list if someone volunteers
   to maintain it.
3) An FAQ list will be maintained.
4) GNUPLOT is a command-driven interactive function plotting program which:
   a) Plots data or functions.
   b) Has been tested on Unix, VMS, MSDOS, MS-Windows, OS/2, Amiga, and
      Atari platforms.
   c) Supports many different graphics devices.
   d) Is authored by Thomas Williams, Colin Kelley, Russell Lang,
      Dave Kotz, John Campbell, Gershon Elber, and many others.
   e) Is not part of the GNU project.

STATUS: Unmoderated
-------------------------------------------------------------------------------


From wbardwel@el_padre.mitre.org (Bill Bardwell)
Newsgroups: comp.graphics.avs
Subject: How to tell if an output is connected?
Keywords: AVS output port
Message-ID: <1992Aug14.205855.14035@linus.mitre.org>
Date: 14 Aug 92 20:58:55 GMT
Sender: news@linus.mitre.org (News Service)
Organization: The MITRE Corporation
Lines: 11
Nntp-Posting-Host: el_padre.mitre.org

-- 
How do you tell if an output port is connected?
I have a module that takes an avsimage field (aka 4-vector 2D byte),
and displays it nicely on an 8bit screen (which the normal
"display image" doesn't since it won't dynamically choose and
allocate colors.) and output the image and color map
on ports, but this is time consuming and would be nice to avoid,
when not needed.  
---------------------------------------
William Bardwell
wbardwel@elara.mitre.org


From kims@ncsa.uiuc.edu (Kim Stephenson)
Newsgroups: comp.graphics.avs
Subject: Renderman
Message-ID: <Bt57ro.BvG@news.cso.uiuc.edu>
Date: 17 Aug 92 19:35:44 GMT
Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
Organization: National Center for Supercomputing Applications
Lines: 8

We're looking for an AVS module which will dump geometry data to PIXAR's 
Renderman.  If it is not currently (or soon) available we want to check 
into writting one but are trying to determine the potential problems and a 
timeline.  If anyone has worked with Renderman's toolkit or knows of an 
existing module any information/advice would be appreciated.

Kim Stephenson
NCSA


From G.Coulter@uk.ac.daresbury (G. Coulter)
Newsgroups: comp.graphics.avs
Subject: Topological Surface data
Message-ID: <1992Aug18.081049.14540@gserv1.dl.ac.uk>
Date: 18 Aug 92 08:10:49 GMT
Sender: news@gserv1.dl.ac.uk (netnews)
Reply-To: G.Coulter@uk.ac.daresbury
Organization: Daresbury Laboratory, UK
Lines: 14

Hi

I am looking for a repository or FTP site where
I can obtain same surface data of say the earth
or one of the other planets in our solar system
to use as a landscape for an AVS animated flyby
sequence. The data can be in geom format or a
simple 2d uniform topological map that can be
extruded using FIELD_2_MESH. Once again 
anything is OK as long as it has a fair varaition
in height (Altitude).


Thanks. Gary   -> G.Coulter@uk.ac.daresbury


From stearman@mr4dec.enet.dec.com (Susan Stearman)
Newsgroups: comp.graphics.avs
Subject: Re: Developers AVS and DEC???
Message-ID: <1992Aug19.143146.6448@ryn.mro4.dec.com>
Date: 19 Aug 92 15:13:28 GMT
References: <5943@lhdsy1.lahabra.chevron.com>
Sender: news@ryn.mro4.dec.com (USENET News System)
Organization: Digital Equipment Corporation
Lines: 30


In article <5943@lhdsy1.lahabra.chevron.com>, drj@lhdsy1.lahabra.chevron.com (Dave R. Jones) writes...

In response to David Jones post, I offer the following reply from Digital's 
Workstation Business Manager.  

"
  . Digital recognizes the inconsistencies, such as the problem cited by 
    Mr. Jones, that currently exist in multi-vendor AVS environment, and 
    have been working with Advanced Visual Systems Inc. to remedy them.


  . Digital and AVS Inc. recently signed a Memorandum of Understanding 
    concerning a restructuring of the Digital AVS relationship that would 
    eliminate problems of the type mentioned by Mr. Jones from Chevron.


  . Our goal is to have a definitive plan and agreement in place by the
    end of September, and we believe that that will remedy the problem
    Mr. Jones cites.
"

As soon as our negotiations with Advanced Visual Systems are completed, we 
will post an update to this newsgroup.  Thank you for your patience on this 
complicated issue.

Susan Stearman
stearman@mr4dec.enet.dec.com
Visualization Applications Marketing
Digital Equipment Corp.


From richards@hermes.chpc.utexas.edu (Jon T. Richardson)
Newsgroups: comp.graphics,comp.graphics.visualization,comp.graphics.avs,comp.image.processing
Subject: Help: Surfaces from contours
Message-ID: <1992Aug19.171527.4914@chpc.utexas.edu>
Date: 19 Aug 1992 17:15:27 GMT
Sender: richards@chpc.utexas.edu (Jon T. Richardson)
Followup-To: comp.graphics.visualization
Organization: The University of Texas System - CHPC
Lines: 67


Dear Netters,

I need to create a 3D surface from cross-section contours of a
biological cell.  The cross-sections are quite complicated, having a number of
compartments and branches.  If you know of any code/applications/papers which
might be in the direction of a solution to this problem, I would greatly
appreciate any help you can give.

I'm in the process of reading/obtaining the following papers:

Sabin "Contouring - the state of the art""Contouring - the state of the art"
   in fundamental Algorithms for Computer Graphics, Springer Verlag, 1985
Elvins, "A Survey of Algorithms for Volume Visualization~
   Computer Graphics quarterly, ACM Siggraph. 26:3, August 1992
Keppel, "Approximating Complex Surfaces by Triangulation of
    Contour lines,"  IBM J of R&D, Volume 19, Number 1, January 1975, pp 2-11.
Fuchs, Kedem, and Uselton, "Optimal Surface
    Reconstruction from Planar Contours," CACM October 1977
Ekoule, Peyrin, Odet, "A Triangulation Algorithm from Arbitrary Shaped
    Multiple Planar Contours," ACM Transactions on Graphics, April 1991
Hoppe, DeRose, Duchamp, McDonald, Stuetlzle "Surface Reconstruction from
    unorganized points" Siggraph 92 proceedings
Y Breseler, Fessler and Macovski, "A Bayesian approach to
    reconstruction from incomplete projections of a multiple object 3D domain."
    IEEE transactions on Pat. Anal. Mach Intell., 11(8):840-858, August 1989.
Meyers, Skinner and Sloan, "Surfaces from contours: The correspondence and
    branching problems." Graphics Interface '91
Vemuri, Mitiche and Aggarwal, "Curvature based representation of objects
    from range data", Image and Vision computing, 4(2):107-114, 1986.
T A Foley. "Interpolation to scattered data on a spherical domain."
    in Algorithms for Approximation II
Nielson, Foley, Hamann and Lane, "Visualizing and Modeling scattered
    multivariate data." IEEE CG & A, 11(3):47-55, May 1991.
Miller, Breen, E Lorensen, O'Bara and Wozny, "Geometrically Deformed Models:
    A Method for Extracting Closed Geometric Models from Volume Data",
    Computer Graphics. July 1991.
Lin, Chen and Chen, "A new surface interpolation technique for
    reconstructing 3d objects from serial cross-sections."  Computer Vision,
    Graphics, and Image Processing, 48:124-143, 1989.
Kass, Witken and Terzopoulos, "Snakes: Active contour models.",  International
    Journal of Computer Vision, pp 321-331, 1988.
Terzopoulos, Witken and Kass, "Symmetry-seeking models and 3d object
    reconstruction." International Journal of Computer vision, October 1987.
Miller et al,  "Extracting geometric models through constraint minimization."
    Visualization '90 Proceedings,
Course notes from "Intro to Scientific visualization", Siggraph 92 course.

For software, I'm not picky about what form the data has to be in, but
it wouldn't hurt if it were amenable to AVS.

Please followup to comp.graphics.visualization or directly to me and I'll
post a summary.

Thank you very much in advance,

Jon.

|------------------------------------------------------------------------|
| Jon T Richardson                        :  richards@chpc.utexas.edu    |
| Scientific Visualization Group          :  CHPC, 10100 Burnet Rd       |
| Center for High Performance. Computing  :  Austin, TX 78758            | 
-- 
|------------------------------------------------------------------------|
| Jon T Richardson                   :  richards@chpc.utexas.edu         |
| Scientific Visualization Group     :  CHPC, 10100 Burnet Rd            |
| Cntr for High Perf. Computing      :  Austin, TX 78758                 | 


From yang@mtu.edu (Xiaoyang Yang)
Subject: How to get control of mouse in AVS and ....
Message-ID: <1992Aug19.194436.18199@mtu.edu>
Sender: yang@mtu.edu (Xiaoyang Yang-grad)
Nntp-Posting-Host: fishlab10.fsh.mtu.edu
Organization: Michigan Technological University
References:  <1992Aug12.195814.5682@menudo.uh.edu>
Date: Wed, 19 Aug 1992 19:44:36 GMT
Lines: 19

Hi geniuses

           I wanted to if there is any way in AVS that you can control
of mouse in the way of what you can do with PHIGS/PEX/etc graphic package.
For example, you have a subroutines in PHIGS for you to request such 
functionalities as to PICK an object, to LOCATE a position of/for an object,
or whatever.    Can I do the similar thing with AVS?  Any idea will be
very helpful.

           Hope you get my problem.

Thanks
Xiaoyang


-- 
===========================
my signature:     Y + X + Y
===========================


From keg@hansen1.ncd.com (Ken Garnett)
Date: 19 Aug 92 19:34:46 GMT
Sender: news@NCD.COM
Organization: Network Computing Devices, Mt. View, CA, USA
Keywords: CAD/CAM 3-D-Graphics Visualization
Nntp-Posting-Host: hansen2
Lines: 15

I'm looking for manufacturers of input devices commonly known as "Dial Boxes"
or "Knob Boxes".  These are units composed of multiple rheostat-like knobs
which each can generate ranges of integer values.

If anyone has information on who manufactures these devices, I'd appreciate
any pointers to them.  Detailed information like model names/numbers would
be helpful, too, if you've got that handy...

Thanks much!

-- 
- Ken Garnett
  Network Computing Devices, Inc.                keg@ncd.com
  350 North Bernardo Avenue
  Mountain View, CA  94043                       415-691-2112


From lake@cwjcc.INS.CWRU.Edu (Dr. Robin Lake)
Subject: Re: Dial/Knob Boxes?
Message-ID: <1992Aug20.012228.8409@usenet.ins.cwru.edu>
Keywords: CAD/CAM 3-D-Graphics Visualization
Sender: news@usenet.ins.cwru.edu
Nntp-Posting-Host: cwjcc.ins.cwru.edu
Reply-To: lake@po.CWRU.Edu
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
References: <12715@lupine.ncd.com>
Date: Thu, 20 Aug 92 01:22:28 GMT
Lines:       26

In article <12715@lupine.ncd.com> keg@hansen1.ncd.com (Ken Garnett) writes:
>I'm looking for manufacturers of input devices commonly known as "Dial Boxes"
>or "Knob Boxes".  These are units composed of multiple rheostat-like knobs
>which each can generate ranges of integer values.
>
>If anyone has information on who manufactures these devices, I'd appreciate
>any pointers to them.  Detailed information like model names/numbers would
>be helpful, too, if you've got that handy...
>
>Thanks much!
>
>-- 
>- Ken Garnett
>  Network Computing Devices, Inc.                keg@ncd.com
>  350 North Bernardo Avenue
>  Mountain View, CA  94043                       415-691-2112


In that the Stardent/Kubota Pacific Titan comes with an optional dial box,
8 dials in 4x2 arrangement, a quick e-mail to support@kpc.com may get you
a lead to their source.

Rob Lake
BP Research
lake@rcwcl1.dnet.bp.com


From dlc@convex.com (Dominique Le Corre)
Subject: Re: How to get control of mouse in AVS and ....
Message-ID: <1992Aug20.075743.26561@convex.com>
Sender: usenet@convex.com (news access account)
Nntp-Posting-Host: convex1.convex.com
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
References: <1992Aug12.195814.5682@menudo.uh.edu> <1992Aug19.194436.18199@mtu.edu>
Date: Thu, 20 Aug 1992 07:57:43 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.
Lines: 12


AVS incorporates a mechanism called upstream transform & picking.
This mechanism allows an upstream module to get information from
a downstream module (typically the geometry viewer, which sends
information about selected objects, picked vertices, object
transformations,etc..).
It is used by some standard modules, like probes, arbitrary slicers,
hedgehog,stream lines, particle advector, but you can use it also
for your own modules.

D.LC



From dlc@convex.com (Dominique Le Corre)
Subject: UCD_qsort & UCD_bsearch
Message-ID: <1992Aug20.080200.26862@convex.com>
Sender: usenet@convex.com (news access account)
Nntp-Posting-Host: convex1.convex.com
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
Date: Thu, 20 Aug 1992 08:02:00 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.
Lines: 14


Hi,
Does anybody know what the following AVS routines do and what are 
their arguments ?
UCD_qsort
UCD_bsearch
UCD_qsorti
UCD_bsearchi

Thanx in advance.
D.LC
dlc@cvxfr.fr.convex.com




From merritt@provolone.bchem.washington.edu (Ethan A Merritt)
Newsgroups: comp.graphics,comp.periphs,comp.graphics.avs
Subject: Re: Dial/Knob Boxes?
Keywords: CAD/CAM 3-D-Graphics Visualization
Message-ID: <1992Aug20.173052.8036@u.washington.edu>
Date: 20 Aug 92 17:30:52 GMT
Article-I.D.: u.1992Aug20.173052.8036
References: <12715@lupine.ncd.com>
Sender: news@u.washington.edu (USENET News System)
Reply-To: merritt@u.washington.edu
Followup-To: comp.graphics.avs
Organization: University of Washington
Lines: 36


In article <12715@lupine.ncd.com>, keg@hansen1.ncd.com (Ken Garnett) writes:
|> I'm looking for manufacturers of input devices commonly known as
"Dial Boxes"
|> or "Knob Boxes".  These are units composed of multiple rheostat-like knobs
|> which each can generate ranges of integer values.
|> 
|> If anyone has information on who manufactures these devices, I'd appreciate
|> any pointers to them.  Detailed information like model names/numbers would
|> be helpful, too, if you've got that handy...
|> 
	The ones I have are made by Spectragraphics / 9707 Waples St /
San Diego 92121 / (619)450-0611.  They are re-sold by DEC for use with
DEC workstations, but should be usable anywhere since they just plug in to
a normal serial port.

	I am posting this rather than simply mailing a response because
it raises a gripe I have with a lack of flexibility in AVS as regards to
interactive input.  It would be awfully nice if there were some generalized
input port to all the 3-D viewers (particularly "render geometry") which
would take ascii input and rotate/scale/translate/etc.  That way one
could actually _use_ the dial box (it's not supported on the AVS version
I have), or bind function keys to give pure axial rotations, discrete scaling
increments, or whatever.  I.e., whatever bit of code is polling the mouse
buttons and pointer motion could equally well pay attention to input on the
ascii port.

	Any hope of seeing such an approach in a future version? Or anyone
have any bright ideas about how to approximate it given the tools that are
there right now?  I realize that one could create modules which essentially
take over the maintenance of the transformation matrices upstream of the
geometry viewer, but this seems like a wasteful duplication of code and
likely of compute time also.

					Ethan A Merritt
					merritt@u.washington.edu


From jscherer@novell.com
Newsgroups: comp.graphics.avs
Subject: avs for the NeXT?
Message-ID: <1992Aug20.194514.510@novell.com>
Date: 20 Aug 92 19:45:14 GMT
Sender: usenet@novell.com (The Netnews Manager)
Reply-To: jscherer@novell.com
Organization: Novell, Inc.
Lines: 8
Nntp-Posting-Host: tsnext

Does a version of avs exist for the NeXT computer?

--
John Scherer
778 Shetland Ct. 
San Jose, CA  95127

internet: jscherer@novell.com


From mag@minerva.inesc.pt (Manuel Gamito)
Newsgroups: comp.graphics,comp.graphics.avs,comp.soft-sys.khoros,comp.sys.sgi
Subject: Time Dependent Visualization on Explorer,AVS,Khoros,...
Message-ID: <1992Aug20.165002.23549@inesc.pt>
Date: 20 Aug 92 16:50:02 GMT
Sender: usenet@inesc.pt (USENET News System)
Organization: INESC, Lisboa, Portugal
Lines: 22
Nntp-Posting-Host: minerva.inesc.pt

Hello net!

I am starting to work on a project involving the dinamics of rigid
bodies.
I would like to use one scientific visualization package for this but I
don't know wich one is best.

I know Explorer already (since I'm on an IRIS Indigo) but it doesn't
seem to handle explicitly time varying phenomena.

Am I wrong about Explorer?
Is there other systems better for this kind of simulations over
time like apE???, Khoros, Avs or others.

If you don't know all these systems just tell about the one(s) you know.

Much thanks!!!
-- 
Manuel Noronha Gamito, INESC          		| email: mag@minerva.inesc.pt
R. Alves Redol, 9 Apartado 10105		| mcsun!inesc!mag@uunet.UU.NET
1017 LISBOA CODEX				| Phone: +351 1 3100094
PORTUGAL					| Fax:   +351 1 525843


From highnam@slcs.slb.com (Peter Highnam)
Newsgroups: comp.graphics.avs
Subject: Using a different X display ?
Message-ID: <1992Aug20.190530.6787@slcs.slb.com>
Date: 20 Aug 92 19:05:30 GMT
Sender: news@slcs.slb.com (News Administrator)
Organization: Schlumberger Laboratory for Computer Science
Lines: 19
Nntp-Posting-Host: speedy


 I would like to display an image/pixmap on an X display
 other than that which the AVS kernel is using.  I (and
 the Module Generator) wrote a simple module that takes
 a pixmap input and a display name typein.  It doesn't
 work.  The remote window appears but as soon as the
 code attempts a XGetImage the module takes a BadMatch X11
 error and dies.  Probing a little further I discovered
 that any attempt to treat the pixmap field of the AVSpixdata
 structure as the id of a Drawable kills the module...
 (The other fields of AVSpixdata are just fine.)

 Suggestions appreciated.

 Thanks,
 Peter
-- 
 Schlumberger Laboratory for Computer Science, PO Box 200015,  Austin,
 TX 78720-0015 ;;  512-331-3736  ;;  highnam@slcs.slb.com (Internet)


From James Peters <peters@convex.COM>
Subject: Re: Dial/Knob Boxes?
Message-ID: <1992Aug20.212306.2541@convex.com>
Originator: peters@mikey.convex.com
Keywords: CAD/CAM 3-D-Graphics Visualization
Sender: usenet@convex.com (news access account)
Nntp-Posting-Host: mikey.convex.com
Reply-To: peters@convex.COM (James Peters)
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
References: <12715@lupine.ncd.com> <1992Aug20.173052.8036@u.washington.edu>
Date: Thu, 20 Aug 1992 21:23:06 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.
Lines: 56

In article <1992Aug20.173052.8036@u.washington.edu> merritt@u.washington.edu writes:
>
>In article <12715@lupine.ncd.com>, keg@hansen1.ncd.com (Ken Garnett) writes:
>|> I'm looking for manufacturers of input devices commonly known as
>"Dial Boxes"
>|> or "Knob Boxes".  These are units composed of multiple rheostat-like knobs
>|> which each can generate ranges of integer values.
>|> 
>|> If anyone has information on who manufactures these devices, I'd appreciate
>|> any pointers to them.  Detailed information like model names/numbers would
>|> be helpful, too, if you've got that handy...
>|> 
>	The ones I have are made by Spectragraphics / 9707 Waples St /
>San Diego 92121 / (619)450-0611.  They are re-sold by DEC for use with
>DEC workstations, but should be usable anywhere since they just plug in to
>a normal serial port.
>
>	I am posting this rather than simply mailing a response because
>it raises a gripe I have with a lack of flexibility in AVS as regards to
>interactive input.  It would be awfully nice if there were some generalized
>input port to all the 3-D viewers (particularly "render geometry") which
>would take ascii input and rotate/scale/translate/etc.  That way one
>could actually _use_ the dial box (it's not supported on the AVS version
>I have), or bind function keys to give pure axial rotations, discrete scaling
>increments, or whatever.  I.e., whatever bit of code is polling the mouse
>buttons and pointer motion could equally well pay attention to input on the
>ascii port.
>
>	Any hope of seeing such an approach in a future version? Or anyone
>have any bright ideas about how to approximate it given the tools that are
>there right now?  I realize that one could create modules which essentially
>take over the maintenance of the transformation matrices upstream of the
>geometry viewer, but this seems like a wasteful duplication of code and
>likely of compute time also.
>
>					Ethan A Merritt
>					merritt@u.washington.edu

each dial vendor has device dependent driver sw. stellar supported the
DIGIT dialbox through its dialbox mgr which allowed you to attach the 
dials to widgets/parameters in avs. the dial driver is buried in the avs
kernel so providing support for all dial devices would be none trivial.
the only way a standard dial interface could be developed is to have all 
input devices ie dials, spaceballs, powergloves etc rolled into X then
basically all you have to do is watch for events and handle them accord-
ingly. i don't know when and if X will cover this.

regards,
james, peters@convex.com

BTW the DATA/Dials_Control module available at the avs international center
was a product of the new dialbox interface introduced in avs2 which forced you
to bind via the dialbox manager. if you want to roll your own dialbox inter-
face i would start with this module and add your dial driver. you will be
pretty limited to just translations instead of ability to bind to any widget
through the dialbox mgr.


From dlc@convex.com (Dominique Le Corre)
Subject: RdUcdAnim & WrUcdAnim
Message-ID: <1992Aug21.162428.19597@convex.com>
Keywords:  ucd animation
Sender: usenet@convex.com (news access account)
Nntp-Posting-Host: convex1.convex.com
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
Date: Fri, 21 Aug 1992 16:24:28 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.
Lines: 17


Hi, AVSers
2 new modules are available at IAC : WrUcdAnim and RdUcdAnim,
to write and read UCD animation sequences.
WrUcdAnim captures node positions, node data, cell data,
model data or any mix of these components for every time step.
RdUcdAnim reads back all or part of the stored data for each time step.
Optionally, a "preload" mode allows you to read all time steps into
memory, and then cycle to pointers.
Read the .txt files first to see which parts are functional.
D.LC
Enjoy.

Dominique Le Corre
dlc@cvxfr.fr.convex.com




From rthomson@mesa.dsd.es.com (Rich Thomson)
Subject: Re: Dial/Knob Boxes?
Message-ID: <1992Aug26.042007.19662@dsd.es.com>
Keywords: CAD/CAM 3-D-Graphics Visualization
Sender: usenet@dsd.es.com
Nntp-Posting-Host: 130.187.85.21
Reply-To: rthomson@dsd.es.com (Rich Thomson)
Organization: Design Systems Division, Evans & Sutherland, SLC, UT
References: <12715@lupine.ncd.com> <1992Aug20.012228.8409@usenet.ins.cwru.edu>
Date: Wed, 26 Aug 92 04:20:07 GMT
Lines: 21

In article <12715@lupine.ncd.com> keg@hansen1.ncd.com (Ken Garnett) writes:
>I'm looking for manufacturers of input devices commonly known as "Dial Boxes"
>or "Knob Boxes".  These are units composed of multiple rheostat-like knobs
>which each can generate ranges of integer values.
>
>If anyone has information on who manufactures these devices, I'd appreciate
>any pointers to them.  Detailed information like model names/numbers would
>be helpful, too, if you've got that handy...

Evans & Sutherland makes an 8 knob dial box (each with an eight
character LED display above each dial).  We support the dial box
through the X Input Extension (which is what the AVS port uses).  I'm
not sure what the model/number is, but you should be able to find out
by calling our 800 number: 1-800-367-7460.

						-- Rich
-- 
	Repeal the personal income tax; vote Libertarian in 1992.
Disclaimer: I speak for myself, except as noted; Copyright 1992 Rich Thomson
UUCP: ...!uunet!dsd.es.com!rthomson			Rich Thomson
Internet: rthomson@dsd.es.com	IRC: _Rich_		PEXt Programmer


From d-lewart@uiuc.edu (Daniel S. Lewart)
Newsgroups: comp.apps.spreadsheets,comp.graphics,comp.graphics.avs,comp.graphics.explorer,comp.graphics.visualization
Subject: Straw Poll on Gnuplot newsgroup name
Message-ID: <BtLz56.B1@news.cso.uiuc.edu>
Date: 26 Aug 92 20:48:42 GMT
Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
Reply-To: d-lewart@uiuc.edu (Daniel S. Lewart)
Followup-To: news.groups
Organization: University of Illinois at Urbana
Lines: 33
Originator: dslg0849@uxa.cso.uiuc.edu

These are the comp.apps and comp.graphics branches of the USENET hierarchy:
-------------------------------------------------------------------------------
comp.apps.spreadsheets	Spreadsheets on various platforms.
comp.graphics		Computer graphics, art, animation, image processing.
comp.graphics.avs	The Application Visualization System.
comp.graphics.explorer	The Explorer Modular Visualisation Environment (MVE).
comp.graphics.research	Highly technical computer graphics discussion. (Moderate
comp.graphics.visualization	Info on scientific visualization.
-------------------------------------------------------------------------------

This is a preferential straw poll so we can finally pick a name and have
a vote.  There are three candidates:
	comp.apps.gnuplot
	comp.apps.graphics.gnuplot
	comp.graphics.gnuplot
Of course, write-ins will be counted too.  Please cut out and edit the
section below and email it to me.

Remember email/reply for straw poll and follow-up to news.groups for further
discussion.

Thank you,
Daniel Lewart
d-lewart@uiuc.edu
----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<---
My votes for Gnuplot group names (1=favorite, 2=second favorite, ...) are:
1)
2)
3)

My name is
My email address is
----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<---


From hsingh@Turing.chem.uh.edu (Harpreet Singh)
Subject: Do you know what this message means ??
Message-ID: <1992Aug27.185940.8014@menudo.uh.edu>
Sender: usenet@menudo.uh.edu (USENET News System)
Nntp-Posting-Host: turing.chem.uh.edu
Organization: Dept. of Chemistry
Date: Thu, 27 Aug 1992 18:59:40 GMT
Lines: 22


Hi,
	I am getting the following message with a module of mine. If
someone has some idea it would be pretty helpful


!tg_cbnewin 0x2000004 0x7fdfce44 0x2000004 0x7fdfcdfc 0x63746f72
!tg_cbnewin 0x2000004 0x7fdfd614 0x2000004 0x7fdfd5cc 0x1d5a3634
Fatal server bug!
Fatal server bug!
tigr fatal error:tigr fatal error:
My_module: tcp_read failed.
tcp_read: No such device or address


Thanks
Harpreet
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%   Harpreet Singh                      e-mail: hsingh@hobbes.chem.uh.edu  %
%   @University Of Houston              v-mail: (713) 748-7292             %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


From James Peters <peters@convex.COM>
Subject: Re: Do you know what this message means ??
Message-ID: <1992Aug28.152114.4350@convex.com>
Originator: peters@mikey.convex.com
Sender: usenet@convex.com (news access account)
Nntp-Posting-Host: mikey.convex.com
Reply-To: peters@convex.COM (James Peters)
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
References: <1992Aug27.185940.8014@menudo.uh.edu>
Date: Fri, 28 Aug 1992 15:21:14 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.
Lines: 25

In article <1992Aug27.185940.8014@menudo.uh.edu> hsingh@Turing.chem.uh.edu (Harpreet Singh) writes:
>	I am getting the following message with a module of mine. If
>someone has some idea it would be pretty helpful
>
>!tg_cbnewin 0x2000004 0x7fdfce44 0x2000004 0x7fdfcdfc 0x63746f72
>!tg_cbnewin 0x2000004 0x7fdfd614 0x2000004 0x7fdfd5cc 0x1d5a3634
>Fatal server bug!
>Fatal server bug!
>tigr fatal error:tigr fatal error:
>My_module: tcp_read failed.
>tcp_read: No such device or address
>
>Thanks
>Harpreet
>--
>%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>%   Harpreet Singh                      e-mail: hsingh@hobbes.chem.uh.edu  %
>%   @University Of Houston              v-mail: (713) 748-7292             %
>%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

per harpreet this is coming from a stardent/kpc titan p2 workstation.
the version of avs is 4.0.

regards,
james, peters@convex.com


From wave@media.mit.edu (Michael B. Johnson)
Subject: Re: Do you know what this message means ??
Message-ID: <1992Aug28.233743.29191@news.media.mit.edu>
Sender: news@news.media.mit.edu (USENET News System)
Organization: MIT Media Laboratory
References: <1992Aug27.185940.8014@menudo.uh.edu> <1992Aug28.152114.4350@convex.com>
Date: Fri, 28 Aug 1992 23:37:43 GMT
Lines: 36

In article <1992Aug28.152114.4350@convex.com> peters@convex.COM (James Peters) writes:
>>In article <1992Aug27.185940.8014@menudo.uh.edu> hsingh@Turing.chem.uh.edu (Harpreet Singh) writes:
>>>	I am getting the following message with a module of mine. If
>>>someone has some idea it would be pretty helpful
>>>
>>>!tg_cbnewin 0x2000004 0x7fdfce44 0x2000004 0x7fdfcdfc 0x63746f72
>>>!tg_cbnewin 0x2000004 0x7fdfd614 0x2000004 0x7fdfd5cc 0x1d5a3634
>>>Fatal server bug!
>>>Fatal server bug!
>>>tigr fatal error:tigr fatal error:
>>>My_module: tcp_read failed.
>>>tcp_read: No such device or address
>>>
>>per harpreet this is coming from a stardent/kpc titan p2 workstation.
>>the version of avs is 4.0.
>>

Well, all I can tell you about it is that "tigr" is a name I've seen
in reference to the Titan's framebuffer, so my guess would be you've
stumbled on some rather next bug in their X server implementation on
that hardware.  The tcp_read stuff is what you get when modules and/or
the avs kernel start dying badly.

You really should give us more information if you want us to help.

Have you run your module using avs_dbx and stepped through it?  What
does your module do?  Does AVS continue to function after you get 
these error messages or does the whole process go down?  More details,
please...


-- 

-->  Michael B. Johnson
-->  MIT Media Lab      --  Computer Graphics & Animation Group
-->  (617) 253-0663     --  wave@media-lab.media.mit.edu


From evp@oliver.sun.ac.za (Etienne van der Poel)
Newsgroups: comp.graphics.avs
Subject: AVS does not close input file?
Message-ID: <1992Aug30.153547.15303@hippo.ru.ac.za>
Date: 30 Aug 92 15:35:47 GMT
Article-I.D.: hippo.1992Aug30.153547.15303
Sender: news@hippo.ru.ac.za
Organization: Rhodes University, Grahamstown, South Africa
Lines: 48
X-Newsreader: Tin 1.1 PL5

Hi

I am in the process of writing a module that reads an external data file (which
is in a non-AVS format) and outputs data in the AVS field format. The input 
file name is specified with a file name browser. The file is opened, and the
data read into memory with a parser (the data is in the form of a formal grammar).
The user then selects a subset of the data, which is then output in the AVS
field format.

Everything works fine, until the filename parameter is changed. The parser tries
to continue parsing at the end of previous file!? It is as if the previous file
is never closed.

Here is the code. Could some guru please point out my mistake. Please E-mail me
directly.  Oh yes, the module is written as a subroutine.

-----
int read_mbpo_compute( output, infilename, extract)
  AVSfield  **output;
  char       *infilename;
  char       *extract;
{
  FILE *infile=NULL;

  if (!infilename)                     /* if no infilename             */
    return(1);

  if (!(infile = fopen(infilename, "r")))  /* open the input file      */
    {
      AVSerror("Cannot open input file %s", infilename);
      return(0);
    }
  mbpo_read( infile);                  /* parse the input file         */
  fclose( infile);                     /* close the input file         */

  check_extracted_select( extract);    /* mark data to be extracted    */
  write_output( output);               /* write extracted data         */
  return(1);
}
-----

Etienne  

\_\_\_ \_    \_ \_\_\_  \_\_\_\_\_\_\_           Department of Computer Science
 \_     \_    \_ \_   \_ \_\_\_\_\_\_\_\_\_\_\_   University of Stellenbosch
  \_\_   \_    \_ \_\_\_  \_\_\_\_\_\_\_\_         Stellenbosch 7600
   \_      \_ \_   \_      \_\_\_\_\_\_\_\_\_\_\_\_ South Africa
    \_\_\_   \_     \_      \_\_\_\_\_\_\_\_\_\_     Internet: evp@cs.sun.ac.za


From d-lewart@uiuc.edu (Daniel S. Lewart)
Subject: RESULT: Straw Poll --> comp.graphics.gnuplot
Message-ID: <Btu9oo.7vG@news.cso.uiuc.edu>
Originator: dslg0849@uxa.cso.uiuc.edu
Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
Reply-To: d-lewart@uiuc.edu (Daniel S. Lewart)
Followup-To: news.groups
Organization: University of Illinois at Urbana
Date: Mon, 31 Aug 1992 08:17:11 GMT
Lines: 90

The straw poll for the name of the Gnuplot newsgroup is complete, and the
winner is `comp.graphics.gnuplot'.  I shall post a CFV shortly.

Follow-up to news.groups.

Thank you for voting!
Daniel Lewart
d-lewart@uiuc.edu
-------------------------------------------------------------------------------
A  comp.apps.gnuplot            10
B  comp.apps.graphics.gnuplot    6
C  comp.graphics.gnuplot        32
D  Write-ins                     3
   Total                        51
-------------------------------------------------------------------------------
A  comp.apps.gnuplot

A B C
1 3 2   d-lewart@uiuc.edu (Daniel S. Lewart)
1 - -   dj@woodruff.weru.ksu.edu (DJ D. Ding)
1 2 3   whiteley@slug.ssc.gov (James Whiteley)
1 2 3   rthomson@dsd.es.com (Rich Thomson)
1 3 2   rcodk@topcat.catt.citri.edu.au (David Kershaw)
1 2 3   mroussel@alchemy.chem.utoronto.ca (Marc Roussel)
1 - 2   weber@rhrk.uni-kl.de (Christoph Weber-Fahr)
1 - -   ddebry@dsd.es.com (David DeBry)
1 - -   brutzman@cs.nps.navy.mil (Don Brutzman)
1 3 2   carolo@cse.ucsc.edu (Carol Osterbrock)

B  comp.apps.graphics.gnuplot

A B C
- 1 -   chip@chinacat.unicom.com (Chip Rosenthal)
- 1 2   cudcv@csv.warwick.ac.uk (Rob McMahon)
2 1 3   russell@alpha3.ersys.edmonton.ab.ca (Russell Schulz)
2 1 3   lilleyc@computer-science.manchester.ac.uk (Chris Lilley)
- 1 -   thalli@piis10.joanneum.ac.at (Georg Thallinger)
2 1 3   ullwer@orgel.informatik.uni-stuttgart.de (Christof Ullwer)

C  comp.graphics.gnuplot

A B C
- - 1   USERKJWH@mtsg.ubc.ca (KJWH)
3 2 1   dob@inel.gov (Dave Brooks)
3 2 1   dps7679@hexad.boeing.com (David P. Smith)
3 2 1   ssi!fcc@uunet.UU.NET (Frank C. Christofferson)
2 3 1   gershon@gr.cs.utah.edu (Elber Gershon)
3 2 1   russo@rudedog.nrl.navy.mil (Kevin Russo)
2 3 1   cobb@betsy.mc.ti.com (Chip Cobb)
3 2 1   przemek@rrdstrad.nist.gov (Przemek Klosowski)
2 3 1   al@stanley.cis.brown.edu (Andre Lehovich)
- - 1   jvl@mickey.aero.org (John V. Langer)
2 - 1   nancy@ux5.lbl.gov (Nancy Johnston)
3 2 1   ian@vortex.yorku.ca (Ian Lumb)
- - 1   woo@ra-next.arc.nasa.gov (Alex Woo)
2 3 1   JDC@NAUVAX.UCC.NAU.EDU (John Campbell)
2 - 1   black@seismo.CSS.GOV (Mike Black)
3 - 1   hendrix@oasys.dt.navy.mil (Dane Hendrix)
2 3 1   Klaus.Steinberger@Physik.Uni-Muenchen.DE (Klaus Steinberger)
2 3 1   rjl@monu1.cc.monash.edu.au (Russell Lang)
2 3 1   panya@sl.t.u-tokyo.ac.jp (Panyarak Ngamsritragul)
2 3 1   Christopher.Hadley@cl.cam.ac.uk (Chris Hadley)
3 2 1   rjh2@lehigh.edu (Ronald J. Hartranft)
- - 1   hobbes@spacemanspiff.den.mmc.com (Stephen Camp)
2 3 1   spotz@cfdlab.ae.utexas.edu (William Spotz)
2 - 1   bongo@splash.Princeton.EDU (Ameet A. Ravel)
2 3 1   i6040504@ws.rz.tu-bs.de (Holger Holthoff)
3 2 1   bernhard@devon.geologie.uni-freiburg.de (Bernhard Ehrminger)
2 - 1   droyster@mosaic.uncc.edu (David Royster)
3 2 1   kaufman@delta.eecs.nwu.edu (Michael L. Kaufman)
- - 1   schuette@roadkill.nrl.navy.mil (Larry Schuette)
2 3 1   roelle@sigi.jhuapl.edu (Curtis Roelle)
3 2 1   CSMRO114@uoft02.utoledo.edu (Gus Sharara)
2 3 1   arrouye@imag.fr (Yves Arrouye)

D  comp.graphics.gnuplot.info [Write-in]

A B C
4 3 2   gnulists@ai.mit.edu (Len Tower Jr.)

D  comp.graphics.plotting [Write-in]

A B C
- 3 2   uunet!fe2o3!rusty@uxc.cso.uiuc.edu (Rusty Haddock)

D  gnu.gnuplot [Write-in]

A B C
3 - 2   rrosen@cesl.rutgers.edu (Robert Rosenbaum)
-------------------------------------------------------------------------------


From thorpe@doppler.ncsc.org (Steve Thorpe)
Subject: IAC module update
Message-ID: <BtutMz.Gru@doppler.ncsc.org>
Keywords: AVS, modules, International AVS Center
Organization: North Carolina Supercomputing Center
Date: Mon, 31 Aug 1992 15:28:10 GMT

Hi AVSers,

Many thanks to everyone who has recently submitted new modules or
module updates to the International AVS Center!  I've just added a 
batch to the ftp site, and am including their descriptions below.  

These and other AVS modules are freely available from avs.ncsc.org
(128.109.178.23).  If you have written any AVS modules
but haven't submitted them to the IAC yet, please take the time to 
send them in to us.  A few minutes of clean up and documentation
of modules on your part may save another AVS user from hours 
of code development that could have been time spent on something
else.

To learn more about the International AVS Center, how to download and
submit modules, just check out the files AVS_README and AVS_CATALOG
using anonymous ftp to the above address.  Or send any mail message
to avsemail@ncsc.org to receive an automated reply containing these
files.

Thanks again to all submitters, and please keep them coming!

-Steve
----------------------------------------------------------------
   Steve Thorpe, Application Visualization System Specialist
International AVS Center, North Carolina Supercomputing Center
PO Box 12889   3021 Cornwallis Rd, RTP, NC 27709   avs@ncsc.org
----------------------------------------------------------------

Name        : Extrusion       Version      : 1.000     Mod Number : 1313
Author      : Feizal Mirza, University of Texas CHPC
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : This module reads an ASCII file consisting of lists of x & y
              points and constructs a 3-D geometry object using the
              points in the file as vertices. It uses the value specified
              by the user in the depth dial for the depth of the object.

Name        : FITS_read       Version      : 1.000     Mod Number : 1306
Author      : D. LE CORRE, CONVEX S.A
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C&FORTRAN
Ported to   : Convex
Description : This DATA INPUT module reads a FITS (Flexible Image
              Transport System) file into a field, and optionally to a
              text window. For primary data or image extensions, the
              number of dimensions is derived from the NAXIS keyword. For
              Ascii and binary tables, the number of dimensions may be 1 or
              2, depending on a parameter. Random Groups do not seem to be
              supported (I did'nt see any example of them).

Name        : QUAL_field      Version      : 1.000     Mod Number : 1321
Author      : Marc Curry, North Carolina Supercomputing Center
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : The QUAL field module is used to selectively grab data
              elements from a large output plot file and map them to the
              geometry of an example river. The geometry can be changed
              (with some effort) to match that of any river. The codes that
              generate the output plot files used by this module are
              QUAL2E and QUAL2E-UNCAS which were developed by Linfield
              Brown (Dept. of Civil Eng, Tufts Univ.) and Thomas Barnwell
              (EPA, Athens GA.).

Name        : RdUcdAnim       Version      : 1.000     Mod Number : 1316
Author      : D. LE CORRE, CONVEX S.A
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : This DATA input module animates a sequence of data applied
              to a UCD structure. The base format is exactly the same as the
              standard UCD, except that you can specify a 6-th value on the
              first line (if you use ASCII format) , giving the maximum
              number of time steps to consider. By default, allocation is
              provided for at most 256 time steps.

Name        : geometry_sphere Version      : 1.000     Mod Number : 1320
Author      : Marc Curry, North Carolina Supercomputing Center
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun Convex
Description : This geometry sphere module demonstrates how to convert a
              set of vertices into a geomtry format for viewing within
              AVS. Also, some simple widgets are provided to take care of
              (what were) program parameters. The sphere is actually a
              triangle mesh approximating a sphere by recursive
              subdivision into more and more triangles. The first
              approximation is an octahedron, with each level of
              refinement increasing the number of triangles by a factor
              of 4.

Name        : read_points     Version      : 1.000     Mod Number : 1311
Author      : Penny Rheingans, US EPA Scientific Visualization Center
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Read observation locations and variable values from an
              ASCII file. From these observations build a 1D irregular
              (scatter) field with one element for each observation.

Name        : read_ucd_points Version      : 1.000     Mod Number : 1310
Author      : Penny Rheingans, US EPA Scientific Visualization Center
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Read observation locations and variable values from an
              ASCII file. From these observations build a ucd structure
              field with one node for each observation. The cells of the
              structure are of type UCD_POINT.

Name        : read_uniform    Version      : 2.000     Mod Number : 1075
Author      : Wes Bethel, Lawrence Berkeley Laboratory
Submitted   : 10/10/91        Last Updated : 08/30/92  Language   : C
Ported to   : Sun Convex HP
Description : This module reads data in ascii format into a "uniform
              field" data structure. The disk file is structured to
              contain information about the field at the beginning of the
              file, followed by the data.

Name        : grey_scales     Version      : 1.000     Mod Number : 1315
Author      : Rob Kuyper, Univeristy of Technology Delft, The
              Netherlands
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : The module takes an image as input an produces a black and
              white version of the same image as output. The number of grey
              scales is adjustable by a dial. The grey level is produced in
              the same way as with the command xpr to print windows on a
              laserjet. The advantage of adjusting the number of grey
              levels is the fact that the produced image shows the edges
              between different colors better. The output can be printed
              on a laserjet which results in a much better picture then
              without this module. In order to have white as one of the grey
              levels, the roundoff works like a 'floor'.

Name        : scatter_to_sparsVersion      : 1.000     Mod Number : 1309
Author      : Penny Rheingans, US EPA Scientific Visualization Center
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Convert a 1D field containing scattered data points into a
              (potentially) sparsely filled uniform field. The output
              field has as many dimensions as the input field did
              coordinate dimensions. For example, if the input is a 1D
              3-space field, the output will be a 3D 3-space field. Each
              dimension of the output field will extend from the minimum
              value to the maximum value for that coordinate in the input
              field. Coordinates in the input field are truncated to
              integers. Accordingly, if a dimension of the input field
              extends from 15.3 to 19.0, the output field will have 5
              elements in that dimension.

Name        : strip_cfd       Version      : 1.000     Mod Number : 1319
Author      : Rob Kuyper, Univeristy of Technology Delft, The
              Netherlands
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : strip cfd is a filter module which changes a cfd dataset in
              order to remove the staggering of velocity components (in
              finite volume methods) or to remove virtual points from the
              dataset.

Name        : Colored_bounds  Version      : 2.000     Mod Number : 1200
Author      : D. LE CORRE, CONVEX S.A
Submitted   : 05/08/92        Last Updated : 08/30/92  Language   : C
Ported to   : DEC Kubota Convex HP IBM
Description : This mapper module generates a geometry consisting of 6
              orthogonal slices (2 in each dimension) from a 3D scalar
              field. By default, the 6 ortho slices are placed at the hull
              of the input field. The faces of this geometry are colored
              from the scalar field value.

Name        : Field_grid      Version      : 1.000     Mod Number : 1307
Author      : Penny Rheingans, US EPA Scientific Visualization Center
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Generates a labelled grid and/or axes for field data. The
              extents of the grid or axes are the extents of the data (or
              slightly larger).

Name        : UCD_grid        Version      : 1.000     Mod Number : 1308
Author      : Penny Rheingans, US EPA Scientific Visualization Center
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Generates a labelled grid and/or axes for ucd data. The
              extents of the grid or axes are the extents of the data (or
              slightly larger).

Name        : new_bubbleviz   Version      : 1.000     Mod Number : 1318
Author      : Wes Bethel, Lawrence Berkeley Laboratory
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC HP
Description : The bubbleviz module generates spheres of various radii
              and colors at the element locations of a 1D, 2D or 3D field.
              This is a "cuberille" style of volume visualization,
              except that it uses spheres rather than cubes. This module
              can be used for non-uniform input fields.

Name        : ucd_to_prim     Version      : 1.000     Mod Number : 1312
Author      : Penny Rheingans, US EPA Scientific Visualization Center
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : This module takes an input ucd structure and generates a
              geometric primitive (sphere or prism) for each node of the
              structure. Primitives are colored according to a selected
              value at the node and an optional input colormap. If no
              colormap is provided, primitives will be mapped with a grey
              scale.

Name        : WrUcdAnim       Version      : 1.000     Mod Number : 1317
Author      : D. LE CORRE, CONVEX S.A
Submitted   : 08/30/92        Last Updated : 08/30/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : 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.

Name        : BP_Coroutine    Version      : 1.000     Mod Number : 1325
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : This module is a source example of how to write a
              free-running asynchronous coroutine that provides data
              to AVS on the output port when data is ready. In its present
              form, it free-runs, that is continually sends data to AVS as
              fast as it can be processed. The project specific version of
              this had external calls to obtain data from a data
              acquisition instrument.

Name        : Edit_String     Version      : 1.000     Mod Number : 1328
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : DEC
Description : The Edit String module puts up a LONG dialog box, allows
              typing of any string, then with either "OK" or "CANCEL"
              controls, will output this string to the output port of the
              module. The next time the "Edit" button is pushed, the
              dialog box reappears, with the old string, which can be
              edited. This module is for long expressions, lists of ints,
              etc, where the normal string type_in widget is too small.
              The dialog box comes up with nicer colours than the default
              grey.

Name        : Read_Hologram   Version      : 1.000     Mod Number : 1322
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : FORTRAN
Ported to   : Convex HP
Description : A well-commented Reader for 2D field data, in FORTRAN, that
              combines ASCII file inport in fixed FORTRAN FORMAT, and
              does numeric computation on the data before sending it to
              the output port. It allows multiplication of a coefficient
              on one particular row, defined by a channel dial. This is
              intended as a working example of a FORTRAN read module, to be
              modified by others.

Name        : Tick_Marks      Version      : 1.000     Mod Number : 1338
Author      : Jeffrey A Thingvold, National Center for Supercomputing
              Applications
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : The tick mark module creates sheets with major and minor
              line grids along the three primary axes. It makes
              polytriangle objects, not lines, so they can have variable
              thickness. It also has label annotation on the 3D object.

Name        : animated_track  Version      : 1.000     Mod Number : 1329
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Animated Track uses the "track" widget to control
              transformations by producing a 4x4 transformation
              matrix, or using direct geometry object transformation
              control. The track control is in "immediate" mode, so that
              transformations are send dynamically in a stream to the
              rest of the network. The module has both Field and Geom
              output ports, so that either one or both may be used. The
              module is a coroutine, so that animation sequences could be
              added by inserting matrix modification code to the inner
              loop.

Name        : endif           Version      : 1.000     Mod Number : 1336
Author      : John Tee, AVS Inc. Consultant
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : FORTRAN
Ported to   : DEC Convex HP
Description : Two modules, "if" and "endif" can be used to make a logical
              branch in a flow network. The "if" module copies the input to
              one of two output ports, based on a boolean flag, while
              "endif" copies one of two input ports data to the output
              port, closing the condition. Different processing
              modules can then be placed along the two logical branches of
              the network. Both modules are in Fortran, and dynamically
              allocate new space for the output fields.

Name        : if_2            Version      : 1.000     Mod Number : 1337
Author      : John Tee, AVS Inc. Consultant
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : FORTRAN
Ported to   : Convex HP
Description : Two modules, "if" and "endif" can be used to make a logical
              branch in a flow network. The "if" module copies the input to
              one of two output ports, based on a boolean flag, while
              "endif" copies one of two input ports data to the output
              port, closing the condition. Different processing
              modules can then be placed along the two logical branches of
              the network. Both modules are in Fortran, and dynamically
              allocate new space for the output fields.

Name        : read_blokjes    Version      : 1.000     Mod Number : 1332
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Read Blokjes is a module that imports blocks, or bricks, and
              creates geometric objects appropriate for the Geometry
              Viewer. The format is from a CFD package called FLOWTHERM
              from Flowmerics Ltd., Kingston, Surrey, England, KT2 5AA.
              This module is only one part of a more extensive interface
              system. As each block is separate, the property on each one
              can be edited, changing colour, transparency, rendering
              mode, etc. Each block has a name, type, and start and end
              corner points.

Name        : read_semper     Version      : 1.000     Mod Number : 1339
Author      : Michel DROZ
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Read Semper accesses an image file format from the SEMPER
              image processing system. The entire file is read into
              memory, and sent to the Image output port for further
              processing by other AVS modules. The Y scan line order is
              reversed compared to other AVS images, so the image will
              appear upside down unless reversed with "mirror". The
              images are generally in "xxx.pic" named file.

Name        : Geom_Duplicate  Version      : 1.000     Mod Number : 1335
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Merge up to 4 seperate geometries into one, with the
              multiple geom input ports, then replicate the combined
              object N times with a positional offset between them. Each
              copy is a unique object in the Geometry Viewer, so may be
              transformed or have properties edited independently.

Name        : Nvect_to_2d     Version      : 1.000     Mod Number : 1323
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : FORTRAN
Ported to   : Convex HP
Description : Converts "field 1D uniform real N-vector" to "field 2D
              uniform real scalar" by making the vector-length into the
              second dimension

Name        : image_tile      Version      : 1.000     Mod Number : 1330
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : Creates a replicated (tiled) version of the input image. It
              uses a simple horizontal pixel duplication, to make a small
              postage stamp image fill a box. The input image height and
              width is reported. This module was used in a demo to a design
              studio that manufactures ceramic tiles for kitchens and
              bathrooms. Maybe you know someone in wallpaper or fabric?
              It is also used to synthesize a Y dimension, to create an
              image from 1D data.

Name        : color_legend    Version      : 2.000     Mod Number : 1019
Author      : Wes Bethel, Lawrence Berkeley Laboratory
Submitted   : 10/10/91        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Kubota Convex HP IBM
Description : This module takes an input colormap and generates a "color
              legend," consisting of a number of geometry objects which
              may be subsequently rendered using the geometry viewer
              module. The range of colors in the color scale is controlled
              by the input colormap. All colors in the colormap are
              represented in the output color scale. In addition to the
              smoothly shaded "color bar", the user may control various
              parameters relating to labeling characterisitics, and
              legend orientation. Version 2 fixes (by Dr. John Tee, AVS
              Inc consultant) make the code more portable by using
              standard AVS routine calls.

Name        : scatter_arrows  Version      : 1.000     Mod Number : 1326
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC HP
Description : This module draws vectors with arrow heads from scatter
              input showing vector data at the specified positions. The
              module will draw both 2D and 3D vectors, as required. The
              Scale dial is simply a length multiplier.

Name        : scatter_bounds  Version      : 1.000     Mod Number : 1334
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : This module draws a white bounding box from scatter input
              (1D irregular fields, or random collections of points)
              showing data min/max positions. It can be used with
              "scatter dots".

Name        : scatter_cubes   Version      : 1.000     Mod Number : 1333
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : Sun DEC Convex HP
Description : This module draws variable size coloured cubes from
              scatter input showing scalar data at the specified
              positions. It can be used in place of "scatter dots". The
              Scale dial is simply a size multiplier. The size of each cube
              is taken by the first vector if "Variable", otherwise it is
              set to "Scale" size in "Uniform" mode. The colour of each
              cube is independently controled from the remaining three
              vector quantities. If the input vector length is 1
              (scalar), the colour will default to white.

Name        : print_iv_pick   Version      : 1.000     Mod Number : 1324
Author      : Ian Curington, Advanced Visual Systems
Submitted   : 08/31/92        Last Updated : 08/31/92  Language   : C
Ported to   : DEC HP
Description : 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.







