-
Notifications
You must be signed in to change notification settings - Fork 86
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
All avgoutcoverage = 0 #190
Comments
Hello, Just following up on this issue. Is there any headway? |
Sorry - difficult to get to bamsurgeon stuff lately. When I've seen this in the past it's usually due to the realignment step failing somewhere. If the original .bam was created via (e.g.) bwa mem, make sure the same aligner is used for realignment ( |
Thank you! It is starting to mutate successfully. However, some mutations are being skipped because is states there are no reads in the region. But when I look at those specific sites, they have adequate coverage (i.e. 95X). Do you know why this could happen? Results: samtools depth -a chr1 177131994 96 |
Hello! Any updates on this issue? |
Hello,
I am trying to mutate a rather large genome, here is the command:
python ~/bamsurgeon/bin/addsnv.py -v input_mutations.bed -f realvariants_Ayumu.sorted.golden.newheader.bam -r panTro6.autosomal.fa -o realvariants_Ayumu_genome0_1.newheader.sorted.golden.newheader.mutated.bam
It run's without an issue until the end in which I get this error:
ERROR 2021-12-10 12:39:50,440 no succesful mutations
Looking at each individual mutation being generated, they all have this issue:
INFO 2021-12-10 12:39:48,728 haplo_chr7_43034975_43034975 avgincover: 102.666667, avgoutcover: 0.000000
WARNING 2021-12-10 12:39:48,729 haplo_chr7_43034975_43034975 dropped for outcover/incover < 0.9
Essentially all avgoutcover is zero and they get dropped. The average coverage across these genomes is 100X, so I am confused why there are so little output reads. I have also had an issue with the organization of the reference genome and the BAM file, and I have since fixed that issue by reorganizing the header of the BAM using samtools reheader.
Best,
Mark
The text was updated successfully, but these errors were encountered: