LIVEdataset aec-bench@releasetasks 552models 18last submission … · built …
electricalwith-tool

Bandwidth Calculation

Calculates network bandwidth demand for an ITS device inventory by summing camera, controller, and sensor data rates. The reduced method applies a network overhead allowance and future capacity buffer to produce base, peak, and required bandwidth values.

with-tool: The model is given an executable Python calculator script.

Standards

IEEE 802.3NTCIP

Tags

bandwidthcommunicationsdeterministicelectricalitsnetwork

How this task is generated

One template produces many comparable benchmark tasks while keeping the scoring contract fixed.

  1. 01

    Template

    The reusable contract shown on this page.

  2. 02

    Scenario

    An archetype and site context are sampled.

  3. 03

    Difficulty tier

    Inputs may be hidden at harder tiers.

  4. 04

    Task prompt

    The model responds with the declared outputs.

Parameters

Inputs the model receives, and the outputs it is scored on.

Inputs

8 inputs

Always given

Included directly in every task prompt.

7
Show 7 inputs

  • Camera count

    camera_count

    Number of cameras

    0 – 200

  • Camera data rate

    camera_data_rate_mbps

    Data rate per camera

    0 – 50 Mbps

  • Controller count

    controller_count

    Number of controllers

    0 – 200

  • Controller data rate

    controller_data_rate_mbps

    Data rate per controller

    0 – 5 Mbps

  • Sensor count

    sensor_count

    Number of sensors

    0 – 1000

  • Sensor data rate

    sensor_data_rate_mbps

    Data rate per sensor

    0 – 5 Mbps

  • Network overhead pct

    network_overhead_pct

    Network protocol and peak overhead allowance

    0 – 50 %

Hidden at higher difficulty

Visible in easier tasks and withheld in one or more harder tiers.

1

  • Future capacity buffer pct

    future_capacity_buffer_pct

    Future capacity buffer

    Hidden at hard difficulty.

    0 – 100 %

Scored outputs

3 outputs

Base bandwidth mbps

base_bandwidth_mbps

Device bandwidth before allowances

Scores if within ±3% of the reference value.

Peak demand mbps

peak_demand_mbps

Bandwidth after network overhead

Scores if within ±3% of the reference value.

Required bandwidth mbps

required_bandwidth_mbps

Bandwidth after overhead and future buffer

Scores if within ±3% of the reference value.

Difficulty

Each template is sampled at three tiers. Harder tiers may hide inputs, forcing the model to infer them from the scenario description.

easy

All inputs given

Small node with all rates given

Network overhead pct restricted to: 15

Future capacity buffer pct restricted to: 25

medium

All inputs given

Mixed ITS device inventory

hard

Some inputs hidden

Future buffer hidden in corridor planning context

Hidden inputs

  • Future capacity buffer pctfuture_capacity_buffer_pct

Prompt replacement text

Use the future capacity buffer implied by {{ archetype.description }}.

Future capacity buffer pct restricted to: 25

Task bundle

The exact instruction and parameter contract used to generate this task, pinned to the published library source.

/workspace

  • instruction.md
  • bandwidth-calculation_calc.py

Teal lines show Jinja input conditions, not task visibility policy. A line renders only when that input or tool is visible.

1You are a senior ITS communications engineer sizing network bandwidth.2 3## Given4 5| Parameter | Value | Unit |6|-----------|-------|------|7| Cameras | {{ camera_count }} | count |8| Camera data rate | {{ camera_data_rate_mbps }} | Mbps each |9| Controllers | {{ controller_count }} | count |10| Controller data rate | {{ controller_data_rate_mbps }} | Mbps each |11| Sensors | {{ sensor_count }} | count |12| Sensor data rate | {{ sensor_data_rate_mbps }} | Mbps each |13| Network overhead | {{ network_overhead_pct }} | % |14{% if future_capacity_buffer_pct is defined %}15| Future capacity buffer | {{ future_capacity_buffer_pct }} | % |16{% endif %}17 18## Constraints19 20- Sum device count times data rate for base bandwidth.21- Apply network overhead to get peak demand.22- Apply future capacity buffer to peak demand.23 24## Output Format25 26Include a JSON block with exactly these keys:27 28```json29{30 "base_bandwidth_mbps": <numeric_value>,31 "peak_demand_mbps": <numeric_value>,32 "required_bandwidth_mbps": <numeric_value>33}34```35 36Write your complete solution to `/workspace/output.md`.37

Scenario archetypes

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.

Small intersection

small_intersection

Small signalised intersection communications node

urban-intersectionsuburban-corridor
Parameter ranges
camera_count
1 – 6
camera_data_rate_mbps
2 – 8
controller_count
1 – 4
controller_data_rate_mbps
0.05 – 0.5
sensor_count
2 – 20
sensor_data_rate_mbps
0.01 – 0.2

Corridor network

corridor_network

Road corridor ITS aggregation network

motorway-corridortunnel-approach
Parameter ranges
camera_count
10 – 80
camera_data_rate_mbps
2 – 12
controller_count
5 – 40
controller_data_rate_mbps
0.05 – 1
sensor_count
20 – 300
sensor_data_rate_mbps
0.01 – 0.5

Example task

motorway-corridor-corridor-network-preview — hard difficulty, some inputs hidden.

Road corridor ITS aggregation network. motorway-corridor. Required outputs: base_bandwidth_mbps, peak_demand_mbps, required_bandwidth_mbps

The model sees

Scenario context and visible inputs.

camera_count
10 to 80
camera_data_rate_mbps
2 to 12 Mbps
controller_count
5 to 40
controller_data_rate_mbps
0.05 to 1 Mbps
sensor_count
20 to 300
sensor_data_rate_mbps
0.01 to 0.5 Mbps
network_overhead_pct
0 to 50 %

Executable tool: bandwidth-calculation_calc.py

The model must infer

Inputs withheld at this difficulty.

  • Future capacity buffer pct

    future_capacity_buffer_pct

Stand-in text in the prompt

Use the future capacity buffer implied by {{ archetype.description }}.

The model must produce

The scored JSON answer schema.

{
  "base_bandwidth_mbps": <number>,
  "peak_demand_mbps": <number>,
  "required_bandwidth_mbps": <number>
}
  • base_bandwidth_mbps · scored within ±3%
  • peak_demand_mbps · scored within ±3%
  • required_bandwidth_mbps · scored within ±3%