{"claim":{"id":"eea6380c-fe86-471a-bef1-c6512b03e29d","submission_id":"73c2a3d3-02b9-4bb4-ad89-cf393e5a16e2","submission_revision_id":"41820a5b-aa0c-469a-bfea-6b6aa2b701b2","builder":"builder-01","status":"active","claimed_at":"2026-10-15T15:24:36.575986Z","delivered_at":null,"ended_at":null,"delivery_note":null,"end_reason":null},"task":{"submission_id":"73c2a3d3-02b9-4bb4-ad89-cf393e5a16e2","submission_revision_id":"41820a5b-aa0c-469a-bfea-6b6aa2b701b2","revision_version":1,"submission_status":"under_review","submitted_at":"2026-09-07T06:27:45.608177Z","submitter_name":"Yufan Zhang","submitter_email":"yufanz@umd.edu","task":{"status":"submitted","version":1,"extra_fields":{"difficulty_self_test":{"estimated_score":"<1%"}},"submitted_at":"2026-09-07T06:27:45.608177+00:00","industry_domain":"Transportation Engineering","task_short_name":"sumo_ale_bus_priority_1","operating_system":"Linux","task_description":"Objective:\nDesign a robust transit signal priority policy for two bus routes operating along a congested seven-intersection urban arterial. Reduce bus schedule delay and bus travel-time variability while protecting general traffic, side streets, traffic-signal safety, and network throughput.\n\nStarting State:\nThe input package contains a SUMO 1.26.0 model of a 2.4 km arterial corridor with seven signalized intersections (J0–J6), two arterial lanes in each direction, side streets, two bus lines, eight bus stops, 16 scheduled bus trips, stochastic bus dwell times, and 8,554 regular vehicles during the visible morning-peak scenario. A valid no-priority starter policy and the required JSON schema are provided in public/solution.json and public/solution.schema.json.\n\nInstructions & Rules:\nModify only public/solution.json. Configure the bus lateness threshold, request detection distance, green-extension duration, early-green duration, priority-request duration, and the intersections at which transit priority is enabled. All submitted values must satisfy the ranges and types specified in the schema.\n\nThe policy must not modify the road network, traffic demand, bus routes, bus departures, dwell times, timetables, stops, vehicle types, signal phase states, simulation period, or evaluator. Buses and regular vehicles may not be removed, delayed, or otherwise manipulated to improve the result.\n\nEvery evaluated scenario must keep general-traffic mean time loss within 110% of its corresponding no-priority baseline, keep the maximum side-street queue at or below 180 m, maintain baseline throughput, produce zero teleports, preserve at least 19 seconds of minimum green, and leave all yellow and all-red clearance intervals unchanged.\n\nFinal evaluation includes one visible scenario and four private scenarios containing undisclosed bus-lateness, dwell-time, traffic-demand, and bus-headway disturbances. Traffic-demand perturbations may be up to 15%.\n\nDeliverable:\nSubmit the completed public/solution.json file. The policy will be executed by a private server-side SUMO and TraCI evaluator and assigned a continuous score from 0 to 100.","software_licensing":"Free/Open Source","evaluation_criteria":null,"verification_method":"Evaluate the submitted policy by deterministic simulated performance rather than exact equality with the reference JSON.\n\n1. Validate the submission\n\nThe submitted public/solution.json must parse successfully and contain exactly the required schema_version, eligibility, priority, and J0–J6 intersection fields. Additional or missing fields are invalid.\n\nRequire:\n- lateness_threshold_s: integer from 0 to 300\n- request_distance_m: integer from 50 to 250\n- green_extension_s: integer from 0 to 15\n- early_green_s: integer from 0 to 12\n- priority_duration_s: integer from 5 to 30\n- J0 through J6: Boolean values\n\nConfirm that all fixed network, demand, bus, stop, timetable, detector, configuration, and signal-clearance inputs remain unchanged.\n\n2. Run the evaluation\n\nRun the submission using SUMO 1.26.0 and the fixed TraCI transit-priority controller on the visible scenario and four private scenarios. Identical inputs and submissions must produce identical results.\n\nFor each scenario, calculate:\n\ntransit_objective =\n    bus_mean_delay_s\n  + 250 * bus_travel_time_cv\n\nLower values are better.\n\n3. Enforce hard constraints\n\nEvery scenario must independently satisfy:\n\n- general_traffic_mean_time_loss_s <= 1.10 times that scenario’s no-priority value\n- max_side_street_queue_m <= 180\n- throughput >= that scenario’s no-priority throughput\n- teleports = 0\n- minimum green >= 19 seconds\n- yellow and all-red clearance intervals unchanged\n\nIf any scenario violates any hard constraint, the final score is 0.\n\n4. Combine scenarios\n\nUse a weight of 0.40 for the visible scenario and 0.15 for each of the four private scenarios:\n\nsubmission_weighted_objective =\n    0.40 * visible_objective\n  + 0.15 * hidden_objective_1\n  + 0.15 * hidden_objective_2\n  + 0.15 * hidden_objective_3\n  + 0.15 * hidden_objective_4\n\n5. Calculate the final score\n\nFor a valid and feasible submission, calculate:\n\nscore = 100 * (245.729950 - submission_weighted_objective)\n              / (245.729950 - 171.475937)\n\nRound the result to three decimal places and clip it to the range [0, 100].\n\nThe fixed no-priority policy anchors a score of 0. The expert reference, with a weighted objective of 171.475937, anchors a score of 100. Intermediate feasible performance receives a proportional intermediate score.\n\nInvalid JSON, modified fixed inputs, failed simulation, missing or non-finite metrics, or any hard-constraint violation receives 0. If multiple submissions reach the 100-point cap, use the lower raw weighted objective as the tie-breaker.","software_and_version":"Eclipse SUMO 1.26.0, Python 3.11.16, TraCI 1.26.0, sumolib 1.26.0","specific_requirements":null,"expected_completion_time":null},"files":[{"file_id":"3a324466-e5d9-440f-9c64-9d3de9b32c22","filename":"sumo_robust_transit_signal_priority_1_input.zip","category":"input_materials","content_type":"application/zip","size_bytes":68222},{"file_id":"49b4ce94-1c76-49f7-8f89-0f2d6e197cac","filename":"sumo_robust_transit_signal_priority_1_reference.zip","category":"reference_output","content_type":"application/zip","size_bytes":306495}],"deep_review":{"overall_verdict":"Accept","review_text":"**Overall Verdict:** Accept — The task is complete, objectively evaluable, and end-to-end reachable, with only a negligible evaluator-semantic refinement remaining.\n\n**Completeness Check:**\n- Instruction: Complete — The objective, permitted decision variables, immutable artifacts, constraints, and deliverable are explicit and internally consistent.\n- Inputs: Complete — The public package contains the SUMO network, visible demand, bus schedules, stops, detectors, configuration, starter policy, task instructions, and strict JSON schema.\n- Toolchain: Complete — A Linux-compatible, version-pinned Python 3.11 and SUMO 1.26.0 environment is defined with a lockfile and environment checks using legally obtainable open-source software.\n- Reference output: Complete — The protected package contains the expert policy, four distinct hidden scenarios, no-control and expert reports, verification guidance, and evaluator implementation.\n- Rubric: Complete — Validation, per-scenario objectives, hard constraints, scenario weights, normalization anchors, rounding, clipping, failure handling, and tie-breaking are specified.\n\n**File and Task Reachability:**\nThe attachment classification is `reachable`, and the end-to-end task classification is `reachable`. Both `sumo_robust_transit_signal_priority_1_input.zip` and `sumo_robust_transit_signal_priority_1_reference.zip` were inspected. Their actual ZIP formats and byte counts match the manifest; both test cleanly and contain no encrypted members, traversal paths, links, device entries, or excessive expansion. Every member was inventoried. JSON documents parsed successfully; evaluator and environment source files were read without execution; XML files were inspected structurally and representatively. Independent XML XSD validation was unavailable in the review environment, but the files are readable SUMO XML, internal counts and references are consistent, duplicate fixed artifacts match byte-for-byte, and every embedded authoritative SHA-256 value matches its artifact. The visible and hidden demand counts, 16 buses per scenario, eight declared stops, seven signal programs, schedule metadata, route references, baseline metrics, expert metrics, weighted objectives, and score arithmetic are mutually consistent. No attachment content was omitted from review, although the thousands of repetitive vehicle records were assessed structurally rather than line by line. Solver-visible inputs are separated from the protected expert policy, hidden scenarios, baselines, and evaluator. A contributor can edit only `public/solution.json`; the private evaluator validates it, verifies immutable inputs, runs five deterministic simulations, enforces feasibility, and computes the continuous score. License keys, accounts, tokens, and other credentials are not required from the contributor. Confidential, proprietary, or internal material may be evaluated as submitted evidence without requiring additional disclosure.\n\n**Special Screening:**\nNone. Public-benchmark identifiability was not independently checked because external search is outside the permitted evidence boundary; the supplied evidence does not affirmatively support any screening label.\n\n**Recommended Changes:**\nThe task and evidence package are ready; no material changes are required. As an optional refinement, make `priority_duration_s` independently affect control eligibility after detection or remove it from the decision space. The current controller requires a live bus observation on every action step, so the configured hold interval does not materially persist a request once that observation disappears.","reviewed_at":"2026-09-07T06:36:27.360400Z"},"claim":{"id":"eea6380c-fe86-471a-bef1-c6512b03e29d","submission_id":"73c2a3d3-02b9-4bb4-ad89-cf393e5a16e2","submission_revision_id":"41820a5b-aa0c-469a-bfea-6b6aa2b701b2","builder":"builder-01","status":"active","claimed_at":"2026-10-15T15:24:36.575986Z","delivered_at":null,"ended_at":null,"delivery_note":null,"end_reason":null}},"revision_is_current":true}