uber / h3-go / 38593278043
100%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 20
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 100.0%. Remained the same
38593278043

push

github

web-flow 
conformance: state the parity contract and its knife edges (#166)

The README described the mechanism of every comparison but never said in
one place what passing the suite promises. The reasons behind the
tolerances, the inputs on which two correct implementations may
legitimately differ, and the one place the pure-Go port is allowed to
give a better answer than the reference were spread over PR text.

Add a "What conformance means" section ahead of the layout. It states
the contract: discrete outputs identical, coordinates within 1e-11
degrees of arc, measures within 1e-9 relative or the angular floor. It
explains why the coordinate bound is an angle and not a latitude and a
longitude, with the 1/cos(lat) amplification measured at the worst
resolution 4 cell, and why the bound is a floor on agreement rather than
a ceiling on accuracy, citing the exact-projection check. It names the
knife-edge inputs the suite keeps out by construction: points on cell
edges, polygon vertices on cell edges in the full and overlapping modes,
nearly antipodal pairs, and compiler contraction of multiply-adds. It
distinguishes the reference failing from its own buffer estimate, where
the better answer passes, from gridDistance refusing a pair, which an
implementation must reproduce. It lists what is unspecified because the
reference does not specify it.

The x/h3go package comment now points at the contract.

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

4550 of 4550 relevant lines covered (100.0%)

4163563.42 hits per line

Jobs
ID Job ID Ran Files Coverage
1 Go- - 38593278043.1 20
100.0
GitHub Action Run
Source Files on build 38593278043