|
[Sponsors] |
Problem with periodically repeated partially overlapping patches / nested cyclicACMI |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
October 27, 2014, 05:28 |
Problem with periodically repeated partially overlapping patches / nested cyclicACMI
|
#1 |
New Member
Patrick Kopper
Join Date: Oct 2014
Posts: 1
Rep Power: 0 |
Dear all,
I'm a student from Germany working on my Bachelor thesis in turbomachinery simulation. I have a problem with a nested cyclicACMI boundary condition involving other patch types than "wall". I've tried the tutorial with this patch type and it works perfectly. In my case however I want OpenFOAM to use translationally shifted copies of the same patch on the initially non overlapping areas. As it's quite hard to explain I've created a test case with two blocks in Salome. The two blocks have a side length of 100 and are displaced relative to another by 50. What I want to do is couple the non overlapping region on one side of the overlap area to the non overlapping region of the other patch on the other side. I've tried using a nested cyclicACMI boundary condition by creating three patch copies in my createBafflesDict using the definition below (only attached the definition for one side): Code:
ACMI1 { type faceZone; zoneName couple1Faces; patches { master { name ACMI1_couple; type cyclicACMI; matchTolerance 0.0001; neighbourPatch ACMI2_couple; nonOverlapPatch ACMI1_offset; transform translational; separationVector (0 0 0); } master2 { name ACMI1_offset; type cyclicACMI; matchTolerance 0.0001; neighbourPatch ACMI2_offset; nonOverlapPatch ACMI1_blockage; transform translational; separationVector (-100 0 0); } master3 { name ACMI1_blockage; type wall; } } } Code:
AMI: Creating addressing and weights between 270 source faces and 298 target faces AMI: Patch source sum(weights) min/max/average = 0, 1, 0.501221 AMI: Patch target sum(weights) min/max/average = 0, 1, 0.476506 AMI: Creating addressing and weights between 270 source faces and 298 target faces AMI: Patch source sum(weights) min/max/average = 0, 1, 0.498779 AMI: Patch target sum(weights) min/max/average = 0, 1, 0.523494 --> FOAM FATAL ERROR: Inconsistent ACMI patches ACMI2_couple and ACMI2_offset. Patches should have identical topology From function Foam::label Foam::cyclicACMIPolyPatch::nonOverlapPatchID() const in file AMIInterpolation/patches/cyclicACMI/cyclicACMIPolyPatch/cyclicACMIPolyPatch.C at line 408. I've uploaded my test case to my dropbox, please feel free to look into it using the link below: https://www.dropbox.com/s/owjqh1ah9z...ested.tar?dl=0 Thanks in advance, Patrick |
|
October 10, 2017, 11:01 |
|
#2 |
New Member
Join Date: May 2017
Posts: 7
Rep Power: 9 |
I did not check your case. This is my though. When you create cyclicAMCI by createBaffles, you firstly remove 0 folder. Later, re-create 0 folder.
my best |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[mesh manipulation] Sharp edge problem on concave patches using polyDualMesh without error | keepfit | OpenFOAM Meshing & Mesh Conversion | 1 | November 25, 2014 15:28 |
[blockMesh] Merging edge patches | Yosmcer | OpenFOAM Meshing & Mesh Conversion | 11 | November 16, 2014 15:51 |
problem with cyclicAMI and wall distance | Maff | OpenFOAM Bugs | 5 | August 14, 2014 15:41 |
Regarding periodic BC in ICEM generated grid | Tarak | OpenFOAM | 32 | April 30, 2013 15:46 |
Problem with cyclic patches | sven | OpenFOAM Running, Solving & CFD | 0 | December 5, 2011 15:27 |