in a structure analogous to the igenomes package. In addition, commonly usedgenomes are also available at/fdb/gmap_post20210308/common_genomes. This path is also thedefault path gmap and gsnap use to look for genome files, so a particular genomeis available there it is sufficient to provide the genome name with -dgenome_name to any of the tools without also specifying the genomedirectory with -D.
Gsnap scales well with the number of threads all the way to 32, though the mostefficient use is probably around 24 threads with this input data set. Note that gsnap does not start any extra processes or threads, so --nthreads=$SLURM_CPUS_PER_TASK is appropriate unless the output ispiped into another process such as samtools. In that case the number of threads usedby the second process has to be subtracted from the number of threads given togsnap.
Batch scripts should use the $SLURM_CPUS_PER_TASK environmentvariable to determine the number of threads to use. This variable is set byslurm according to the number of requested cores. An example script for gsnapmight look like the following:
I spent a while wondering why it wouldn't realise I had the gsnap in my plugin folder. Also if you have audacity 1.3 up you dont need the VST enabler that some of the posts were about. It doesn't hurt if you have got it in there though.
xargs -P can help parallelize gsnap invocation to levels, where nproc tells it the number of processing units available to the current process (which may be less than the number of online processors).