Fix bug with "historic" switch #200
Merged
Conversation
This file contains 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
This addresses the following error: Error with implementation of 'historic' switch in runbatch.py
Technical Details
Implementation notes
Additional changes (if any)
Switches added/removed/changed (if any)
Issues resolved (if any)
Known incompatibilities (if any)
Relevant sources or documentation (if any)
Is the model cleaner/better/faster/smaller than before? If so, how?
Validation / Comparison Report
Link to report and/or example plots
(if pertinent) How big is the default run folder (runs/{base}_ref_seq/) before and after the change?
(if pertinent) What is the run time for ref_seq on the same machine before and after the change?