-
Notifications
You must be signed in to change notification settings - Fork 130
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
Should I use -a or -g when demultiplexing ONT reads with dual barcodes? #799
Comments
The difference between For The distinction between required and optional is only necessary for linked adapters (the one with the The rules are like this:
So if you know your reads are long enough so that you should see both primers or if you want to ensure you only have full-length sequences in your demultiplexed output, use (You could also make the first adapter required and leave the second one optional by writing this in the FASTA file: |
Thanks for the quick answer! That definitely clears things up for me. I have a follow up question though, after reading through the documentation more. When demultiplexing, does cutadapt require the complete barcode to be present for it to count? For example, for BARCODE it would identify and trim BARCODEsequence and not CODEsequence. Basically, I want to make sure that I only keep reads with a complete barcode. |
To require the full barcode to be present, use an anchored adapter. You can either add the
or, as a shortcut, add the |
cutadapt 4.9
I have 16S amplicon reads that were sequenced with ONT that I am trying to demultiplex. Each sample was PCR barcoded with a 13 base barcode on both ends, so I expect a read to start with a barcode and end with its reverse complement. I put together a fasta file of all my pairs, some are listed below.
The problem I run into is whether to use the
-a
or-g
flag. Looking through the documentation I see it used almost interchangeably for linked adapters, but I get different outputs depending on which I use and I'm not sure which is correct. I used the below commands, for referenceThe text was updated successfully, but these errors were encountered: