EXP: switch to using calc-full-gather.py #18
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.
This PR switches slainte over to using
calc-full-gather.pyfrom https://github.com/ctb/2024-calc-full-gather / sourmash-bio/sourmash_plugin_branchwater#187, which does not run a whole newgatherwith a picklist, but instead calculates the columns starting from the fastgather output.This has the advantage of being lower memory and faster, per sourmash-bio/sourmash#2950. This is especially true for large nasty rumen samples, ugh.
Before this gets merged, we would need to fix
calc-full-gatherto work with multiple databases, among perhaps other things.