-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node numbering is inconsistent #3120
Comments
Code to replicate this issue in: #3119
|
Further more, I am getting this error: >>> mapdl.nplot(vtk=True, show_node_numbering=True)
---------------------------------------------------------------------------
TypeError Traceback (most recent call last)
Cell In[4], line 1
----> 1 mapdl.nplot(vtk=True, show_node_numbering=True)
File ~/Other_pymapdls/pymapdl_0/pymapdl/src/ansys/mapdl/core/mapdl_extended.py:1104, in _MapdlCommandExtended.nplot(self, nnum, vtk, **kwargs)
1102 labels = [{"points": pcloud.points, "labels": pcloud["labels"]}]
1103 points = [{"points": self.mesh.nodes}]
-> 1104 return general_plotter([], points, labels, mapdl=self, **kwargs)
1106 # otherwise, use the built-in nplot
1107 if isinstance(nnum, bool):
TypeError: general_plotter() got an unexpected keyword argument 'show_node_numbering' |
I think the error comes when plotting the labels. The node IDs seems correct. |
This issue seems to happen not only on element numbering, but with general geometrical entities. Here is a minimal example creating 3 keypoints and connecting the first two with a line:
The output shows keypoint 1 connected to keypoint 3 instead of 2: This is an import issue, specially when setting boundary conditions and/or mesh refinement over complex geometries. |
There is a problem with the label indexes. A fix is in progress. |
that's strange..... I will check it. @mcMunich Can you post the code example for this? |
Discussed in #3119
Originally posted by YMDONG23 May 23, 2024
hello :)
When I use the BEAM188 unit to calculate, the node number displayed in the eplot window is not the same as the node number when vtk=False. What is the reason?
If you could discuss with me, thank you very much for your help!
The text was updated successfully, but these errors were encountered: