Difference between revisions of "The On Ramp/Level 1/Post-Process"

From PHASTA Wiki
Jump to: navigation, search
(Visualization File)
Line 1: Line 1:
 +
In this section we will learn how to set-up the Visualization file which Paraview (Our flow visualization software) reads in, and how to utilise Paraview to analyze our flow field solutions.
  
 
== Visualization File ==
 
== Visualization File ==
In order for Paraview to know which restart and geombc files to process, we need to give it this information by means of a <code>.pht</code> meta-data file. In the directory where the case was run, <code>.../8-1-Chef/Run/</code> for our example, you will need to create/copy the meta-data file with a <code>.pht</code> file extension. The common practice is to name this file <code>flow.pht</code> and to only include the file in your <code>Run</code> directory when you are ready to launch Paraview. You can copy over an example file from the tutorials folder called <code>flow.pht</code>. A detailed explanation of what is inside of the <code>.pht</code> file is provided in this  [https://fluid.colorado.edu/tutorials/tutorialVideos/ParaviewWithMark_meta_data_description.mp4 video].
+
In order for Paraview to know which restart and geombc files to process, we need to give it this information by means of a <code>.pht</code> meta-data file. In the directory where the PHASTA case was run, <code>.../8-1-Chef/Run/</code> for our example, you will need to create/copy a meta-data file with a <code>.pht</code> file extension. Common practice is to name this file <code>flow.pht</code> and to only include the file in your <code>Run</code> directory when you are ready to launch and work in Paraview. You can copy over an example <code>.pht</code> file from the tutorials folder called <code>flow.pht</code>. A detailed explanation of the variables inside of the <code>.pht</code> file is provided in this  [https://fluid.colorado.edu/tutorials/tutorialVideos/ParaviewWithMark_meta_data_description.mp4 video].
  
 
==Visualizing Fields and Computing Quantities==
 
==Visualizing Fields and Computing Quantities==
Line 7: Line 8:
 
As always, set the environment (if you have not done so already) by using:
 
As always, set the environment (if you have not done so already) by using:
  
  more ~kjansen/soft-core.sh
+
  <code>more ~kjansen/soft-core.sh</code>
  
To open the visualization tool paraview, run the command:
+
To open the visualization tool Paraview, run the command:
  
 
  vglrun paraview
 
  vglrun paraview
  
A tutorial on how to navigate the GUI to visualize solution fields as well as compute other solution fields is given [https://fluid.colorado.edu/tutorials/tutorialVideos/ParaviewWithMark_viz_fields.mp4 here].
+
It is common practice to be in the directory where your <code>.pht</code> file is located when you run the <code>vglrun paraview</code> command. This sets the working directory in Paraview to the one which contains your <code>.pht</code> file, and you can then quickly open that file without having to search for it.
 +
 
 +
A tutorial on how to navigate the GUI to visualize solution fields as well as compute other solution fields is given in this [https://fluid.colorado.edu/tutorials/tutorialVideos/ParaviewWithMark_viz_fields.mp4 video].
 +
 
 +
'''Note:''' You can also open a specific Paraview build by setting the path to the executable file. For example, a Paraview v5.7.0 executable file was built in the following directory: <code>/users/jeffhadley/Builds/build-paraview-v5.7.0/bin/</code>. So, to run this specific build of paraview you would run the command:
 +
 
 +
<code>vglrun /users/jeffhadley/Builds/build-paraview-v5.7.0/bin/paraview</code>

Revision as of 10:51, 18 June 2021

In this section we will learn how to set-up the Visualization file which Paraview (Our flow visualization software) reads in, and how to utilise Paraview to analyze our flow field solutions.

Visualization File

In order for Paraview to know which restart and geombc files to process, we need to give it this information by means of a .pht meta-data file. In the directory where the PHASTA case was run, .../8-1-Chef/Run/ for our example, you will need to create/copy a meta-data file with a .pht file extension. Common practice is to name this file flow.pht and to only include the file in your Run directory when you are ready to launch and work in Paraview. You can copy over an example .pht file from the tutorials folder called flow.pht. A detailed explanation of the variables inside of the .pht file is provided in this video.

Visualizing Fields and Computing Quantities

As always, set the environment (if you have not done so already) by using:

more ~kjansen/soft-core.sh

To open the visualization tool Paraview, run the command:

vglrun paraview

It is common practice to be in the directory where your .pht file is located when you run the vglrun paraview command. This sets the working directory in Paraview to the one which contains your .pht file, and you can then quickly open that file without having to search for it.

A tutorial on how to navigate the GUI to visualize solution fields as well as compute other solution fields is given in this video.

Note: You can also open a specific Paraview build by setting the path to the executable file. For example, a Paraview v5.7.0 executable file was built in the following directory: /users/jeffhadley/Builds/build-paraview-v5.7.0/bin/. So, to run this specific build of paraview you would run the command:

vglrun /users/jeffhadley/Builds/build-paraview-v5.7.0/bin/paraview