-
Dear PyAnsys Team, I’m currently working with .rst files using PyMAPDL to extract specific results based on load step and substep numbers. My simulation setup involves multiple load steps with several substeps, and I need to retrieve data precisely from specific substeps within these load steps. However, when I attempt to parse the result sets using result.parse_step_substep(), I receive only integer indices representing the result sets, rather than a tuple containing the actual load step and substep numbers. For example, my .rst file shows 3 result sets, but the step info returned is simply 0, 1, and 2, without any clear mapping to the original load step and substep numbers from the simulation. Given this, I have two questions:
Thank you for your assistance and support. Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 8 replies
-
Hi @ncbhatt - let me move the discussion to PyMAPDL. Pinging also @ansys/pymapdl-maintainers for assistance |
Beta Was this translation helpful? Give feedback.
-
Hi @ncbhatt For a better post processing experience with this I would suggest using PyMAPDL and taking advantage of the enhanced output formats discussed here near the bottom of the page. Say I had a two load step solution and saved just the last substep of the first solve, and all the substeps of the second. Then using the SET command to list the available load/sub/result sets dumped to a dataframe would look something like this: You can use the other enriched output types and see how they align with the listing information. Then parse the list/array as needed. Mike |
Beta Was this translation helpful? Give feedback.
-
Hi @mikerife, |
Beta Was this translation helpful? Give feedback.
-
I created a repository. Whatever I did is here https://github.com/ncbhatt/ANSYS-Data-Extractor?tab=readme-ov-file |
Beta Was this translation helpful? Give feedback.
Hi @ncbhatt
This is a little confusing but the functionality you are asking about is the PyMAPDL Reader and not PyMAPDL. For better or worse the reader is packaged with PyMAPDL but it works differently. If you review its documentation the parse_step_substep returns a ccumulative list.
For a better post processing experience with this I would suggest using PyMAPDL and taking advantage of the enhanced output formats discussed here near the bottom of the page. Say I had a two load step solution and saved just the last substep of the first solve, and all the substeps of the second. Then using the SET command to list the available load/sub/result sets dumped to a dataframe would look something…