Open carmencita opened 2 years ago
Hi @carmencita
This is a tricky question, but I think your solution of sticking everything into the -a
option might indeed just work (and it is also probably the only solution as Trim Galore doesn't expose all of the options and functions of Cutadapt for simpilicity reasons).
--nextseq 10
(mutually exclusive with -q 20
) and -o ...
should be Trim Galore options, so you should be able to specify these on Tower, or via external arguments to the pipeline?
I am not exactly sure why you would want to choose the option --discard-trimmed
as it sounds like a fairly harsh call (if it contains either polyA or adapter it will get booted entirely? Would quality trimming affect this as well?
Hi
I also have the same issue. Did you manage to solve this already? Putting everything in the -a option does not work for me.
trim_galore -a " polyA=A{20} -a QUALITY=G{20} -a r1adapter=A{18}AGATCGGAAGAGCACACGTCTGAACTCCAGTCAC;min_overlap=3;max_error_rate=0.100000 -a r1polyA=A{18} -g r1adapter=AGATCGGAAGAGCACACGTCTGAACTCCAGTCAC;min_overlap=20 -n 4" --nextseq 10 input.fq.gz
results in this error message
Multicore support not enabled. Proceeding with single-core trimming.
Path to Cutadapt set as: 'cutadapt' (default)
Cutadapt seems to be working fine (tested command 'cutadapt --version')
Cutadapt version: 2.7
single-core operation.
No quality encoding type selected. Assuming that the data provided uses Sanger encoded Phred scores (default)
Adapter sequence must contain DNA characters only (A,C,T,G or N)
Thanks in advance
Which version are you using? My guess is that it may simply be too old (current is 0.6.10).
I'm using the one from nf-core, so 0.6.7.
Hi!
I am trying to implement the following cutadapt command using TrimGalore:
to analyse Lexogen data
I know that TrimGalore can be used with different adaptor sequences (https://github.com/FelixKrueger/TrimGalore/issues/86). The equivalent TrimGalore command using multiple adaptors would then look as follows:
However, I am unsure how to provide the --discard-trimmed , the changing -O and the --nextseq 10 option as they are executed in different rounds. Should I put them under the TrimGalore -a option? Or is there a workaround you could suggest? For the context: I would like to use cutadapt via TrimGalore because TrimGalore is integrated in the Nextflow RNA-seq pipeline. Thank you for your help.