reconstructParMesh: report cells in multiple cellZones

Summary

reconstructParMesh warns about cells present in multiple cellZones

Steps to reproduce

Run tutorials/heatTransfer/chtMultiRegionSimpleFoam/cpuCabinet - look at output of reconstructParMesh (currently not stored)

Example case

See above

What is the current bug behaviour?

Reports lots & lots of warnings where there should be none.

What is the expected correct behavior?

Relevant logs and/or images

/*---------------------------------------------------------------------------*\
| =========                 |                                                 |
| \\      /  F ield         | OpenFOAM: The Open Source CFD Toolbox           |
|  \\    /   O peration     | Version:  2204                                  |
|   \\  /    A nd           | Website:  www.openfoam.com                      |
|    \\/     M anipulation  |                                                 |
\*---------------------------------------------------------------------------*/
Build  : 8ac11f1079-20220615 OPENFOAM=2204 patch=220610 version=com
Arch   : "LSB;label=32;scalar=64"
Exec   : reconstructParMesh -region domain0 -constant
Date   : Jun 20 2022
Time   : 10:59:15
Host   : preston
PID    : 26872
I/O    : uncollated
Case   : /home/preston2/mattijs/OpenFOAM/OpenFOAM-plus/work/develop/openfoam/tutorials/heatTransfer/chtMultiRegionSimpleFoam/cpuCabinet/junk
nProcs : 1
trapFpe: Floating point exception trapping enabled (FOAM_SIGFPE).
setNaN : Initialise allocated memory to NaN enabled (FOAM_SETNAN).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 5, maxFileModificationPolls 20)
allowSystemOperations : Allowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Merge individual processor meshes back into one master mesh.
Use if the original master mesh has been deleted or the processor meshes
have been modified (topology change).
This tool will write the resulting mesh to a new time step and construct
xxxxProcAddressing files in the processor meshes so reconstructPar can be
used to regenerate the fields on the master mesh.

Not well tested & use at your own risk!

Merge assuming correct, fully matched procBoundaries.

Using region: domain0

Found 10 processor directories
    Reading database "junk/processor0"
    Reading database "junk/processor1"
    Reading database "junk/processor2"
    Reading database "junk/processor3"
    Reading database "junk/processor4"
    Reading database "junk/processor5"
    Reading database "junk/processor6"
    Reading database "junk/processor7"
    Reading database "junk/processor8"
    Reading database "junk/processor9"

Time = constant

--> FOAM Warning : 
    From static void Foam::polyMeshAdder::add(const Foam::UPtrList<Foam::polyMesh>&, const Foam::UList<Foam::List<int> >&, const labelListList&, const labelListList&, const labelListList&, const labelListList&, const Foam::UList<Foam::List<int> >&, const Foam::UList<Foam::List<int> >&, const Foam::UList<Foam::List<int> >&, Foam::polyTopoChange&, Foam::labelListList&, Foam::labelListList&, Foam::labelListList&)
    in file polyMeshAdder/polyMeshAdder.C at line 2755
    Cell:11382 centre:(-0.0054958661 0.048956076 -0.070567223) is in two zones:domain0 and v_MRF
    This is not supported. Continuing with first zone only.

Environment information

• OpenFOAM version : v2112 (or even earlier?)
• Operating system :
• Hardware info :
• Compiler :

Possible fixes

• check that cellZones are consistent across processors
• make simple testcase

added bug label

changed the description

assigned to @Mattijs

• splitMeshRegions preserves the cellZones, independent of the splitting action (using connectivity or using existing cellZones)
• splitMeshRegions -cellZones will now write regions with all cells in each region in their cellZone
• topoSet is used to add another cellZone
• but now the cells will be in multiple regions and most utilities cannot handle this - e.g. reconstructPar

mentioned in commit 4850f1dc

closed via commit 4850f1dc