-
Notifications
You must be signed in to change notification settings - Fork 83
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
Read Group not added to bam files generated by bowtie2, which causes GATK genotyping to fail #655
Comments
I looked a bit further into the
The RG info might be added in a later step that I may be skipping, but it would be best to add them during the initial alignment (or right after).
|
Add Read Group information to `bowtie2` mapping to fix issue [nf-core#655 ]
I've added the PR to fix this issue (adding exactly the same RG info as the |
Updating @IdoBar 's solution for an example of how the RG info should be added to the
|
@TCLamnidis could you also add to your 2.5 PR? |
@kclem @TCLamnidis will have a couple of questions for you regarding the exact implementation going into here #1021, as per your request |
Check Documentation
I have checked the following places for your error:
- nf-core/eager FAQ/troubleshooting can be found here
Description of the bug
Read Group information is not added to the
bam
files generated by bowtie2, which causes GATK ug genotyping to fail.Steps to reproduce
Steps to reproduce the behaviour:
nextflow run nf-core/eager -r 2.2.2 -params-file bt2local.gatkug.json -c /home/ibar/.nextflow/awoonga.config -resume
Content of
bt2local.gatkug.json
:Expected behaviour
The
bam
files should have Read Group information to allow for subsequent genotyping withgatk
.Log files
Have you provided the following extra information/files:
.nextflow.log
fileDingo_aDNA_NF2.log
System
Nextflow Installation
Container engine
Additional context
This is the output of
picard ValidateSamFile -I D12_PE.mapped.bam
:The text was updated successfully, but these errors were encountered: