| Jasfss |
August 17, 2016 15:21 |
Quote:
Originally Posted by hlk
(Post 614411)
A common problem that would confirm that the parallel installation failed is if you see repeated lines of output - aka, several lines with iteration #0.
|
This had happened in previous failed attempts to install with mpirun support, but the install I have now does not have this issue, and I can confirm that it is successfully utilizing mpi support.
For example, if I attempt to run the euler test case for the naca0012, simply modifying the .cfg to output to Paraview rather than Tecplot, say doing
Code:
mpirun -np 4 SU2_CFD inv_NACA0012.cfg
in the terminal after navigating to the correct directory, I can see in the output from the terminal:
Quote:
-------------------------- Output Information ---------------------------
Writing a flow solution every 250 iterations.
Writing the convergence history every 1 iterations.
The output file format is Paraview ASCII (.vtk).
Convergence history file name: history.
Forces breakdown file name: forces_breakdown.dat.
Surface flow coefficients file name: surface_flow.
Flow variables file name: flow.
Restart flow file name: restart_flow.dat.
|
So it recognizes that the output files should output as .vtk paraview files, like I input in the .cfg. After it goes through the iterations, I then get
Quote:
-------------------------- File Output Summary --------------------------
Writing comma-separated values (CSV) surface files.
Merging coordinates in the Master node.
Merging solution in the Master node.
Writing SU2 native restart file.
Writing the forces breakdown file.
|
But, the flow and solution_flow outputs are not actually rewritten into .vtk. I still have older versions sitting in the directory from when I was running on serial and outputting to Tecplot, but nothing new has been written with regards to these solutions. |
