GitLab

Summary

For a boundary condition, assume there are two MappedFile-object entries: R and L.

The condition definition could look like as follows:

condition
{
    type         condition;

    R
    {
        type    mappedFile;
        mapMethod  nearest;
    }
    L
    {
        type    mappedFile;
        mapMethod  nearest;
    }
}

However, utilities invoking MappedFile::writeData, e.g. decomposePar, writes out all the subdictionaries into the same scope:

condition
{
    type         condition;

    R           mappedFile;
    mapMethod   nearest;

    L           mappedFile;
    mapMethod   nearest;
}

The above is problematic because we have multiple mapMethod entries within the same scope.

Steps to reproduce

NA

Example case

NA

What is the current bug behaviour?

NA

What is the expected correct behavior?

@mark's comment:

Should probably be writing out RCoeffs { mapMethod ...; } and LCoeffs { ... }

Relevant logs and/or images

NA

Environment information

api      = 2102
patch    = 210414
HEAD     = 739c1c1d61
version  = com
compiler = Clang (system)
         = clang version 9.0.1 
mpi      = SYSTEMOPENMPI
         = mpirun (Open MPI) 1.10.7.0.5e373bf1fd
OS       = Description:	openSUSE Leap 15.1
opts     = linux64ClangDPInt32Opt

Possible fixes

NA @Mattijs