search

jgaetel / cutadapt

Automatically exported from code.google.com/p/cutadapt
0 stars 0 forks source link

Allow IUPAC ambiguities in adapter #83

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Another pesky feature request: It would be useful to allow IUPAC ambiguities 
beyond the "wildcard" N as currently implemented. Perhaps this would make 
cutadapt incredibly slow? Here's an example:

cat input.fasta
>seq1
AGTCCATAGCT
>seq2
AGTTCATAGCT

cutadapt -g ^AGTYC input.fasta

>seq1
ATAGCT
>seq2
ATAGCT

Original issue reported on code.google.com by jodonnel...@gmail.com on 9 Oct 2014 at 12:00

GoogleCodeExporter commented 9 years ago 
I've just implemented this. The functionality will be part of cutadapt 1.7. 
There should be no difference in speed, so this is enabled by default.

Original comment by marcel.m...@tu-dortmund.de on 20 Oct 2014 at 8:31