Polyscope and Geometry central disagree on the number of halfedges in a mesh ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- computer-graphics
Research direction
Start by reproducing the snippet with readManifoldSurfaceMesh(), registerSurfaceMesh(), and addHalfedgeScalarQuantity(). Compare the halfedges() count with the registered surface mesh count, then trace where those counts are established. Done means the discrepancy is explained and the halfedge scalar quantity handles the same mesh consistently, with a regression check if the project has one.
Written by the indexing model from the issue text.
Description
Not sure if anyone else has found this or if I am doing this wrong but I have found that when loading a mesh in with geometry central and then trying to add a halfedge scalar value to the mesh in polyscope I get an error as polyscope thinks there is fewer halfedges than geometry central does. Incase I am doing something stupid I have added a snipped below.
polyscope::init();
//Load Mesh
std::tie(mesh, geometry) = readManifoldSurfaceMesh("QuadMesh.obj");
//Register Mesh
sm = polyscope::registerSurfaceMesh("my mesh", geometry->vertexPositions, mesh->getFaceVertexList());
//Object to store halfedge values
HalfedgeData<int> visitedHE(*mesh, 0);
// Filling data (This is not the way I am actually doing it, but its essentially the same )
for(Halfedge he : mesh->halfedges()){
visitedHE[he] =1;
}
sm->addHalfedgeScalarQuantity("HEvisit", visitedHE)->setEnabled(true);
polyscope::show();
From the mesh I have Geometry Central thinks that I have 10974 halfedges but polyscope thinks I have 10928 halfedges??
If I am missing something obvious then please let me know.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 242
- Avg merge
- 11m
- Merged PRs (30d)
- 1
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/polyscope
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Rust Version Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in nmwsharp/polyscope
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
flutter-webrtc/flutter-webrtc#2206 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google-ai-edge/LiteRT-LM#3739 ·
-
Component: GLib
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
brave/brave-browser#59300 ·
-
Mute ydb/tests/functional/dstool/test_canonical_requests.py.Test.test_group_take_snapshot in main Openai_reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ydb-platform/ydb#53974 · 3 comments ·