|
[Sponsors] |
.cfg not actually writing paraview vtk (or general outputs) |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
August 17, 2016, 12:51 |
.cfg not actually writing paraview vtk (or general outputs)
|
#1 |
New Member
Michael
Join Date: Jul 2016
Location: Huntsville, Alabama
Posts: 9
Rep Power: 9 |
I've been running the simple Euler NACA0012 test case to validate my SU2 installation (after having to remake and install to allow mpi support) and I've noticed something. Even though I've specified "PARAVIEW" as the output format and it shows up as this, not only is nothing being written in paraview .vtk, but the only things being written are the adjoint files (as .dat). Not really sure what to check for or fix in this case. I can give a copy of the .cfg and the terminal outputs if that would help.
|
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Cht tutorial in 15 | braennstroem | OpenFOAM Running, Solving & CFD | 197 | June 10, 2015 03:02 |
Newbie: Install ParaView 3.81 on OF-1.6-ext/OpenSuse 11.2? | lentschi | OpenFOAM Installation | 1 | March 9, 2011 02:32 |
[OpenFOAM] Visualization with ParaView (in general) | sega | ParaView | 7 | February 1, 2010 02:24 |
[OpenFOAM] Problem writing Legacy VTK file | raptor3x | ParaView | 1 | June 23, 2009 16:10 |