Skip to content

fix(run): name the real reason when the library iRT re-prediction is skipped - #93

Merged
RobbinBouwmeester merged 2 commits into
mainfrom
fix/irt-warning-under-multihead
Sep 17, 2026
Merged

RobbinBouwmeester merged 2 commits into
mainfrom
fix/irt-warning-under-multihead

Conversation

@RobbinBouwmeester

Copy link
Copy Markdown
Member

Seen in tonight's six-file Astral experiment log: run-experiment: keeping the imported library iRT because no predict_frag.deeplc_python is configured while a DeepLC interpreter was configured and the multi-head calibration ran. repredicts_library_irt returns 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 the else branch in both run and run-experiment attributed the skip to a missing interpreter.

Now: warn only when predict_frag.deeplc_python is actually absent; otherwise an info line says the multi-head calibration takes over. No behaviour change.

cargo fmt, cargo check locally; CI runs the rest.

🤖 Generated with Claude Code

RobbinBouwmeester and others added 2 commits September 16, 2026 22:39
…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>
@RobbinBouwmeester
RobbinBouwmeester merged commit d229cd6 into main Sep 17, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant