![]() The script names are not important (only the names of the inputs must match the writer names). all Python files copied from the case's DATA directory), and tries to use them with Catalyst writers. When running, code_saturne checks all Python files in its execution directory (i.e. If using lighter Catalyst editions, filters defined in the script but not available in the given edition will fail. We generally use a full ParaView build for Catalyst output. 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. Whichever solution is chosen, the directory must exist or be created when the code runs. The generated scripts also allows defining a root path for outputs. To avoid generating all images or extract outputs directly in the execution directory, is is possible to add a prefix such as postprocessing to the file names in the exports definition. Note that the exports definition dialog often takes up quite a bit of vertical space in the ParaView GUI, but rather than closing it, it can be moved to a tab along with the Information and Properties tabs. Under ParaView, use Catalyst -> Define Exports and select data or images to extract.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.In code_saturne, define a writer with a name matching the ParaView input's name, and associate the same meshes as were associated with the writer used for initial output. Under ParaView, use File -> Save Catalyst State to generate a Python co-processing script.Ĭopy or move the exported script to the case's DATA directory. Under ParaView, use Extractors to define data or images to extract. 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. define an output writer using the "catalyst" format (or change the format of an existing one). ![]() copy the script to a case's DATA directory.modify that script if necessary or desired.export a catalyst Python script from ParaView.produce an initial output using a post-hoc output format (EnSight, MED, or CGNS).To define in-situ postprocessing output, the following steps are required: Code_saturne can generate postprocessing output directly with ParaView Catalyst, provided support for this tool is specified at build time (see installation documentation). ![]()
0 Comments
Leave a Reply. |