Skip to content

Issue with plot_nodal_displacement #905

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

Closed
pmaroneh opened this issue Feb 17, 2022 · 5 comments
Closed

Issue with plot_nodal_displacement #905

pmaroneh opened this issue Feb 17, 2022 · 5 comments
Assignees

Comments

@pmaroneh
Copy link
Contributor

It appears that the method plot_nodal_displacement() can be accessed in two ways:

  • Method 1: through mapdl.result.plot_nodal_displacement() of the pyMAPDL reader. In this method, the result number uses a 0-indexing (so the first result set is obtained through mapdl.result.plot_nodal_displacement(0)). I've been able to successfully use this method on a model:
    image
    However I understand that the pyMAPDL reader is legacy, so its use is not recommended.
  • Method 2: through mapdl.post_processing.plot_nodal_displacement(), which belongs to the pyMAPDL module (not pyMAPDL Reader). I have two issues here:
  1. Some examples of the pyMAPDL doc use the method from pyMAPDL reader, which makes it confusing, as these two methods do not take the same arguments. See https://mapdldocs.pyansys.com/user_guide/mapdl_examples.html?highlight=plot_nodal_displacement for reference
  2. I've not been able to use this method on the same model shown above:
    image
@pmaroneh pmaroneh added the Bug label Feb 17, 2022
@akaszynski
Copy link
Collaborator

I think we should depreciate the usage of pymapdl-reader and then move towards using just PyMAPDL or DPF.

Integration with PyDPF would be great. @rlagha, is there an easy way to dpf installed on Linux on GitHub? Do we have instructions for that?

@CesarRodriguezPereira
Copy link

I think we should depreciate the usage of pymapdl-reader and then move towards using just PyMAPDL or DPF.

Just my 2 cents, I think this may be good in the long run, but backwards compatibility might be a bit of a pain then. I'd say that most people that currently use PyMapdl are familiar with using the result = mapdl.result idiom, which returns a type ansys.mapdl.reader.rst.Result, so many of us use pymapdl-reader unknowingly, instead of the postprocessing that's directly embeded within ansys.mapdl-core. Maybe having the result object be part of the core could help in phasing out the use of the reader library.

@akaszynski
Copy link
Collaborator

Maybe having the result object be part of the core could help in phasing out the use of the reader library.

Agreed. Ideally the result attribute would be an instance of ansys.dpf.core.model.Model.

@germa89 germa89 self-assigned this Feb 22, 2022
@rlagha
Copy link

rlagha commented Feb 22, 2022

@cbellot000 please could you work with @germa89 on this?
@akaszynski

@germa89
Copy link
Collaborator

germa89 commented Feb 16, 2024

Closing on favor of #1298

@germa89 germa89 closed this as completed Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants