I want to run FastQC in CASAVA mode before and after trimming to check the effect of trimming (i.e., using fastqc --casava).
FastQC only recognises CASAVA input files if they are in the above format. From the FastQC help:
--casava Files come from raw casava output. Files in the same sample
group (differing only by the group number) will be analysed
as a set rather than individually. Sequences with the filter
flag set in the header will be excluded from the analysis.
Files must have the same names given to them by casava
(including being gzipped and ending with .gz) otherwise they
won't be grouped together correctly.
So, in order to be compatible with FastQC/CASAVA, skewer has to use output file names that have exactly the same format of input files (currently it add a -trimmed-pair1 or -trimmed-pair2 suffix).
Is it possible to implement this feature? I see two options:
adding a --casava argument that doesn't modify the file names and preserves the CASAVA format;
let the user completely in charge of deciding the file name format of the output files (with the default being the input file name format). In this scenario, the --output argument can just be the output directory, rather than the basename of the output files.
I have CASAVA input files in the format:
I want to run FastQC in CASAVA mode before and after trimming to check the effect of trimming (i.e., using
fastqc --casava
).FastQC only recognises CASAVA input files if they are in the above format. From the FastQC help:
So, in order to be compatible with FastQC/CASAVA, skewer has to use output file names that have exactly the same format of input files (currently it add a
-trimmed-pair1
or-trimmed-pair2
suffix).Is it possible to implement this feature? I see two options:
--casava
argument that doesn't modify the file names and preserves the CASAVA format;--output
argument can just be the output directory, rather than the basename of the output files.Thanks!