Implement feature(s) for post-processing of trial simulations.
With existing workflows at the time of writing, post-processing is generally done by Paraview using exodus file format.
- Common or routine post-processing may be done using tools such as PyVista.
- However, post-processing requirements are often bespoke to the experiment being run. A workflow that allows the user to re-use a custom post-processing pipeline automatically on any/all trials would also be valuable. One way to achieve this in ParaView would be to have the user perform their post-processing on any trial (or template / default value model) and save the python state.
sledo could then have a function which takes in this state file, replaces the filename with the filepath to a specific trial's output file, and re-runs it. This should allow creating the same visualisation of any trial.
Implement feature(s) for post-processing of trial simulations.
With existing workflows at the time of writing, post-processing is generally done by Paraview using exodus file format.
sledocould then have a function which takes in this state file, replaces the filename with the filepath to a specific trial's output file, and re-runs it. This should allow creating the same visualisation of any trial.