Interpolate Solution from Different Mesh - Revision history

Conrad54418: /* Alternative to Using MATLAB for Reformatting */

2026-06-04T23:00:06Z

‎Alternative to Using MATLAB for Reformatting

2026-06-04T22:56:42Z

‎Process Overview (manual)

2026-06-04T22:54:02Z

‎Turbulent, Compressible, Unstructured Mesh

2026-04-02T17:53:35Z

‎Alternative to Using MATLAB for Reformatting

2025-11-17T18:07:55Z

‎Process Overview (manual)

2025-03-29T17:12:56Z

‎Alternative to Using MATLAB for Reformatting

2025-03-29T16:22:01Z

‎Turbulent, Compressible, Unstructured Mesh

2025-02-20T16:42:35Z

‎Alternative to Using MATLAB for Reformatting

2025-02-02T13:56:27Z

‎Alternative to Using MATLAB for Reformatting

2025-02-02T13:54:24Z

‎Alternative to Using MATLAB for Reformatting

@@ Line 126: / Line 126: @@
 for entropy code with eddy viscosity:
   awk '{print $13,$14,$15,$2,$3,$4,$5,$6,$9,$10,$11,$8,$7,$1}' test.dat > solInterp.1
-and don’t forget to put this into a directory called solnTarget (which is inside 1-procs_case) and also to turn on the flag in solver.inp <code>Load and set 3D IC: True</code> for the 1 step that Joe mentioned. Finally, if you are worried about that one step messing up your solution recent versions of the code can take
+and don’t forget to put this into a directory called solnTarget (which is inside 1-procs_case) and also to turn on the flag in solver.inp <code>Load and set 3D IC: True</code> for the 1 step advance in PHASTA. Finally, if you are worried about that one step messing up your solution recent versions of the code can take
        iexec : 0
 or
       Number of Timesteps: 0
 to not take any  actual steps.  Note however that only very recent version of the code have the iexec conditional moved AFTER the loading of the interpolated solution but it should be pretty easy to figure out where to move that  conditional.   Alternatively, the second option also  skips over the time stepping and writes the solution  AFTER applying the boundary conditions which can be useful to see as well to confirm you have the intended BC’s set (iexec :0 won’t detect this)

@@ Line 104: / Line 104: @@
 # Load the target case .pht file into ParaView
 # Use the 'Resample from dataset' filter and select the source (new mesh file) and input (MergeBlocks) blocks accordingly
-# Save the output as a .csv file. Write a single time step and select scientific notation to 12 decimals. NOTE: sometimes ParaView will make an error and write zeros where it can't quite find the closest point when doing the solution transfer. In this case, the .csv file needs to be manually edited to replace the zeros for pressure and temperature with realistic values.
+# Save the output as a .csv file. Write a single time step and select scientific notation to 12 decimals. NOTE: sometimes ParaView will make an error and write zeros where it can't quite find the closest point when doing the solution transfer. In this case, the .csv file needs to be manually edited to replace the zeros for pressure and temperature with realistic values (the branch <code>conrad54418/NSI_hypersonics</code> has automated this fix).
 # The .csv file can now be reformatted and renamed with MATLAB to match the expected form of solInterp.1.
 # Advance PHASTA one step in serial, then convert to desired number of processors using Chef.

@@ Line 93: / Line 93: @@
 == Turbulent, Compressible, Unstructured Mesh ==
-Currently, the only version of PHASTA that is set up to handle this type of solution transfer is the <code>conrad54418/connor_primitive</code> branch (as of 6/22/22). Creating the <code>solInterp.1</code> file can be automated via a script or done manually (see below).
+Only certain versions of PHASTA are set up to handle this type of solution transfer (branches like <code>conrad54418/connor_primitive</code> or <code>conrad54418/connor_entropy</code>). Creating the <code>solInterp.1</code> file can be automated via a script or done manually (see below).
 === Process Overview (scripted) ===

@@ Line 121: / Line 121: @@
 For primitive code turbulent:
-  awk '{print $9,$10,$11,$3,$5,$6,$7,$4,$2}' test.dat > solInterp.1
+  awk '{print $8,$9,$10,$2,$4,$5,$6,$3,$1}' test.dat > solInterp.1
 for entropy code laminar:
   awk '{print $12,$13,$14,$1,$2,$3,$4,$5,$8,$9,$10,$7,$6}' test.dat > solInterp.1

@@ Line 103: / Line 103: @@
 # Load existing solution into ParaView. Use the 'MergeBlocks' filter to convert to serial case.
 # Load the target case .pht file into ParaView
-# Use the 'Resample from dataset' filter and select the source (new mesh file) and target (MergeBlocks) blocks accordingly
+# Use the 'Resample from dataset' filter and select the source (new mesh file) and input (MergeBlocks) blocks accordingly
 # Save the output as a .csv file. Write a single time step and select scientific notation to 12 decimals. NOTE: sometimes ParaView will make an error and write zeros where it can't quite find the closest point when doing the solution transfer. In this case, the .csv file needs to be manually edited to replace the zeros for pressure and temperature with realistic values.
 # The .csv file can now be reformatted and renamed with MATLAB to match the expected form of solInterp.1.

@@ Line 118: / Line 118: @@
 Replace the commas with spaces:
   sed -i 's/,/\ /g' test.dat
-Rearrange the columns  to be what solInterp.1 wants.  It is probably a good idea to do a <code>head -1 PVinterp0.csv</code> to be sure as you might have more or less fields than I did but use that header to find the column numbers (starting from 1, not 0) to write x, y, z, p, u, v, w, T, sclr. For primitive code turbulent:
+Rearrange the columns  to be what solInterp.1 wants.  It is probably a good idea to do a <code>head -1 PVinterp0.csv</code> to be sure as you might have more or less fields than I did but use that header to find the column numbers (starting from 1, not 0) to write x, y, z, p, u, v, w, T, sclr. NOTE: Even with the same data files, different versions of PV will produce different ordering so '''CHECK'''.
   awk '{print $9,$10,$11,$3,$5,$6,$7,$4,$2}' test.dat > solInterp.1
 for entropy code laminar: