Skip to content

Claude Sonnet 5.5 (effort default (no --effort flag) · thinking on) on Optimal single-machine job sequence (weighted tardiness with precedence)

AClaude Sonnet 5.5default · thinking on · Claude Code 2.1.299 (headless -p) · cloud · 2026-10-20 · by @bobsiopener

Trust 80%Fully autonomoussuccess · first try
Estimated cost
$0.06
Wall time
34s
Human step-ins
0
Outcome
Pass

Compare with other models on this task →

Summary

Exact prompt

# Optimal job sequence: minimum total weighted tardiness with precedence `input.json` (synthetic) has `start` (time the machine becomes free), `jobs` (`id`, processing time `p`, weight `w`, `due`) and `precedence` (pairs [a, b]: a must come before b, not necessarily directly). One machine, no idle time, no preemption. Write `solve.py` (Python 3 standard library only); `python solve.py input.json answer.json`. Find a sequence of all jobs that respects every precedence pair and **minimises** total weighted tardiness: sum of w * max(0, C - due), where C is the job's completion time (start + sum of p up to and including the job). Any optimal sequence is accepted. Fresh instances have **20 and 21 jobs**; each run has a 90-second limit. ## answer.json `{"sequence": [job ids in order], "total_weighted_tardiness": integer}` ## Scoring Hidden checks (partial credit; all must pass). A sequence is **valid** if it is a permutation of the job ids, respects every precedence pair, and the reported objective equals the scorer's recomputation for that sequence. It is **optimal** if that objective equals the true minimum (the scorer has the optimum). `fixture_valid_sequence`, `fixture_optimal` (given 18-job instance); `fresh_20_jobs_valid`, `fresh_20_jobs_optimal`; `fresh_21_jobs_optimal`.

Greedy rules (WSPT, EDD, swaps) give valid but suboptimal sequences; an exact method (subset dynamic programming or a tight branch and bound) is needed. Original benchmark task written for usecaserank.com (not based on a specific public post). Headless, offline run on a reproducible fixture. Each run's notes say how its cost was measured (estimates are marked).

Success criteria: 1. fixture_valid_sequence 2. fixture_optimal 3. fresh_20_jobs_valid 4. fresh_20_jobs_optimal 5. fresh_21_jobs_optimal

Setup notes: Use Case Scout batch 12 case m07-weighted-tardiness-optimal (offline, synthetic fixture). Prepared with batch12/prepare.sh; hidden key/checker kept outside the agent's work dir (temp dir during the run). Prompt = TASK.md verbatim. Scored with the case's scorer: `python score.py WORKDIR KEYDIR` (python3, run from the case dir). Tools: Read/Write/Edit/Glob/Grep/Bash, web disabled. Single run, no retries. 1-min load average at scoring 0.31 (8 cores). Claude Code's own reported cost for claude-sonnet-5.5: $0.056755. Score: 5/5. Cost is an ESTIMATE: measured tokens x pricing.json list price (Claude Pro subscription, nothing billed); input_tokens include cache reads and writes. Single run.

Estimated cost List-price estimate; not actually billed.

Metrics

Estimated cost
$0.06
Wall time
34s
Human step-ins
0
Turns
5
Model usage
ModelInput tokOutput tokCost
AClaude Sonnet 5.5anthropic/claude-sonnet-5.5effort default (no --effort flag) · thinking on97,2451,649$0.06

Reproduce this run

  1. Use the use case prompt on the use case page.
  2. Same setup: Claude Sonnet 5.5 (anthropic/claude-sonnet-5.5, effort default (no --effort flag) · thinking on) via Claude Code 2.1.299 (headless -p), cloud.
  3. It counts as a success only if it meets every success criterion: 1. fixture_valid_sequence 2. fixture_optimal 3. fresh_20_jobs_valid 4. fresh_20_jobs_optimal 5. fresh_21_jobs_optimal
  4. Log model, tokens, wall time, human step-ins and the evidence log, then submit it as a reproduction. A different model? Submit a head-to-head rerun.

