tp pulse (K-LD feature benchmark)¶
| suite id | ld_tp_pulse |
| domain | packaging |
| language | LD-textual |
| difficulty | easy |
| validation status | candidate |
| origin | authored |
| license | CC-BY-4.0 |
K-LD executable-semantics feature suite (rung10_wp2/family)
What is proved¶
From benchmarks/packaging/ld_tp_pulse/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 |
!Out || Trig |
The pulse output is asserted only in response to a trigger. |
Variants¶
| file | expected verdict | violates | method |
|---|---|---|---|
tp_pulse.ld |
VIOLATION | none | expert |
Files¶
| file | what it is | size | sha256 |
|---|---|---|---|
benchmark.yml |
benchmark metadata | 0.5 KB | 7563816983a4 |
props.yaml |
property file | 0.2 KB | 41a09daeebdc |
tp_pulse.ld |
ladder program, textual DSL | 0.1 KB | 76ee94cb20f9 |
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.
No ESBMC run is recorded against this task yet. The lessons carry the recorded runs; see Reproducing to make your own.