-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
merge paired-end sequences #116
Comments
@tshauck – hi there I just made some progress in this PR ArcInstitute/ScreenPro2#40. You may see my codes in I already uploaded toy data after R1/R2 merge in ScreenPro2; I can also upload the original files if that helps. |
Hey, nice progress! And thanks for sharing the files. Let me follow up this weekend after I've had a chance to look at #103 and #105 in the context the Also, a mildly unrelated side note, it's funny to see |
@abearab, I was looking at this a bit, and wanted to see what you thought an ideal interface for you would be here? E.g. SELECT *
FROM merge_paired_end_reads('path/to/read_1.fastq', 'path/to/read_2.fastq', 'ADAPTER1', 'ADAPTER2') Or for, SELECT *
FROM merge_reads('path/to/read_1.fastq', 'ADAPTER1') Is this what you had in mind for doing it all in biobear, or if you have other thoughts maybe you could sketch out some pseudo code for your ideal solution? Thanks! |
Hi @tshauck – I found this cartoon and it may give you a better sense for merging read pairs. I think your |
This is helpful, thanks! It looks like bbmerge may have a nice paper describing their approach: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5657622/ |
merge-paired-end-sequences
Originally posted by @abearab in #102 (comment)
The text was updated successfully, but these errors were encountered: