|
[Sponsors] |
preserving Patches CyclicAMI parallel processing |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
October 7, 2021, 16:56 |
preserving Patches CyclicAMI parallel processing
|
#1 |
Senior Member
qutadah
Join Date: Jun 2021
Location: USA
Posts: 101
Rep Power: 5 |
I am trying to preserve patches of cyclicAMI, as described in the User-Guide, i should include some code in my decomposeParDict and topoSetDict...
Constraints These are constraints applied to the decomposition. Typical uses might be e.g. to keep a cyclicAMI patch on a single processor (might speed up simulation) or have maximum local donors in an overset case." I have tried the following solution on following post: preservepatches for cyclicAMI in decomposeParDict: constraints { // Keep all of faceSet on a single processor. This puts all cells // connected with a point, edge or face on the same processor. // (just having face connected cells might not guarantee a balanced // decomposition) // The processor can be -1 (the decompositionMethod chooses the // processor for a good load balance) or explicitly provided (upsets // balance) processors { type singleProcessorFaceSets; sets ( (front -1) //(f1 -1) (back -1) ); // enabled true; } } in topoSetDict: actions ( { name front; type faceSet; action new; source patchToFace; sourceInfo { name "front"; } } { name back; type faceSet; action new; source patchToFace; sourceInfo { name "back"; } } ); i did however try including it and i recieve an error when running the case. I am trying to see if it might speed up simulation as mentioned in the user guide " Should i run the case normally decomposePar, pimpleFoam, and then reconstructPar, or should i include a specific command because we have a new topoSetDict we didnt have before? Or is there another way to do this if this is the wrong way to do it? Thanks! Error: --> FOAM FATAL IO ERROR: keyword singleProcessorFaceSets is undefined in dictionary "/hsmstorage/work/rababqjt/3D_Pump_SinglePhase/02_3D_Pumpe_M1_IncreasedGap_Qw68_CyclicAMI_SST_pim ple/system/decomposeParDict.constraints.processors" file: /hsmstorage/work/rababqjt/3D_Pump_SinglePhase/02_3D_Pumpe_M1_IncreasedGap_Qw68_CyclicAMI_SST_pim ple/system/decomposeParDict.constraints.processors from line 49 to line 53. From function const Foam::entry& Foam::dictionary::lookupEntry(const Foam::word&, bool, bool) const in file db/dictionary/dictionary.C at line 566. FOAM exiting |
|
October 11, 2021, 09:39 |
|
#2 |
Member
Join Date: Feb 2020
Posts: 79
Rep Power: 6 |
Hi,
I see that enable true is commented. Could you try without comment ? |
|
October 11, 2021, 11:41 |
|
#3 |
Senior Member
qutadah
Join Date: Jun 2021
Location: USA
Posts: 101
Rep Power: 5 |
I have a question,
where does the back and front come from? because my boundaries are defined such as: INT_BLADE_2-SIDE-1 { type cyclicAMI; inGroups 1(cyclicAMI); nFaces 1056; startFace 14209224; matchTolerance 0.0001; transform coincidentFullMatch; neighbourPatch INT_BLADE_2-SIDE-2; method faceAreaWeightAMI; } INT_BLADE_2-SIDE-2 { type cyclicAMI; inGroups 1(cyclicAMI); nFaces 704; startFace 14210280; matchTolerance 0.0001; transform coincidentFullMatch; neighbourPatch INT_BLADE_2-SIDE-1; method faceAreaWeightAMI; } should i be inputting INT_BLADE_2-SIDE-2 , and so on instead of front and back? I dont understand what the front and back is exactly.. thanks |
|
October 11, 2021, 11:42 |
|
#4 | |
Senior Member
qutadah
Join Date: Jun 2021
Location: USA
Posts: 101
Rep Power: 5 |
Quote:
i did try without commenting and it gives error. -> FOAM FATAL IO ERROR: keyword singleProcessorFaceSets is undefined in dictionary "/hsmstorage/work/rababqjt/3D_Pump_SinglePhase/02_3D_Pumpe_M1_IncreasedGap_Qw68_CyclicAMI_SST_pim ple/system/decomposeParDict.constraints.processors" file: /hsmstorage/work/rababqjt/3D_Pump_SinglePhase/02_3D_Pumpe_M1_IncreasedGap_Qw68_CyclicAMI_SST_pim ple/system/decomposeParDict.constraints.processors from line 49 to line 54. From function const Foam::entry& Foam::dictionary::lookupEntry(const Foam::word&, bool, bool) const in file db/dictionary/dictionary.C at line 566. |
||
Tags |
cyclicami, decomposepar, parallel decomposepar |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] Creating mesh for cyclicAMI boundaries | otaolafr | OpenFOAM Meshing & Mesh Conversion | 3 | October 11, 2022 01:07 |
Parallel processing of OpenFOAM cases on multicore processor??? | g.akbari | OpenFOAM Running, Solving & CFD | 31 | November 1, 2017 10:25 |
Parallel Processing by region | Swift | OpenFOAM Running, Solving & CFD | 0 | July 30, 2015 09:42 |
problem with cyclicAMI and wall distance | Maff | OpenFOAM Bugs | 5 | August 14, 2014 15:41 |
Cyclic patches and parallel postprocessing problems | askjak | OpenFOAM Bugs | 18 | October 27, 2010 04:35 |