Since the pipelines can take a while to run, it’s best if you use a screen session. By using a screen session, Snakemake stays “active” in the shell while it’s running, there’s no risk of the connection going down and Snakemake stopping. `screen -S <name of session>` to start a new screen session and `screen -r <name of session` to reattach to the screen session. In the screen session activate the conda environment.
Configure your paths, but keep the variable names that are already in the config file. See below for more details.
#### Run the pipeline on the cluster:
First test the pipeline with a dry run: `snakemake -np`. This will show you the steps and commands that will be executed. Check the commands and file names to see if there’s any mistake. If all looks ok, you can now run your pipeline