|
[Sponsors] |
Setting up Parallel Simulations of Dynamic Mesh |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
September 23, 2014, 20:18 |
Setting up Parallel Simulations of Dynamic Mesh
|
#1 |
New Member
Will
Join Date: Dec 2011
Posts: 17
Rep Power: 15 |
I'm find setting up new models for waveFoam and waveDyMFoam (which are essentially icoFoam and IcoDyMFoam) to be a process of random luck.
The process of creating a Mesh, Assigning values to the mesh (like Alpha levels and initial velocities), and splitting it across processors seems to require a lot more care and just when I think I get it - it doesn't. To give an illustration, our Allrun script has the following form Code:
#!/bin/sh . $WM_PROJECT_DIR/bin/tools/RunFunctions runApplication surfaceFeatureExtract runApplication blockMesh runApplication decomposePar runParallel snappyHexMesh 40 -overwrite # reconstruct runApplication reconstructParMesh -mergeTol 1e-6 -constant \rm -rf 0 \cp -r 0.org 0 rm -rf processor* mv log.decomposePar log.decomposePar1 runApplication setWaveField runApplication decomposePar runParallel wave[DyM]Foam 40 parReconstructPar -n 20 I hate this script, since we split the mesh for snappyHexMesh, pull it all back together just to assign velocities and water levels to all the cells (with setWaveField) and then split it again. However, its the only way I get it to work consistently. Has anyone managed to get setWaveField to work sensible in parallel - which I know it can do. Another issue that perplexes me, is that I see in many example the following lines or an appropriate variant, at the bottom of each file within 0.org Code:
"procBoundary.*" { type processor; value uniform (0 0 0); } As an example in 0.org/alpha.water contains Code:
/*--------------------------------*- C++ -*----------------------------------*\ | ========= | | | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox | | \\ / O peration | Version: 1.5-dev | | \\ / A nd | Revision: 1740 | | \\/ M anipulation | Web: http://www.OpenFOAM.org | \*---------------------------------------------------------------------------*/ FoamFile { version 2.0; format ascii; class volScalarField; location "0"; object alpha.water; } // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // dimensions [0 0 0 0 0 0 0]; internalField uniform 0; boundaryField { bottom { type zeroGradient; // no flow through boundary } backWall { type zeroGradient; } inlet { type waveAlpha; refValue uniform 0; refGrad uniform 0; valueFraction uniform 1; value uniform 0; } outlet { type zeroGradient; } atmosphere { type inletOutlet; inletValue uniform 0; value uniform 0; } ccell { type zeroGradient; } "procBoundary.*" { type processor; value uniform (0 0 0); } } |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
sliding mesh problem in CFX | Saima | CFX | 46 | September 11, 2021 08:38 |
Reconstruction after parallel run with dynamic mesh refinement | sebonator | OpenFOAM | 9 | June 14, 2018 08:38 |
Dynamic Mesh moving interface help | akash.iitb | FLUENT | 0 | August 24, 2010 00:53 |
Cells with t below lower limit | Purushothama | Siemens | 2 | May 31, 2010 22:58 |
Warning 097- | AB | Siemens | 6 | November 15, 2004 05:41 |