Merge branch 'develop' into fix-BIOPET-583

docs/general/config.md

@@ -70,9 +70,9 @@ In the `tags` key inside a sample or library users can supply tags that belong t
 The settings config enables a user to alter the settings for almost all settings available in the tools used for a given pipeline.
 This config file should be written in either JSON or YAML format. It can contain setup settings like:
 
- * references,
- * cut offs,
- * program modes and memory limits (program specific),
+ * references
+ * cut offs
+ * program modes and memory limits (program specific)
  * Whether chunking should be used
  * set program executables (if for some reason the user does not want to use the systems default tools)
  * One could set global variables containing settings for all tools used in the pipeline or set tool specific options one layer 
@@ -128,9 +128,13 @@ It is also possible to set the `"species"` flag. Again, we will default to `unkn
 # More advanced use of config files.
 ### 4 levels of configuring settings
 In biopet, a value of a ConfigNamespace (e.g., "reference_fasta") for a tool or a pipeline can be defined in 4 different levels.
+
  * Level-4: As a fixed value hardcoded in biopet source code
+ 
  * Level-3: As a user specified value in the user config file
+ 
  * Level-2: As a system specified value in the global config files. On the LUMC's SHARK cluster, these global config files are located at /usr/local/sasc/config.
+ 
  * Level-1: As a default value provided in biopet source code.
 
 During execution, biopet framework will resolve the value for each ConfigNamespace following the order from level-4 to level-1. Hence, a value defined in the a higher level will overwrite a value define in a lower level for the same ConfigNamespace.
@@ -172,4 +176,4 @@ biopet template Gentrap -o gentrap_config.yml -s gentrap_run.sh
 | -o | --outputConfig | Path (**required**) | Name of the config file that gets generated.|
 | -s | --outputScript | Path (optional) | Biopet can also output a script that can be directly used for running the pipeline, the call of the pipeline is generated with the config file as input. This parameter sets the name for the script file.|
 | -t | --template | Path (optional) | A template file with 2 placeholders *%s* is required for generating the script. The first placeholder will be replaced with the name of the pipeline, the second with the paths to the sample and settings config files. When Biopet has been pre-configured to use the default template file, then setting this parameter is optional. |
-|    | --expert |  | This flag enables the user to configure a more extensive list of parameters for the pipeline. |
\ No newline at end of file
+|    | --expert |  | This flag enables the user to configure a more extensive list of parameters for the pipeline. |

docs/pipelines/mapping.md

@@ -49,7 +49,7 @@ All other values should be provided in the config. Specific config values toward
 | ---- | ---- | -------- |
 | output_dir | Path (**required**) | directory for output files |
 | reference_fasta | Path (**required**) | Path to indexed fasta file to be used as reference |
-| aligner | String (optional) | Which aligner to use. Defaults to `bwa`. Choose from [`bwa`, `bwa-aln`, `bowtie`, `gsnap`, `tophat`, `stampy`, `star`, `star-2pass`, `hisat2`] |
+| aligner | String (optional) | Which aligner to use. Defaults to `bwa`. Choose from [`bwa-mem`, `bwa-aln`, `bowtie`, `bowtie2`, `gsnap`, `tophat`, `stampy`, `star`, `star-2pass`, `hisat2`] |
 | skip_flexiprep | Boolean (optional) | Whether to skip the flexiprep QC step (default = False) |
 | skip_markduplicates | Boolean (optional) | Whether to skip the Picard Markduplicates step (default = False) |
 | skip_metrics | Boolean (optional) | Whether to skip the metrics gathering step (default = False) |

docs/pipelines/yamsvp.md

-# Introduction
-
-# Invocation
-
-# Example
-Note that one should first create the appropriate [configs](../general/config.md).
-
-# Testcase A
-
-# Testcase B
-
-# Examine results
-
-## Result files
-
-## Best practice
-
-# References