Revert #128: a benchmark baseline must be the bare model, no system prompt#175
Merged
Merged
Conversation
|
lol? |
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.
Reverts #128.
A baseline arm is the control: the bare model with the task and nothing else. #128 gave it a system prompt ("Provide just one example for any given task, and no commentary or usage examples"), which:
Any prompt on the baseline tilts the comparison ("write the minimum amount of code" would erase the gap; the opposite would inflate it). The fair control is no prompt at all. The rambling critique in #126 is already answered by the agentic benchmark, so the single-shot baseline does not need de-rambling.
🤖 Generated with Claude Code