|August 14, 2012, 02:10||
reconstructParMesh + GGI problem
Join Date: Jan 2010
Posts: 123Rep Power: 8
I found a very strange problem when I tried to reconstructParMesh with the GGI results (a rotating propeller). The simulation was run with 128 cores
1st run: the case was run from t = 0 to t = 1. I used the reconstructParMesh to reconstruct the data without any problem. The data was good under Paraview
2nd run: due to the limited hard drive space on the cluster, I removed everything except for t =1 in the processor0 to processor127. the case was run from t = 1 to t = 2 without any problem. Again, I used the reconstructParMesh to reconstruct my data without error. However, the mesh geometry was completely wrong (looks like the node connectivity was lost, points are not connected correctly)
Did anyone have the same problem before?
Was this because I removed the 0 directory from each of the processor1-processor127 directories?
Should I change the startTime in the controDict as I realise that reconstructParMesh tends to create a polyMesh directory at time - startTime in the controlDict before it does the reconstruction processor?
I really appreciate if anyone used the reconstructParMesh.
|Thread||Thread Starter||Forum||Replies||Last Post|
|UDF compiling problem||Wouter||Fluent UDF and Scheme Programming||6||June 6, 2012 04:43|
|Problem Importing Geometry ProE to CFX||fatb0y||CFX||3||January 14, 2012 20:42|
|Adiabatic and Rotating wall (Convection problem)||ParodDav||CFX||5||April 29, 2007 19:13|
|problem with GGI interfaces||strider||CFX||6||May 29, 2006 14:20|
|GGI interface problem (CFX-5.7.1)||Jesper||CFX||3||May 14, 2005 18:06|