-
-
September 27, 2017 at 11:19 am
admin
Ansys EmployeeMeshing application issues this error message to alert the user that same geometrical entity is selected in two different Named Selections. This is problematic as Named Selections are used to apply boundary conditions and having one edge/face in two different Named Selections may lead to conflicting conditions assigned to the same boundary. Therefore this issue must be resolved before exporting the mesh in a solver-readable format. You can resolve this issue by identifying the overlapping geometry in Named Selections. You can right click on Mesh object in the Outline panel, and select Show > Geometry in Overlapping Named Selections. This will highlight the offending geometry in the Graphics window. For better visibility of the highlighted geometry, you may want to switch to the wireframe mode. Now you can check the Named Selections that contains these entities and ensure that each of them are only included in one Named Selection. Once all overlaps are resolved, you can proceed with the mesh update and export.
-
September 27, 2017 at 11:19 am
admin
Ansys EmployeeHow to Fix the Error: "Mesh Exporter does not Support Overlapping Geometry in Named Selections"?
-
February 14, 2020 at 2:05 pm
CFDKING
SubscriberI am dealing with 2D thermal-fluid flow with the contact region of solid surface.
What I did in the design modeller is that I have created 2 different surfaces by using add frozen method. As you know , in that way it will allow me to create seperate surfaces properly. (note: each surfaces has been created by seperate lines)
in the contact line I have two different surface lines. the first line should belong to fluid zone and the other should belong to solid zone as a boundary condition.(because later on i will solve coupling system and assign interface to these lines) I have assign it surface by surface. Let say, the fuild boundary line belongs to the surface which is used for fuild mesh zone and the other belongs to the surface which is used for solid mesh zone.(note: these lines are identically same but on the different surface)
I have checked it from show dependency option and each boundary lines belongs two different surfaces.
I have generated mesh. However, when I transfer it to the fluent it gives me an error saying overlapping named selection exists.
Where did I do a mistake? Anyone knows it?
-
February 14, 2020 at 4:04 pm
Rob
Forum ModeratorDid you create a multibody part?
-
February 14, 2020 at 7:26 pm
CFDKING
SubscriberHi, Thanks for reply. Can you please a little extend your question? Because I dont know what it is and might solve my problem. Hint: I have seperate surfaces in the model tree. And to have a consistent (conformal) mesh , I have created " form a part". -
February 17, 2020 at 5:52 am
Keyur Kanade
Ansys EmployeeOnce you create single part with 'form a part' then the mesh will be conformal. This means you will have single edge between two surfaces.
As a practice you can give named selections in Meshing instead of DM.
-
February 17, 2020 at 8:56 am
CFDKING
SubscriberNo, I have solved this issue by selecting shared topology as "IMPRINTS". In that way, in the meshing part I had contact regions that allows me to create two different BC in a same line. Thanks. -
February 17, 2020 at 11:18 am
Rob
Forum ModeratorYes, except you also now have a non conformal mesh. Nothing wrong with that, but conformal mesh will tend to be marginally faster and more accurate (dependent on jumps in cell size etc).
-
February 17, 2020 at 11:29 am
CFDKING
SubscriberHi rwoolhou,
I have a conformal mesh with IMPRINTS methods. Are you sure that it is not creating conformal mesh?
Each cells are touching each other in the transition area.
Note: I asked this because it might seem like conformal but indeed it may not work as conformal behind the scenery. ???
-
February 17, 2020 at 2:33 pm
Rob
Forum ModeratorIf you have two labels at the contact position & walls on transfer to Fluent it's non-conformal. Note, it's possible to have a non-conformal mesh with the same mesh on both sides, just to confuse things. If you have a wall - wall:shadow pair or interior zone at that location in Fluent you're fully conformal and good to run the model. If not you may need to set up a mesh (grid) interface.
If I remember correctly, imprint was originally intended to create the face splits but then not connect the surfaces for reasons that no one could ever explain: it later became useful with user specified share topology/connect for a few applications. Whether that's changed since I last tried it is unknown!
-
February 17, 2020 at 3:20 pm
-
October 15, 2021 at 3:19 pm
Parsons444
Subscriber.Hello,
Regarding the initial title on this post. Initially I had one named selection for the sky, however this gave the error as described in the post. However, after changing the selection to a seperate section, I am still getting the same error. Please could someone provide some advice as to how to fix this?
. -
April 26, 2022 at 1:52 pm
skydownunder
Subscriber.Try to review your named selections. I also encounter the same issue before and noticed that some faces/objects are included in 2 named selections. After I separate and re-select it, the error was no more.
.
-
- The topic ‘How to Fix the Error: “Mesh Exporter does not Support Overlapping Geometry in Named Selections”?’ is closed to new replies.
-
3572
-
1188
-
1076
-
1063
-
952
© 2025 Copyright ANSYS, Inc. All rights reserved.