Benchmarks
comb or (K-LD feature benchmark)
|
|
| suite id |
ld_comb_or |
| domain |
building_automation |
| language |
LD-textual |
| difficulty |
easy |
| validation status |
validated |
| origin |
authored |
| license |
CC-BY-4.0 |
K-LD executable-semantics feature suite (rung10_wp2/family)
What is proved
From benchmarks/building_automation/ld_comb_or/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 |
!Y || A || B |
Output Y is energised only when contact A or B is closed. |
Variants
| file |
expected verdict |
violates |
method |
comb_or.ld |
SAFE |
none |
expert |
Files
| file |
what it is |
size |
sha256 |
benchmark.yml |
benchmark metadata |
0.5 KB |
8041d2a33380 |
comb_or.ld |
ladder program, textual DSL |
0.1 KB |
5ff8f9e0c445 |
props.yaml |
property file |
0.2 KB |
1c69e0ba66fd |
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.
ld_comb_or__comb_or (props.yaml, expected SAFE): v8.4 SAFE