How runs are scored: Methodology.

Was this useful?

⇄ Rerun on another model

Automated checks

Trust 80% comes from these checks (how Trust % works).

Evidence log
[
 {
  "duration_api_ms": 24373,
  "stop_reason": "end_turn",
  "session_id": "[REDACTED]",
  "total_cost_usd": 0.0567549,
  "usage": {
   "input_tokens": 10,
   "cache_creation_input_tokens": 7826,
   "cache_read_input_tokens": 89409,
   "output_tokens": 1649,
   "output_tokens_details": {
    "thinking_tokens": 325
   },
   "server_tool_use": {
    "web_search_requests": 0,
    "web_fetch_requests": 0
   },
   "service_tier": "standard",
   "cache_creation": {
    "ephemeral_1h_input_tokens": 7826,
    "ephemeral_5m_input_tokens": 0
   },
   "inference_geo": "global",
   "iterations": [
    {
     "input_tokens": 2,
     "output_tokens": 345,
     "cache_read_input_tokens": 19997,
     "cache_creation_input_tokens": 368,
     "cache_creation": {
      "ephemeral_5m_input_tokens": 0,
      "ephemeral_1h_input_tokens": 368
     },
     "type": "message"
    }
   ],
   "speed": "standard",
   "fallback_credit": null
  },
  "modelUsage": {
   "claude-sonnet-5-5": {
    "inputTokens": 10,
    "outputTokens": 1649,
    "cacheReadInputTokens": 89409,
    "cacheCreationInputTokens": 7826,
    "webSearchRequests": 0,
    "costUSD": 0.0567549,
    "contextWindow": 1000000,
    "maxOutputTokens": 128000,
    "thinkingTokens": 325,
    "canonicalModel": "claude-sonnet-5-5",
    "provider": "firstParty",
    "costBasis": "list"
   }
  },
  "permission_denials": [],
  "terminal_reason": "completed",
  "fast_mode_state": "off",
  "fast_mode_disabled_reason": "sdk_opt_in_required",
  "subagent_stats": {
   "spawned": 0,
   "requested": {
    "background": 0,
    "foreground": 0,
    "unset": 0
   },
   "started_in_background": 0,
   "max_depth": 0,
   "spawned_by_subagents": 0,
   "completed": 0,
   "failed": 0,
   "killed": {
    "parent": 0,
    "user": 0,
    "system": 0
   },
   "refused": {
    "depth_limit": 0,
    "concurrency_limit": 0,
    "budget": 0
   },
   "by_type": {}
  },
  "safety_stops": 0,
  "is_error": false,
  "num_turns": 5,
  "subtype": "success",
  "api_error_status": null,
  "result": "`solve.py` is written. It uses an exact dynamic program over sets of jobs that satisfy the precedence pairs, so it returns a true optimum. I checked it only on the 18-job fixture and one stress test, not on the hidden 20- and 21-job instances.\n\n- **Fixture:** on the 18-job `input.json` it ran in 0.3 seconds. It found a sequence with total weighted tardiness 462. I did not check that sequence against the precedence pairs or the objective with a separate script. I also don't know whether 462 is the true minimum, since I don't have the scorer's value.\n- **Stress test:** I added 3 random jobs to the fixture and removed all precedence pairs. That made a 21-job instance with the largest possible search space, and it took about 8 seconds, well inside the 90-second limit.\n\nRun it with `python3 solve.py input.json answer.json`. The sandbox has no `python` command, only `python3`.\n\nI did not save the stress-test file anywhere in the working directory. `answer.json` there is the fixture's output.",
  "ttft_ms": 2077,
  "type": "result",
  "duration_ms": 33575,
  "uuid": "[REDACTED]",
  "ttft_stream_ms": 1888,
  "time_to_request_ms": 329,
  "first_content_frame_ms": 1888,
  "queued_turn_count": 0,
  "result_index": 0
 }
]

Get new runs and ranking changes weekly