ansys / pymapdl

Pythonic interface to MAPDL

Home Page:https://mapdl.docs.pyansys.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Remark on Documentation Notes for "PostProcessing.nodal_displacement(...)" and "PostProcessing.nodal_component_stress(...)" and maybe others?

SvenKan opened this issue · comments

Description of the modifications

Dear pyMAPDL-Team,

I came upon the following issue you might want to look into:

On the Documentation pages of the commands: "PostProcessing.nodal_displacement(...)" and "PostProcessing.nodal_component_stress(...)" it says in the "Notes" section:

"This command always returns all nodal displacements regardless of if the nodes are selected or not."

After (the solution of a static analysis and) the reselection of a subset of nodes both commands gave me a list with only the nodal displacements/component stresses of the selected nodes. (see code below)

I find this (consider node selection) more useful than the commands always returning all displacements/stresses, but it is in contrary to the current Notes on the documentation pages.

Thank you
Sven

Links to the documentation pages:
https://mapdl.docs.pyansys.com/version/0.67/api/_autosummary/ansys.mapdl.core.post.PostProcessing.nodal_displacement.html
https://mapdl.docs.pyansys.com/version/0.67/api/_autosummary/ansys.mapdl.core.post.PostProcessing.nodal_component_stress.html

Useful links and references

        test = mapdl.post_processing.nodal_component_stress('x').tolist()   # len() = 2503

        print(mapdl.esel("all"))
        print(mapdl.nsle("R", "corner"))    # Element: SHELL281 
        
        test2 = mapdl.post_processing.nodal_component_stress('x').tolist()  # len() = 691
        
        sel = mapdl.post_processing.selected_nodes.tolist()                 # len() = 2503   True if node is selected.
        sptest = [ x for x in test if sel[test.index(x)] ]                  # len() = 691
        
        # test2 and sptest are identical, despite Documentation Notes saying the selected nodes do not matter.

Hi @SvenKan !!

Thank you a lot for reporting this! I will have a look and fix the documentation if needed.