Skip to content

fix: bring crameri up to spec with v8 - #143

Open
tlambert03 wants to merge 2 commits into
pyapp-kit:mainfrom
tlambert03:fix-crameri
Open

fix: bring crameri up to spec with v8#143
tlambert03 wants to merge 2 commits into
pyapp-kit:mainfrom
tlambert03:fix-crameri

Conversation

@tlambert03

Copy link
Copy Markdown
Member

continuing with #141 ... this brings crameri to complete parity with the current v8 data on zenodo. and adds a parity test:

  • Regenerates the four tables SCM 8 revised but didn't reverse (tokyo 56/255, acton 34, bamako 20, batlowK 14)
  • re-cuts the five maps from feat: update for crameri v8 #83 that were stored at 5 decimals instead of 6, and repoints the remaining __source__ pins to the 8.0.1 deposit (zenodo 8409685) — those tables are byte-identical in both deposits, so that part is metadata only.

All 40 crameri maps are now bit-exact against SCM 8.0.1. Adds
test_crameri_data_parity (oracle: cmcrameri 1.10, which vendors the same
deposit) so this can't drift again.

@tlambert03 tlambert03 changed the title bring crameri up to spec with v8 fix: bring crameri up to spec with v8 Aug 9, 2026
@codecov

codecov Bot commented Aug 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.56%. Comparing base (8040ef7) to head (98b3b81).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #143   +/-   ##
=======================================
  Coverage   95.56%   95.56%           
=======================================
  Files         168      168           
  Lines        2186     2188    +2     
=======================================
+ Hits         2089     2091    +2     
  Misses         97       97           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant