Benchmarks
seal in (Structured Text rendering)
|
|
| suite id |
st_seal_in |
| domain |
motor_control |
| language |
ST |
| difficulty |
easy |
| validation status |
candidate |
| origin |
authored |
| license |
CC-BY-4.0 |
| syntax pair of |
ld_seal_in |
One of five renderings of the same seal-in latch, for cross-language comparison
What is proved
From benchmarks/motor_control/st_seal_in/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 |
!Run || !Stop |
Stop always drops the seal-in coil: Run and Stop never hold together. |
Variants
| file |
expected verdict |
violates |
method |
seal_in.st |
SAFE |
none |
expert |
Files
| file |
what it is |
size |
sha256 |
benchmark.yml |
benchmark metadata |
0.6 KB |
a4b04bd6c038 |
props.yaml |
property file |
0.2 KB |
ebfe6cdbb2fc |
seal_in.st |
structured text |
0.3 KB |
151889afdc34 |
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.
st_seal_in__seal_in__viac via C (props.yaml, expected SAFE): master SAFE