remesh docs advertise an IntrinsicGeometryInterface& overload the code doesn't have
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- cpp
- Domain
- documentation
Research direction
Compare the remeshing page with include/geometrycentral/surface/remeshing.h at the reported revision, then inspect the implementation's use of vertexPositions and faceNormal. Confirm whether the documented IntrinsicGeometryInterface overload is intended; done means the docs and available declarations no longer disagree, or the intended API change is clearly identified for follow-up.
Written by the indexing model from the issue text.
Description
Version: master @ 1e8e43d2 (and the docs site as of 2026-06-01).
The remeshing docs (https://geometry-central.net/surface/algorithms/remeshing/)
show:
void remesh(ManifoldSurfaceMesh& mesh, IntrinsicGeometryInterface& geom, RemeshOptions options = defaultRemeshOptions);
void remesh(ManifoldSurfaceMesh& mesh, IntrinsicGeometryInterface& geom, MutationManager& mm, RemeshOptions options = defaultRemeshOptions);
But include/geometrycentral/surface/remeshing.h (unchanged since
2022-12-09) declares only VertexPositionGeometry& overloads, and the
implementation uses geom.vertexPositions[...] / geom.faceNormal(...)
(smoothing to circumcenters, computing split midpoints in 3D) — so it
genuinely requires an embedded geometry and cannot run on a bare
IntrinsicGeometryInterface.
So either the docs are aspirational/stale, or an intended
IntrinsicGeometryInterface& overload was never merged. Either way the
documented signature won't compile against the current code. (Context: we
were hoping to remesh an intrinsic triangulation directly; the docs implied
it was supported.)
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 183
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nmwsharp/geometry-central
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
nmwsharp/geometry-central#256 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
nmwsharp/geometry-central#255 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
nmwsharp/geometry-central#253 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
nmwsharp/geometry-central#246 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
nmwsharp/geometry-central#234 ·
All issues in nmwsharp/geometry-central
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
autowarefoundation/autoware_universe#13413 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
automated-analysis bug memory-safety
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·