aboutsummaryrefslogtreecommitdiff
path: root/doc/html/VizReaders.html
blob: a6e23cfa2f83378381967fb77a885351225dc33c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
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>