Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
openfoam
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Development
openfoam
Commits
96de893e
Commit
96de893e
authored
12 years ago
by
andy
Browse files
Options
Downloads
Patches
Plain Diff
ENH: Updated ACMI tutorial notes
parent
dc0ad78e
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tutorials/incompressible/pimpleDyMFoam/oscillatingInletACMI2D/README
+34
-31
34 additions, 31 deletions
...ncompressible/pimpleDyMFoam/oscillatingInletACMI2D/README
with
34 additions
and
31 deletions
tutorials/incompressible/pimpleDyMFoam/oscillatingInletACMI2D/README
+
34
−
31
View file @
96de893e
...
...
@@ -8,14 +8,8 @@ Each ACMI patch requires the specification of a 'non-overlapping' patch. In
this example, the non-overlapping patches are described as walls, e.g. taken
from the constant/polyMesh/boundary file:
1. First ACMI p
o
atch pair applied to the inlet channel outlet
1. First ACMI patch pair applied to the inlet channel outlet
ACMI1_blockage
{
type wall;
nFaces 40;
startFace 43680;
}
ACMI1_couple
{
type cyclicACMI;
...
...
@@ -26,16 +20,16 @@ from the constant/polyMesh/boundary file:
neighbourPatch ACMI2_couple;
nonOverlapPatch ACMI1_blockage;
}
1. Second ACMI poatch pair applied to the fixed mesh region inlet
ACMI2_blockage
ACMI1_blockage
{
type wall;
nFaces
96
;
startFace 43
7
60;
nFaces
40
;
startFace 436
8
0;
}
1. Second ACMI patch pair applied to the fixed mesh region inlet
ACMI2_couple
{
type cyclicACMI;
...
...
@@ -46,6 +40,12 @@ from the constant/polyMesh/boundary file:
neighbourPatch ACMI1_couple;
nonOverlapPatch ACMI2_blockage;
}
ACMI2_blockage
{
type wall;
nFaces 96;
startFace 43760;
}
In the above, the ACMI1_blockage and ACMI1_couple patches occupy the same space,
...
...
@@ -56,7 +56,10 @@ The duplicate patches are initially created using the createBaffles utility.
Firstly, the original (non-duplicated) patch faces are collected into zones
using the topoSet utility.
Each ACMI/no-overlapping patch pair is specified using a master-slave approach.
Note: when specifying the ACMI patch-pairs, the coupled patch must be specified
before its associated non-overlapping patch.
Each ACMI/non-overlapping patch pair is specified using a master-slave approach.
However, since we are generating boundary patches (which are always master
patches) the slave patches are simply defined using 'dummy' entries, e.g.:
...
...
@@ -65,22 +68,8 @@ patches) the slave patches are simply defined using 'dummy' entries, e.g.:
patches
{
// create blockage patch
master
{
//- Master side patch
name ACMI1_blockage;
type wall;
}
slave1 // dummy entries only
{
//- Slave side patch
name ACMI1_blockage;
type wall;
}
// create cyclic ACMI patch
master
2
master
{
//- Master side patch
name ACMI1_couple;
...
...
@@ -90,12 +79,26 @@ patches) the slave patches are simply defined using 'dummy' entries, e.g.:
nonOverlapPatch ACMI1_blockage;
transform noOrdering;
}
slave
2
// dummy entries only
slave // dummy entries only
{
//- Slave side patch
name ACMI1_couple;
type patch;
}
// create blockage patch
master2
{
//- Master side patch
name ACMI1_blockage;
type wall;
}
slave12 // dummy entries only
{
//- Slave side patch
name ACMI1_blockage;
type wall;
}
}
Boundary conditions must then be applied to all geometric patches in the usual,
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment