View Issue Details

IDProjectCategoryView StatusLast Update
0003960OpenFOAMBugpublic2023-02-22 23:52
Reporternainavinod Assigned Tohenry  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformRed Hat OSrhelOS Version7.9
Summary0003960: NearWallFields functionObject for large Overset (Multi-region) meshes not working
DescriptionTo sample near wall fields in the moving region of an overset simulation, at frequent time steps, the following function was called:


nearWallFields1
{
    // Mandatory entries
    type nearWallFields;
    libs (fieldFunctionObjects);
    fields
    (
        (U UNear)
        (p pNear)
    );
    patches (Propeller); // moving wall
    distance 1e-3;

    // Optional (inherited) entries
    log true;
    region region1; //overset region; background region is region0 (default)
    enabled true;
    timeStart 0;
    timeEnd 0.03;
    executeControl timeStep;
    executeInterval 5;
    writeControl timeStep;
    writeInterval 10;
}


This gives the following error:


--> FOAM Warning :

    request for objectRegistry region1 from objectRegistry Overset0_RPM2000_Inflow5processor0 failed
    available objects of type objectRegistry are
1(region0)

    From const Type& Foam::objectRegistry::lookupObject(const Foam::word&, bool) const [with Type = Foam::objectRegistry]
    in file ~/OpenFOAM/OpenFOAM-v2006/src/OpenFOAM/lnInclude/objectRegistryTemplates.C at line 463.
    From bool Foam::functionObjectList::read()
    in file db/functionObjects/functionObjectList/functionObjectList.C at line 895

--> while loading function object 'nearWallFields1'


How should the moving region be defined as a new region, without actually splitting the mesh (as done in splitMeshRegions)?
Steps To ReproduceTried it in the tutorial case $FOAM_TUTORIALS/incompressible/overPimpleDyMFoam/simpleRotor by adding the sub-dictionary:

nearWallFields1
{
    // Mandatory entries
    type nearWallFields;
    libs (fieldFunctionObjects);
    fields
    (
        (U UNear)
        (p pNear)
    );
    patches (hole); // moving wall
    distance 3e-4;

    // Optional (inherited) entries
    log true;
    region region1; //overset region; background region is region0 (default)
    enabled true;
    timeStart 0;
    timeEnd 0.1;
    executeControl timeStep;
    executeInterval 10;
    writeControl timeStep;
    writeInterval 10;
}

Works for default region (region0) but does not for region1.
Additional InformationThe naming of regions as region0 and region1 has been taken from the checkMesh operation:

Checking topology...
    Boundary definition OK.
    Cell to face addressing OK.
    Point usage OK.
    Upper triangular ordering OK.
    Face vertices OK.
   *Number of regions: 2
    The mesh has multiple regions which are not connected by any face.
  <<Writing region information to "constant/cellToRegion"
  <<Writing region 0 with 42141036 cells to cellSet region0
  <<Writing region 1 with 25334521 cells to cellSet region1
TagsNo tags attached.

Activities

henry

2023-02-22 23:52

manager   ~0012958

There is no overset capability is the official OpenFOAM releases from the OpenFOAM Foundation.

The OpenFOAM Foundation is the organisaton which holds the copyright of the OpenFOAM software and documentation, whose purpose is to manage and distribute OpenFOAM as free, open source software for the benefit of its users.

Issue History

Date Modified Username Field Change
2023-02-22 23:01 nainavinod New Issue
2023-02-22 23:52 henry Assigned To => henry
2023-02-22 23:52 henry Status new => closed
2023-02-22 23:52 henry Resolution open => no change required
2023-02-22 23:52 henry Note Added: 0012958