Pedestrian clearance time s
pedestrian_clearance_time_s
Temporary pedestrian clearance time
Scores if within ±3% of the reference value.
Calculates source-bound temporary pedestrian timing, VMS legibility, staged ITS network load, PoE headroom, battery backup, and detour delay metrics from a deterministic SSC-16 task-owned source pack.
with-tool: The model is given an executable Python calculator script.
One template produces many comparable benchmark tasks while keeping the scoring contract fixed.
01
The reusable contract shown on this page.
02
An archetype and site context are sampled.
03
Inputs may be hidden at harder tiers.
04
The model responds with the declared outputs.
Inputs the model receives, and the outputs it is scored on.
24 inputs
Included directly in every task prompt.
Crossing width
crossing_width_m
SIGNAL-16-TIMING-04 temporary pedestrian crossing width
Pedestrian walk speed
pedestrian_walk_speed_m_s
SIGNAL-16-TIMING-04 pedestrian walk speed
Pedestrian startup time
pedestrian_startup_time_s
SIGNAL-16-TIMING-04 startup allowance
Provided ped clearance
provided_ped_clearance_s
SIGNAL-16-TIMING-04 provided clearance interval
Vms character height
vms_character_height_mm
DEVICE-16-RELOC-04 VMS character height
Vms legibility factor m per mm
vms_legibility_factor_m_per_mm
DEVICE-16-RELOC-04 source-owned legibility factor
Available vms viewing distance
available_vms_viewing_distance_m
TTC-16-PLAN-04 available VMS viewing distance
Signal controller data
signal_controller_data_mbps
NET-16-TOPO-04 signal controller data load
Vms data
vms_data_mbps
NET-16-TOPO-04 VMS data load
Cctv data
cctv_data_mbps
NET-16-TOPO-04 CCTV data load
Detector data
detector_data_mbps
NET-16-TOPO-04 detector data load
Gateway overhead
gateway_overhead_mbps
NET-16-TOPO-04 gateway overhead
Network capacity
network_capacity_mbps
NET-16-TOPO-04 staged network capacity
Cctv poe
cctv_poe_w
POWER-16-SCHED-04 CCTV PoE load
Detector poe
detector_poe_w
POWER-16-SCHED-04 detector PoE load
Router poe
router_poe_w
POWER-16-SCHED-04 router PoE load
Vms modem poe
vms_modem_poe_w
POWER-16-SCHED-04 VMS modem PoE load
Poe budget
poe_budget_w
POWER-16-SCHED-04 PoE budget
Signal controller load
signal_controller_load_w
POWER-16-SCHED-04 signal controller power load
Vms power load
vms_power_load_w
POWER-16-SCHED-04 VMS power load
Battery backup hours
battery_backup_hours
POWER-16-SCHED-04 battery backup duration
Provided battery
provided_battery_kwh
POWER-16-SCHED-04 provided battery energy
Allowable detour delay
allowable_detour_delay_s
TTC-16-PLAN-04 allowable detour delay
Estimated detour delay
estimated_detour_delay_s
TTC-16-PLAN-04 estimated detour delay
12 outputs
pedestrian_clearance_time_s
Temporary pedestrian clearance time
Scores if within ±3% of the reference value.
pedestrian_clearance_margin_s
Provided clearance minus required clearance
Scores if within ±3% of the reference value.
required_vms_legibility_distance_m
Required VMS legibility distance
Scores if within ±3% of the reference value.
vms_legibility_margin_m
Available viewing distance minus required legibility distance
Scores if within ±3% of the reference value.
network_load_mbps
Total staged ITS network load
Scores if within ±3% of the reference value.
network_headroom_mbps
Network capacity minus load
Scores if within ±3% of the reference value.
poe_load_w
Total staged PoE load
Scores if within ±3% of the reference value.
poe_headroom_w
PoE budget minus staged load
Scores if within ±3% of the reference value.
battery_required_kwh
Battery energy required for staged ITS backup
Scores if within ±3% of the reference value.
battery_margin_kwh
Provided battery energy minus required battery energy
Scores if within ±3% of the reference value.
detour_delay_margin_s
Allowable detour delay minus estimated delay
Scores if within ±3% of the reference value.
overall_pass_score
1.0 when timing, VMS, network, PoE, battery, and delay checks pass
Scores if within ±0.1% of the reference value.
Each template is sampled at three tiers. Harder tiers may hide inputs, forcing the model to infer them from the scenario description.
For this template, difficulty scales through parameter and scenario ranges rather than hidden information.
The exact instruction and parameter contract used to generate this task, pinned to the published library source.
/workspace
Teal lines show Jinja input conditions, not task visibility policy. A line renders only when that input or tool is visible.
1You are a staged road and ITS engineer checking a task-owned synthetic SSC-16 package for temporary signals, VMS, CCTV, communications, power, and detour operation during construction.2 3Use only the task-owned synthetic source pack values shown below for numeric grading. External MUTCD, ITS, NTCIP, work-zone traffic, and temporary services workflows shape the context only; they are not extra data sources for this instance.4 5## Source Objects6 7- Product: `SSC-16-LH-04`8- Temporary traffic plan: `TTC-16-PLAN-04`9- Device relocation schedule: `DEVICE-16-RELOC-04`10- Signal timing sheet: `SIGNAL-16-TIMING-04`11- Network topology: `NET-16-TOPO-04`12- Power schedule: `POWER-16-SCHED-04`13- Stage operations memo: `MEMO-16-STAGEOPS-04`14 15## Source Values16 17| Item | Value |18|------|-------|19| Crossing width | {{ crossing_width_m }} m |20| Pedestrian walk speed | {{ pedestrian_walk_speed_m_s }} m/s |21| Pedestrian startup time | {{ pedestrian_startup_time_s }} s |22| Provided pedestrian clearance | {{ provided_ped_clearance_s }} s |23| VMS character height | {{ vms_character_height_mm }} mm |24| VMS legibility factor | {{ vms_legibility_factor_m_per_mm }} m/mm |25| Available VMS viewing distance | {{ available_vms_viewing_distance_m }} m |26| Signal controller data | {{ signal_controller_data_mbps }} Mbps |27| VMS data | {{ vms_data_mbps }} Mbps |28| CCTV data | {{ cctv_data_mbps }} Mbps |29| Detector data | {{ detector_data_mbps }} Mbps |30| Gateway overhead | {{ gateway_overhead_mbps }} Mbps |31| Network capacity | {{ network_capacity_mbps }} Mbps |32| CCTV PoE load | {{ cctv_poe_w }} W |33| Detector PoE load | {{ detector_poe_w }} W |34| Router PoE load | {{ router_poe_w }} W |35| VMS modem PoE load | {{ vms_modem_poe_w }} W |36| PoE budget | {{ poe_budget_w }} W |37| Signal controller load | {{ signal_controller_load_w }} W |38| VMS power load | {{ vms_power_load_w }} W |39| Battery backup duration | {{ battery_backup_hours }} h |40| Provided battery energy | {{ provided_battery_kwh }} kWh |41| Allowable detour delay | {{ allowable_detour_delay_s }} s |42| Estimated detour delay | {{ estimated_detour_delay_s }} s |43 44## Required Checks45 46- Pedestrian clearance time equals crossing width divided by walk speed plus startup time.47- VMS legibility distance equals character height times the source-owned legibility factor.48- Network and PoE loads are sums of the staged device schedule.49- Battery energy covers signal controller, VMS, and PoE load over the backup duration.50- Detour delay margin is allowable delay minus estimated delay.51 52## Output Format53 54Write a compact memo to `/workspace/output.md`. Include a source-boundary statement that this is a task-owned synthetic source pack, preserve the source object IDs above, and state whether the baseline checks pass.55 56Do not claim authority approval, accepted project evidence, software export validity, full standards compliance, executable source-pack hardening, generated benchmark readiness, or benchmark readiness.57 58Include a fenced JSON block with exactly these numeric keys:59 60```json61{62 "pedestrian_clearance_time_s": <numeric_value>,63 "pedestrian_clearance_margin_s": <numeric_value>,64 "required_vms_legibility_distance_m": <numeric_value>,65 "vms_legibility_margin_m": <numeric_value>,66 "network_load_mbps": <numeric_value>,67 "network_headroom_mbps": <numeric_value>,68 "poe_load_w": <numeric_value>,69 "poe_headroom_w": <numeric_value>,70 "battery_required_kwh": <numeric_value>,71 "battery_margin_kwh": <numeric_value>,72 "detour_delay_margin_s": <numeric_value>,73 "overall_pass_score": <numeric_value>74}75```76 Each generated task is drawn from one of these realistic scenario bands.
Site contexts ground each scenario in a real locale the model can use to infer hidden values.
ssc16_staged_its_case
Staged road and ITS relocation case
ssc16-staged-its-case-preview — hard difficulty, all inputs given.
Staged road and ITS relocation case. Required outputs: pedestrian_clearance_time_s, pedestrian_clearance_margin_s, required_vms_legibility_distance_m, vms_legibility_margin_m, network_load_mbps, network_headroom_mbps
Scenario context and visible inputs.
Executable tool: staged-road-its-relocation-package_calc.py
Inputs withheld at this difficulty.
Nothing. All inputs are supplied.
The scored JSON answer schema.
{
"pedestrian_clearance_time_s": <number>,
"pedestrian_clearance_margin_s": <number>,
"required_vms_legibility_distance_m": <number>,
"vms_legibility_margin_m": <number>,
"network_load_mbps": <number>,
"network_headroom_mbps": <number>,
"poe_load_w": <number>,
"poe_headroom_w": <number>,
"battery_required_kwh": <number>,
"battery_margin_kwh": <number>,
"detour_delay_margin_s": <number>,
"overall_pass_score": <number>
}