Open germa89 opened 1 year ago
Imho that would be a huge improvement. I'm not sure how much is covered via #1299, but one major issue forcing me again and again to go back to PyMAPDL Reader or PyMAPDL is the difference in plotting capabilities. I'm not sure if this is still correct, but e.g. animations are only possible (with lots of limitations) using animate_nodal_displacement. The capabilities of formating plots in general is most limited using DPF.
Summary
Currently there is duplication regarding the post-processing of MAPDL results. There are three libraries which can do this job:
Intended Outcome
Effort should be merged toward only one single library for post-processing. The current general agreement is to go with DPF.
Any post-processing reference and function inside pymapdl should point to DPF equivalent.
How will it work?
Retro-compatibility should be ensured. This process should be transparent to the user. Use DPF to implement
post_processing
module. It requires to change 3-4 functions which are doing most of the heavy work.Stages/steps
Notes
This issue replace https://github.com/pyansys/pymapdl_roadmap/issues/2