[ICEM] Meshing problem in Formula one

diamondx · January 20, 2013, 10:14

may i know where does the problem lie ??

Far · January 20, 2013, 19:19

Ali this method is perfect. But I am not able to generate the volume mesh in the inner domain through denauly. No matter Whatever I do, I always get one big larger than inner domain!!!!

diamondx · January 20, 2013, 20:43

how come ?? you did it already with tgrid ???

Far · January 28, 2013, 06:00

Now I am trying to generate denauly using surface mesh as shown in previous posts. But volumes are leaking as can be seen attached Figs.
What is the problem? I checked through build topology and did not find any problem there.

diamondx · January 28, 2013, 08:55

but if you remove the small box and consider the big beometry , wil it work ???
How about in t-grid ? will it do same ?

Far · January 28, 2013, 09:13

Big box is deleted so there is only small box (should be same now? ). Tgrid does make the grid and even prisms successfully but there is some thing strange happening there as well (quite different than ICEM)

Far · January 28, 2013, 09:57

Tgrid is making prisms in the first wing (from left to right on screen) correctly but it is penetrating prism inside the wing instead of extruding them on wing 2 and 3. See attached pics and files are also attached.

https://dl.dropbox.com/u/68746918/Inneronly.rar

diamondx · January 28, 2013, 11:33

i get the same mesh as you

PSYMN · January 28, 2013, 11:55

Quote:

Originally Posted by Far

Now I am trying to generate denauly using surface mesh as shown in previous posts. But volumes are leaking as can be seen attached Figs.
What is the problem? I checked through build topology and did not find any problem there.

That doesn't look like leaking... It is some other problem. I have seen it before, but not for years. I recall it had something to do with an edit operation that triggered a bug where the nodes were mis-numbered during the save operation.

There are two sets of node numbers, the ones in the forground and the ones in the background...

Basically, it messes up the surface mesh node numbers in the background so that when delaunay runs it gets the wrong connectivity.

To fix it, try running the Edit mesh option to re-number nodes before running delaunay.

Marinus · April 21, 2013, 07:50

Quote:

Originally Posted by PSYMN

That doesn't look like leaking... It is some other problem. I have seen it before, but not for years. I recall it had something to do with an edit operation that triggered a bug where the nodes were mis-numbered during the save operation.

There are two sets of node numbers, the ones in the forground and the ones in the background...

Basically, it messes up the surface mesh node numbers in the background so that when delaunay runs it gets the wrong connectivity.

To fix it, try running the Edit mesh option to re-number nodes before running delaunay.

I am having the same problem, re-numbering the nodes did not fix it. Any other suggestions?

Far · April 21, 2013, 08:50

Delete mesh and regenerate surface mesh. After that compute mesh.

PS: There is no clear pattern for this problem to happen

Marinus · April 23, 2013, 10:40

Quote:

Originally Posted by Far

Delete mesh and regenerate surface mesh. After that compute mesh.

PS: There is no clear pattern for this problem to happen

Eventually the problem did not show up when I first made an octree mesh, then after saving deleting the volume mesh and then computing the delauney volume mesh from the surface mesh.

Somewhere during saving the element numbers were changed automatically, however when I tried doing this manually it did not fix the problem. Maybe I did this wrong. Luckely I found a working solution

.

Thanks for the help.

Far · April 23, 2013, 11:45

What working solution you found?

Marinus · April 23, 2013, 12:36

Quote:

Originally Posted by Far

What working solution you found?

As I described, first I saved the octree mesh. Then deleted the volume mesh, then created Delaunay. Works for me.

January 20, 2013, 10:14		#101
diamondx Super Moderator Ghazlani M. Ali Join Date: May 2011 Location: Tokyo, Japan Posts: 1,385 Blog Entries: 23 Rep Power: 29	may i know where does the problem lie ?? __________________ Regards, New to ICEM CFD, try this document --> https://goo.gl/KAOIwm Ali

January 20, 2013, 20:43		#103
diamondx Super Moderator Ghazlani M. Ali Join Date: May 2011 Location: Tokyo, Japan Posts: 1,385 Blog Entries: 23 Rep Power: 29	how come ?? you did it already with tgrid ??? __________________ Regards, New to ICEM CFD, try this document --> https://goo.gl/KAOIwm Ali

January 28, 2013, 06:00	Problem in Denauly mesh	#104
Far Super Moderator Sijal Join Date: Mar 2009 Location: Islamabad Posts: 4,553 Blog Entries: 6 Rep Power: 54	Now I am trying to generate denauly using surface mesh as shown in previous posts. But volumes are leaking as can be seen attached Figs. What is the problem? I checked through build topology and did not find any problem there.

January 28, 2013, 08:55		#105
diamondx Super Moderator Ghazlani M. Ali Join Date: May 2011 Location: Tokyo, Japan Posts: 1,385 Blog Entries: 23 Rep Power: 29	but if you remove the small box and consider the big beometry , wil it work ??? How about in t-grid ? will it do same ? __________________ Regards, New to ICEM CFD, try this document --> https://goo.gl/KAOIwm Ali

January 28, 2013, 11:33		#108
diamondx Super Moderator Ghazlani M. Ali Join Date: May 2011 Location: Tokyo, Japan Posts: 1,385 Blog Entries: 23 Rep Power: 29	i get the same mesh as you __________________ Regards, New to ICEM CFD, try this document --> https://goo.gl/KAOIwm Ali

January 20, 2013, 19:19		#102
Far Super Moderator Sijal Join Date: Mar 2009 Location: Islamabad Posts: 4,553 Blog Entries: 6 Rep Power: 54	Ali this method is perfect. But I am not able to generate the volume mesh in the inner domain through denauly. No matter Whatever I do, I always get one big larger than inner domain!!!!

January 28, 2013, 09:13		#106
Far Super Moderator Sijal Join Date: Mar 2009 Location: Islamabad Posts: 4,553 Blog Entries: 6 Rep Power: 54	Big box is deleted so there is only small box (should be same now? ). Tgrid does make the grid and even prisms successfully but there is some thing strange happening there as well (quite different than ICEM)

January 28, 2013, 09:57		#107
Far Super Moderator Sijal Join Date: Mar 2009 Location: Islamabad Posts: 4,553 Blog Entries: 6 Rep Power: 54	Tgrid is making prisms in the first wing (from left to right on screen) correctly but it is penetrating prism inside the wing instead of extruding them on wing 2 and 3. See attached pics and files are also attached. https://dl.dropbox.com/u/68746918/Inneronly.rar

April 21, 2013, 08:50		#111
Far Super Moderator Sijal Join Date: Mar 2009 Location: Islamabad Posts: 4,553 Blog Entries: 6 Rep Power: 54	Delete mesh and regenerate surface mesh. After that compute mesh. PS: There is no clear pattern for this problem to happen

April 23, 2013, 11:45		#113
Far Super Moderator Sijal Join Date: Mar 2009 Location: Islamabad Posts: 4,553 Blog Entries: 6 Rep Power: 54	What working solution you found?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Problem with querying the meshing database in CFX-Pre	ashtonJ	CFX	18	April 18, 2023 23:49
[Other] Hex meshing problem DM12	patrick	ANSYS Meshing & Geometry	7	January 9, 2015 07:21
[GAMBIT] 3D boundary layer and meshing problem in GAMBIT 2.4.6	prashanthreddyh	ANSYS Meshing & Geometry	1	December 20, 2011 00:35
[ICEM] Hexa meshing blocking problem	fergal	ANSYS Meshing & Geometry	0	June 28, 2011 10:01
Strange ANSYS Meshing 13.0 Problem	brunob	ANSYS Meshing & Geometry	3	June 21, 2011 20:03