aboutsummaryrefslogtreecommitdiff
path: root/doc/html/VizReaders.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/VizReaders.html')
-rw-r--r--doc/html/VizReaders.html109
1 files changed, 109 insertions, 0 deletions
diff --git a/doc/html/VizReaders.html b/doc/html/VizReaders.html
new file mode 100644
index 0000000..a6e23cf
--- /dev/null
+++ b/doc/html/VizReaders.html
@@ -0,0 +1,109 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
+<html>
+ <head>
+ <title>IEEIO Readers</title>
+ </head>
+
+ <body bgcolor="#F0F0F0">
+ <h1>Readers for Visualization Systems</h1>
+ <hr>
+ <h1>AVS Reader</h1>
+ <a href="http://bach.ncsa.uiuc.edu/Viz/AVS">AVS</a> is a product
+ of
+ <a href="http://www.avs.com">Advanced Visual Systems Inc.</a>
+ and is very popular for 3D data visualization problems. The
+ reader for AVS is a module called <b>Read_IEEEIO</b> and
+ provides roughly the same user interface as the HDF reader
+ module provided by NCSA. You use the file browser to select an
+ IEEEIO file to open (the file extension for this type of file is
+ <i>.ieee</i> or <i>.raw</i>. If more than one record is found
+ in the file then an integer dial will appear that allows you to
+ select records in the file.<p>
+
+ By default, the module will set the extents of the dataset to be
+ equal to the dimensions of the object with an origin at 0,0,0
+ (eg. if your object is an array with dimensions {30,40,50}
+ then the extents will be set so that the origin of the data in
+ 3D space is {0.0,0.0,0.0} and its maximum extent will be
+ {30.0,40.0,50.0}). The module recognizes attributes with the
+ following names
+ (<a href="UsingF77.html#WriteAttribs">F77</a>,
+ <a href="UsingC.html#WriteAttribs">C</a>,
+ <a href="UsingC++.html#WriteAttribs">C++</a>)<a
+ href="Using.html">
+ <img border=0 src="Images/info.s.gif"> </a>
+ <UL>
+ <LI><b>origin</b><br>
+ This will set the origin (min_extent) of the dataset in 3D
+ space in AVS.
+ This can be a vector of Float32 or Float64 numbers with a
+ length equal to the number of dimensions in the dataset.
+ <LI><b>delta</b><br>
+ This is the delta-spacing (dx) between elements of the
+ dataset. This is multiplied by the number of elements in
+ the dimension to get the total size of that coordinate of
+ the dataset. It normally used with the <b>origin</b> attribute.
+ This can be a vector of Float32 or Float64 numbers with a
+ length equal to the number of dimensions in the dataset.
+ <LI><b>min_ext</b><br>
+ This will treat the dataset as a bounding box and
+ set the min_extent of the dataset in 3D space in AVS.
+ This can be a vector of Float32 or Float64 numbers with a
+ length equal to the number of dimensions in the dataset.
+ <LI><b>max_ext</b><br>
+ This works with <b>min_ext</b> and sets the maximum extent
+ of the bounding box of the dataset in AVS (the max_extent).
+ This can be a vector of Float32 or Float64 numbers with a
+ length equal to the number of dimensions in the dataset.
+ </UL>
+ <p>
+
+ <b>Download Read_IEEEE for AVS</b><br>
+ <UL>
+ <LI><a href="AVSreadIEEE.tar.Z">AVSreadIEEE.tar.Z</a> :
+ The full tarred source (the files it contains are described
+ below).
+ <LI><a href="src/Makefile.AVSreadIEEE">Makefile</a> :
+ The makefile to build the module.
+ It assumes you have already built <a href="Aquiring.html">libieeeio.a</a>.
+ <LI><a href="src/AVSreadIEEE.c">AVSreadIEEE.c</a> :
+ The AVS module wrapper for the reader.
+ <LI><a href="src/AVSreadcpp.cc">AVSreadcpp.cc</a> :
+ The actual guts of the module that does the reading using libieeeio.a.
+ </UL>
+ To compile, you need to change the <b>AVS_PATH</b> variable
+ to point to the root of your avs installation and then type
+ <b>make</b> to build the module.<p>
+ <hr>
+
+ <h1>IDL/PV-Wave Reader</h1>
+ <a href="http://www.rsinc.com">IDL</a> and PV-Wave have a common
+ root in that they originated from a language developed by
+ David Stearns at the University of Colorado.<a
+ href="http://consult.ncsa.uiuc.edu/docs/viz/Idl/"><img
+ border=0 src="Images/info.s.gif"></a> Both
+ are now competing products with many differences in their
+ capabilities but the underlying language is pretty
+ much the identical. So this reader will work in either system.<p>
+
+ Since this is implemented as a native IDL/Wave procedure, you
+ need not compile or link the IEEEIO libraries on your system
+ to make use of this. It is completely portable since IDL is
+ an interpreted language.<p>
+
+ <b>Download IDL/PV-Wave IEEEIO reader</b><br>
+ <UL>
+ <LI><a href="src/ieeereader.pro">ieeereader.pro</a> : The
+ IDL/Wave IEEEIO Reader procedure.
+ <LI><a href="UsingIDL.html">Information on how to use the
+ IDL/Wave IEEEIO Reader</a>
+ </UL>
+
+ <hr>
+ <address><a href="mailto:jshalf@suttung.aei-potsdam.mpg.de">John Shalf</a></address>
+ <!-- Created: Tue Apr 8 17:04:45 MDT 1997 -->
+ <!-- hhmts start -->
+Last modified: Tue Apr 8 18:27:05 MDT
+<!-- hhmts end -->
+ </body>
+</html>