{"id":375,"date":"2018-09-25T11:27:41","date_gmt":"2018-09-25T10:27:41","guid":{"rendered":"http:\/\/ri.itservices.manchester.ac.uk\/csf3\/?page_id=375"},"modified":"2026-07-20T17:53:20","modified_gmt":"2026-07-20T16:53:20","slug":"answers","status":"publish","type":"page","link":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/software\/applications\/answers\/","title":{"rendered":"ANSWERS"},"content":{"rendered":"<h2>Overview<\/h2>\n<p><a href=\"http:\/\/www.answerssoftwareservice.com\/\">ANSWERS<\/a> provides Monte Carlo software tools for nuclear criticality safety and reactor physics analysis.<\/p>\n<ul>\n<li>MCBEND 10a_ru1, 11a_ru0<\/li>\n<li>MONK 12b_ru0, 12b_ru_mpi, 10a_ru0, 10a_ru0_x64, 10b_ru0_x64<\/li>\n<li>WIMS 11a_dv10(serial), 11a_dv10(mpi)<\/li>\n<li>WIMS 11b_dv11(serial), 11a_dv11(mpi)<\/li>\n<li>WIMS 11b_dv14(mpi)<\/li>\n<li><del>VisualWorkshop 3b_ru0<\/del><\/li>\n<li><del>VisualWorkshop 4a_ru0<\/del><\/li>\n<li>VisualWorkshop 5a_ru0<\/li>\n<\/ul>\n<p>The following products are available upon request (we have not written modulefiles for these as they are rarely used. If you use them on Redqueen you may set up their environment manually. Please contact us if you require a modulefile for these products).<\/p>\n<ul>\n<li>MONK 9a_ru1<\/li>\n<li>WIMS 9a_ru1<\/li>\n<li>vista-ray3a ru0<\/li>\n<li>visage5a_ru0<\/li>\n<li>launchpad2a_ru0<\/li>\n<li>WimsBuilder 2a_ru0, 3a_ru0<\/li>\n<\/ul>\n<h2>Restrictions on use<\/h2>\n<p>Access to this software is restricted to a specific research group. Please <a href=\"\/csf3\/overview\/help\/\">contact us<\/a> for more information.<\/p>\n<h2>Set up procedure<\/h2>\n<p>To access the software you must first load <em>one<\/em> of the following modulefiles:<\/p>\n<pre>\r\n# MONK\r\nmodule load apps\/binapps\/answers\/monk\/12b_ru0_mpi     # 64bit parallel MPI version\r\nmodule load apps\/binapps\/answers\/monk\/12b_ru0         # 64bit serial version\r\nmodule load apps\/binapps\/answers\/monk\/10b_ru0_mpi     # 64bit parallel MPI version\r\nmodule load apps\/binapps\/answers\/monk\/10b_ru0         # 64bit serial version\r\nmodule load apps\/binapps\/answers\/monk\/10a_ru0_64bit   # 64bit parallel MPI version\r\n<strong>module load apps\/binapps\/answers\/monk\/10a_ru0         # <strong>32bit<\/strong> serial version (not recommended but works)<\/strong>\r\n\r\n# WIMS\r\nmodule load apps\/binapps\/answers\/wims\/11c_dv3_mpi     # 64bit parallel MPI version (restricted to a specific research group)\r\nmodule load apps\/binapps\/answers\/wims\/11b_dv14_mpi    # 64bit parallel MPI version\r\nmodule load apps\/binapps\/answers\/wims\/11b_dv11_mpi    # 64bit parallel MPI version\r\nmodule load apps\/binapps\/answers\/wims\/11b_dv11        # 64bit serial version\r\nmodule load apps\/binapps\/answers\/wims\/11a_dv10_mpi    # 64bit parallel MPI version\r\nmodule load apps\/binapps\/answers\/wims\/11a_dv10        # 64bit serial version\r\nmodule load apps\/binapps\/answers\/wims\/10a_ru0         # <strong>32bit<\/strong> serial version (not recommended but works)\r\n\r\n# VisualWorkshop\r\n# See below.\r\n<\/pre>\n<h3>VisualWorkshop<\/h3>\n<p>This application should be run as an <em>interactive<\/em> job (see below for more details.) You should load the modulefile on the login node.<\/p>\n<pre>\r\nmodule load apps\/binapps\/answers\/visualworkshop\/5a\r\n  #\r\n  # You will also need to load the modulefile for the sim tool that you wish to run\r\n  # from inside VisualWorkshop. For example, if you intend to run WIMS then please\r\n  # load the required wims modulefile. See above.\r\n\r\n<strong>\r\n# NO LONGER WORKS ON CSF3\r\nmodule load apps\/binapps\/answers\/visualworkshop\/3b\r\nmodule load apps\/binapps\/answers\/visualworkshop\/3a\r\n<\/strong>\r\n<\/pre>\n<h2>Nuclear Data Libraries<\/h2>\n<p>Various nuclear data libraries are available in the directory given by the environment variable:<\/p>\n<pre>$ANSWERS_DATA\r\n<\/pre>\n<p>For example, to see what is available, run:<\/p>\n<pre>ls $ANSWERS_DATA\r\n<\/pre>\n<p>You can use the <code>$ANSWERS_DATA<\/code> in your jobscripts (see below for examples).<\/p>\n<h2>Manuals<\/h2>\n<p>After loading a modulefile you can access the software manuals in the installation area. Use the <code>evince<\/code> command to read PDF manuals on the CSF login node.<\/p>\n<pre>\r\n$ ls $ANSWERS_HOME\/manuals\r\n$ evince $ANSWERS_HOME\/manuals\/getting_started.pdf >\/dev\/null 2>&1&\r\n<\/pre>\n<h2>Running the applications<\/h2>\n<p>Please do not run MONK or WIMS on the login node. Jobs should be submitted to the compute nodes via batch.<\/p>\n<p>VisualWorkshop will only run if the <code>srun<\/code> interactive session can be scheduled by the system (i.e., if there is a free core available in the interactive area).<\/p>\n<h2>VisualWorkshop (GUI)<\/h2>\n<p>Load the appropriate modulefile (see above) then use <code>srun<\/code> to launch the VisualWorkshop GUI on a compute node. For example:<\/p>\n<pre>\r\n# On the login node\r\nmodule load apps\/binapps\/answers\/visualworkshop\/5a\r\n\r\n# Also load the the sim tool you wish to run from within VisualWorkshop. For example:\r\nmodule load apps\/binapps\/answers\/wims\/.....\r\n\r\n# Start an interactive session on a compute node with a number of cores for the sim tool\r\nsrun -p interactive -n 1 -c 4 -t 60 visualworkshop\r\n                     ###  ###  ####\r\n                      #    #     # Wallclock limit. 60 is 60 minutes. Max is 0-6 (0 days, 6 hours).\r\n                      #    #\r\n                      #    # <strong>Number of cores that the simulation tool (e.g., WIMS, MONK) will use.<\/strong>\r\n                      #\r\n                      # Must be 1. Using -n 1 ensures only one copy of the GUI starts!\r\n<\/pre>\n<p>If there are free cores on an interactive node on which to run the application the GUI will start. If all of the interactive resources are in use then you will not receive an allocation. Please try again later.<\/p>\n<p>Note that in the VisualWorkshop GUI, you will need to increase the number of cores used by the simulation tool from <code>1<\/code> (the initial default) to the number you requested on the command-line with the <code>-c<\/code> flag (<code>4<\/code> in the above example):<br \/>\n<a href=\"\/csf3\/wp-content\/uploads\/VisualWorkshop-parallel-red.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/VisualWorkshop-parallel-red.png\" alt=\"VisualWorkshop number of cores for a parallel simulation\" width=\"473\" height=\"145\" class=\"alignnone size-full wp-image-12452\" srcset=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/VisualWorkshop-parallel-red.png 473w, https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-content\/uploads\/VisualWorkshop-parallel-red-300x92.png 300w\" sizes=\"auto, (max-width: 473px) 100vw, 473px\" \/><\/a><\/p>\n<h2>MONK<\/h2>\n<h3>Serial batch job submission<\/h3>\n<p>Make sure you have the required MONK modulefile loaded then create a batch submission script, for example:<\/p>\n<pre>#!\/bin\/bash --login\r\n#SBATCH -p serial\r\n#SBATCH -t 1-0    # Wallclock limit (days-hours). Required!\r\n                  # Max permitted is 7 days (7-0).\r\n\r\nmodule purge\r\n# We recommend loading the modulefile in the jobscript (change to your required version)\r\nmodule load apps\/binapps\/answers\/monk\/10b_ru0\r\n\r\nmonk10b.out datsets=datsets.lis\r\n<\/pre>\n<p>Submit the jobscript using:<\/p>\n<pre>sbatch <em>scriptname<\/em><\/pre>\n<p>where <em>scriptname<\/em> is the name of your jobscript.<\/p>\n<h3>Parallel batch job submission<\/h3>\n<p>Make sure you have the required MONK modulefile loaded then create a batch submission script, for example:<\/p>\n<pre>#!\/bin\/bash --login\r\n#SBATCH -p multicore  # Partition is required. Runs on an AMD Genoa hardware.\r\n#SBATCH -n numcores   # (or --ntasks=) where numcores is between 2 and 168.\r\n#SBATCH -t 4-0        # Wallclock limit (days-hours). Required!\r\n                      # Max permitted is 7 days (7-0).\r\n\r\nmodule purge\r\n# We recommend loading the modulefile in the jobscript (change to your required version)\r\nmodule load apps\/binapps\/answers\/monk\/10b_ru0_mpi\r\n\r\nmpirun -n $SLURM_NPROCS monk10b_mpi.out datsets=datsets.lis\r\n\r\n<\/pre>\n<p>Submit the jobscript using:<\/p>\n<pre>sbatch <em>scriptname<\/em><\/pre>\n<p>where <em>scriptname<\/em> is the name of your jobscript.<\/p>\n<h2>WIMS<\/h2>\n<h3>Serial batch job submission<\/h3>\n<p><!--- Please note that WIMS <em>must<\/em> be run on 12-core nodes. Even if you are using <em>fewer<\/em> than 12 cores the software will still check that there is a maximum of 12 cores in the node. We have now removed the 12-core InfiniBand connected nodes (and replaced them with 24-core and 32-core nodes) so it will not be possible to run multi-node jobs. To ensure your job lands on a 12 core node, use the following: ---><\/p>\n<p>Create a batch submission script, for example:<\/p>\n<pre>#!\/bin\/bash --login\r\n#SBATCH -p serial\r\n#SBATCH -t 1-0    # Wallclock limit (days-hours). Required!\r\n                  # Max permitted is 7 days (7-0).\r\n\r\nmodule purge\r\n### We recommend loading the modulefile in the jobscript (change to your required version)\r\nmodule load apps\/binapps\/answers\/wims\/11a_dv10\r\n\r\n### Change this to select your required nuclear library\r\nexport LIBRARY=$ANSWERS_DATA\/w10j312v1.dat\r\n\r\nwims11a_dv10_64.out library=$LIBRARY input=.\/my_sim.txt output=.\/my_sim.out space=8000000\r\n<\/pre>\n<p>Submit the jobscript using:<\/p>\n<pre>sbatch <em>scriptname<\/em><\/pre>\n<p>where <em>scriptname<\/em> is the name of your jobscript.<\/p>\n<h3>Parallel batch job submission<\/h3>\n<p>Create a batch submission script, for example:<\/p>\n<pre>#!\/bin\/bash --login\r\n#SBATCH -p multicore  # Partition is required. Runs on an AMD Genoa hardware.\r\n#SBATCH -n numcores   # (or --ntasks=) where numcores is between 2 and 168.\r\n#SBATCH -t 4-0        # Wallclock limit (days-hours). Required!\r\n                      # Max permitted is 7 days (7-0).\r\n\r\nmodule purge\r\n### We recommend loading the modulefile in the jobscript (change to your required version)\r\nmodule load apps\/binapps\/answers\/wims\/11a_dv10_mpi\r\n\r\n### Change this to select your required nuclear library\r\nexport LIBRARY=$ANSWERS_DATA\/w10j312v1.dat\r\n\r\n### You must specify the full path to the wims executable using \r\n### $WIMS_HOME\/wims11a_dv10_64.out otherwise your job will fail\r\n### if it tries to run the wecco executable as part of the job.\r\n\r\nmpirun -n $SLURM_NPROCS $WIMS_HOME\/wims11a_dv10_64.out library=$LIBRARY \\\r\n          input=.\/my_sim.txt output=.\/my_sim.out space=8000000\r\n\r\n<\/pre>\n<p>Submit the jobscript using:<\/p>\n<pre>sbatch <em>scriptname<\/em><\/pre>\n<p>where <em>scriptname<\/em> is the name of your jobscript.<\/p>\n<h2>Further info<\/h2>\n<ul>\n<li><a href=\"http:\/\/www.answerssoftwareservice.com\/\">ANSWERS website<\/a><\/li>\n<\/ul>\n<h2>Updates<\/h2>\n<p>None.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview ANSWERS provides Monte Carlo software tools for nuclear criticality safety and reactor physics analysis. MCBEND 10a_ru1, 11a_ru0 MONK 12b_ru0, 12b_ru_mpi, 10a_ru0, 10a_ru0_x64, 10b_ru0_x64 WIMS 11a_dv10(serial), 11a_dv10(mpi) WIMS 11b_dv11(serial), 11a_dv11(mpi) WIMS 11b_dv14(mpi) VisualWorkshop 3b_ru0 VisualWorkshop 4a_ru0 VisualWorkshop 5a_ru0 The following products are available upon request (we have not written modulefiles for these as they are rarely used. If you use them on Redqueen you may set up their environment manually. Please contact us if you.. <a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/software\/applications\/answers\/\">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-375","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/375","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=375"}],"version-history":[{"count":24,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/375\/revisions"}],"predecessor-version":[{"id":12459,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/375\/revisions\/12459"}],"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=375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}