Learning Forum

[kevinu2]

Hello, I am trying to setup a linear periodic B.C. in Mechanical. I am getting the following error message: "The meshing algorithm cannot find matching topology. Please verify the topology and the position as well as the orientation of any associated coordinate systems."

The mesh builds successfully, but when solving, it says the mesh file is corrupted. Based on previous threads, I have checked the area and number of nodes for the high and low sides of the geometry. Both are exactly equal. See attached images. This geometry should repeat in the y direction to infinity. I also have a swept mesh in the z direction. Could that be an issue? Is there another reason for this error? Help appreciated!

Kevin

[Aniket]

can you also share images of details of the symmetry region? In addition to nodes, make sure the number of edges and vertices are all the same on both sides.

-Aniket

Forum Rules & Guidelines

[kevinu2]

Here are the details of the symmetry. Do you mean the number of geometry edges and vertices or the mesh edges and vertices? How would I get Mechanical to report those numbers?

Thanks!

[peteroznewman]

In Mechanical, on the Display tab, click the Show Vertices button, and Close Vertices button.

If you see non-matching vertices on the High and Low sides, open the geometry in SpaceClaim. On the Repair tab, click Extra edges and remove any with the green check mark, then click Split Edges and remove any with the green check mark.

[kevinu2]

Thanks for the help all, I figured it out. The vertices all matched, turns out I had the wrong value for the Linear Shift distance. I had entered the nominal value between high and low surfaces from the CAD used to generate the geometry. But when I measured the distance between vertices in the Ansys Mechanical geometry, the value is slightly different in the last few decimal places. Not sure why, could be rounding, unit conversion, or import artifact. Using the measured value in Mechanical, it now meshes without error. Something else to check for anyone reading this in the future.