grep
'dJust running on one at time:
None found
Trying without anchoring (removing the "^" in front, so need not start at the front exactly):
Found a lot, but they are in the middle of the reads. Looking at the "length" column of the output above, that's the length of things trimmed, ranging from 57 to 241. The majority were around 88-91 bases, which makes sense if these amplicons are V1/V3, and this is a V2 primer.
None found
Without anchoring:
Cutting off lots again, bulk at 156 and 176. Makes sense again if these are V1/V3 amplicons, and this is a V2 primer ๐
So I think that's why you were able grep
these, but not really get 'em with cutadapt, they're just in the middle of the reads ๐
Took one seq from 11_GS_FWD.fastq.gz and blasting against the 16S db to get a ref sequence. With that we can see where we align, and can look at the reference for hints of primers (even if they happen to be cut off from our seqs already - which happens sometimes without our knowing, potentially complicating this further, ha)
Top hit was to this bugger, hitting it's seq at its positions 22-285:
Getting full-length of that ref sequence:
Looking at where we aligned to:
Since the 27F primer is right in front of where our amplicon starts, it suggests these primers were trimmed off already.
Got corresponding reverse read of one we did above:
Blasted against our reference sequence from above:
Aligned to ref positions 265-527:
Broken down on reference:
Before aligned-portion of full fragment
This matches this common starting position 27 primer (AGAGTTTGATCMTGGCTCAG); with a 'T' in front on the ref here
Aligned portion of whole amplified fragment in reference (forward and reverse read โ spans 506 bases in this ref)
After aligned-portion
First 16 bases of the after aligned-portion are a common position 534 primer (CAGCAGCCGCGGTAAT)
So i think the forward and reverse primers were already trimmed. If it's possible different samples have been treated differently, you may want to check some of them in a similar fashion ๐