CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   OpenFOAM Post-Processing (https://www.cfd-online.com/Forums/openfoam-post-processing/)
-   -   reconstrucPar error (https://www.cfd-online.com/Forums/openfoam-post-processing/196079-reconstrucpar-error.html)

Ilias_T December 31, 2018 07:42

Quote:

Originally Posted by cojua8 (Post 672859)
You are right,

there is no "constant" in any processor* directory, but checking decomposePar log there are no errors.

I think the problem comes when running renumberMesh, it creates a new "1e-5" folder with the renumbered polymesh and fields and then decomposePar doesn't create a constant subfolder into processor*.

So I guess I have to move the renumbered polymesh to constant and after that run decomposePar, am I right?

Hello,

I have nearly the same problem with OpenFOAMv5. When I run decomposePar, processor* directories are createded but inside them are only the time directories which include the initial conditions and a polymesh file.

In the OpenFoam site https://www.openfoam.com/documentati...s-parallel.php says that:


"On completion of decomposePar, a set of subdirectories will have been created, one for each processor, in the case directory. The directories are named processorN where N represents a processor number and contains a time directory, containing the decomposed field descriptions, and a constant/polyMesh directory containing the decomposed mesh description."

why the constant file it is not created? Without this I could not reconstructPar.

Thanks!

Ilias_T December 31, 2018 07:44

Quote:

Originally Posted by 9434 (Post 703831)
you can also manually make a constant directory in each processor directory and move polyMesh which is in "processor*/0 or 1".

I check this and it works. Is there any command to do it simultaneously for all processors?

Thank you!

WaterHammer1985 December 31, 2018 12:47

.
 
Quote:

Originally Posted by Ilias_T (Post 720437)
I check this and it works. Is there any command to do it simultaneously for all processors?

Thank you!


Not sure if there is an OpenFOAM utility to do it or not but running a script in the case folder may do the trick:

for dir in processor*/; do mkdir -- "$dir/constant"; done
for i in {0..439}; do cp -v ~/case/constant/* processor$i/constant/; done

*change "439" to the number of processor folders

Ilias_T January 1, 2019 16:51

Quote:

Originally Posted by WaterHammer1985 (Post 720456)
Not sure if there is an OpenFOAM utility to do it or not but running a script in the case folder may do the trick:

for dir in processor*/; do mkdir -- "$dir/constant"; done
for i in {0..439}; do cp -v ~/case/constant/* processor$i/constant/; done

*change "439" to the number of processor folders

Hello and thank you very much for your answer!

The first line operates well, with the second though I faced the error:

cp: omitting directory '/home/hliast/OpenFOAM/hliast-5.0/run/case/constant/extendedFeatureEdgeMesh'
cp: omitting directory '/home/hliast/OpenFOAM/hliast-5.0/run/case/constant/polyMesh'
'/home/hliast/OpenFOAM/hliast-5.0/run/case/constant/transportProperties' -> 'processor0/constant/transportProperties'
cp: omitting directory '/home/hliast/OpenFOAM/hliast-5.0/run/case/constant/triSurface'

the constant contains only transportProperties and turbulenceProperties.

Its not a flaw of your script but a crucial misunderstanding of OpenFoam that I have.

I begun my simulation using sHM without -overwrite (to check Mesh steps), so after its completion I have three time folders in my case, each one contains one step of sHM. So with -latest time in my ControlDict I could use simpleFoam without problems.

However, when I begin parallel executions, I faced problems in reconstructPar after simpleFoam, since in the time directories there are only one file containing polymesh or uniform and the initial conditions. As a mater of fact, the reconstructPar could not find the constant directory. One solution, as you said, is to cut manually the the the file uniform from the last convergence time step and put it in a constant file. I tried a simple modification on your script:

for dir in processor*/; do mkdir -- "$dir/constant"; done
for dir in processor*/; do mv $dir/$103/uniform $dir/constant/; done

(103 the convergence step) but it didn't work since I have no experience in coding.

1. Could you help me with this modification in order to to cut manually the the file uniform in the last convergence time step and put it in a constant file?

2. Could you make me some suggestions about my perspective of the process, since I want to check the steps of sHM and not use -overwrite. (*I try to cut the polymesh file in 3 time directory and put it in a constant file before decomposePar everything looks fine in processor* (all include a constant file) but simpleFoam run 1000 time step immediately with very strange results ,why? )

thank in advance WaterHammer1985!

WaterHammer1985 January 2, 2019 15:43

1. I'm not sure exactly how to do what you want but I think you will want to use cp -r instead of mv in line 2 of your code. If you use mv, it'll move the directory on the first loop then it won't have that directory to move during the 2nd and subsequent loops. If that doesn't work, I'd suggest looking through and/or posting at https://unix.stackexchange.com/ since that isn't an OpenFoam specific question, someone there will likely be able to assist.

2. One way to isolate the problem may be to create Case 1 and run sHM step 1. Then copy Case 1 (making Case 2) and run sHM step 2 with -overwrite. Then copy Case 2 (making Case 3) and run sHM step 3 with -overwrite. This will keep everything separated and you can compare Case 1/2/3 mesh results in parafoam.

Ilias_T January 4, 2019 12:31

Thank toy very much WaterHammer1985!

beatlejuice February 12, 2019 03:48

Hello WaterHammer1985,


did you (or anyone else) solve the issue to open a decomposed case in paraview when using the fileHandler collated format?

WaterHammer1985 February 12, 2019 17:36

.
 
Quote:

Originally Posted by beatlejuice (Post 724445)
Hello WaterHammer1985,


did you (or anyone else) solve the issue to open a decomposed case in paraview when using the fileHandler collated format?


No, I had to give up trying and just stopped using the fileHandler. If you do figure it out though I'd definitely like to know!


All times are GMT -4. The time now is 16:02.