You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SCRIP 0/360 seam duplicates nodes, giving euler_characteristic = 1 on a closed sphere #1782
A closed global SCRIP mesh reports euler_characteristic = 1 instead of 2.
SCRIP files store corner longitudes in 0..360 and include both endpoints of the seam: outCSne8 has 30 corners at lon=0 and 30 at lon=360. Those are the same meridian, but the reader's dedup compares (lon, lat) pairs literally, so the seam gets two sets of nodes and the mesh is topologically split along it.
mesh
duplicate node coords
V
E
F
χ
outCSne8
15
407
790
384
1
ne30pg2
119
21,727
43,326
21,600
1
HEALPix z3 (control)
0
770
1,536
768
2
The HEALPix control has no duplicates and gives the right answer, which locates the problem in the SCRIP path rather than in the Euler computation.
Both meshes are reported as closed: true, so a caller gets a closure verdict that disagrees with the characteristic printed beside it.
What did you expect to happen?
χ = 2 for a closed sphere, and nodes on the 0/360 seam merged.
Same class as #1692 (coincident nodes), but the trigger here is specifically the 0/360 seam in SCRIP rather than general coincidence, and it reproduces on the meshes already in test/meshfiles. Unchanged by #1775 — that PR swaps the dedup algorithm but compares the same (lon, lat) pairs, so it inherits the behaviour rather than causing it.
Activity