Deletions Too Big
See original GitHub issueI’ve noticed sometimes both addindel.py
and addsv.py
will make deletions that are larger than what’s specified.
For example, calling python $addindel -v $indels -f $originalBam -p 8 -d 0 -r $fasta --picardjar $picardjar --aligner mem --insane -o $indelBam
with $indels:
22 38827224 38827245 0.5 DEL
results in a deletion almost 2kb (should be 21bp):
The log file looks normal: a list of 20 reads, then
indel DEL:22:38827224:38827245 38827224 FIX get_mutstr 19.0416666667 16.0416666667 0.5 0.0
Is this a known issue?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Error 'Delete Operation Too Large' or too slow when you ...
'Delete Operation Too Large You can't delete more than 100,000 combined objects and child records at the same time. Select fewer records to...
Read more >DNA Deletion and Duplication and the Associated Genetic ...
Deletions involve the loss of DNA sequences. Phenotypic effects of deletions depend on the size and location of deleted sequences on the genome....
Read more >This file is too big to recycle, Do you want to permanently ...
This file is too big to recycle, Do you want to permanently delete it · Go to your Desktop screen. · Right-click Recycle...
Read more >How To Fix "This File Is Too Big To Recycle" In Windows 11
Fix “File is too big to recycle, Do you want to permanently delete it” · Go to your Desktop and right-click on Recycle...
Read more >Large Chromosome Deletions, Duplications, and Gene ... - NCBI
Using high density SNP microarrays, we find that chromosome deletions, duplications and gene conversions were significantly more frequent in ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry for the delay in responding - what you’re running into is that addsv doesn’t specify mutations exactly: the chromosome/start/stop coordinates in the variant input file define regions where addsv will attempt to make a contig and the other fields are information about the type of mutation you’re trying to make. The exact coordinates of the breakpoints will be defined in the truth file e.g. generated with the included makevcf_sv script.
I don’t think my modification changed it’s behavior: though maybe I should have just changed the condition on 522 to
if len(a) > a and a[1] != "-1"
.