{"id":424,"date":"2018-09-26T16:41:55","date_gmt":"2018-09-26T15:41:55","guid":{"rendered":"http:\/\/ri.itservices.manchester.ac.uk\/csf3\/?page_id=424"},"modified":"2025-05-02T17:31:19","modified_gmt":"2025-05-02T16:31:19","slug":"relion","status":"publish","type":"page","link":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/software\/applications\/relion\/","title":{"rendered":"Relion"},"content":{"rendered":"<h2>Overview<\/h2>\n<p><a href=\"http:\/\/www2.mrc-lmb.cam.ac.uk\/relion\/index.php\/Main_Page\">Relion<\/a> is program that employs an empirical Bayesian approach to refinement of (multiple) 3D reconstructions or 2D class averages in electron cryo-microscopy (cryo-EM). It is developed in the group of <a href=\"http:\/\/www2.mrc-lmb.cam.ac.uk\/groups\/scheres\/\">Sjors Scheres<\/a> at the <a href=\"http:\/\/www2.mrc-lmb.cam.ac.uk\/\">MRC Laboratory of Molecular Biology<\/a>.<\/p>\n<p>Version 5.0 is installed on CSF3. It has been  compiled from source using the Intel v19.1.1 compiler and OpenMPI 4.1.1. Currently only the GPU version has been compiled. The Relion user-interface has been enabled. <\/p>\n<p>Versions 3.0.6, 3.0.8, 3.1-beta, 3.1-beta2 and 3.1.0 are installed on CSF3. They have been compiled from source using the Intel v18.0.3 compilers and OpenMPI 3.1.4. Versions are available for CPU-only usage (with and without CPU Acceleration functions compiled) and GPU (Nvidia v100) usage. All versions have been compiled with the Relion user-interface enabled.<\/p>\n<p>Older versions 2.1 and 3.0-beta are also installed. They have been compiled from source using the Intel v17.0.7 compilers and OpenMPI 3.1.1. Versions are available for CPU-only usage (non accelerated) and GPU (Nvidia v100) usage. All versions have been compiled with the Relion user-interface enabled.<\/p>\n<p>Some of the CPU-only versions use the Relion-accelerated CPU code compiled with Intel Compiler multiple code-path optimizations for AVX, AVX2 and AVX512 architectures. This means the application can be run on any of the CSF3 compute nodes and some functions will use optimized versions for the CPU in that compute node.<\/p>\n<h2>Restrictions on use<\/h2>\n<p>There are no restrictions on accessing this software on the CSF. The software is released under the GNU GPL v2 license. The authors request you cite the use of the software in your publications &#8211; please see <a href=\"http:\/\/www2.mrc-lmb.cam.ac.uk\/relion\/index.php\/Main_Page\">the Relion website<\/a> for details.<\/p>\n<h2>Set up procedure<\/h2>\n<p>To access the software you must first load <strong>one<\/strong> of the following modulefiles, according to whether you wish to run on CPU-only or GPU nodes:<\/p>\n<h3>5.0.0 version<\/h3>\n<p>This version has been compiled with the Intel 19.1.2 compiler.<\/p>\n<pre>\r\n# Released 5.0.0 version\r\nmodule load apps\/intel-19.1\/relion\/5.0.0-gpu-sp-all        # Single-precision GPU\r\n\r\n<\/pre>\n<p>The modulefile <code>apps\/intel-19.1\/relion\/<em>VERSION<\/em>-<em>ARCH<\/em><strong>-all<\/strong><\/code> is a convenience modulefile to load several other modulefile that you will usually need to use relion successfully. It will load the following modulefiles:<\/p>\n<pre>\r\napps\/intel-19.1\/relion\/<em>VERSION<\/em>-<em>ARCH<\/em>      # Matches the version in the -all name\r\napps\/intel-19.1\/ctffind\/4.1.14           # ctffind3 is also available on the CSF3\r\napps\/intel-19.1\/unblur\/1.0.2\r\napps\/intel-19.1\/summovie\/1.0.2\r\napps\/binapps\/gctf\/1.06\r\n<\/pre>\n<h3>3.1.0 versions<\/h3>\n<p>This version has been compiled with the Intel 18.0.3 compiler.<\/p>\n<pre>\r\n# NOTE: Currently the CSF3 will only do single-node multi-core CPU and GPU jobs. You cannot\r\n#       run larger multi-node jobs.\r\n\r\n# Released 3.1.0 version\r\nmodule load apps\/intel-18.0\/relion\/3.1.0-gpu-sp-all         # Single-precision GPU\r\nmodule load apps\/intel-18.0\/relion\/3.1.0-cpuacc-sp-all      # Single-precision CPU-Accelerated\r\nmodule load apps\/intel-18.0\/relion\/3.1.0-cpu-sp-all         # Single-precision CPU\r\n<\/pre>\n<p>The modulefile <code>apps\/intel-18.0\/relion\/<em>VERSION<\/em>-<em>ARCH<\/em><strong>-all<\/strong><\/code> is a convenience modulefile to load several other modulefile that you will usually need to use relion successfully. It will load the following modulefiles:<\/p>\n<pre>\r\napps\/intel-18.0\/relion\/<em>VERSION<\/em>-<em>ARCH<\/em>      # Matches the version in the -all name\r\napps\/intel-18.0\/ctffind\/4.1.13           # ctffind3 is also available on the CSF3\r\napps\/intel-18.0\/unblur\/1.0.2\r\napps\/intel-18.0\/summovie\/1.0.2\r\napps\/binapps\/gctf\/1.06\r\n<\/pre>\n<p>If you wish to use a different version of the external tools than that provided by the <code>-all<\/code> modulefile then load the modulefile <em>without<\/em> the <code>-all<\/code> in the name and then load the individual modulefiles needed for each external tool.<\/p>\n<h3>3.1 beta versions<\/h3>\n<details>\n<summary class=\"h4\">More info&#8230;<\/summary>\n<p>This version has been compiled with the Intel 18.0.3 compiler.<\/p>\n<pre>\r\n# NOTE: Currently the CSF3 will only do single-node multi-core CPU and GPU jobs. You cannot\r\n#       run larger multi-node jobs.\r\n\r\n# A new build of the 3.1-beta source (includes relion_convert_to_tiff[_mpi]). Commit 06afb9f.\r\nmodule load apps\/intel-18.0\/relion\/3.1-beta<strong>2<\/strong>-gpu-sp-all     # Single-precision GPU \r\nmodule load apps\/intel-18.0\/relion\/3.1-beta<strong>2<\/strong>-cpuacc-sp-all  # Single-precision CPU-Accelerated\r\nmodule load apps\/intel-18.0\/relion\/3.1-beta<strong>2<\/strong>-cpu-sp-all     # Single-precision CPU\r\n\r\n# Older build of the 3.1-beta source. Commit 7f8d1d6.\r\nmodule load apps\/intel-18.0\/relion\/3.1-beta-gpu-sp-all      # Single-precision GPU\r\nmodule load apps\/intel-18.0\/relion\/3.1-beta-cpuacc-sp-all   # Single-precision CPU-Accelerated\r\nmodule load apps\/intel-18.0\/relion\/3.1-beta-cpu-sp-all      # Single-precision CPU\r\n<\/pre>\n<p>The modulefile <code>apps\/intel-18.0\/relion\/<em>VERSION<\/em>-<em>ARCH<\/em><strong>-all<\/strong><\/code> is a convenience modulefile to load several other modulefile that you will usually need to use relion successfully. It will load the following modulefiles:<\/p>\n<pre>\r\napps\/intel-18.0\/relion\/<em>VERSION<\/em>-<em>ARCH<\/em>      # Matches the version in the -all name\r\napps\/intel-18.0\/ctffind\/4.1.13           # ctffind3 is also available on the CSF3\r\napps\/intel-18.0\/unblur\/1.0.2\r\napps\/intel-18.0\/summovie\/1.0.2\r\napps\/binapps\/gctf\/1.06\r\n<\/pre>\n<p>If you wish to use a different version of the external tools than that provided by the <code>-all<\/code> modulefile then load the modulefile <em>without<\/em> the <code>-all<\/code> in the name and then load the individual modulefiles needed for each external tool.<br \/>\n<\/details>\n<h3>3.0.8 version<\/h3>\n<p>This version has been compiled with the Intel 18.0.3 compiler.<\/p>\n<details>\n<summary class=\"h4\">More info&#8230;<\/summary>\n<pre>\r\n# NOTE: Currently the CSF3 will only do single-node multi-core CPU and GPU jobs. You cannot\r\n#       run larger multi-node jobs.\r\nmodule load apps\/intel-18.0\/relion\/3.0.8-gpu-sp-all      # Single-precision GPU\r\nmodule load apps\/intel-18.0\/relion\/3.0.8-cpuacc-sp-all   # Single-precision CPU-Accelerated\r\nmodule load apps\/intel-18.0\/relion\/3.0.8-cpu-sp-all      # Single-precision CPU\r\n<\/pre>\n<p>The modulefile <code>apps\/intel-18.0\/relion\/3.0.8-<em>ARCH<\/em>-all<\/code> loads:<\/p>\n<pre>\r\napps\/intel-18.0\/relion\/3.0.8-<em>ARCH<\/em>      # Matches the version in the -all name\r\napps\/intel-18.0\/ctffind\/4.1.13         # ctffind3 is also available on the CSF3\r\napps\/intel-18.0\/unblur\/1.0.2\r\napps\/intel-18.0\/summovie\/1.0.2\r\napps\/binapps\/gctf\/1.06\r\n<\/pre>\n<p>If you wish to use a different version of the external tools than that provided by the <code>-all<\/code> modulefile then load the modulefile <em>without<\/em> the <code>-all<\/code> in the name and then load the individual modulefiles needed for each external tool.<br \/>\n<\/details>\n<h3>3.0.6 version<\/h3>\n<p>This version has been compiled with the Intel 18.0.3 compiler.<\/p>\n<details>\n<summary class=\"h4\">More info&#8230;<\/summary>\n<pre>\r\n# NOTE: Currently the CSF3 will only do single-node multi-core CPU and GPU jobs. You cannot\r\n#       run larger multi-node jobs.\r\nmodule load apps\/intel-18.0\/relion\/3.0.6-gpu-sp-all      # Single-precision GPU code\r\n<\/pre>\n<p>The modulefile <code>apps\/intel-18.0\/relion\/3.0.6-gpu-sp-all<\/code> loads:<\/p>\n<pre>\r\napps\/intel-18.0\/relion\/3.0.6-gpu-sp      # Matches the version in the -all name\r\napps\/intel-18.0\/ctffind\/4.1.13           # ctffind3 is also available on the CSF3\r\napps\/intel-18.0\/unblur\/1.0.2\r\napps\/intel-18.0\/summovie\/1.0.2\r\napps\/binapps\/gctf\/1.06\r\n<\/pre>\n<p>If you wish to use a different version of the external tools than that provided by the <code>-all<\/code> modulefile then load the modulefile <em>without<\/em> the <code>-all<\/code> in the name and then load the individual modulefiles needed for each external tool.<br \/>\n<\/details>\n<h3>3.0-beta version<\/h3>\n<p>This version has been compiled with the Intel 17.0.7 compiler.<\/p>\n<details>\n<summary class=\"h4\">More info&#8230;<\/summary>\n<pre>\r\n# NOTE: Currently the CSF3 will only do single-node multi-core CPU and GPU jobs. You cannot\r\n#       run larger multi-node jobs.\r\n\r\n# Version 3.0-beta CPU-only + default external tools (see below) - RECOMMENDED\r\nmodule load apps\/intel-17.0\/relion\/3.0-beta-cpu-dp-all     # Double-precision CPU-only code\r\nmodule load apps\/intel-17.0\/relion\/3.0-beta-cpu-sp-all     # Single-precision CPU-only code\r\n\r\n# ... as above without default external tools\r\nmodule load apps\/intel-17.0\/relion\/3.0-beta-cpu-dp\r\nmodule load apps\/intel-17.0\/relion\/3.0-beta-cpu-sp\r\n\r\n# Version 3.0-beta GPU (nvidia v100) + default external tools (see below) - RECOMMENDED\r\nmodule load apps\/intel-17.0\/relion\/3.0-beta-gpu-dp-all      # Double-precision GPU code\r\nmodule load apps\/intel-17.0\/relion\/3.0-beta-gpu-sp-all      # Single-precision GPU code\r\n\r\n# ... as above without default external tools\r\nmodule load apps\/intel-17.0\/relion\/3.0-beta-gpu-dp\r\nmodule load apps\/intel-17.0\/relion\/3.0-beta-gpu-sp\r\n\r\n# Version 2.1 CPU and GPU\r\nmodule load apps\/intel-17.0\/relion\/2.1-cpu                  # CPU-only\r\nmodule load apps\/intel-17.0\/relion\/2.1-gpu-dp               # Double-precision GPU code\r\nmodule load apps\/intel-17.0\/relion\/2.1-gpu-sp               # Single-precision GPU code\r\n<\/pre>\n<p>The modulefiles with <code>-all<\/code> in their name are helper modulefiles which simply load the main relion modulefile (for the corresponding version) and the modulefiles for the external tools used by relion. To see what is loaded run:<\/p>\n<pre>\r\nmodule show  apps\/intel-17.0\/relion\/3.0-beta-cpu-dp-all\r\n<\/pre>\n<p>The modulefile <code>apps\/intel-17.0\/relion\/3.0-beta-cpu-dp-all<\/code> loads:<\/p>\n<pre>\r\napps\/intel-17.0\/relion\/3.0-beta-cpu-sp      # Matches the version in the -all name\r\napps\/intel-17.0\/ctffind\/4.1.10              # ctffind3 is also available on the CSF3\r\napps\/intel-17.0\/unblur\/1.0.2\r\napps\/intel-17.0\/summovie\/1.0.2\r\napps\/binapps\/gctf\/1.06\r\n<\/pre>\n<p>If you wish to use a different version of the external tools than that provided by the <code>-all<\/code> modulefile then load the modulefile <em>without<\/em> the <code>-all<\/code> in the name and then load the individual modulefiles needed for each external tool.<br \/>\n<\/details>\n<p>All modulefiles will also load automatically the compiler and MPI modulefiles for you.<\/p>\n<h2>Running the application<\/h2>\n<p>Relion can be run with a GUI on the login node. This is mainly used to select input files and set up job parameters. The GUI will then submit your job to the batch queues.<\/p>\n<p>Users must <em>always<\/em> run the main processing in <strong>batch<\/strong> (where the GUI permits submission to the batch system), never directly on the login node. This requires correct settings in the GUI, as instructed below. <\/p>\n<p>Relion tools other than the GUI found running on the login node will be terminated <em>without warning<\/em>.<\/p>\n<p>Please note, a tutorial on using Relion to process your data is beyong the scope of this page, which only describes how to run the application on the CSF. Please follow the <a href=\"http:\/\/www2.mrc-lmb.cam.ac.uk\/groups\/scheres\/relion13_tutorial.pdf\">Relion Turorial (pdf)<\/a> on the Relion website if you are new to the software.<\/p>\n<h3>Running the GUI<\/h3>\n<p>Once the modulefile file is loaded you should navigate to your Relion project directory (this is important &#8211; it will usually contain a <code>Micrographs<\/code> subdirectory) and then run <code>relion<\/code> on the login node. For example:<\/p>\n<pre>\r\ncd ~\/scratch\/my_relion_project\/\r\nrelion\r\n<\/pre>\n<p>It will display the following GUI (click on image to enlarge):<br \/>\n<a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-general.png\"><img decoding=\"async\" src=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-general.png\" alt=\"Relion main user interface\" width=\"500\" class=\"size-full wp-image-432\" srcset=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-general.png 804w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-general-300x196.png 300w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-general-768x501.png 768w\" sizes=\"(max-width: 804px) 100vw, 804px\" \/><\/a><\/p>\n<p>Various operations can be performed by selecting from the list on the left hand side (Micrograph inspection, CTF estimation and so on). These operations allow you to specify use of the batch system, as detailed below.<\/p>\n<p>Note: To re-activate a greyed-out <code>Run<\/code> button, press <code>Alt+R<\/code> in the GUI.<\/p>\n<h3>Using the GUI to run in Batch<\/h3>\n<p>Each Relion processing operation (Micrograph inspection, CTF estimation etc) has a <em>Running<\/em> tab in its GUI page. There are three possible types of <em>Running<\/em> tab:<\/p>\n<ol class=\"gaplist\">\n<li>Greyed-out (e.g., select <em>Import<\/em> from the list). This operation does not require the batch system:<br \/>\n<a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-import-red.png\"><img decoding=\"async\" src=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-import-red.png\" alt=\"Relion greyed out batch options\" width=\"500\" class=\"alignnone size-full wp-image-438\" srcset=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-import-red.png 804w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-import-red-300x191.png 300w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-import-red-768x489.png 768w\" sizes=\"(max-width: 804px) 100vw, 804px\" \/><\/a><\/li>\n<li>Active for MPI job (e.g., select <em>CTF estimation<\/em> from the list). This operation will generate a batch script and submit it:<br \/>\n<a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-ctfest-running-batch-red.png\"><img decoding=\"async\" src=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-ctfest-running-batch-red.png\" alt=\"Relion MPI batch options\" width=\"500\" class=\"alignnone size-full wp-image-439\" srcset=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-ctfest-running-batch-red.png 804w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-ctfest-running-batch-red-300x191.png 300w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-ctfest-running-batch-red-768x489.png 768w\" sizes=\"(max-width: 804px) 100vw, 804px\" \/><\/a><br \/>\nThe options should be set as follows:<\/p>\n<ul class=\"nogaplist\">\n<li>Number of MPI procs: 1 for serial jobs, 2-32 for single-node jobs using Intel compute nodes (see <strong>Queue name<\/strong> below), 2-168 for single-node jobs using AMD compute nodes (see <strong>Queue name<\/strong> below). We recommend using single-node, 2-32 cores initially. If using a GPU node you <em>must<\/em> use <code>smp.pe<\/code> and between 2-8 CPU cores <em>per v100 GPU<\/em> or 2-12 CPU cores <em>per A100 GPU<\/em>. Hence if, for example you request 2 v100 GPUs you can request up to 16 CPU cores in <code>smp.pe<\/code>.<\/li>\n<li><strong>Submit to queue?<\/strong>: You <strong>must<\/strong> set this to <strong>Yes<\/strong>. If you fail to do this your job will run on the login node and will be killed by the sysadmins. <em>Users found repeatedly forgetting to turn on the Submit to queue option will be banned from using this software.<\/em><\/li>\n<li><strong>Queue name<\/strong>: Use <code>smp.pe<\/code> for single node jobs (2-32 cores) on Intel compute nodes or <code>amd.pe<\/code> for single node jobs (2-168 cores) on AMD compute nodes.<\/li>\n<li>If using the GPU version: GPU node flag: Use <code>v100=<em>N<\/em><\/code> OR <code>a100=<em>N<\/em><\/code> where <code><em>N<\/em><\/code> is the number of required GPUs. This should be between 1 and 4 depending on your granted access to the GPU nodes (permission to use the GPUs <a href=\"\/csf3\/batch\/gpu-jobs\">must be requested<\/a> &#8211; without the appropriate settings applied to your CSF account by the sysadmins, GPU jobs will not run.) For the Queue name, you <em>must<\/em> use <code>smp.pe<\/code> and between 2-8 CPU cores <em>per v100 GPU<\/em> or 2-12 CPU cores <em>per A100 GPU<\/em>.<\/li>\n<li>Queue submit command: leave as <code>qsub<\/code><\/li>\n<li>Standard submission script: leave as\n<pre>\/opt\/apps\/apps\/intel-<em>XY.Z<\/em>\/relion\/<em>version<\/em>\/bin\/relion_qsub.sh<\/pre>\n<\/li>\n<li>Additional arguments: leave blank<\/li>\n<\/ul>\n<\/li>\n<li>Active for MPI+OpenMP job (e.g., select <em>2D classification<\/em> from the list). This operation will generate a batch script and submit it:<br \/>\n<a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-red.png\"><img decoding=\"async\" src=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-red.png\" alt=\"Relion MPI and OpenMP batch options\" width=\"500\" class=\"alignnone size-full wp-image-440\" srcset=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-red.png 804w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-red-300x191.png 300w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-red-768x489.png 768w\" sizes=\"(max-width: 804px) 100vw, 804px\" \/><\/a><br \/>\nThe options should be set as follows:<\/p>\n<ul class=\"nogaplist\">\n<li>Number of MPI procs: 1 for serial jobs, 2-32 for single-node jobs using Intel compute nodes (see <strong>Queue name<\/strong> below), 2-168 for single-node jobs using AMD compute nodes (see <strong>Queue name<\/strong> below). We recommend using single-node, 2-32 cores initially. If using a GPU node you <em>must<\/em> use <code>smp.pe<\/code> and between 2-8 CPU cores <em>per v100 GPU<\/em> or 2-12 CPU cores <em>per A100 GPU<\/em>. Hence if, for example you request 2 v100 GPUs you can request up to 16 CPU cores in <code>smp.pe<\/code>.<\/li>\n<li>Number of threads: you can leave as 1 or specify the number of threads each MPI process will use. Note that in Relion v3.0.6, 3.0.8 and 3.1-beta (and later) the number of cores requested by the batch script will be <em>Num MPI Procs X num threads<\/em>. For example if you request 2 MPI processes with each one running 4 threads, the jobscript will correctly request 8 cores for the batch job. In versions installed before 3.0.6, you must load an extra modulefile named:\n<pre>apps\/intel-17.0\/relion\/corestest<\/pre>\n<p> for the correct number of cores to be calculated if you request more than one thread.<\/li>\n<li><strong>Submit to queue?<\/strong>: You <strong>must<\/strong> set this to <strong>Yes<\/strong>. If you fail to do this your job will run on the login node and will be killed by the sysadmins. <em>Users found repeatedly forgetting to turn on the Submit to queue option will be banned from using this software.<\/em><\/li>\n<li><strong>Queue name<\/strong>: Use <code>smp.pe<\/code> for single node jobs (2-32 cores) on Intel compute nodes or <code>amd.pe<\/code> for single node jobs (2-168 cores) on AMD compute nodes.<\/li>\n<li>If using the GPU version: GPU node flag: Use <code>v100=<em>N<\/em><\/code> OR <code>a100=<em>N<\/em><\/code> where <code><em>N<\/em><\/code> is the number of required GPUs. This should be between 1 and 4 depending on your granted access to the GPU nodes (permission to use the GPUs <a href=\"\/csf3\/batch\/gpu-jobs\">must be requested<\/a> &#8211; without the appropriate settings applied to your CSF account by the sysadmins, GPU jobs will not run.) For the Queue name, you <em>must<\/em> use <code>smp.pe<\/code> and between 2-8 CPU cores <em>per v100 GPU<\/em> or 2-12 CPU cores <em>per A100 GPU<\/em>.<\/li>\n<li>Queue submit command: leave as <code>qsub<\/code><\/li>\n<li>Standard submission script: leave as\n<pre>\/opt\/apps\/apps\/intel-<em>XY.Z<\/em>\/relion\/<em>version<\/em>\/bin\/relion_qsub.sh<\/pre>\n<\/li>\n<li>Additional arguments: leave blank<\/li>\n<\/ul>\n<\/li>\n<li>If using multiple GPUs you must also specify how many GPUs to use and also <em>which <\/em>GPUs to use. This is done via the <em>Running<\/em> tab and the <em>Compute<\/em> tab. For example, suppose you wish to use all 4 GPUs on a node, first you need to request this many GPUs:<br \/>\n<a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-miltigpu-red-1.png\"><img decoding=\"async\" src=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-miltigpu-red-1.png\" alt=\"Specify how many GPUs to use\" width=\"500\" class=\"alignnone size-full wp-image-4110\" srcset=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-miltigpu-red-1.png 808w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-miltigpu-red-1-300x189.png 300w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-running-batch-miltigpu-red-1-768x485.png 768w\" sizes=\"(max-width: 808px) 100vw, 808px\" \/><\/a><br \/>\nYou must then indicate the GPU ids to use on the <em>Compute<\/em> tab.<br \/>\n<a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-compute-which-gpu-red.png\"><img decoding=\"async\" src=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-compute-which-gpu-red.png\" alt=\"Specify which GPUs to use\" width=\"500\" class=\"alignnone size-full wp-image-4108\" srcset=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-compute-which-gpu-red.png 808w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-compute-which-gpu-red-300x189.png 300w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/relion-2Dclass-compute-which-gpu-red-768x485.png 768w\" sizes=\"(max-width: 808px) 100vw, 808px\" \/><\/a><br \/>\nThe GPU IDs should always begin with <code>0<\/code> and further GPUs can be added by separating the IDs with colons. For example, if using two GPUs you would specify <code>0:1<\/code>. These IDs will be mapped to the physical GPUs assigned to your job.<\/li>\n<\/ol>\n<h3>Submitting the Batch Job from the GUI<\/h3>\n<p>Once you have set the <em>Running<\/em> tab options as indicated above press the <code>Run!<\/code> button to submit an auto-generated jobscript to the batch system. It may appear that nothing has happened when you do this. However, you should check on the job using the usual <code>qstat<\/code> command by running it in a command-line window on the CSF. It will report whether your job is queued or running. If you see no output then you job has finished (either successfully or because an error occurred).<\/p>\n<p>The auto-generated jobscript will be written to your current directory (your Relion project directory) and will be named similar to the operation being performed with a <code>.script<\/code> extension. For example:<\/p>\n<pre>\r\nrun_ctffind_submit.script\r\n<\/pre>\n<p>The usual output and error output from the job will be written to files with <code>.out<\/code> and <code>.err<\/code> extensions respectively. You should check these for further information about your job. For example:<\/p>\n<pre>\r\nrun_ctffind.out\r\nrun_ctffind.err\r\n<\/pre>\n<h3>Summary<\/h3>\n<ul>\n<li>Where the <em>Running<\/em> panel is active, ensure you set the <em>Submit to Queue<\/em> option to be <em>Yes<\/em>.<\/li>\n<li>Select the number of MPI procs to use.<\/li>\n<li>If available, the number of threads specifies how many threads each MPI process will use. The batch job will request <em>num MPI proc X num threads<\/em> cores in the batch system.<\/li>\n<li>Set the <em>Queue Name<\/em> so be <em>smp.pe<\/em> or <em>amd.pe<\/em>.\n<li>Pressing the <em>Run!<\/em> button will submit an auto-generated jobscript to the batch system.<\/li>\n<li>Check on your job by running <code>qstat<\/code> in a terminal window on the CSF.<\/li>\n<\/ul>\n<h2>Advanced: Custom Batch Script Template<\/h2>\n<p>This section is for advanced users familiar with Relion and the CSF batch system. In most cases the default settings will work for you and you should not need to follow this section.<\/p>\n<p>Relion auto-generates jobscripts by filling in place-holders in a <em>qsub template file<\/em> named <code>relion_qsub.sh<\/code>. It is possible for you to take a copy of this file, modify it and have Relion use your new template each time you submit a job via the Relion GUI. The following steps are required:<\/p>\n<ol>\n<li>Exit Relion if the GUI is currently running<\/li>\n<li>Copy the system-wide template file (for example in to a directory in your home area):\n<pre>\r\ncp $RELION_QSUB_TEMPLATE ~\/my_relion_project\/\r\n<\/pre>\n<\/li>\n<li>Edit the template (see below for more information):\n<pre>\r\ngedit ~\/my_relion_project\/qsub.sh\r\n<\/pre>\n<\/li>\n<li>Update the environment setting indicating where the template file is:\n<pre>\r\nexport RELION_QSUB_TEMPLATE=~\/my_relion_project\/qsub.sh\r\n<\/pre>\n<\/li>\n<li>Restart Relion:\n<pre>\r\nrelion\r\n<\/pre>\n<\/li>\n<\/ol>\n<p>The default template file contains:<\/p>\n<pre>\r\n#!\/bin\/bash\r\n### Requests XXXcoresXXX in batch which is number of mpiprocs X threads\r\n#$ -pe XXXqueueXXX XXXcoresXXX\r\n#$ -e XXXerrfileXXX\r\n#$ -o XXXoutfileXXX\r\n#$ -cwd\r\n#$ -V\r\n#$ -l \"XXXextra1XXX\"         # If using the GPU version will request v100 GPUs\r\n                             # If using the CPU version, can be blank (\"\") or\r\n                             # can request an CPU architecture (e.g., skylake)\r\n\r\nmpiexec -n XXXmpinodesXXX  XXXcommandXXX\r\n<\/pre>\n<p>The <code>XXX.....XXX<\/code> keywords are the place-holders that will be replaced with the settings you specify in the Relion GUI. You should leave the <code>-pe<\/code> setting as is. However, you may wish to add other <a href=\/csf3\/batch\/qsub-options\/\">CSF options<\/a> such as<\/p>\n<pre>\r\n#$ -m ea                           # Email me when job ends or aborts\r\n#$ -M &#109;&#x79;&#x2e;&#101;&#x6d;&#x61;&#105;&#x6c;&#x40;&#109;&#x61;&#x6e;&#99;&#x68;&#x65;&#115;&#x74;&#x65;&#114;&#x2e;&#x61;&#99;&#x2e;&#x75;&#107;    # You must supply an email address\r\n<\/pre>\n<p>Alternatively you may want to add other commands to the jobscript, for example:<\/p>\n<pre>\r\n# Report the date before running\r\ndate\r\nmpiexec -n XXXmpinodesXXX  XXXcommandXXX\r\n<\/pre>\n<h2>Advanced: Hand-crafting Jobscripts<\/h2>\n<p>If you wish to submit a batch job <em>manually<\/em> from the command-line (using your own batch script) in the traditional CSF manner, then you can ask Relion to display the command it will use in its auto-generated jobscript. <\/p>\n<p>Start the Relion GUI, select the operation to perform (e.g., 2D Classification), select the <em>Running<\/em> tab, make any changes to the settings then press the <code>Print command<\/code> button to display in your shell window what Relion uses in its jobscript. <\/p>\n<p>For example, the following is displayed for the <em>2D Classification example above<\/em>:<\/p>\n<pre>\r\n`which relion_refine_mpi` --o Class2D\/run1 --i particles.star \\\r\n --dont_combine_weights_via_disc --preread_images --pool 1000 --pad 2 --ctf  \\\r\n --iter 25 --tau2_fudge 2 --particle_diameter 275 --fast_subsets --K 200 \\\r\n --flatten_solvent  --zero_mask --strict_highres_exp 25 --oversampling 1 \\\r\n --psi_step 12 --offset_range 5 --offset_step 4 --norm --scale --j 1 <strong>--gpu<\/strong>\r\n                                                                 #     #\r\n                                                                 #     # Using the GPU version\r\n                                                                 #\r\n                                                                 # Number of threads\r\n<\/pre>\n<p>Hence you can write your own jobscript to run this command. Ensure that you add the usual <code>mpirun<\/code> command and specify the correct number of cores. For example:<\/p>\n<pre>\r\n#!\/bin\/bash\r\n#$ -cwd                  # Run from current directory\r\n#$ -V                    # Inherit modulefile settings\r\n#$ -pe smp.pe 8          # We'll use 8 cores (single-node). Can be 2-32. Remove line for serial job.\r\n                         # If using a GPU (see next flag) can be up to max 8 <em>per<\/em> v100 GPU.\r\n                         # For example, you can specify up to 16 cores if using 2 GPUs.\r\n\r\n# Add this line if using the GPU version\r\n#$ -l v100=1             # Number of GPUs (1-4) depending on access granted\r\n                         # Or use a100=1 for the A100 GPUs\r\n\r\n# If using the GPU node fast temporary storage, copy dataset to it. EG:\r\ncp -r ~\/scratch\/<em>my_em_data_dir<\/em> $TMPDIR\r\n\r\n# We must add the usual mpirun command as used in many CSF jobscripts\r\n<strong>mpirun -n $NSLOTS<\/strong> `which relion_refine_mpi` --o Class2D\/run1 --i particles.star \\\r\n  --dont_combine_weights_via_disc --preread_images --pool 1000 --pad 2  --ctf  \\\r\n  --iter 25 --tau2_fudge 2 --particle_diameter 275 --fast_subsets  --K 200 \\\r\n  --flatten_solvent  --zero_mask  --strict_highres_exp 25 --oversampling 1 \\\r\n  --psi_step 12 --offset_range 5 --offset_step 4 --norm --scale --j 1 <strong>--gpu<\/strong>\r\n                                                                  #    #\r\n                                                                  #    # Using the GPU version\r\n                                                                  #\r\n                                                                  # Number of threads\r\n\r\n# Note: Files copied to $TMPDIR (fast node-local storage) will be deleted automatically\r\n# at the end of your job.\r\n<\/pre>\n<p>Notice that we have added <code>mpirun -n $NSLOTS<\/code> to the start of the command that Relion reported. Relion will automatically add this when it auto-generates a jobscript.<\/p>\n<p>You should then submit your jobscript using the usual <code>qsub<\/code> command:<\/p>\n<pre>\r\nqsub <em>myjobscript<\/em>\r\n<\/pre>\n<p>where <em>myjobscript<\/em> is the name of your jobscript.<\/p>\n<h2>Further info<\/h2>\n<ul>\n<li><a href=\"http:\/\/www2.mrc-lmb.cam.ac.uk\/relion\/index.php\/Main_Page\">Relion website<\/a><\/li>\n<\/ul>\n<h2>Updates<\/h2>\n<p>None.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview Relion is program that employs an empirical Bayesian approach to refinement of (multiple) 3D reconstructions or 2D class averages in electron cryo-microscopy (cryo-EM). It is developed in the group of Sjors Scheres at the MRC Laboratory of Molecular Biology. Version 5.0 is installed on CSF3. It has been compiled from source using the Intel v19.1.1 compiler and OpenMPI 4.1.1. Currently only the GPU version has been compiled. The Relion user-interface has been enabled. Versions.. <a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/software\/applications\/relion\/\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":86,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-424","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/424","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/comments?post=424"}],"version-history":[{"count":20,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/424\/revisions"}],"predecessor-version":[{"id":9692,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/424\/revisions\/9692"}],"up":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/86"}],"wp:attachment":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/media?parent=424"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}