Skip to content
Snippets Groups Projects
Commit a43f80ee authored by Fanny Wegner's avatar Fanny Wegner
Browse files

Replace phylo_exercise.md

parent 8bdd98b0
No related branches found
No related tags found
No related merge requests found
......@@ -47,7 +47,7 @@
* You can find the references here
```
/shares/amr.imm.uzh/data/projects/Blockcourse_BIO296/FS2023/Participants_data/illumina/ref/data/$USER/ngs/illumina/ref
/shares/amr.imm.uzh/data/projects/Blockcourse_BIO296/FS2023/Participants_data/illumina/ref
```
* The singularity image for `snippy` is here
......@@ -83,10 +83,13 @@
**TIP FOR JOB ARRANGEMENT**:
In your batch script, you can submit child jobs. You could for example have a general `snippy` batch script. From within this script, you submit another array job, that calls the SNPs for each sample. When all child jobs have finished, your script continues with any of the additional tasks, like generating the SNP alignment, which needs the output from all child jobs as input.
For this task it could make sense to write two scripts, with one being nested within the other.
For example, the SNP-calling step could be a job array script, that is called from within another script that then uses this output to generate the MSA and the tree.
In order for your main script to wait for the results of all child jobs, you add the option `-W` to your sbatch command, for example:
For this to work, you just submit your job array script from within the other submission script as usual with `sbatch`. However, in order for the "outer" script to wait for all launched child jobs to finish, you need to specify the flag `-W`.
this snippy.sh script submits another job array script within:
```
#!/usr/bin/env bash
#SBATCH --time=10:00:00
......@@ -109,7 +112,7 @@
```
However, this is just one idea.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment