FWeindel's picture
Document intended and actual output-limit evidence in all v2/v3 READMEs
d6c2550 verified
|
Raw History Blame
3.81 kB

Trajectory statistics

214,720 attempts across 6,710 tasks of crosscodeeval_v2, kept and excluded, each counted once. Task success counts are in the dataset overview.

Metric qwen3-30b-instruct-2507 qwen3-30b-thinking
Recorded attempts 107,360 107,360
Median agent turns 2 2
Median input tokens per attempt 3,865 3,723
Median output tokens per attempt 393 1,504
Median agent runtime (seconds) 6 20
Median verifier runtime (seconds) 1 1

Medians use recorded measurements only.

Plots

Trace measurements

Trace outcomes

Most frequent commands

Commands are counted as submitted, not as successful executions.

Per-model plots: qwen3-30b-instruct-2507, qwen3-30b-instruct-2507, qwen3-30b-instruct-2507, qwen3-30b-thinking, qwen3-30b-thinking, qwen3-30b-thinking.

Data

Attempts without a saved conversation: 1; without a verifier reward: 2. Their missing measurements stay empty.

Evaluation settings

Context is the total prompt plus response window for one model call. The response budget includes reasoning tokens and is not a whole-attempt token budget.

Model Context tokens (configured) Intended response tokens per call Output-limit evidence Thinking Sampling
openai/qwen3-30b-instruct-2507 32768 8192 No explicit request cap in sampled saved configs; actual fallback cap unknown off {"min_p": 0, "temperature": 0.7, "top_k": 20, "top_p": 0.8}
openai/qwen3-30b-thinking 32768 8192 No explicit request cap in sampled saved configs; actual fallback cap unknown on {"min_p": 0, "temperature": 0.6, "top_k": 20, "top_p": 0.95}

Configured limits are not measurements of token usage. A missing explicit response cap does not mean unlimited generation: the serving context, backend defaults, stopping conditions and task timeouts still apply. Unknown historical settings are not filled from current model defaults.

Historical output-limit bug: the intended per-response limit was stored as top-level max_tokens, but the affected Terminus path did not forward it as llm_call_kwargs.max_tokens. Thus these sampled runs did not request the intended explicit cap. Generation instead depended on the backend's fallback allowance, available context, stopping conditions and agent timeout. The exact fallback limit is not established by the saved configurations; it must not be reported as 8,192 or 16,384 enforced tokens, or as unlimited.

The table reports settings found in 6 sampled saved trial configurations, not an exhaustive audit of every attempt or direct proof of server settings. Historical runs and retries may differ. Sampling values are recorded explicitly rather than inferred from today's model-card defaults. Agent and verifier wall-clock budgets remain task-specific; sampled resolved limits are in settings and evidence. Context is not the sum of tokens across all turns. The current forwarding fix does not retroactively change these pass@k results.