sampledTriSurfaceMesh reading surfaces from region directory

    IOobject
    (
        dict.lookup("surface"),
        mesh.time().constant(), // instance
        "triSurface",           // local
        mesh,                   // registry
        IOobject::MUST_READ,
        IOobject::NO_WRITE,
        false
    ),

So surfaces are taken from the mesh registry, which means regionName/constant/triSurface for etc. Could, however, have them taken from mesh.time() so that they use the main constant/triSurface

@Mattijs @Prashant

cross-reference EP#598

changed the description

• some surfaces read&registered from constant/triSurface, some from constant//triSurface
• the registry and file location should be consistent
• are surfaces global or region-local?
• following uses are region-local:

discreteSurface
sampledTriSurfaceMesh
regionCoupledBase
cyclicAMIPolyPatch
mappedPatchBase

changed the description

Conclusion: probably more user friendly to have the top-level directory. Potential name conflicts if the surfaces are registered will needed to be dealt with manually.

closed via commit af7b0c86ed9e465c70def77e0fbce0c5f41884e2

mentioned in commit af7b0c86ed9e465c70def77e0fbce0c5f41884e2

mentioned in commit 272374d3f64e88f082ed6eb3a769478513a743b9

mentioned in commit 4514bc23841854548ecd774a044acec06690976d

mentioned in commit 701a3cc7

mentioned in commit 07fd1aec

mentioned in commit 218ca2f7