-
Notifications
You must be signed in to change notification settings - Fork 52
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
Multiple entries in remap.fq*.gz for single read pair #18
Comments
Looking at my older runs of WASP, it seems that reads were output multiple times in the fastq files in the past as well. I guess the bug here may be that this read pair doesn't make it through the filtering step even though it aligns to the same spot. I've added files to the zip that show this. |
Hi Chris, thanks for the bug report, looking into this now... |
I think I found the problem and have committed a fix here: Thanks again for the bug report and let us know if you have any further issues. |
Thanks Graham. It seems the results (e.g. whether a read pair is kept or not) from the mapping pipeline weren't affected by this bug right? |
I am not 100% certain, but unfortunately I think that it could have The other outstanding issue is that Step #5 (rmdup) does not currently On Thu, Jun 25, 2015 at 12:50 PM, Christopher DeBoever <
|
It turns out the 'fix' I made was not correct and has created some issues with the PE reads. I have reverted to the old version and I am working on fixing the original issue (which was minor by comparison). |
Sounds good, I was actually looking at the code last week although so far On Mon, Jul 27, 2015 at 2:39 PM, Graham McVicker notifications@github.com
|
I've been able to clean up the code a bit and add a lot of documentation and some tests (0170a01). I actually looked into this bug and it turns out it's not a bug. The two reads both overlap the SNP so the three possible read pairs are output. I added a test for the data I provided initially. I can make a pull request, but I was also wondering if we could add an option to specify that the input bam file is already coordinate sorted? I can add that in before I make the pull request. |
Hi Chris, That changes and test look great. You are welcome to add an option to Thanks a lot for your help! Graham On Mon, Aug 3, 2015 at 3:17 PM, Christopher DeBoever <
|
I've used the mapping part of WASP successfully before, but for some reason I've started seeing what seems to be a bug where the sequence for a single read pair is written to the remap.fq*.gz files multiple times:
I've made a zip with files to reproduce the bug. I used the latest version of find_intersecting_snps.py from master.
https://dl.dropboxusercontent.com/u/3886457/wasp_bug.zip
The text was updated successfully, but these errors were encountered: