|
[Sponsors] |
February 21, 2012, 11:59 |
Problematic Interfaces- Can't trace source
|
#1 |
New Member
Casey Harwood
Join Date: Feb 2012
Posts: 3
Rep Power: 14 |
Hello all,
I'm quite the CFD amateur, so please bear with me if I make any ignorant remarks. I've been working on modeling flow past a foil in a rectangular flow channel. My focus is on the characteristic flow through a finitely-small gap between the foil tip and the wall. I'm paying special attention to the boundary-layer and vortex interactions, so my mesh is extremely fine near the foil tip and in the wake. I'm working with several meshes between 6 million and 16 million elements. I've divided the flow domain into three segments. I've specified free-slip walls upstream of the first division, and no-slip everywhere downstream. By parameterizing the upstream division, I'm hoping to exert control over the boundary layer thickness on the wall. The third segment maintains the no-slip condition but does away with the structured mesh to spare me some elements, and because the vortices of interest convect out of the boundary layer pretty quickly. I've formed the three sections into a multibody part in DesignModeler, and I've ensured that the mesh is contiguous. CFX Pre recognizes the setup as a single domain and automatically recognizes 1:1 contact regions. I've specified them as fluid-fluid interfaces with conservative flux in Pre. When I execute the runs, however, I'm still getting a spurious wall (I think.) For whatever reason, it's walling-up my outlet and exiting with an overflow error. I've tried different ways of specifying the interfaces (manually and with automatic detection,) and I keep getting the same result for all of my meshes. Is there some trick I'm missing? I haven't tried inserting a connection prior to meshing yet, but I was under the impression that its not necessary if the bodies form a single part with a contiguous mesh. Thanks much, Casey |
|
February 21, 2012, 12:07 |
|
#2 |
New Member
Casey Harwood
Join Date: Feb 2012
Posts: 3
Rep Power: 14 |
Here's a figure of my domain and boundary conditions for reference.
|
|
Tags |
interface domains |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[swak4Foam] swak4foam building problem | GGerber | OpenFOAM Community Contributions | 54 | April 24, 2015 17:02 |
[swak4Foam] swak4Foam-groovyBC build problem | zxj160 | OpenFOAM Community Contributions | 18 | July 30, 2013 14:14 |
"parabolicVelocity" in OpenFoam 2.1.0 ? | sawyer86 | OpenFOAM Running, Solving & CFD | 21 | February 7, 2012 12:44 |
DxFoam reader update | hjasak | OpenFOAM Post-Processing | 69 | April 24, 2008 02:24 |
DecomposePar links against liblamso0 with OpenMPI | jens_klostermann | OpenFOAM Bugs | 11 | June 28, 2007 18:51 |