-
Notifications
You must be signed in to change notification settings - Fork 92
In situ postprocessing with ParaView Catalyst
code_saturne can generate postprocessing output directly with ParaView Catalyst, provided support for this tool is specified at build time (see installation documentation).
To define in-situ postprocessing output, the following steps are required:
- produce an initial output using a post-hoc output format (EnSight, MED, or CGNS)
- define your visualization in ParaView
- export a catalyst Python script from ParaView
- modify that script if necessary or desired
- copy the script to a case's DATA directory
- define an output writer using the "catalyst" format (or change the format of an existing one)
- run the computation
Under ParaView, after loading the input file, it is recommended to rename the input node in the pipeline, to use the name that will be chosen for the catalyst output writer.
Under ParaView, use Catalyst -> Define Exports and select data or images to extract.
Note that if using PARAVIS under the Salome platform, the trace must be deactivaed under Salome File->Preferences.
Under ParaView, export state.
In code_saturne define a writer with a name matching the ParaView input's name (here code_saturne_writer_name
), and associate the same meshes as were associated with the writer used for initial output.