-
Notifications
You must be signed in to change notification settings - Fork 51
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
No alignment when adapters are found #16
Comments
Hello, What do you mean that you take the first few base-pairs of the read as the adapter sequence? For the alignment you drew, I think that I would not expect there to be adapter sequence present. Adapter sequence shows up when you have the opposite case, something like this (excuse the bogus alignment): read1: -------AAAAAAAAAAAA In this case the overhang is read2 coming before read1. This is what happens when the underlying fragment is shorter than the read length. If you use the first few BP of read1 as the “adapter” then SeqPrep will go ahead and assume that the pair of reads starts with the adapter sequence (is an adapter dimer), in which case you want to throw it out completely. Make sense? Thanks, On Apr 2, 2014, at 6:52 AM, mairae [email protected] wrote:
|
Hello John, It is true, that I don't necessarily want/expect to see adapter sequences at the beginning of a read in the SeqPrep alignment. The alignment I drew did not come from SeqPrep though and was just to demonstrate that I would expect that the two reads in question should be able to be merged. My data mostly looks like this:
(So the fragment should not be shorter than the read lengths, but it's only a few bases longer.)
or
with trimmed adapter sequences. Is this not what I should be expecting? And on a related note: I think, in an earlier version, it was possible, to put empty strings as adapter sequences (-A '' -B ''), but it does not seem to be working anymore. (Similar problem: SeqPrep reports the reads as "Pairs With Adapters" and as "Pairs Discarded".) Best regards, |
There wouldn’t be an or situation like you drew below. The way illumina adapters work it would always be the second case if indeed adapter sequences are present. They always happen after the genomic DNA in the first read. When there is no genomic DNA present, then it happens at the beginning of the first read. If the adapter happens at the beginning of the first read then there should not be any genomic DNA present, unless you are following a non-standard paired-end illumina protocol, like long insert mate-pair or something. On Apr 3, 2014, at 4:53 AM, mairae [email protected] wrote:
|
I'm trying to merge reads with SeqPrep.
I have read 1:
and read 2:
Looking at them, they do have a perfect overlap.
Then I took the first few base pairs of each read as adapter sequences:
And used SeqPrep to merge them:
But it seems not to be able to do the alignment. Am I missing something?
(When I put something like CCCCCCCCCCCCC as adapters, the reads get merged.)
Thanks a lot,
Marie
The text was updated successfully, but these errors were encountered: