Skip to content

Stronger logprob baseline: add a min-token-logprob feature to the Gate A comparison #9

Description

@solarkyle

Gate A's headline (+0.065 LODO increment over logprob-only) uses the committed logprob feature set. A follow-up analysis on related data found that a stronger output-confidence baseline (min token logprob over the answer) closes much of the gap in some settings.

Task: rerun the Gate A LODO comparison with a min-token-logprob feature added to the baseline set, on the published Stage 1 features. If the increment shrinks, that is a result we want on record; if it survives, the claim gets stronger. CPU-only.

Do not touch campaign/frozen/ — this is a new analysis, not a re-fit of frozen artifacts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    analysis ideaNew analysis over the published traces/features — usually no GPU neededhelp wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions