search

shane-c-lawson / breseq

Automatically exported from code.google.com/p/breseq
Other
0 stars 0 forks source link

ambiguous results being predicted with certanty #58

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Breseq REL11008
2. blast the reads aligning to new MOB3 junction (150 into 1)

What is the expected output? What do you see instead?
Expect that IS150 can be inserting into any copy of IS1 (except the one at 
4,503,503-4,504,271 which has several snps in this region that are not present 
in the reads). Instead see that it is predicted as inserting at 23674 with 
certainty.

What version of the product are you using? On what operating system?
lonestar revision c633c5005425 

Please provide any additional information below.
I suspect that MOB1 has the same issue, but i havn't looked at it in the same 
level of depth.
Jeff has mentioned a flag of 'ambiguous=1' as the final column for these types 
of events.

Original issue reported on code.google.com by Daniel.D...@gmail.com on 20 Sep 2012 at 6:55

Attachments: