isoSurfaceTopo does not respect bounds keyword

Summary

isoSurface and isoSurfaceCell are properly truncated using bounds, but isoSurfaceTopo is not, the keyword seems to be ignored. Since I see const boundBox& bounds = boundBox::invertedBox as a parameter to the constructor, I figure this is a bug, and not a missing feature.

Steps to reproduce

• Grab the damBreak tutorial and run it.
• Put the attached test file into system.
• Run postProcess -func test
• Open the generated vtp files in Paraview and observe that the interfaceIsoSurfaceTopo.vtp is not truncated and x = 0.25, whereas the other two are.

Environment information

• OpenFOAM version : v1912
• Operating system : irrelevant
• Hardware info : irrelevant
• Compiler : irrelevant

test

(The dambreak is perhaps a poor choice, since it's 2d, but I originally discovered this on a 3D case of mine.)

@mark @Mattijs

Thanks for the prod. This is still pending on the to-do list. The bounds handling for the other types are treated by a subset mesh (real, or ad hoc). Needed to check what this might have needed for topological matching.

• for the topo version seems to work okay with a cellZones().selection() as a bitSet. Might have something usable for the Dec release.

mentioned in commit dbc5bbdc

mentioned in commit 28516bc6

mentioned in commit ccde68d4

@mark - anything further for this ticket?

Seems to be resolved. Can reopen as needed

closed