-
Notifications
You must be signed in to change notification settings - Fork 7
Quick Start
This page shows minimal examples of running the ExSeq pipeline. For more information refer to the other wiki sections.
Minimal Usage:
./runPipeline.sh
This will run the pipeline pulling parameters (input directories, number of rounds etc.) from a file in the same directory named:
loadParameters.m
The repository contains a template with annotated parameters with the most important ones described in the Parameters section.
Usage specifying command line parameters pulling unused parameters from the load parameters file.
./runPipeline [OPTIONS]
The options which should be defined for most data sets are:
-
-Nnumber of rounds or '--auto-config' to calculate from files. -
-bfile basename -
-Iinput image directory -
-Ooutput directory containing folders described in Input Data Preparation. -
-Llog directory
Optionally to run specific stages can use:
-
-sto skip stages running all not listed -
-eto run only specific stages.
Either option can have a comma separated list of one or more of the following:
setup-cluster, color-correction, normalization, registration, puncta-extraction, base-calling
For a full list of command line options use the refer to the options section or use the help option:
-h
For these examples, assume we have a directory of input images, which are either direct from microscope or have been run through a deconvolution application, as follows.
/mp/nas1/share/ExSEQ/ExSeqSlice/input
We can either set this (or any other options shown) in a loadParameters.m file in the same directory but in this case we will specify this input directory with a command line option.
ex 1)
$ ./runPipeline.sh -I /mp/nas1/share/ExSEQ/ExSeqSlice/input --auto-config -b sa0916slicedncv
The number of rounds is set automatically from files in the input directory, and sets the file basename (project name) to sa0916slicedncv running all stages.
ex 2)
$ ./runPipeline.sh -I /mp/nas1/share/ExSEQ/ExSeqSlice/input --auto-config auto -b sa0916slicedncv -s setup-cluster,color-correction,normalization,registration,puncta-extraction
In addition to ex 1) parameters, we set to skip stages of most of the stages only running the base calling stage. We could have alternatively used the specific stage option like so:
-e base-calling
- 1 Setup Cluster
- 2 Color Correction
- 3 Normalization
- 4 Registration
- 5 Puncta Extraction
- 6 Base Calling
- Performance Profile
- Example Batching
- Summary Reporting (link to page) / Analysis (link to page) All of above would be bullet points but thought each folder with useful scripts in the repository would have its own page with example usages and descriptions for the files under the given directory. Unsure on this as haven't used anything under these directories directly myself (i.e not through runPipeline) apart from tests/perf-profile/summarize-stat-logs.sh. Should any of these have a separate page? Note have not made pages for this yet as not sure how many should be made or if this break down makes sense.
- Troubleshooting