DReAMM Overview
This flow chart (click here for larger image) outlines the principal DReAMM Operations and Control Panels (menus). Note that:
- Most often, mesh objects will be triangulated surfaces or tetrahedral or cuboidal volumes.
- File formats for meshes can be OpenDX (.dx suffix), 3df (.3df, from CAD software), or ASCII VRML 1.0 (.wrl).
- Meshes output by MCell for DReAMM are in OpenDX format. MCell also exports molecule and effector site positions and states in OpenDX format for visualization with DReAMM.
- For MCell simulations, the names are defined in the MDL (Model Description Language) files used for the simulations.
- In cases of other mesh input files, existing object names are used whenever possible. Otherwise DReAMM will assign default names (object_1, object_2, & ).
- You can use UNIX-style wildcard characters to filter names (see Filtering Objects) and dramatically speed up operations on thousands of objects.
- You can use very long object names without dramatic speed penalties (up to 1024 characters per name).
- In Default mode, all of the selected objects receive the same color, opacity, and shading, as well as other rendering properties (e.g., choice of glyph for molecules or effector sites).
- In Custom mode, each object is looked up by name in a user-editable table (see the Overview of Lookup Tables tutorials). If the matching object name is found in the table, the corresponding properties are applied, otherwise the object is omitted (not rendered). Custom settings include the option of user-editable Color and Opacity Maps on an object-by-object basis (see Advanced DReAMM tutorials).
- As when selecting objects, wildcard filtering can be used when assigning custom properties to speed up operations on thousands of objects.
- Software rendering is performed by the computer's CPU (central processing unit), while hardware rendering is performed by the video card's GPU (graphical processing unit).
- If DReAMM is running with PSC_DX (required for DReAMM v.3.x), hardware rendering matches software rendering. If DReAMM is running with OpenDX, hardware rendering does not include two-sided lighting and also suffers from some shading bugs.
- Hardware rendering can be much faster than software rendering but is limited to objects that can fit in the memory on the video card.
- Software rendering is slower than hardware rendering but may be advantageous or required for large objects, and is also used for additional flexibility and features when Saving Images and/or rendering Stereo pairs.









