domainlib.a -- pid not matching domain number ?

February 2, 2008, 06:12

Hi all,

I have a problem with 'domainlib.a', and need help from someone who knows a bit about ICEM internals: I used this lib to write a converter for unstructured ICEM grids. In a previous unstructured grid (probably Ansys v10. ICEM), the domains are indexed and named as follows (using domainlib routine DFDNAME):

0. ORFN 1. PPS

2. PSS ...

... 22. prescribed nodes 23. curve nodes 24. surface nodes 25. volume nodes 26. periodic_nodes_0 27. periodic_nodes_1

Up to #21, these are domains as shown by ICEM user interface, and from #22 on appear some domains I did not know about, i.e. not created by me, probably for internal usage by ICEM.

Now I created another unstructured grid, with Ansys v11 ICEM, these internal domains appear upfront, with slightly different names:

0. periodic_nodes_0 1. periodic_nodes_1

2. prescribed nodes 3. curve nodes

4. surface nodes 5. volume nodes

6. GEOM 7. INLET

8. OUTLET ...

However, the PID (Property ID) of the elements (as retrieved by domainlib routine DFRDEL), start counting from somewhere in the middle (i.e. with an offset of -4 or so).

No the question is: Is there some domainlib routine that helps mapping, is there a new convention I do not know about, or is ICEM now all of a sudden incompatible with domainlib.a ?

Thanks Christian Fuchs

February 2, 2008, 07:51

Apparently the error occured because I used 'hex.uns', which is different from the final '<project>.uns. I have no problems with the latter one.

February 2, 2008, 06:12	domainlib.a -- pid not matching domain number ?	#1
Christian Fuchs Guest Posts: n/a	Hi all, I have a problem with 'domainlib.a', and need help from someone who knows a bit about ICEM internals: I used this lib to write a converter for unstructured ICEM grids. In a previous unstructured grid (probably Ansys v10. ICEM), the domains are indexed and named as follows (using domainlib routine DFDNAME): 0. ORFN 1. PPS 2. PSS ... ... 22. prescribed nodes 23. curve nodes 24. surface nodes 25. volume nodes 26. periodic_nodes_0 27. periodic_nodes_1 Up to #21, these are domains as shown by ICEM user interface, and from #22 on appear some domains I did not know about, i.e. not created by me, probably for internal usage by ICEM. Now I created another unstructured grid, with Ansys v11 ICEM, these internal domains appear upfront, with slightly different names: 0. periodic_nodes_0 1. periodic_nodes_1 2. prescribed nodes 3. curve nodes 4. surface nodes 5. volume nodes 6. GEOM 7. INLET 8. OUTLET ... However, the PID (Property ID) of the elements (as retrieved by domainlib routine DFRDEL), start counting from somewhere in the middle (i.e. with an offset of -4 or so). No the question is: Is there some domainlib routine that helps mapping, is there a new convention I do not know about, or is ICEM now all of a sudden incompatible with domainlib.a ? Thanks Christian Fuchs

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
[snappyHexMesh] Number of cells in mesh don't match with size of cellLevel	colinB	OpenFOAM Meshing & Mesh Conversion	14	December 12, 2018 08:07
[snappyHexMesh] SnappyHexMesh for internal Flow	vishwa	OpenFOAM Meshing & Mesh Conversion	24	June 27, 2016 08:54
[snappyHexMesh] jagged, ragged edges...	ziemowitzima	OpenFOAM Meshing & Mesh Conversion	138	July 23, 2012 23:41
Reynolds Number matching in Cavity flow	Endee	Main CFD Forum	6	April 20, 2010 04:47
[snappyHexMesh] external flow with snappyHexMesh	chelvistero	OpenFOAM Meshing & Mesh Conversion	11	January 15, 2010 19:43

February 2, 2008, 07:51	Re: domainlib.a -- SOLVED.	#2
Christian Fuchs Guest Posts: n/a	Apparently the error occured because I used 'hex.uns', which is different from the final '<project>.uns. I have no problems with the latter one.