#Issue#97: How to use command=analyze #100
Open
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
fabioseel
reviewed
Dec 16, 2025
Contributor
fabioseel
left a comment
fabioseel
left a comment
There was a problem hiding this comment.
Does it actually use the previous run?
I thought it evaluates the date / time on the spot and thus never works, but maybe I'm wrong.
Contributor
|
Also I think the easier way (instead of manipulating the experiment config file) is to just add it as a command line argument, maybe worth mentioning |
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.
Closes #97
command=analyze not working is not a bug, but just insufficient documentation. Updated README.md on how to use analyze command