View Issue Details

IDProjectCategoryView StatusLast Update
0003896OpenFOAMBugpublic2022-10-11 11:32
Reporterbillie Assigned Towill  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionreopened 
PlatformGNU/LinuxOSOtherOS Version(please specify)
Product Version10 
Fixed in Version10 
Summary0003896: Creation of cyclic baffles fails with OpenFOAM 10
DescriptionI am trying to migrate my models from OpenFOAM 8 to OpenFOAM 10. I noticed the commit https://github.com/OpenFOAM/OpenFOAM-10/commit/f93300ee111726d1f583fc016c14123d5e07383a which required changes to the input syntax for baffle creation.
Steps To ReproducePreviously the baffle was defined using e.g.:
internalFacesOnly true;
fields true;

baffles
{
    inte_eval_baffle
    {
        region fluid_body;
        type faceZone;
        zoneName inte_eval;
        patchPairs
        {
            type cyclic;
            transformType none;
        }
    }
}

For OpenFAOM 10 I changed it to e.g.:
internalFacesOnly true;
fields true;

baffles
{
    inte_eval_baffle
    {
        region fluid_body;
        type faceZone;
        zoneName inte_eval;
        owner
        {
            name inte_eval_baffle_side0;
            type cyclic;
            neighbourPatch inte_eval_baffle_side1;
            transform none;
        }
        neighbour
        {
            name inte_eval_baffle_side1;
            type cyclic;
            neighbourPatch inte_eval_baffle_side0;
            transform none;
        }
    }
}

When running createBaffles using the new format I get the following error:
--> FOAM FATAL ERROR:
problem : my edge:(0 1) in master points:(0 1) v.s. masterEdgeVerts:(2147483647 2147483647)

    From function void Foam::globalMeshData::calcGlobalEdgeOrientation() const
    in file meshes/polyMesh/globalMeshData/globalMeshData.C at line 1209.

If necessary I can attach the full log and an example case.
Additional InformationWhen using "fields true" in createBafflesDict the operation succeeds but later decomposPar fails because obviously the fields are not defined for the baffle sides.

Related question. I am doing this because I want to evaluate the pressure at a faceZone. This does not work (or at least I found no way to do so directly) thus I created the cyclic baffle to evaluate the pressure like for a boundary patch. Is there a way to avoid the creation of the patches. If yes the problem wouldn't be relevant.
TagsNo tags attached.

Activities

henry

2022-10-06 09:56

manager   ~0012763

User support request.

will

2022-10-07 08:34

manager   ~0012764

On reflection, actually yes, can you please upload the case that reproduces this failure. If a failure mechanism has been introduced by recent changes then it would be good to find and fix it.

> I am doing this because I want to evaluate the pressure at a faceZone.

In which case your use of createBaffles is unnecessary. Any post-processing evaluation that is possible for a patch is also possible on a faceZone. Actually helping you do this would be user support, which we do not provide here.

billie

2022-10-07 16:14

reporter   ~0012766

> On reflection, actually yes, can you please upload the case that reproduces this failure. If a failure mechanism has been introduced by recent changes then it would be good to find and fix it.

Please find attached the test case. Curious if there is actually an issue.

> In which case your use of createBaffles is unnecessary. Any post-processing evaluation that is possible for a patch is also possible on a faceZone. Actually helping you do this would be user support, which we do not provide here.

Understood that there is no user support. If I am not mistaken I can just replace the regionType patch with faceZone. Looks like this was not possible when I set this up the first time.
testCase.7z (1,562,076 bytes)

will

2022-10-11 11:32

manager   ~0012788

It's actually got nothing to do with createBaffles. It's a failure in patch distance calculation in the new "profile" stuff in the flow rate inlet boundary condition. The patch wave couldn't handle an un-split baffle. Fixed in 10 and dev as of these commits:

https://github.com/OpenFOAM/OpenFOAM-10/commit/9cc5fdb7ff0565e167176411afc6127b46ddf75e
https://github.com/OpenFOAM/OpenFOAM-dev/commit/ebb02bc894529cd798fa244e074508931bf6e87e

Issue History

Date Modified Username Field Change
2022-10-06 09:43 billie New Issue
2022-10-06 09:56 henry Assigned To => henry
2022-10-06 09:56 henry Status new => closed
2022-10-06 09:56 henry Resolution open => no change required
2022-10-06 09:56 henry Note Added: 0012763
2022-10-07 08:34 will Assigned To henry => will
2022-10-07 08:34 will Status closed => feedback
2022-10-07 08:34 will Resolution no change required => reopened
2022-10-07 08:34 will Note Added: 0012764
2022-10-07 08:35 will Status feedback => new
2022-10-07 16:14 billie Note Added: 0012766
2022-10-07 16:14 billie File Added: testCase.7z
2022-10-11 11:32 will Status new => resolved
2022-10-11 11:32 will Fixed in Version => 10
2022-10-11 11:32 will Note Added: 0012788