Closed sluke123 closed 8 years ago
Hi,
sorry about that. I am not sure I understand, can you give an example? That way I can try to find the bug and a solution.
cheers
Instead of this:
- algorithm:
aligner: false
mark_duplicates: false
mixup_check: qsignature
realign: false
recalibrate: false
variantcaller: false
analysis: variant2
description: 020-20
files:
- /path/to/ready.bam
genome_build: hg38
metadata:
batch: 020-20-batch
phenotype: tumor
it had
- algorithm:
aligner: false
mark_duplicates: false
mixup_check: qsignature
realign: false
recalibrate: false
variantcaller: false
analysis: variant2
description: 020-20
files:
- /path/to/ready.bam
genome_build: hg38
mixup_check: qsignature_full
metadata:
batch: 020-20-batch
phenotype: tumor
I guess your template was?, I am trying to reproduce this and see what is the problem:
- algorithm:
aligner: false
mark_duplicates: false
mixup_check: qsignature
realign: false
recalibrate: false
variantcaller: false
analysis: variant2
genome_build: hg38
thanks
Actually I had the variantcaller as a list – perhaps it was that giving me a problem? If so please close the issue.
algorithm:
aligner: false
mark_duplicates: false
mixup_check: qsignature
realign: false
recalibrate: false
variantcaller: [false]
analysis: variant2
genome_build: hg38
The sample yaml file then had mixup_check: qsignature in the algorithm section, and at the top level.
Sally Luke Associate Principal Scientist
AstraZeneca IT | R&D Information 2 Riverside, Granta Park, Great Abington, Cambridge CB21 6GH M: +44 (0) 7818 523808
From: Lorena Pantano [mailto:notifications@github.com] Sent: 09 June 2016 14:10 To: chapmanb/bcbio-nextgen bcbio-nextgen@noreply.github.com Cc: Luke, Sally sally.luke@astrazeneca.com; Author author@noreply.github.com Subject: Re: [chapmanb/bcbio-nextgen] Template command for qsignature (#1423)
I guess your template was?, I am trying to reproduce this and see what is the problem:
algorithm:
aligner: false
mark_duplicates: false
mixup_check: qsignature
realign: false
recalibrate: false
variantcaller: false
analysis: variant2
genome_build: hg38
thanks
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/chapmanb/bcbio-nextgen/issues/1423#issuecomment-224889274, or mute the threadhttps://github.com/notifications/unsubscribe/APSBqYRkfysrR-HR4YshpiXaa05y6KX8ks5qKBCkgaJpZM4Iw-4J.
AstraZeneca UK Limited is a company incorporated in England and Wales with registered number:03674842 and its registered office at 1 Francis Crick Avenue, Cambridge Biomedical Campus, Cambridge, CB2 0AA.
This e-mail and its attachments are intended for the above named recipient only and may contain confidential and privileged information. If they have come to you in error, you must not copy or show them to anyone; instead, please reply to this e-mail, highlighting the error to the sender and then immediately delete the message. For information about how AstraZeneca UK Limited and its affiliates may process information, personal data and monitor communications, please see our privacy notice at www.astrazeneca.comhttps://www.astrazeneca.com
Here's the template, it was run on bam files:
# Template for paired (tumor/normal) variant calling
# see http://bcbio-nextgen.readthedocs.org/en/latest/contents/configuration.html for more options!
---
details:
- analysis: variant2
genome_build: hg38 # [hg19, GRCh37, mm10, rn5]
mixup_check: qsignature_full
# In order to do paired variant calling, samples should belong to the
# same batch ("batch" under "metadata" below") and have a "phenotype"
# field stating either "normal" or tumor". For each batch there
# should be a sample with "tumor" phenotype and a sample with "normal"
# phenotype (no more than two samples per batch)
algorithm:
aligner: false # [bwa, bowtie, bowtie2, mosaik, novoalign, false], set to false for targeted panels that use pcr
mark_duplicates: false
recalibrate: false # [gatk, false]
realign: false # [gatk, gkno, false]
mixup_check: qsignature
variantcaller: [false] # Valid values are "mutect", "varscan", "freebayes", "vardict"
Edit. Ugh. We put mixup_check
there twice in the template ourselves! Oops..
Hi,
nice, mystery solved!
Template command on the yaml file with qsignature duplicates the entry in the alignment section and the top level of the sample yaml