Repository navigation
Show progress during long robustness experiments - #5
Draft
DylanCosto wants to merge 1 commit into
Draft
DylanCosto wants to merge 1 commit into
DylanCosto wants to merge 1 commit into
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.
Genome-wide robustness experiments can run for many minutes with no intermediate output. Add readable stage changes and periodic term counts on stderr, with
--progress jsonfor workflow tools,--progress quiet, and a positive--progress-interval(30 seconds by default).Updates distinguish processed, common-callable baseline and excluded terms for each score. Scoring checks the interval between blocks of 256 terms; this is not a heartbeat during input loading or a runtime estimate. The final
completeevent is emitted only after input re-verification and publication ofreport.json. Progress settings and timestamps stay outside scientific outputs. Ordinary error diagnostics still appear on stderr, and a closed log consumer does not invalidate the experiment.Validation:
Stacked on #4. The prepared 128-person release candidate is preserved; this follow-on does not change its evidence or publish a release.