ICEM HDF Connectivity

Glockenspiel · June 30, 2009, 19:04

Hello All,

I've been given a simple, 5 block, structured mesh of a cylinder generated in ICEM and exported in the HDF5 format. Unfortunately, it seems that the transformation vector given in the ICEM-generated HDF5 file is not consistent with the SIDS-CGNS standard. Would anyone happen to know what the relationship of the <Constant Index, First Index, Second Index> to the SIDS connectivity standard is for structured meshes?

Thanks
-Glockenspiel

Glockenspiel · July 2, 2009, 00:43

Thought I'd update this for anyone else that might encounter the problem. The ICEM generated <Constant Index, First Index, Second Index> for the current block patch correspond (more or less) to the index locations of the standard SIDS transformation vector. The donor patch <Constant Index, First Index, Second Index> values are then substituted into the transformation vector.

I.E.
My Block Vector
<1,2,3> (these are you index values)
Donor Block Vector
<3,1,2>

...substituting the first value yields:
<3,_,_>
the second:
<3,1,_>
finally:
<3,1,2>

Of course, you'll need to program in some sort of logic to consider the bounds of the abutting faces (i.e. a i-low abutting against a k-low face) and for the case where you might have a negative value in one of the block indices indicating the start/end nodal locations differ between the blocks.

At any rate, I hope this can help someone...if clarification is needed just post a reply and I'll do my best to assist.

June 30, 2009, 19:04	ICEM HDF Connectivity	#1
Glockenspiel New Member Join Date: Jun 2009 Posts: 3 Rep Power: 17	Hello All, I've been given a simple, 5 block, structured mesh of a cylinder generated in ICEM and exported in the HDF5 format. Unfortunately, it seems that the transformation vector given in the ICEM-generated HDF5 file is not consistent with the SIDS-CGNS standard. Would anyone happen to know what the relationship of the <Constant Index, First Index, Second Index> to the SIDS connectivity standard is for structured meshes? Thanks -Glockenspiel

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
ICEM BC to FLUENT	Simon	CFX	3	September 9, 2008 18:08
Design Modeler to ICEM.....	Joe	CFX	0	January 24, 2008 04:39
re: ICEM vs. ICEM WB	Wooster	CFX	4	October 15, 2007 13:47
ICEM 10 mesh scale foe CFX	Korsh Mik	CFX	2	October 7, 2005 10:07
ICEM CFD 5.1 Hex-Tet mesh merging failure	bogesz	CFX	1	January 29, 2005 07:46

July 2, 2009, 00:43		#2
Glockenspiel New Member Join Date: Jun 2009 Posts: 3 Rep Power: 17	Thought I'd update this for anyone else that might encounter the problem. The ICEM generated <Constant Index, First Index, Second Index> for the current block patch correspond (more or less) to the index locations of the standard SIDS transformation vector. The donor patch <Constant Index, First Index, Second Index> values are then substituted into the transformation vector. I.E. My Block Vector <1,2,3> (these are you index values) Donor Block Vector <3,1,2> ...substituting the first value yields: <3,_,_> the second: <3,1,_> finally: <3,1,2> Of course, you'll need to program in some sort of logic to consider the bounds of the abutting faces (i.e. a i-low abutting against a k-low face) and for the case where you might have a negative value in one of the block indices indicating the start/end nodal locations differ between the blocks. At any rate, I hope this can help someone...if clarification is needed just post a reply and I'll do my best to assist.