bug: mapdl.aplot(show_area_numbering=True) not working correctly

[CesarRodriguezPereira]

The show_area_numbering option within the aplot method is not working correctly. When I use it the only numeric display I get is a "None" label. Lines and line numbering work correctly, which makes me think only this method is pointing to an empty variable rather than the area numbers (possibly the mapdl.geometry.anum?).

I'm using ansys.mapdl-core version 0.58.0.

I'm attaching an image where you can see the options and the mapdl.geometry.anum printed.

[akaszynski]

Looks like the area numbers aren't being mapped over. Thanks for pointing this out, I'll see if I can reproduce this bug locally.

[akaszynski]

Corrected in db07367f9837d2f19567a7bb4e90ebeeb98b7c0e

from ansys.mapdl.core import launch_mapdl, Mapdl
mapdl = launch_mapdl()

mapdl.prep7()
mapdl.block(0, 1, 0, 1, 0, 1)
mapdl.aplot(show_area_numbering=True, color_areas=True, show_lines=True,
            line_width=10, lighting=False)

---

I'll have this out in the next release.

[CesarRodriguezPereira]

Are you sure the fix works? I've tested it, and while it now shows area numbers, they don't correspond with the area numbers withing mapdl, or even those within mapdl.geometry.anum

In this cell, after making some geometry I plot it and call the geometry.anum property. As you can see, the top area in the screenshot is numbered 14, when the anum list only goes up to 10 in this geometry.

Tested in ansys.mapdl-core 0.58.1. Hope this helps.

[akaszynski]

I'll fix that. Thanks for pointing that out. I tested on basic geometry too, and I'm not sure what's causing the issue at the moment.

[CesarRodriguezPereira]

I'll fix that. Thanks for pointing that out. I tested on basic geometry too, and I'm not sure what's causing the issue at the moment.

Geometry complexity doesn't seem to be a factor. I've just realised the block where you tested it also is showing numbers up to 12, when there should be only 6 areas.

[akaszynski]

Totally missed that (it's been a long week!). There's a way I can programmatically check to make sure the areas on the mesh at least match the areas from mapdl.geometry.anum. I should have added that to the tests.

[akaszynski]

Found the issue. The area plotting mechanism within pymapdl isn't great. I effectively have to copy the areas, mesh them with a finite element mesh (using MESH200 elements), stream or write it out, and then read it in. There's no direct interface to the MAPDL geometry tessellation, and even if there was, we'd still have to convert that tessellated mesh into something that pymapdl could use.

Ideally, I'd just use the IGESOUT after ALLSEL,BELOW,ALL, but there isn't a good IGES to tessellated geometry converter. In fact, the the one that I wrote pyiges only works well with lines and even then, the performance isn't great.

I'll try to come up with a better solution, but there may not be one for a while given how many layers this goes down.

[akaszynski]

Good news! I thought we were dead in the water with this one, but it turns out I just had the orientation wrong. Plus, I can work around the element area plotting restriction so we can get plots without duplicating the plots. It's still not ideal, but at least we'll be able to number our meshes.

I'll try to have this out soon. Would you mind pulling from master (or testing a branch) once I've gotten this working?

[akaszynski]

Working in ansys-core-mapdl==0.58.2. See the new docs at: https://mapdldocs.pyansys.com/examples/index.html#geometry-examples https://mapdldocs.pyansys.com/user_guide/mesh_geometry.html