Most mapping tools need an index file of the reference genome for mapping. The computation of these index files can take a long time.
Our mapping tool scripts check if there already is an index for the respective tool and only build it, if it is not found.
If you face any index related errors, either set the parameter
$recompute_index=True or delete the old index to recalculate it.
Mapping Input Files
The paths assume you are using our suggested input structure. Example input files you can find in our examples section.
You can find the required input files in the tool-specific documentation.
Fastq files for paired end mapping. The directories are separated in
casedir. The controldir is the default folder for all analyses. The casedir is only used for differential splicing analysis.
input/fastq/controldir/*yourFastqFile1*_1.fastq input/fastq/controldir/*yourFastqFile1*_2.fastq input/fastq/controldir/*yourFastqFile2*_1.fastq input/fastq/controldir/*yourFastqFile2*_2.fastq . . .
The fasta reference for your organism. Mapping tools usually only need it for indexing (see tool specific documentation).
annotation reference file.
Only needed by some tools. Chromosome-wise fasta files for your organism to build an index with bowtie.
input/bowtie_fastadir/1.fa input/bowtie_fastadir/2.fa input/bowtie_fastadir/3.fa input/bowtie_fastadir/4.fa . . . input/bowtie_fastadir/X.fa input/bowtie_fastadir/Y.fa
- Optional: Index
Tool specific index file(s). If no index file is found in the index folder it will be built the first time you run the tool. This might take some time. If you want to provide your own index please make sure it is in the correct format and file names. Since the index is usually built based on the fasta reference we recommend to name the index based on the fasta reference (default). You can change the
indexnamevariable in the config script.
To provide a fair baseline while maintaining easy usability, per default we run the tools with their default variables. The default parameters can be changed by editing the ENTRYPOINT.sh scripts of each tool. The variables used by mapping ENTRYPOINT.sh scripts can be set in the
mapping_config.sh files in the
scripts folder. For a usual analysis you should not need to change these parameters.