-
Notifications
You must be signed in to change notification settings - Fork 32
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
Problem of forget to indel alignment-quality to your bam-file #133
Comments
Hi @Xiang-Leo, This look more like a problem with the workflow itself. The commands in those rules look fine. I can't see what is actually being used in Best, |
I'm sorry for the clipped command. Actually I run three commands: lofreq indelqual --dindel -f NC_045512.2.fasta -o 05_map2covid.lofreq.indelqual.bam 03_map2covid.sort.bam # 05_map2covid.lofreq.indelqual.bam means the generated quality file
lofreq alnqual -b 05_map2covid.lofreq.indelqual.bam NC_045512.2.fasta > 06_map2covid.lofreq.alqual.bam
lofreq call --call-indels -f NC_045512.2.fasta -o 07_map2covid.lofreq.vcf 06_map2covid.lofreq.alqual.bam Usually, if there are 3 or less files, it will report no problems. While I run snakemake with more then 10 files, it will report |
Also, when I run these commands step by step, it also report the warning |
Hi @Xiang-Leo, The series of commands you gave looks correct, i.e.:
I assume you removed the indexing commands for the sake of brevity. The fact that the behaviour changes with more files, hints at a workflow problem. Can you see how the Snakemake commands change between one working input and one input that doesn't work? Thanks, |
Hi, I met the problem of
WARNING(lofreq_call.c|main_call): 5 indel calls (before filtering) were made without indel alignment-quality! Did you forget to indel alignment-quality to your bam-file?
when I ran lofreq within Snakemake.Here are the rules:
It's quite strange since there are no problems when run one file with snakemake, but if there are several files to run, it report error of indel alignment-quality.
The text was updated successfully, but these errors were encountered: