Add flag to (optionally) zero pad the vcf filename. #7783
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
rsasch
approved these changes
Apr 19, 2022
Also (optionally) change the naming of the intervals file to match that of the VCFs
gbggrant
force-pushed
the
gg_VS-373_ZeroPadVcfNames
branch
from
d663ffc to
f93d654
Compare
This was referenced Mar 17, 2023
Closed
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 changes GvsExtractCallset to optionally pad the output VCFs with a leading zero. They are named in a similar fashion to the (also optionally renamed) interval list shards.
If the input
zero_pad_output_vcf_filenamesis set to true (the default) the VCFs and interval files will be named as such:An example workflow is here
If the input
zero_pad_output_vcf_filenamesis set to false, the workflow will name things as it has in the past:An example workflow is here