ZipperMesh silent failure in one-cell-wide 2D overset problems
Description
For overset cases with overlapping surface meshes (such as combined internal/external flow problems where an integration zone is required), the zipper mesh routine can fail to produce a zipper mesh for certain meshes that are one cell wide without raising an error message. I have observed multiple meshes where , e.g., 3 of the 4 overlap regions produce good zipper mesh cells but one has a gap.
Steps to reproduce issue
Placeholder, need to produce an open source-able test case
Current behavior
Zipper mesh debug info showed "Starting String ...." with no further debug info printed for that string (some kind of early exit is happening)
Zipper mesh successfully created for same mesh if I extrude two cells wide instead of just one.
Expected behavior
Zipper mesh created for each overlap region
Code versions
- Operating System: Amazon Linux, WSL2
- This repository: 2.5 (february 2022 following Sabet's zipper mesh segfault fix)
By adding debug print statements I know that it's taking the early out here: https://github.com/mdolab/adflow/blob/4b179a0cdcd139fe74b874c9745e868e8b183cee/src/overset/stringOps.F90#L1468