Add explainable, persistable Declare constraints to path search - #17
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds data-aware Declare constraints to bounded path search, persists the
constraints and search configuration in LTSVisualizer graph JSON, and explains
why each returned path satisfies the enabled constraints.
Constraint monitors remain the source of truth for path pruning and acceptance.
Explanations are reconstructed only for accepted paths, avoiding explanation
history on every queued search candidate.
What changed
Data-aware Declare constraints
Standard Alternate semantics
Align the positive Alternate family with standard Declare/MP-Declare semantics:
later target before another qualifying activation occurs.
activation since the previous qualifying target.
also matches.
The former non-standard
betweenoperand and the following unsupportednegative variants were removed:
Constrained path search
limits.
Explainability
display its transition data in the inspector.
history to queued search candidates.
Persistence
Persist and restore:
Computed paths and explanations are not persisted. Rerunning the search
reconstructs them from the restored configuration.
Imported data is validated for:
Validation
Automated:
Manual validation using the multidimensional-array graph:
Notes
independently in future work.