fix(run): name the real reason when the library iRT re-prediction is skipped - #93
Merged
Merged
Conversation
…skipped With multi-head calibration active (the default since 2026-09-11), repredicts_library_irt returns false because the calibration re-predicts the library itself on the first run, but both orchestrators then warned that no predict_frag.deeplc_python was configured, which was untrue. Warn only when the interpreter is missing; otherwise say that the multi-head step takes over. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Seen in tonight's six-file Astral experiment log:
run-experiment: keeping the imported library iRT because no predict_frag.deeplc_python is configuredwhile a DeepLC interpreter was configured and the multi-head calibration ran.repredicts_library_irtreturns false under multi-head on purpose (the calibration re-predicts the library on the first run, so a base-model re-prediction first would only be overwritten), but theelsebranch in bothrunandrun-experimentattributed the skip to a missing interpreter.Now: warn only when
predict_frag.deeplc_pythonis actually absent; otherwise an info line says the multi-head calibration takes over. No behaviour change.cargo fmt,cargo checklocally; CI runs the rest.🤖 Generated with Claude Code