Dataset Viewer
Auto-converted to Parquet Duplicate
source_code
stringclasses
3 values
state_names
listlengths
4
7
transitions
listlengths
8
23
state_outputs
listlengths
4
7
behavior_summary
stringclasses
3 values
typedef enum { IDLE, LEFT_ON, LEFT_OFF, RIGHT_ON, RIGHT_OFF, HAZARD_ON, HAZARD_OFF } SignalState; typedef enum { TURN_NONE, TURN_LEFT, TURN_RIGHT } TurnRequest; typedef struct { bool hazard_enabled; TurnRequest turn_request; bool phase_expired; } Inputs; typedef struct { bool left_indicator; bool right_indicator; } Out...
[ "IDLE", "LEFT_ON", "LEFT_OFF", "RIGHT_ON", "RIGHT_OFF", "HAZARD_ON", "HAZARD_OFF" ]
[ { "source_state": "IDLE", "target_state": "HAZARD_ON", "trigger_event": "hazard_enabled becomes true", "condition": "hazard_enabled is true; this branch takes priority over turn requests." }, { "source_state": "IDLE", "target_state": "LEFT_ON", "trigger_event": "turn_request becomes ...
[ { "state_name": "IDLE", "output_behavior": "Both left_indicator and right_indicator are false." }, { "state_name": "LEFT_ON", "output_behavior": "left_indicator is true and right_indicator is false." }, { "state_name": "LEFT_OFF", "output_behavior": "Both indicators are false." }, ...
IDLE selects hazard flashing before either turn signal. Each turn signal alternates between its ON and OFF states when phase_expired is true, while a canceled request returns to IDLE and an enabled hazard request takes priority. In either hazard phase, disabling hazards selects a requested left or right signal, or IDLE...
typedef enum { LIGHTS_OFF, LOW_BEAM, HIGH_BEAM, HIGH_BEAM_BLOCKED } BeamState; typedef struct { bool low_beam_request; bool high_beam_request; bool auto_high_beam_enabled; bool oncoming_vehicle_detected; } Inputs; typedef struct { bool low_beam; bool high_beam; } Outputs; void update_state(BeamState *state, const Input...
[ "LIGHTS_OFF", "LOW_BEAM", "HIGH_BEAM", "HIGH_BEAM_BLOCKED" ]
[ { "source_state": "LIGHTS_OFF", "target_state": "LOW_BEAM", "trigger_event": "low_beam_request becomes true", "condition": "low_beam_request is true." }, { "source_state": "LOW_BEAM", "target_state": "LIGHTS_OFF", "trigger_event": "low_beam_request becomes false", "condition": "l...
[ { "state_name": "LIGHTS_OFF", "output_behavior": "Both low_beam and high_beam are false." }, { "state_name": "LOW_BEAM", "output_behavior": "low_beam is true and high_beam is false." }, { "state_name": "HIGH_BEAM", "output_behavior": "Both low_beam and high_beam are true." }, { ...
A low-beam request moves the controller from LIGHTS_OFF to LOW_BEAM. Automatic high beam is entered only when assist is enabled and a high-beam request is active. If an oncoming vehicle is detected under those conditions, the controller uses HIGH_BEAM_BLOCKED, which keeps the low beam on and the high beam off. Removing...
typedef enum { LIGHTS_OFF, POSITION, LOW_BEAM, COURTESY } LampState; typedef struct { bool ignition_on; bool auto_mode; unsigned ambient_lux; bool welcome_request; bool battery_ok; unsigned courtesy_elapsed_ms; } Inputs; typedef struct { bool position_lamps; bool low_beam; } Outputs; void update_state(LampState *state,...
[ "LIGHTS_OFF", "POSITION", "LOW_BEAM", "COURTESY" ]
[ { "source_state": "LIGHTS_OFF", "target_state": "COURTESY", "trigger_event": "welcome_request", "condition": "welcome_request is true and battery_ok is true; this branch has priority over the ignition branches." }, { "source_state": "LIGHTS_OFF", "target_state": "POSITION", "trigger_...
[ { "state_name": "LIGHTS_OFF", "output_behavior": "Both position_lamps and low_beam are false." }, { "state_name": "POSITION", "output_behavior": "position_lamps is true; low_beam is false." }, { "state_name": "LOW_BEAM", "output_behavior": "Both position_lamps and low_beam are true."...
The controller remains in LIGHTS_OFF unless a welcome request with a healthy battery or an applicable ignition condition is present. A welcome request takes priority and enters COURTESY. Manual mode with ignition on selects POSITION; automatic mode selects LOW_BEAM at or below 40 lux. POSITION changes to LOW_BEAM when ...

Automotive Lighting State Machine Code Reasoning Benchmark

This benchmark focuses on mode management and state transitions in automotive lighting ECUs, pairing relevant source code with annotations of state machine behavior. It covers state names, transition events and conditions, and lighting control or other ECU outputs associated with each state. Use it to assess whether models can reconstruct state behavior and key transition logic from code, and to evaluate code understanding and reasoning in automotive lighting electronics.

Technical Specifications

Field Type Description
source_code string Original source code related to lighting ECU mode management and state transitions.
state_names array A list of state names identified in the source code.
transitions array State transitions reconstructed from the source code, including their triggering events and transition conditions.
state_outputs array Lighting control outputs or other ECU output behavior summarized for each state.
behavior_summary string A summary of the state machine's overall behavior, key transition paths, and output logic.

Compliance Statement

Authorization TypeCC-BY-NC-SA 4.0 (Attribution–NonCommercial–ShareAlike)
Commercial UseRequires exclusive subscription or authorization contract (monthly or per-invocation charging)
Privacy and AnonymizationNo PII, no real company names, simulated scenarios follow industry standards
Compliance SystemCompliant with China's Data Security Law / EU GDPR / supports enterprise data access logs

Source & Contact

contact@mobiusi.com

Downloads last month
51