Hard, I'm afraid. Each module does its own thing on each element type - eg. MapToPlane has code to MTP each element type, Isosurface has code to isosurface each element type etc, etc, etc. Often, there are several methods, depending on whether the positions component is regular, partitially regular, or fully irregular. I'm curious - where do problems arise with degenerate cubes? I'll grant the 1/3 overhead for the connections component and neighbors. Anything else?
Greg
Neil Carlson
<[EMAIL PROTECTED]> To:
[email protected]
Sent by: cc:
[EMAIL PROTECTED] Subject: [opendx-dev] adding a
new element type
son.ibm.com
05/30/2002 10:51 AM
Please respond to
opendx-dev
I've got data on a mesh consisting of prism elements. I'm in the
midst of attempting to use degenerate cube elements (it gives the
server severe fits for large meshes--I'll post more on this to the
user list after I've experimented more), but would obviously much
rather use a native prism element if it existed. Does anyone have
a sense of how involved it would be to add such an element type to
DX? Is the element type handling well encapsulated? If it's not
too difficult I'd be tempted to take a stab at it.
--
Neil N. Carlson Motorola, Los Alamos Research Park
Motorola Labs / PSRL 4200 W. Jemez Road, Suite 300
Computational Nanoscience Group Los Alamos, New Mexico 87544
[EMAIL PROTECTED] Fax: (505) 663-5150
Voice: (505) 663-5106 Pager: [EMAIL PROTECTED] or
888-946-2817
