pip install -e .
pip install -e .[test]
pip install -e .[viz] # optional visualization supportpyarinc653 simulates an ARINC 653‑style time‑partitioned system.
It models major/minor frame scheduling, partition execution slices, process timing, IPC channels, and tracing.
System definitions are expressed through Pydantic models and can be loaded from YAML or JSON.
A system defines:
major_frame: total durationminor_frames: ordered list of(partition, duration)windows
Each minor frame activates exactly one partition.
Each partition defines:
idnb_runs- optional
name - optional processes
- optional sampling ports
- optional queuing ports
- optional
scheduling_policy(PRIORITY, RMS, EDF) - optional
hm_table(health monitoring actions per error code)
Channels connect ports across partitions:
- sampling → sampling
- queuing → queuing
Routing occurs at minor‑frame boundaries.
Health monitoring can be defined at:
- partition level via
hm_table - system level via
system_hm_table
Supported actions:
IGNORESTOP_PROCESSRESTART_PROCESSRESTART_PARTITION
Tracing backends include:
NullTracerLoggingTracerJsonTracerBufferedTracerCompositeTracerChromeTracer(Perfetto / chrome://tracing)
from arinc653.config import SystemConfig, MinorFrame, PartitionConfig
from arinc653.scheduler import Scheduler
from arinc653.tracing.null import NullTracer
config = SystemConfig(
major_frame=100,
minor_frames=[
MinorFrame(partition=0, duration=50),
MinorFrame(partition=1, duration=50),
],
partitions=[
PartitionConfig(id=0, nb_runs=1),
PartitionConfig(id=1, nb_runs=1),
],
)
sched = Scheduler(config=config, tracer_factory=lambda pid: NullTracer(pid, "traces"))
sched.run()major_frame: 100
minor_frames:
- partition: 0
duration: 50
- partition: 1
duration: 50
partitions:
- id: 0
nb_runs: 1
sampling_ports:
- name: out
max_message_size: 32
refresh_period: 10
- id: 1
nb_runs: 1
sampling_ports:
- name: in
max_message_size: 32
refresh_period: 10
channels:
- source_partition: 0
source_port: out
dest_partition: 1
dest_port: in
trace_path: traces
tracer: chrome
random_seed: 123
strict: false
tick_duration: 1
major_frame_repeats: 1Run:
arinc653 --config system.yamlsystem_hm_table:
INVALID_SCHEDULE: STOP_PROCESS
partitions:
- id: 0
nb_runs: 1
scheduling_policy: RMS
hm_table:
DEADLINE_MISS: RESTART_PROCESS
processes:
- id: 1
name: SensorTask
priority: 10
period: 50
capacity: 20arinc653 --config system.yamlarinc653 \
--minor-frames "0:50,1:50" \
--partitions "0:1:P0,1:1:P1" \
--strict \
--tick-duration 1 \
--major-frame-repeats 1 \
--trace-path traces \
--tracer chromearinc653 --config system.yaml --tracer chrome
arinc653 --config system.yaml --tracer json
arinc653 --config system.yaml --tracer bufferedRequires pyarinc653[viz]:
arinc653 --plot-ganttReads traces/trace.json and renders a Gantt chart of partition execution.
--print-schedule--list-partitions--dry-run--validate— check configuration without running--dump-trace— print trace.json events--export-schedule FILE— write resolved minor‑frame schedule to JSON
-
Scheduler
Executes major/minor frames and routes IPC channels. -
Partition
Runs execution slices, manages processes, ports, interrupts, syscalls, scheduling policies, and health monitoring. -
Scheduling policies
SupportsPRIORITY,RMS, andEDFfor intra‑partition process scheduling. -
Tracing subsystem
Records events through pluggable backends, including ChromeTracer. -
Configuration
Pydantic models with full validation of schedule, ports, channels, and timing. -
CLI
Loads YAML or manual definitions and runs the system.
Supports tracer override, validation, trace utilities, and Gantt visualization.
See examples/ for complete configurations:
minimal.yaml— basic two‑partition scheduleipc.yaml— sampling/queuing channel routingstrict.yaml— deterministic executionfaults.yaml— fault injectionbuffered.yaml— in‑memory tracingcomposite.yaml— multi‑backend tracingjson.yaml— JSON trace outputchrome.yaml— Perfetto trace output for ChromeTracerlogging.yaml— logging‑based tracingstress.yaml— 10‑partition stress testtrace.yaml— simple trace output examplesystem.json— JSON configuration exampleports.yaml— sampling + queuing ports with IPC routingmulti_partition.yaml— 5‑partition schedule for medium‑complexity systemsviz.yaml— Gantt‑chart‑friendly schedule for--plot-ganttvalidate.yaml— minimal config for--validateschedule.yaml— simple schedule for--export-schedulefaults_storm.yaml— interrupt storm + syscall failure ratecomposite_full.yaml— composite tracer with multiple componentschrome_full.yaml— ChromeTracer with ports, IPC, and faultssystem_ipc.json— JSON config with sampling‑port IPCtrace_format.json— synthetic example showing the trace file structurehm.yaml— partition and system health monitoring configurationrms_edf.yaml— RMS and EDF scheduling examplesdeadline.yaml— periodic processes with deadline miss handling
Run:
arinc653 --config examples/minimal.yaml