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

Station Building Security Lighting Package

Calculates source-bound security lighting metrics from a deterministic SSC-13 task-owned source pack. The template combines a floor plan, lighting grid, CCTV schedule, access-control schedule, network topology, and PoE budget.

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

Standards

CCTV coverage workflowPoE budget reviewaccess-control schedule reviewlighting calculation workflow

Tags

access-controlcctvdeterministicelectricallightingnetworkpoesecurity

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

22 inputs

Always given

Included directly in every task prompt.

22
Show 22 inputs

  • Grid lux 01

    grid_lux_01

    LIGHT-13-GRID-02 grid point 01

    210 lux

  • Grid lux 02

    grid_lux_02

    LIGHT-13-GRID-02 grid point 02

    205 lux

  • Grid lux 03

    grid_lux_03

    LIGHT-13-GRID-02 grid point 03

    198 lux

  • Grid lux 04

    grid_lux_04

    LIGHT-13-GRID-02 grid point 04

    215 lux

  • Grid lux 05

    grid_lux_05

    LIGHT-13-GRID-02 grid point 05

    202 lux

  • Grid lux 06

    grid_lux_06

    LIGHT-13-GRID-02 grid point 06

    196 lux

  • Required illuminance

    required_illuminance_lux

    MEMO-13-SECURITY-02 required maintained illuminance

    160 lux

  • Cctv horizontal pixels

    cctv_horizontal_pixels

    CCTV-13-CAM-02 horizontal pixel count

    1920 px

  • Cctv target width

    cctv_target_width_m

    PLAN-13-ROOM-02 target-zone width

    12 m

  • Required ppm

    required_ppm

    MEMO-13-SECURITY-02 required pixels per metre

    120

  • Camera

    camera_count

    CCTV-13-CAM-02 camera count

    4 count

  • Camera network

    camera_network_mbps

    NET-13-TOPO-02 network load per camera

    5 Mbps

  • Access network

    access_network_mbps

    ACCESS-13-CTRL-02 access network load

    1.5 Mbps

  • Lighting control network

    lighting_control_network_mbps

    LIGHT-13-GRID-02 lighting controller network load

    0.5 Mbps

  • Network overhead factor

    network_overhead_factor

    NET-13-TOPO-02 network overhead factor

    1.15

  • Uplink capacity

    uplink_capacity_mbps

    NET-13-TOPO-02 uplink capacity

    50 Mbps

  • Camera poe

    camera_poe_w

    CCTV-13-CAM-02 PoE load per camera

    12.5 W

  • Access controller

    access_controller_count

    ACCESS-13-CTRL-02 controller count

    3 count

  • Access controller poe

    access_controller_poe_w

    ACCESS-13-CTRL-02 PoE load per controller

    8 W

  • Poe budget

    poe_budget_w

    NET-13-TOPO-02 PoE switch budget

    120 W

  • Matched coverage zones

    matched_coverage_zones

    MEMO-13-SECURITY-02 matched coverage zones

    6 count

  • Required coverage zones

    required_coverage_zones

    MEMO-13-SECURITY-02 required coverage zones

    6 count

Scored outputs

12 outputs

Average illuminance lux

average_illuminance_lux

Average illuminance across the station/security grid

Scores if within ±0.3% of the reference value.

Minimum illuminance lux

minimum_illuminance_lux

Minimum illuminance across the station/security grid

Scores if within ±0.3% of the reference value.

Uniformity ratio

uniformity_ratio

Minimum illuminance divided by average illuminance

Scores if within ±0.3% of the reference value.

Illuminance margin lux

illuminance_margin_lux

Average illuminance minus required illuminance

Scores if within ±0.3% of the reference value.

Cctv pixels per

cctv_pixels_per_m

CCTV pixels per metre

Scores if within ±0.3% of the reference value.

Cctv ppm margin

cctv_ppm_margin

CCTV PPM minus required PPM

Scores if within ±0.3% of the reference value.

Network load mbps

network_load_mbps

Network load including overhead

Scores if within ±0.3% of the reference value.

Network headroom mbps

network_headroom_mbps

Uplink capacity minus network load

Scores if within ±0.3% of the reference value.

Poe load w

poe_load_w

Total camera and access-control PoE load

Scores if within ±0.3% of the reference value.

Poe headroom w

poe_headroom_w

PoE budget minus load

Scores if within ±0.3% of the reference value.

Coverage match fraction

coverage_match_fraction

Matched coverage zones divided by required zones

Scores if within ±0.3% of the reference value.

Overall pass score

overall_pass_score

1.0 when lighting, CCTV, network, PoE, and coverage checks pass

Scores if within ±0.1% 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.

All inputs remain visible at every tier

For this template, difficulty scales through parameter and scenario ranges rather than hidden information.

easy:
All source-pack values given for the SSC-13 station security package
medium:
All source-pack values given for the SSC-13 station security package
hard:
All source-pack values given for the SSC-13 station security package

Task bundle

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

