Stopping distance
stopping_distance_m
Grade-adjusted stopping distance
Scores if within ±3% of the reference value.
Calculates task-owned synthetic SSC-01 metrics for one intersection approach, including grade-adjusted stopping distance, sight-distance margin, yellow interval, all-red interval, and pedestrian clearance.
with-tool: The model is given an executable Python calculator script.
Standards
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.
14 inputs
Included directly in every task prompt.
Approach speed kmh
approach_speed_kmh
SIG-SSC01-002 approach design speed
Approach grade pct
approach_grade_pct
PROF-SSC01-002 signed approach grade; downhill is negative
Reaction time
reaction_time_s
MEMO-SSC01-002 stopping sight-distance reaction time
Braking friction coefficient
braking_friction_coefficient
MEMO-SSC01-002 braking friction coefficient
Available sight distance
available_sight_distance_m
INT-SSC01-002 available approach sight distance
Yellow reaction time
yellow_reaction_time_s
SIG-SSC01-002 yellow interval perception-reaction term
Yellow deceleration
yellow_deceleration_m_s2
SIG-SSC01-002 comfortable deceleration rate for yellow timing
Intersection width
intersection_width_m
INT-SSC01-002 conflict area width
Design vehicle length
design_vehicle_length_m
MEMO-SSC01-002 design vehicle length
All red speed kmh
all_red_speed_kmh
SIG-SSC01-002 clearance speed for all-red interval
Pedestrian startup time
pedestrian_startup_time_s
PED-SSC01-002 startup allowance
Crossing width
crossing_width_m
PED-SSC01-002 crossing width
Pedestrian walk speed
pedestrian_walk_speed_m_s
PED-SSC01-002 pedestrian walk speed
Pedestrian clearance available
pedestrian_clearance_available_s
SIG-SSC01-002 available pedestrian clearance interval
8 outputs
stopping_distance_m
Grade-adjusted stopping distance
Scores if within ±3% of the reference value.
sight_distance_margin_m
Available sight distance minus stopping distance
Scores if within ±3% of the reference value.
yellow_interval_s
Grade-adjusted yellow interval
Scores if within ±3% of the reference value.
all_red_interval_s
Intersection all-red clearance interval
Scores if within ±3% of the reference value.
ped_clearance_required_s
Required pedestrian clearance interval
Scores if within ±3% of the reference value.
ped_clearance_margin_s
Available pedestrian clearance minus required clearance
Scores if within ±3% of the reference value.
grade_adjusted_braking_distance_m
Braking distance component of stopping distance
Scores if within ±3% of the reference value.
overall_pass_score
1.0 when the synthetic sight-distance and clearance checks pass
Scores if within ±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 traffic-safety engineer checking a task-owned synthetic SSC-01 intersection timing, grade, and sight-distance package.2 3Use only the task-owned synthetic source pack values below for numeric grading. MUTCD and AASHTO-style timing and sight-distance workflows shape the context only; they are not extra data sources for this instance.4 5## Scene6 7- Product: `SSC-01-LH-02`8- Intersection plan: `INT-SSC01-002`9- Vertical profile: `PROF-SSC01-002`10- Signal timing sheet: `SIG-SSC01-002`11- Pedestrian crossing case: `PED-SSC01-002`12- Safety memo: `MEMO-SSC01-002`13- Approach: `NB-APPROACH-02`14 15## Source Values16 17| Item | Value |18| --- | --- |19| Approach speed | {{ approach_speed_kmh }} km/h |20| Approach grade | {{ approach_grade_pct }} % |21| Reaction time | {{ reaction_time_s }} s |22| Braking friction coefficient | {{ braking_friction_coefficient }} |23| Available sight distance | {{ available_sight_distance_m }} m |24| Yellow reaction time | {{ yellow_reaction_time_s }} s |25| Yellow deceleration | {{ yellow_deceleration_m_s2 }} m/s2 |26| Intersection width | {{ intersection_width_m }} m |27| Design vehicle length | {{ design_vehicle_length_m }} m |28| All-red speed | {{ all_red_speed_kmh }} km/h |29| Pedestrian startup time | {{ pedestrian_startup_time_s }} s |30| Crossing width | {{ crossing_width_m }} m |31| Pedestrian walk speed | {{ pedestrian_walk_speed_m_s }} m/s |32| Available pedestrian clearance | {{ pedestrian_clearance_available_s }} s |33 34## Required Calculations35 36- Convert speeds from km/h to m/s.37- Use grade as a signed decimal in the stopping-distance and yellow-interval checks.38- Braking distance is `v^2 / (2 x g x (friction + grade))`.39- Stopping distance is reaction distance plus braking distance.40- Sight-distance margin is available sight distance minus stopping distance.41- Yellow interval is `reaction + v / (2 x deceleration + 2 x g x grade)`.42- All-red interval is `(intersection width + vehicle length) / all-red speed`.43- Pedestrian clearance required is startup time plus crossing width divided by walk speed.44- Overall pass score is `1.0` only when sight distance and pedestrian clearance margins are non-negative.45 46Write a compact memo to `/workspace/output.md`. Include a source-boundary statement that this is a task-owned synthetic source pack. Preserve the source IDs above and state that the baseline source pack passes the current synthetic checks.47 48Do not claim authority approval, accepted project evidence, software export validity, full standards compliance, executable source-pack hardening, generated benchmark readiness, or benchmark readiness.49 50Include a fenced JSON block with exactly these numeric keys:51 52```json53{54 "stopping_distance_m": <numeric_value>,55 "sight_distance_margin_m": <numeric_value>,56 "yellow_interval_s": <numeric_value>,57 "all_red_interval_s": <numeric_value>,58 "ped_clearance_required_s": <numeric_value>,59 "ped_clearance_margin_s": <numeric_value>,60 "grade_adjusted_braking_distance_m": <numeric_value>,61 "overall_pass_score": <numeric_value>62}63```64 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.
ssc01_intersection_timing
SSC-01 task-owned synthetic intersection timing and sight-distance package
intersection-approach-grade-signal-clearance-ssc01-intersection-timing-preview — hard difficulty, all inputs given.
SSC-01 task-owned synthetic intersection timing and sight-distance package. intersection-approach-grade-signal-clearance. Required outputs: stopping_distance_m, sight_distance_margin_m, yellow_interval_s, all_red_interval_s, ped_clearance_required_s, ped_clearance_margin_s
Scenario context and visible inputs.
Executable tool: intersection-timing-grade-sight-distance-package_calc.py
Inputs withheld at this difficulty.
Nothing. All inputs are supplied.
The scored JSON answer schema.
{
"stopping_distance_m": <number>,
"sight_distance_margin_m": <number>,
"yellow_interval_s": <number>,
"all_red_interval_s": <number>,
"ped_clearance_required_s": <number>,
"ped_clearance_margin_s": <number>,
"grade_adjusted_braking_distance_m": <number>,
"overall_pass_score": <number>
}