feat: Adding functionality to the complexity command #4
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
aryarm
approved these changes
Sep 23, 2024
aryarm
reviewed
Sep 24, 2024
aryarm
reviewed
Sep 24, 2024
Co-authored-by: Arya Massarat <[email protected]>
Co-authored-by: Arya Massarat <[email protected]>
Co-authored-by: Arya Massarat <[email protected]>
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.
Added functionality to the complexity command, including the ability to compute complexity on regions of a GBZ file, or an entire GFA file.
A notable TODO is to add gbz-base to our testing framework (we need the
queryandgbz2dbutilities. Functions using those were tested locally but not in the test environment. After adding those to our test framework I will also need to add command line tests.