Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setting
According to the manual on PTA, PRISM assumes that the given PTA has no timelocks. However, it is said as well that PRISM also checks for timelocks and reports an error if one is found.
Obviously, this is just best effort as forward (games) and backward algorithms do not always traverse even all reachable states.
Problem
PRISM does not detect the following kind of timelock.
Example
A location (s=0 in the following example) with an invariant (x<=20 in the following example) preventing the further passage of time while there are transitions exiting this location but which are all disabled because some of their edges (the edge to s=2 in the following example) leads to a location with an invariant (y<=10 in the following example) that would be violated when that edge would be taken to late (e.g. at x=20 in the following example).
Checking the property
Pmax=? [ F s=2 ]
would then fail describing the timelock:Output with changed code
Explanation of code for example
What happens is as follows for the edge to s=1
What happens is as follows for the edge to s=2