Repository navigation
Conversation
The Liber Usualis corpus encodes @FACS on the enclosing <neume> element (one bounding box per neume figure) rather than on each individual <nc> -- valid MEI5, just a different convention from encodings that give every note its own zone. _get_element_zone only ever checked the <nc> itself, so every neume component in that corpus silently fell back to the (-1,-1,-1,-1) "not found" sentinel. Search results consume those coordinates directly for both the result thumbnail image and Diva's click-to-focus, so both were broken for every result on this manuscript. Verified the fix resolves all 338,745 neume components across the full 2318-file Liber Usualis corpus (previously all -1,-1,-1,-1), with zero parse errors and no change to manuscripts that already encode facs per-component (existing fixture/tests unaffected). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe MEI parser now inherits a parent neume’s zone when a component lacks its own ChangesNeume zone resolution
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This change restores existing manuscript coordinates for neume components that inherit their enclosing neume’s bounding box, while preserving component-level coordinates. No actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 6 functions across 2 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Based on the naming convention in #987, the filename should be LU-1961_0123.mei.
| "mei_processing", | ||
| "test_mei_files", | ||
| "991961", | ||
| "0123_corr - mei5.mei", |
There was a problem hiding this comment.
Also change the filename to LU-1961_0123.mei here.
The Liber Usualis corpus encodes @FACS on the enclosing element (one bounding box per neume figure) rather than on each individual . _get_element_zone only ever checked the itself, so every neume component in that corpus silently fell back to the (-1,-1,-1,-1) "not found" sentinel. Search results consume those coordinates directly for both the result thumbnail image and Diva's click-to-focus, so both were broken for every result on this manuscript.
Verified the fix resolves all 338,745 neume components across the full 2318-file Liber Usualis corpus (previously all -1,-1,-1,-1), with zero parse errors and no change to manuscripts that already encode facs per-component (existing fixture/tests unaffected).
Summary by CodeRabbit
Bug Fixes
Tests