-
Notifications
You must be signed in to change notification settings - Fork 32
Preparing the input files
khembach edited this page Mar 6, 2019
·
10 revisions
Two types of input files are required for running the ARMOR workflow:
The Snakefile
assumes that the FASTQ files are named according to the pattern:
-
<sample-name>.fastq.gz
for single-end reads -
<sample-name>_R1.fastq.gz
and<sample-name>_R2.fastq.gz
for paired-end reads.
If this is not the case you need to rename the files or modify the Snakefile
accordingly.
The metadata file should be a tab-separated text file, with at least two columns:
- one named
names
, which contains all the values of<sample-name>
from the FASTQ files - one named
type
which is eitherSE
orPE
depending on whether the samples were obtained with a single-end or paired-end protocol.
In addition, any number of columns can be included and used later in the analysis. All variables required for the differential expression analysis should be included as columns in the metadata text file. An example of a metadata text file can be seen here.