Note: the most recent version of this vignette can be found here.
Note: if you use
systemPipeRdata in published research, please cite:
Backman, T.W.H and Girke, T. (2016). systemPipeR: Workflow and Report Generation Environment. BMC Bioinformatics, 17: 388. 10.1186/s12859-016-1241-0.
systemPipeRdata is a helper package
to generate with a single command workflow templates that are intended to be
used by its parent package
systemPipeR (H Backman and Girke 2016).
The systemPipeR project provides a suite of R/Bioconductor packages for designing,
building and running end-to-end analysis workflows on local machines, HPC clusters
and cloud systems, while generating at the same time publication quality analysis reports.
To test workflows quickly or design new ones from existing templates, users can
generate with a single command workflow instances fully populated with sample data
and parameter files required for running a chosen workflow.
Pre-configured directory structure of the workflow environment and the sample data
systemPipeRdata are described here.
systemPipeRdata package is available at Bioconductor and can be installed from within R as follows:
if (!requireNamespace("BiocManager", quietly = TRUE)) install.packages("BiocManager") BiocManager::install("systemPipeRdata")
Also, it is possible to install the development version from Bioconductor.
BiocManager::install("systemPipeRdata", version = "devel", build_vignettes = TRUE, dependencies = TRUE) # Installs Devel version from Bioconductor
library("systemPipeRdata") # Loads the package
library(help = "systemPipeRdata") # Lists package info vignette("systemPipeRdata") # Opens vignette
Load one of the available workflows into your current working directory.
The following does this for the
varseq workflow template. The name of the resulting
workflow directory can be specified under the
mydirname argument. The default
uses the name of the chosen workflow. An error is issued if a directory of the same
name and path exists already.
genWorkenvir(workflow = "varseq", mydirname = NULL) setwd("varseq")
On Linux and OS X systems the same can be achieved from the command-line of a terminal with the following commands.
$ Rscript -e "systemPipeRdata::genWorkenvir(workflow='varseq', mydirname=NULL)"
A collection of workflow templates are available, and it is possible to browse the current availability, as follows:
availableWF(github = TRUE)
This function returns the list of workflow templates available within the package and systemPipeR Organization on GitHub. Each one listed template can be created as described above.
The workflow template choose from Github will be installed as an R package, and also it creates the environment with all the settings and files to run the demo analysis
genWorkenvir(workflow="systemPipeR/systemPipeVARseq", mydirname="NULL") setwd("systemPipeVARseq")
Besides, it is possible to choose different versions of the workflow template,
defined through other branches on the GitHub Repository. By default, the
branch is selected, however, it is possible to define a different branch with the
genWorkenvir(workflow="systemPipeR/systemPipeRNAseq", ref = "singleMachine") setwd("systemPipeRNAseq")
Also, it is possible to download a specific workflow script for your analysis.
The URL can be specified under
url argument and the R Markdown file name in
urlname argument. The default
NULL copies the current version available in the chose template.
genWorkenvir(workflow="rnaseq", url = "https://raw.githubusercontent.com/systemPipeR/systemPipeRNAseq/cluster/vignettes/systemPipeRNAseq.Rmd", urlname = "rnaseq_V-cluster.Rmd") setwd("rnaseq")
It is possible to create a new workflow structure from RStudio
File -> New File -> R Markdown -> From Template -> systemPipeR New WorkFlow.
This interactive option creates the same environment as demonstrated above.
Figure 1: Selecting workflow template within RStudio.
The workflow templates generated by
genWorkenvir contain the following preconfigured directory structure:
input.ymlfiles need to be in the same subdirectory.
Note: Directory names are indicated in green. Users can change this structure as needed, but need to adjust the code in their workflows accordingly.