For the past few years I have been using OpenDX to post-process the results of 
a 3D radiation transport code.  I am concerned that with expected increases in 
the size of the analysis models I may soon reach a point where OpenDX may not 
be a viable option for post-processing.

As a hypothetical example, consider a 3D model with 200,000,000 mesh cells.  
(This is significantly larger than current models, but a realistic projection 
based on trends in computer resources.)  The model geometry is based on a 
structured rectilinear grid which can be represented as a product array of 3 
vectors (i.e., the X, Y, and Z mesh spacings).  Each mesh cell has a 
connection-dependent value (byte or integer) which represents the material 
composition in that cell.  Each cell will also have one (and possibly more) 
position-dependent values (real) which represent an analysis result.  

For typical visualizations, the composition data is processed using Color --> 
ShowBoundary --> Image, typically after passing through an Include module to 
exclude certain materials from the image.  The real data is generally processed 
using Isosurface, with the Isosurface output being Collected with the 
ShowBoundary output.  

It seems to me that I have two options to deal with expected model size 
increases:

1)  Hope for a 64-bit version of OpenDX, preferably one which will run in 
parallel on distributed memory systems, or
2)  Explore other data visualization options

Any suggestions from those of you who have more experience in this area?

Thanks,

Joel Risner
[EMAIL PROTECTED]



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.clearswift.com
**********************************************************************

Reply via email to