/workspace

  • instruction.md
  • station-building-security-lighting-package_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 an electrical security and lighting reviewer checking a task-owned synthetic SSC-13 station/building package.2 3Use only the task-owned synthetic source pack values shown below for numeric grading. External lighting, CCTV, access-control, and network tools shape the workflow context only; they are not extra data sources for this instance.4 5## Scene6 7- Product: `SSC-13-LH-02`8- Floor plan: `PLAN-13-ROOM-02`9- Lighting grid: `LIGHT-13-GRID-02`10- CCTV schedule: `CCTV-13-CAM-02`11- Access-control schedule: `ACCESS-13-CTRL-02`12- Network topology: `NET-13-TOPO-02`13- Security operations memo: `MEMO-13-SECURITY-02`14 15All checks use the same floor/room scene, lighting grid, camera coverage, access devices, and network topology. Do not change device IDs, room geometry, or coverage zones unless you explicitly flag a source conflict.16 17## Source Values18 19| Item | Value |20|------|-------|21| Lighting grid lux values | {{ grid_lux_01 }}, {{ grid_lux_02 }}, {{ grid_lux_03 }}, {{ grid_lux_04 }}, {{ grid_lux_05 }}, {{ grid_lux_06 }} |22| Required illuminance | {{ required_illuminance_lux }} lux |23| CCTV horizontal pixels | {{ cctv_horizontal_pixels }} px |24| CCTV target width | {{ cctv_target_width_m }} m |25| Required PPM | {{ required_ppm }} |26| Camera count | {{ camera_count }} |27| Camera network load | {{ camera_network_mbps }} Mbps each |28| Access network load | {{ access_network_mbps }} Mbps |29| Lighting controller network load | {{ lighting_control_network_mbps }} Mbps |30| Network overhead factor | {{ network_overhead_factor }} |31| Uplink capacity | {{ uplink_capacity_mbps }} Mbps |32| Camera PoE load | {{ camera_poe_w }} W each |33| Access controller count | {{ access_controller_count }} |34| Access controller PoE load | {{ access_controller_poe_w }} W each |35| PoE budget | {{ poe_budget_w }} W |36| Matched coverage zones | {{ matched_coverage_zones }} of {{ required_coverage_zones }} |37 38## Output Format39 40Write a compact security operations memo to `/workspace/output.md`. Include a source-boundary statement that this is a task-owned synthetic source pack. Do not claim authority approval, accepted project evidence, software export validity, full standards compliance, executable real source-pack parsing, generated benchmark readiness, or benchmark readiness.41 42Include a fenced JSON block with exactly these numeric keys:43 44```json45{46 "average_illuminance_lux": <numeric_value>,47 "minimum_illuminance_lux": <numeric_value>,48 "uniformity_ratio": <numeric_value>,49 "illuminance_margin_lux": <numeric_value>,50 "cctv_pixels_per_m": <numeric_value>,51 "cctv_ppm_margin": <numeric_value>,52 "network_load_mbps": <numeric_value>,53 "network_headroom_mbps": <numeric_value>,54 "poe_load_w": <numeric_value>,55 "poe_headroom_w": <numeric_value>,56 "coverage_match_fraction": <numeric_value>,57 "overall_pass_score": <numeric_value>58}59```60

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.

Ssc13 station security case

ssc13_station_security_case

Station/building security lighting case

ssc13-station-security
Parameter ranges

Example task

ssc13-station-security-ssc13-station-security-case-preview — hard difficulty, all inputs given.

Station/building security lighting case. ssc13-station-security. Required outputs: average_illuminance_lux, minimum_illuminance_lux, uniformity_ratio, illuminance_margin_lux, cctv_pixels_per_m, cctv_ppm_margin

The model sees

Scenario context and visible inputs.

grid_lux_01
210 to 210 lux
grid_lux_02
205 to 205 lux
grid_lux_03
198 to 198 lux
grid_lux_04
215 to 215 lux
grid_lux_05
202 to 202 lux
grid_lux_06
196 to 196 lux
required_illuminance_lux
160 to 160 lux
cctv_horizontal_pixels
1920 to 1920 px
cctv_target_width_m
12 to 12 m
required_ppm
120 to 120
camera_count
4 to 4 count
camera_network_mbps
5 to 5 Mbps
access_network_mbps
1.5 to 1.5 Mbps
lighting_control_network_mbps
0.5 to 0.5 Mbps
network_overhead_factor
1.15 to 1.15
uplink_capacity_mbps
50 to 50 Mbps
camera_poe_w
12.5 to 12.5 W
access_controller_count
3 to 3 count
access_controller_poe_w
8 to 8 W
poe_budget_w
120 to 120 W
matched_coverage_zones
6 to 6 count
required_coverage_zones
6 to 6 count

Executable tool: station-building-security-lighting-package_calc.py

The model must infer

Inputs withheld at this difficulty.

Nothing. All inputs are supplied.

The model must produce

The scored JSON answer schema.

{
  "average_illuminance_lux": <number>,
  "minimum_illuminance_lux": <number>,
  "uniformity_ratio": <number>,
  "illuminance_margin_lux": <number>,
  "cctv_pixels_per_m": <number>,
  "cctv_ppm_margin": <number>,
  "network_load_mbps": <number>,
  "network_headroom_mbps": <number>,
  "poe_load_w": <number>,
  "poe_headroom_w": <number>,
  "coverage_match_fraction": <number>,
  "overall_pass_score": <number>
}
  • average_illuminance_lux · scored within ±0.3%
  • minimum_illuminance_lux · scored within ±0.3%
  • uniformity_ratio · scored within ±0.3%
  • illuminance_margin_lux · scored within ±0.3%
  • cctv_pixels_per_m · scored within ±0.3%
  • cctv_ppm_margin · scored within ±0.3%
  • network_load_mbps · scored within ±0.3%
  • network_headroom_mbps · scored within ±0.3%
  • poe_load_w · scored within ±0.3%
  • poe_headroom_w · scored within ±0.3%
  • coverage_match_fraction · scored within ±0.3%
  • overall_pass_score · scored within ±0.1%