{"id":3740,"date":"2019-08-02T16:46:41","date_gmt":"2019-08-02T15:46:41","guid":{"rendered":"http:\/\/ri.itservices.manchester.ac.uk\/csf3\/?page_id=3740"},"modified":"2022-07-11T11:06:15","modified_gmt":"2022-07-11T10:06:15","slug":"guppy","status":"publish","type":"page","link":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/software\/applications\/guppy\/","title":{"rendered":"Guppy"},"content":{"rendered":"

Overview<\/h2>\n

Guppy<\/a> is a data processing toolkit that contains the Oxford Nanopore Technologies’ basecalling algorithms, and several bioinformatic post-processing features. It can be run as a CPU-only app or on the GPUs in the CSF.<\/p>\n

Restrictions on use<\/h2>\n

Access to this software is highly restricted – currently only one research group has a license and you must be an approved member of that research group. Please ask the license holder to contact us requesting access for you. Use of the software will also require you to register with the Oxford Nanopore Community website<\/a>.<\/p>\n

Set up procedure<\/h2>\n

We now recommend loading modulefiles within your jobscript so that you have a full record of how the job was run. See the example jobscript below for how to do this. Alternatively, you may load modulefiles on the login node and let the job inherit these settings<\/abbr>.<\/p>\n

Load one of the following modulefiles:<\/p>\n

# GPU versions (the CUDA modulefile will be loaded automatically for you)\r\nmodule load apps\/binapps\/guppy\/6.1.7-gpu\r\nmodule load apps\/binapps\/guppy\/5.0.16-gpu\r\nmodule load apps\/binapps\/guppy\/5.0.7-gpu\r\nmodule load apps\/binapps\/guppy\/4.4.1-gpu\r\nmodule load apps\/binapps\/guppy\/4.0.14-gpu\r\nmodule load apps\/binapps\/guppy\/3.4.5-gpu\r\nmodule load apps\/binapps\/guppy\/3.1.5-gpu\r\n\r\n# CPU-only version\r\nmodule load apps\/binapps\/guppy\/6.1.7\r\nmodule load apps\/binapps\/guppy\/5.0.16\r\nmodule load apps\/binapps\/guppy\/5.0.7\r\nmodule load apps\/binapps\/guppy\/4.4.1\r\nmodule load apps\/binapps\/guppy\/4.0.14\r\nmodule load apps\/binapps\/guppy\/3.4.5\r\nmodule load apps\/binapps\/guppy\/3.1.5\r\n<\/pre>\n
Running the application<\/h2>\n
Please do not run Guppy on the login node. Jobs should be submitted to the compute nodes via batch.<\/p>\n
The following executables are available. You may run these with the --help<\/code> flag to obtain a list of accepted flags. However please note that the GPU versions must<\/em> be run on a GPU compute node – they will not run (even with just the --help<\/code> flag) on the login node because there is no GPU available there.<\/p>\n
guppy_aligner\r\nguppy_basecaller\r\nguppy_basecaller_1d2\r\nguppy_barcoder\r\n<\/pre>\n
Serial batch job submission<\/h3>\n
Create a batch submission script (which will load the modulefile in the jobscript), for example:<\/p>\n
#!\/bin\/bash --login\r\n#$ -cwd             # Job will run from the current directory\r\n                    # NO -V line - we load modulefiles in the jobscript\r\n\r\n# Load your required version (this is the CPU-only version)\r\nmodule load apps\/binapps\/guppy\/3.1.5\r\n\r\n# Example of using the guppy_basecaller. For a serial (1 core) job ensure\r\n# we only use one that with one basecaller.\r\nguppy_basecaller --cpu_threads_per_caller 1 --num_callers 1 \\\r\n     -i input path<\/em> -s save path<\/em> -c config file<\/em> \r\n<\/pre>\n
Submit the jobscript using:<\/p>\n
qsub scriptname<\/em><\/pre>\n
where scriptname<\/em> is the name of your jobscript.<\/p>\n
Parallel batch job submission<\/h3>\n
Create a batch submission script (which will load the modulefile in the jobscript), for example:<\/p>\n
#!\/bin\/bash --login\r\n#$ -cwd             # Job will run from the current directory\r\n#$ -pe smp.pe 8     # Number of cores. Can be 2--32.\r\n\r\n# Load your required version (this is the CPU-only version)\r\nmodule load apps\/binapps\/guppy\/3.1.5\r\n\r\n# Example of using the guppy_basecaller. For a parallel job ensure\r\n# the number of threads per basecaller X number of basecallers = $NSLOTS (the number of cores)\r\n#\r\n# In this example we request 8 cores so we'll use 4 cores per basecaller and 2 basecallers.\r\nguppy_basecaller --cpu_threads_per_caller 4 --num_callers 2 \\\r\n     -i input path<\/em> -s save path<\/em> -c config file<\/em> \r\n<\/pre>\n
Submit the jobscript using:<\/p>\n
qsub scriptname<\/em><\/pre>\n
where scriptname<\/em> is the name of your jobscript.<\/p>\n
GPU batch job submission<\/h3>\n
Create a batch submission script (which will load the modulefile in the jobscript), for example:<\/p>\n
#!\/bin\/bash --login\r\n#$ -cwd             # Job will run from the current directory\r\n#$ -pe smp.pe 8     # Number of cores. Can be up to 8 per GPU.\r\n#$ -l v100=1        # Number of GPUs\r\n\r\n# Load your required version (this is the GPU-enabled version)\r\nmodule load apps\/binapps\/guppy\/3.1.5-gpu\r\n\r\n# Example of using the guppy_basecaller. For a parallel job ensure\r\n# the number of threads per basecaller X number of basecallers = $NSLOTS (the number of cores)\r\n#\r\n# In this example we request 8 cores so we'll use 4 cores per basecaller and 2 basecallers.#\r\n# NOTE: You should adjust NUMRUNNERS<\/strong><\/em> to suit your needs.\r\nguppy_basecaller --gpu_runners_per_device NUMRUNNERS<\/strong><\/em> \\\r\n     --cpu_threads_per_caller 4 --num_callers 2 \\\r\n     -i input path<\/em> -s save path<\/em> -c config file<\/em> \r\n<\/pre>\n
Submit the jobscript using:<\/p>\n
qsub scriptname<\/em><\/pre>\n
where scriptname<\/em> is the name of your jobscript.<\/p>\n
Further info<\/h2>\n