View Issue Details

IDProjectCategoryView StatusLast Update
0004209OpenFOAMBugpublic2025-02-05 10:16
Reporterpeth Assigned Towill  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
OSarch linux 
Product Version12 
Fixed in Version12 
Summary0004209: Non-conformal mesh with NCC coupling cannot be used as source of mapFields
DescriptionNon-conformal mesh with NCC coupling cannot be used as source map of mapFields, as at the non-conformal coupled boundary of the source mesh causes error.
This also happens if the "patchMap" list is left empty in the target mesh's mapFieldsDict file, i.e. when the problematic boundary is not specified to be included in the interpolation.
Steps To Reproduce#create new sample simulations from tutorial
cp -r $FOAM_TUTORIALS/multiRegion/CHT/misalignedDuct sim_source
cp -r $FOAM_TUTORIALS/multiRegion/CHT/misalignedDuct sim_target

#navigate to sim_source and run it for a few iterations
cd sim_source
./Allrun

#navigate to sim target, and copy the empty mapFieldsDict file from another tutorial to the system folder
cd ../sim_target
cp $FOAM_TUTORIALS/incompressibleFluid/hopperParticles/hopperEmptying/system/mapFieldsDict system/

#generate mesh in new folder by running pre-processing commands from ./Allrun
awk '
{
    if (NR<=14)
    {
        print $0
    }
}' Allrun > Allrun2
chmod +x Allrun2
./Allrun2

#run mapFields, which results in error
mapFields -mapMethod mapNearest -sourceRegion solid -targetRegion solid -sourceTime 1 ../sim_source
TagsNo tags attached.

Activities

cgoessni

2025-02-01 09:05

reporter   ~0013520

Did you try using mapFieldsPar?

will

2025-02-05 10:16

manager   ~0013523

Thanks for the report. Fixed in v12 and in dev:

https://github.com/OpenFOAM/OpenFOAM-12/commit/3538462d506cec36ac20819170fa2a77ffb86812
https://github.com/OpenFOAM/OpenFOAM-dev/commit/4a65ffb0d40e35d50bacd3289747356867519b04

Issue History

Date Modified Username Field Change
2025-01-31 15:17 peth New Issue
2025-02-01 09:05 cgoessni Note Added: 0013520
2025-02-05 10:16 will Assigned To => will
2025-02-05 10:16 will Status new => resolved
2025-02-05 10:16 will Resolution open => fixed
2025-02-05 10:16 will Fixed in Version => 12
2025-02-05 10:16 will Note Added: 0013523