-
Notifications
You must be signed in to change notification settings - Fork 2
Running
This section goes over how to actually execute the workflow
It is highly recommended to start a dry-run first. A dry-run does several things:
- Allows you to see what steps in the workflow need to be completed
- Ensures preliminary configuration is set up correctly
A dry-run does not truly execute any component of the pipeline. No results will be generated.
Do the following to perform a dry-run
snakemake --profile slurm --dry-run
(NOTE 1: If you did not namek your CookieCutter profile slurm, replace the above line with its appropriate name)
(NOTE 2: If you receive an error when running this, replace slurm with ~/.config/snakemake/slurm)
After several seconds, many lines should move through the terminal.
It should end with This was a dry-run (flag -n). The order of jobs does not reflect the order of execution.
If this is not the case, an error has occured, and it will need to be investigated before continuing.
Once you have confirmed that a dry-run will execute successfully, it is time to start a real run of the workflow. This is done much in the same way as a dry run.
- Start your screen session:
screen -S snakemake - Change directories to the workflow (where it was downloaded with
git clone . . .). I don't know where you downloaded the workflow, so this part's up to you - Activate our conda environment:
conda activate snakemake - Start the workflow with
snakemake --profile slurm(or~/.profile/snakemake/slurmif you receive errors at this step) - Once you have verified the workflow is starting with no errors, perform the following to safely detach the screen session (which keeps snakemake running)
-
CTRL + a, d- Press and hold the
controlkey - Press
a. Continue holding control. - Press
d - The session will exit. Verify with
screen -ls. It should say(Detached)in the output.
- Press and hold the
-
From here, the workflow should continue running without errors. If you would like to examine the progress, simply attach back into the screen session.
After logging into the cluster, execute the following:
screen -r snakemake- Your snakemake session is active, with all previous output.
- Exit the screen sesion with the steps as described above
Any log files will be found in the logs directory under the same folder snakemake was started in. Each rule has its own folder, with output files containing the information they are running on (tissue_name, run number, etc.)
Created by Josh Loecker and Brandt Bessell