Skip to content

QuADMESH v0.2.5

Pre-release
Pre-release

Choose a tag to compare

@domattioli domattioli released this 12 Oct 05:15
· 18 commits to main since this release
d52ea1a

Documentation and metadata release, with one algorithm fix: the boundary layer is now routed as the thesis specifies.

Added

  • quadmesh-bench and quadmesh.benchmark: adapter harness comparing QuADMESH+ with other triangle-to-quad methods and, when the executables are installed, Gmsh Blossom-Quad and QuadriFlow (subprocess only, nothing vendored). Results for the bundled meshes are in docs/benchmarks/0.3.0/.

  • n_concave in compute_quality_stats and concave=N in format_quality_report: count of quads with a reflex corner.

  • docs/algorithm.md: one long-form document for the thesis algorithm, the port as implemented, a thesis-versus-port difference table, the experimental global-matching fallback, its relation to Blossom-Quad (Remacle et al. 2012), and MATLAB parity status.

  • tests/test_release_metadata.py: guard test that fails when CITATION.cff or README.md names a DOI other than the Zenodo concept DOI 10.5281/zenodo.20350483.

  • Ethan J. Kubatko (Ohio State University) as second author in CITATION.cff.

  • preserve_boundary option (default False) on run_pipeline and post_process_routine, plus protected_points on post_process_routine and cleanup_boundary_quads, and the CLI flag --preserve-boundary. With it on, boundary-quad cleanup skips any collapse that would delete an original boundary vertex and any shift that would move one. On the four bundled meshes this changes vertices lost from 12, 18, 4 and 2 to 0, at a cost of 1 to 9 extra elements and 0.001 to 0.011 mean skew. The default stays MATLAB-faithful.

Known limitations

  • Some boundary-layer quads can be concave. Smoothing can push a wide pinned boundary corner past 180 degrees. Both are tracked for a later release.

Changed

  • Test fixtures now come from the Valence API through chilmesh.registry (VALENCE_TOKEN), pinned by SHA-256. The GitHub contents fetcher, the GITHUB_TOKEN path and the git-blob pins are removed. Mixed_Test.14 left the registry (Valence#347), so its tests skip.
  • Dependency pin raised to chilmesh>=1.5.5.
  • README opening states what the conversion keeps and adds, and links to docs/algorithm.md. The status banner no longer carries a month stamp.
  • CITATION.cff and README.md cite the Zenodo concept DOI 10.5281/zenodo.20350483 in place of the version DOI 10.5281/zenodo.20351165.
  • Version is 0.2.5 in pyproject.toml, src/quadmesh/__init__.py, and CITATION.cff.
  • scripts/dev_setup.sh installs chilmesh from PyPI by default. Set QUADMESH_CHILMESH_SRC=<path> to editable-install a local CHILmesh checkout instead.

Fixed

  • The per-layer sweep flagged the innermost layer (n_layers - 1) as the boundary layer. It now flags layer 0, which is the boundary layer in chilmesh and in removeTrianglesFun.m. Output keeps zero interior residual triangles, is quad-pure by default, and keeps every original boundary vertex. Mean skew on the bundled structuredMesh1 changes from 0.696 to 0.647, and the expected values in the quality tests were updated (spec 059).
  • fem_smoother now restores the exact coordinates of every boundary vertex after each pass. CHILmesh.direct_smoother pins the boundary with a penalty and left up to 2e-10 of drift (no fixed-vertices argument exists). tests/test_boundary_pinned_smoothing.py covers all bundled triangular meshes. By default run_pipeline can still drop original boundary vertices, because cleanup_boundary_quads collapses boundary quads as the MATLAB code does; smoothing does not cause it. Pass preserve_boundary=True (CLI: --preserve-boundary) to keep all of them.
  • AGENTS.md and scripts/dev_setup.sh stated that chilmesh is not on PyPI. It is (chilmesh>=1.2.1).

Removed

  • docs/algorithm_writeup.md. Its content is section 5 of docs/algorithm.md, relabelled as the experimental fallback path.

Roadmap at 0.2.5

  • Now: boundary-layer quality, including the ENPAC2003 low-skew tail (#90); right-size the test suite (#109).
  • Next: boundary-type-aware layer seeding (#77); a MATLAB parity oracle (#116); wire tri2quad(aggressive=) to CHILmesh merge_elements.
  • Later: parallelization (#38); evaluate a C++ or Rust backend; formal integration with ADMESH and CHILmesh.

How to cite

Mattioli, D. O., & Kubatko, E. J. (2026). QuADMESH+: Quadrangular ADvanced Mesh generator (Version 0.2.5) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.20350483