-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermediate file handling #100
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good though there are bugs being fixed here that should've been caught before. As a high priority, we'll want to add test cases to prevent issues like this. Anything else to add @sorelfitzgibbon @nwiltsie ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks good. @yashpatel6, agreed about the need for tooling to help catch these kinds of bugs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nothing to add other than, I assume it would be rare for users to keep the intermediate files and so no need to compress the intermediate vcfs?
That's right, it would be a rare case and the intent of saving intermediate VCFs would only be temporary so for now I think uncompressed is fine. Besides sizes are substantially small. |
Description
Enable save_intermediate_files in
bcftools.nf
andrtgtools.nf
to publish intermediate files tointermediate
dir when enabled.PR also includes a few bug fixes from previous PR
call_gSV_Delly
andregenotype_gSV_Delly
params.variant_type
instead ofvariant_type
in main.nfCloses #83
Testing Results
Checklist
I have read the code review guidelines and the code review best practice on GitHub check-list.
I have reviewed the Nextflow pipeline standards.
The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
I have set up or verified the branch protection rule following the github standards before opening this pull request.
I have added my name to the contributors listings in the
manifest
block in thenextflow.config
as part of this pull request, am listedalready, or do not wish to be listed. (This acknowledgement is optional.)
I have added the changes included in this pull request to the
CHANGELOG.md
under the next release version or unreleased, and updated the date.I have updated the version number in the
metadata.yaml
andmanifest
block of thenextflow.config
file following semver, or the version number has already been updated. (Leave it unchecked if you are unsure about new version number and discuss it with the infrastructure team in this PR.)I have tested the pipeline on at least one A-mini sample with
run_delly = true
,run_manta = true
,run_qc = true
. Forrun_delly = true
, I have tested 'variant_type' set togSV
,gCNV
, and both. The paths to the test config files and output directories are captured above in the Testing Results section.