Benchmarks
Car door cycle with a stored action (SFC)
|
|
| suite id |
sfc_elevator_door |
| domain |
elevator |
| language |
SFC |
| difficulty |
medium |
| validation status |
candidate |
| origin |
authored |
| license |
CC-BY-4.0 |
Four-step door cycle, authored for SFC language coverage
What is proved
From benchmarks/elevator/sfc_elevator_door/props.yaml. What each kind claims, and what it becomes on either route, is on The properties we prove.
| id |
kind |
claim |
requirement |
P1 |
invariant |
!(moving && door_open) |
The car must never travel with the door open: anyone standing in the doorway is exposed to the running shaft. |
Variants
| file |
expected verdict |
violates |
method |
clean.xml |
SAFE |
none |
expert |
bomb.xml |
VIOLATION |
P1 |
fault-injection |
Files
| file |
what it is |
size |
sha256 |
benchmark.yml |
benchmark metadata |
1.1 KB |
6c5dce993ab0 |
bomb.xml |
ladder program, PLCopen XML |
5.9 KB |
4096b3df387c |
clean.xml |
ladder program, PLCopen XML |
5.8 KB |
cf95eef742f7 |
props.yaml |
property file |
0.2 KB |
a3b9c1966930 |
Recorded runs
A task can carry two routes. ld is ESBMC's ladder front end reading the program directly. via C is the same solver reached through Beremiz and MatIEC, which is the only route that reaches ST, IL, FBD and SFC; see How ESBMC-PLC works.
sfc_elevator_door__bomb (props.yaml, expected VIOLATION): v8.4 unknown — ingestion gate failed on v8.4sfc_elevator_door__bomb__viac via C (props.yaml, expected VIOLATION): master timeoutsfc_elevator_door__clean (props.yaml, expected SAFE): v8.4 SAFE — ingestion gate failed on v8.4sfc_elevator_door__clean__viac via C (props.yaml, expected SAFE): master timeout