Allow detailed logging for lpsreach.#1910
Draft
jkeiren wants to merge 5 commits intomCRL2org:masterfrom
Draft
Conversation
En passant clean up the printing of JSON.
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
1 participant
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.
This is a first proposal to log more information on lpsreach.
In particular, this should help understanding in more detail to what extent the different transition groups, as well as chaining and saturation, contribute to the exploration of the state space in lpsreach.
Right now, all statistics are collected during the exploration, but are only printed at the end of the execution. This is perhaps too naive, especially if we want to use the statistics when exploring models that have many transition groups, and that require many iterations.
We should probably see first if we want to separate logging of statistics, so that statistics can be streamed to (e.g.) a JSON file on the fly, allowing to reduce the memory overhead.