You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Anecdotally, an important part of developing a TLA+ model and debugging it is using trace invariants to describe a sequence of transitions that should be possible under the model. Negating them and finding a counterexample would then confirm the intuition (whereas not finding it would suggest something was wrong).
As a convenience feature, Modelator could accept a simple representation of a run (perhaps in a JSON form, not necessarily with all variables set) and automate a couple of steps to produce a full run.
This feature is related to the idea of runs and perhaps we could use some of the syntax (although, I'd prefer to keep it as simple as possible, since it is a debugging tool).
The text was updated successfully, but these errors were encountered:
Anecdotally, an important part of developing a TLA+ model and debugging it is using trace invariants to describe a sequence of transitions that should be possible under the model. Negating them and finding a counterexample would then confirm the intuition (whereas not finding it would suggest something was wrong).
As a convenience feature, Modelator could accept a simple representation of a run (perhaps in a JSON form, not necessarily with all variables set) and automate a couple of steps to produce a full run.
This feature is related to the idea of runs and perhaps we could use some of the syntax (although, I'd prefer to keep it as simple as possible, since it is a debugging tool).
The text was updated successfully, but these errors were encountered: