Add show-cases tool for per-document regression/improvement analysis#615
Merged
Conversation
Introduces benchmarks/show_cases.py with word-level diffs and file export, and Makefile targets dev-show-regressions / dev-show-improvements. Per-case exports include the field text files alongside the source PDF, gold JATS XML, and both run TEI XMLs so regressions can be inspected end-to-end without leaving the examples directory. SHOW_RUN_B defaults to the first baseline from eval.yml so the common comparison requires no extra arguments beyond SHOW_FIELD.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces benchmarks/show_cases.py with word-level diffs and file export, and Makefile targets dev-show-regressions / dev-show-improvements.
Per-case exports include the field text files alongside the source PDF, gold JATS XML, and both run TEI XMLs so regressions can be inspected end-to-end without leaving the examples directory.
SHOW_RUN_B defaults to the first baseline from eval.yml so the common comparison requires no extra arguments beyond SHOW_FIELD.