|
[Sponsors] |
decomposePar problem: Wrong number of processor divisions in geomDecomp |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
December 8, 2015, 23:11 |
decomposePar problem: Wrong number of processor divisions in geomDecomp
|
#1 |
New Member
Eugene
Join Date: Dec 2015
Posts: 2
Rep Power: 0 |
Need help in solving this problem after I keyed in decomposePar
Selecting decompositionMethod simple --> FOAM FATAL ERROR: Wrong number of processor divisions in geomDecomp: Number of domains : 2 Wanted decomposition : (5 2 1) From function geomDecomp::geomDecomp(const dictionary& decompositionDict) in file geomDecomp/geomDecomp.C at line 50. FOAM exiting Anyone knows what's the problem? |
|
December 9, 2015, 02:45 |
|
#2 |
Senior Member
|
Hi,
The error is explained in error message. You set number of subdomains (numberOfSubdomains) to 2, yet your simpleCoeffs dictionary contains Code:
n (5 2 1); |
|
November 23, 2017, 10:54 |
|
#3 |
Senior Member
Deep
Join Date: Oct 2017
Posts: 180
Rep Power: 9 |
I have similar error.
Code:
--> FOAM FATAL ERROR: Wrong number of processor divisions in geomDecomp: Number of domains : 8 Wanted decomposition : (5 2 1) From function geomDecomp::geomDecomp(const dictionary& decompositionDict) in file geomDecomp/geomDecomp.C at line 50. FOAM exiting |
|
November 23, 2017, 10:56 |
|
#4 |
Senior Member
Deep
Join Date: Oct 2017
Posts: 180
Rep Power: 9 |
Did you mean 8 subdomains ?
|
|
November 23, 2017, 11:28 |
|
#5 |
Member
Ricky
Join Date: Jul 2014
Location: Germany
Posts: 78
Rep Power: 12 |
Hallo,
the way you defined your n "(5 2 1)" corresponds to 10 subdomains. for 8 subdomains you need to define n as "(4 2 1) or (2 4 1) or (2 2 2) or ...". Regards Ricky
__________________
If it is easy, then something is fishy! Last edited by kera; November 23, 2017 at 13:22. |
|
November 23, 2017, 12:04 |
|
#6 | |
Senior Member
Deep
Join Date: Oct 2017
Posts: 180
Rep Power: 9 |
Ohh! It's not the addition but multiplication.
This excerpt from the wiki for decomposePar clarified it. Quote:
|
||
September 5, 2020, 08:47 |
|
#7 | |
New Member
Arne Knies
Join Date: Jun 2020
Posts: 1
Rep Power: 0 |
Quote:
Hi, I'm not sure whether i understood your question correctly, but to me the wiki explanation seems just fine. Maybe imagining a chessboard might help: It's divided 8-fold in x- and y-direction, respectively. So the notation for n would be (8 8 1), multiplying to 64 squares (or hexahedra, accounting for z domain). Hope, this helps someone. |
||
Tags |
decomposepar, openfoam 2.3 |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] Error snappyhexmesh - Multiple outside loops | avinashjagdale | OpenFOAM Meshing & Mesh Conversion | 53 | March 8, 2019 10:42 |
ERROR #001100279 has occurred in subroutine ErrAction. | smnaryal | CFX | 11 | December 20, 2017 17:32 |
decomposePar -allRegions | stru | OpenFOAM Pre-Processing | 2 | August 25, 2015 04:58 |
decomposePar pointfield | flying | OpenFOAM Running, Solving & CFD | 28 | December 30, 2013 16:05 |
AMI interDyMFoam for mixer | danny123 | OpenFOAM Running, Solving & CFD | 4 | June 19, 2013 05:49 |