When I decompose a case and try to decompose this case again with a different number of processes using the --clear option, I get an error message (see additional information).
pyFoamDecompose.py . 4
pyFoamDecompose.py --clear . 6
It seems that the pyFoamDecompose calls decomposePar without the --force option.
---- additional_information ----
user@host:~/OpenFOAM/user-2.1.x/run/twoPhaseEulerFoam/aa_bubblyJet/bubblyJet$ pyFoamDecompose.py --clear . 6
/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 2.1.x |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 2.1.x-9d344f6ac6af
Exec : decomposePar -case /home/user/OpenFOAM/user-2.1.x/run/twoPhaseEulerFoam/aa_bubblyJet/bubblyJet
Date : Aug 02 2012
Time : 16:40:04
Host : "host"
PID : 9089
Case : /home/user/OpenFOAM/user-2.1.x/run/twoPhaseEulerFoam/aa_bubblyJet/bubblyJet
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time
--> FOAM FATAL ERROR:
Case is already decomposed with 4 domains, use the -force option or manually
remove processor directories before decomposing. e.g.,
rm -rf /home/user/OpenFOAM/user-2.1.x/run/twoPhaseEulerFoam/aa_bubblyJet/bubblyJet/processor*
From function decomposePar
in file decomposePar.C at line 241.
FOAM exiting
user@host:~/OpenFOAM/user-2.1.x/run/twoPhaseEulerFoam/aa_bubblyJet/bubblyJet$
Happens that I fixed this problem a couple of weeks ago on my development copy.
Uploaded a patch with the fix. Try to apply the patch with
patch -p0 <DecomposerClear.patch
(you have to be in the right directory for this to work) and report. If it works I'll close the bug. The fix will be in the next release anyway