Difference between revisions of "PHASTA/Extract Wall Shear Stress"
(Created page with "How to extract the wall shear stress vectors from the ybar file containing time-averaged statistics or the restart file containing instantaneous solutions? 1. Go to the director...") |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | How to extract the wall shear stress vectors from the ybar file containing time-averaged statistics or the restart file containing instantaneous solutions? | + | |
| + | ==Compressible Flow== | ||
| + | How to extract the wall shear stress (wss) vectors from the ybar file containing time-averaged statistics or the restart file containing instantaneous solutions? | ||
1. Go to the directory containing the reduced one-part geombc.dat.1 file and the ybar file, for example, ybar.352000-372000.0 | 1. Go to the directory containing the reduced one-part geombc.dat.1 file and the ybar file, for example, ybar.352000-372000.0 | ||
2. Run the following command one by one | 2. Run the following command one by one | ||
| + | <code>mkdir wss</code> ''create a new directory to put the wss vtk file'' | ||
| + | |||
| + | <code>cd wss</code> | ||
| + | |||
| + | <code>ln -s ../geombc.dat.1</code> ''create a softlink of the geombc.dat.1 file'' | ||
| + | |||
| + | <code>cp /users/ychen/develop/phasta/wallshearC/wallshearC/input.config .</code> | ||
| + | |||
| + | <code>cp /users/ychen/develop/phasta/wallshearC/wallshearC/solver.inp .</code> ''input.config and solver.inp here have no real meanings, the only reason is that the code need to read them'' | ||
| + | |||
| + | <code>ln -s ../ybar.352000-372000.0 ybar.372000.0 </code> ''create a softlink of the ybar file, notice that the link only takes the final time step in the file name'' | ||
| + | |||
| + | or <code>ln -s ../restart.372000.0</code> ''if we are extracting wss from the solution field of the restart file'' | ||
| − | + | <code>echo 372000 > numstart.dat</code> | |
| − | + | <code>echo 1 > itagybar.dat</code> ''tell the code to extract wss from the ybar file '' | |
| − | + | <code>mpirun /users/ychen/develop/phasta/wallshearC/wallshearC/bin/x86_64_linux-icc/wallshearC.exe-openmpi > dumpWSS.log 2>&1 & </code> ''run the code'' | |
| − | + | <code>tail -f dumpWSS.log</code> | |
| − | + | ==Incompressible Flow== | |
| − | + | It is easy to do but I need some time to test it. Michele might have a working version. | |
| − | |||
| − | + | '''You are strongly encouraged to build the code under your own directory, probably together with the phSolver toolsets using CMake.''' | |
| − | + | --[[User:Ychen|Ychen]] 13:14, 26 July 2012 (MDT) | |
| − | + | [[Category:PHASTA]] [[Category:Post-processing]] | |
Latest revision as of 11:50, 18 September 2022
Compressible Flow
How to extract the wall shear stress (wss) vectors from the ybar file containing time-averaged statistics or the restart file containing instantaneous solutions?
1. Go to the directory containing the reduced one-part geombc.dat.1 file and the ybar file, for example, ybar.352000-372000.0
2. Run the following command one by one
mkdir wss create a new directory to put the wss vtk file
cd wss
ln -s ../geombc.dat.1 create a softlink of the geombc.dat.1 file
cp /users/ychen/develop/phasta/wallshearC/wallshearC/input.config .
cp /users/ychen/develop/phasta/wallshearC/wallshearC/solver.inp . input.config and solver.inp here have no real meanings, the only reason is that the code need to read them
ln -s ../ybar.352000-372000.0 ybar.372000.0 create a softlink of the ybar file, notice that the link only takes the final time step in the file name
or ln -s ../restart.372000.0 if we are extracting wss from the solution field of the restart file
echo 372000 > numstart.dat
echo 1 > itagybar.dat tell the code to extract wss from the ybar file
mpirun /users/ychen/develop/phasta/wallshearC/wallshearC/bin/x86_64_linux-icc/wallshearC.exe-openmpi > dumpWSS.log 2>&1 & run the code
tail -f dumpWSS.log
Incompressible Flow
It is easy to do but I need some time to test it. Michele might have a working version.
You are strongly encouraged to build the code under your own directory, probably together with the phSolver toolsets using CMake.
--Ychen 13:14, 26 July 2012 (MDT)
