The Databricks RNASeq pipeline requires Databricks Runtime HLS, which is in Beta. Interfaces and pricing are subject to change before general availability.
We recommend running the RNASeq pipeline as a Databricks job. When run interactively, you are charged per DBU as well as per giga base pair.
The pipeline is run as a Databricks job. Most likely, a Databricks employee will set up the initial job for you. The necessary details are:
- The cluster configuration should use Databricks Runtime HLS.
- The task should be the DNASeq notebook provided to you.
- For best performance, use compute optimized instances with at least 60GB of memory. We
- To reduce costs, use all spot workers with the
Spot fall back to On-demandoption selected.
The pipeline accepts a number of parameters that control its behavior. The most important and commonly changed parameters are documented here; the rest can be found in the RNASeq notebook. All parameters can be set for all runs or per-run.
|manifest||n/a||The path of the manifest file describing the input.|
|output||n/a||The path where pipeline output should be written.|
In addition, you must configure the reference genome using environment variables. To use Grch37, set the environment variable:
To use Grch38 instead, set an environment variable like this:
The pipeline consists of two steps:
- Alignment: Map each short read to the reference genome using the STAR aligner.
- Quantification: Count how many reads correspond to each reference transcript.
The operational aspects of the RNASeq pipeline are very similar to the DNASeq pipeline. For more information about manifest format, output structure, and programmatic usage, see DNASeq Pipeline.