feat: LFM2.5-Encoder span-tagger support - #97
Merged
Merged
Conversation
…ng, per-source eval script)
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.
What
Lands the LFM2.5-Encoder span-tagger work that was sitting on the local main (authored July 29): wrapper-prefix weight loading in
scripts/train_lfm_span_detector.pyand a per-source evaluation scriptscripts/evaluate_lfm_span_model.py. Part of the #42 (Lfm2Bi) exploration — issue #42's pointers reference these files.Two mechanical adjustments for CI: ruff formatting on the eval script, and the training self-check's
assertconverted to an explicitRuntimeError(S101).Checklist
Full suite green locally; ruff format + check clean under the CI invocation.
I certify that I have the right to submit this code and that it may be distributed under the repository's MIT license