Repository navigation
Record neural run 3 (held-out: DeBERTa 0.185 vs CRF 0.127, not clear) - #41
Merged
Merged
Conversation
… clearly 24 runs, up to 20 epochs with min_epochs 6, selected on the selection half of the model-drafted dev records. On the 61 held-out documents the best DeBERTa-v3-small run reaches typed F1 0.185 against 0.127 for the CRF (paired +0.058 [-0.008, +0.134]); the false-prerequisite rate is not clearly different (+0.072 [-0.070, +0.196]). DistilBERT stays behind.
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
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.
Summary
reports/neural/run-3/: the third GPU run (Kaggle background version, one T4).min_epochs6.splits/selection-v1/selection.json, 111 docs).Results:
sqrt, 5e-5): the seed mean is 0.197 ± 0.011 held-out typed F1, up from 0.131 in run 2.crf-batches-01-02: paired +0.058 [−0.008, +0.134], not clear.The test split is not touched.
Checks
ruff check,ruff format --check,pytest -m "not slow"(241 passed twice); the reproduce command matches the report.libc++abi: recursive_mutex lock failed) before reporting. Two re-runs were clean. It is intermittent and possibly linked to memory pressure on the development Mac; this is not confirmed.