ANSWERS

Overview

ANSWERS provides Monte Carlo software tools for nuclear criticality safety and reactor physics analysis.

• MCBEND 10a_ru1, 11a_ru0
• MONK 10a_ru0, 10a_ru0_x64, 10b_ru0_x64 (new Sept 2017)
• WIMS 11a_dv10(serial), 11a_dv10(mpi)
• VisualWorkshop 3a_dv4, 3b_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 require a modulefile for these products).

• MONK 9a_ru1
• WIMS 9a_ru1
• vista-ray3a ru0
• visage5a_ru0
• launchpad2a_ru0
• WimsBuilder 2a_ru0, 3a_ru0

Restrictions on use

Access to this software is restricted to a specific research group. Please contact its-ri-team@manchester.ac.uk for more information.

Set up procedure

To access the software you must first load one of the following modulefiles:

module load apps/binapps/answers/monk/10b_ru0_mpi     # 64bit parallel MPI version (note new name)
module load apps/binapps/answers/monk/10b_ru0         # 64bit serial version

module load apps/binapps/answers/monk/10a_ru0_64bit   # 64bit parallel MPI version
module load apps/binapps/answers/monk/10a_ru0         # 32bit serial version

module load apps/binapps/answers/wims/11a_dv10_mpi    # 64bit parallel MPI version
module load apps/binapps/answers/wims/11a_dv10        # 64bit serial version

module load apps/binapps/answers/visualworkshop/3a
module load apps/binapps/answers/visualworkshop/3b

Nuclear Data Libraries

Various nuclear data libraries are available in the directory given by the environment variable:

$ANSWERS_DATA

For example, to see what is available, run:

ls $ANSWERS_DATA

You can use the $ANSWERS_DATA in your jobscripts (see below for examples).

Running the applications

Please do not run MONK or WIMS on the login node. Jobs should be submitted to the compute nodes via batch.

The VisualWorkshop application is run from a script on the login node. This will automatically request an interactive session on a backend compute node. VisualWorkshop will only run if the qrsh interactive session can be scheduled by the system (i.e., if there is a free core available in the interactive area).

VisualWorkshop (GUI)

Load the appropriate modulefile (see above) then run the following command on the CSF login node:

# Run this on the CSF login node. It will request an interactive job.
VisualWorkshop_csf

If there is a free core on an interactive node on which to run the application the GUI will start. If all of the interactive resources are in use you will see a message:

Your "qrsh" request could not be scheduled, try again later.

Please try again later.

If you prefer to start an interactive session first, and then run VisualWorkshop please do the following:

# From the CSF login node request an interactive session
qrsh -l inter -l short

# When you have been logged in to the compute node:
module load apps/binapps/answers/visualworkshop3b

# Now run the app interactively - this won't request a compute node - you are already on one!
VisualWorkshop_inter

Note that the interactive session will run for a maximum of 4 hours.

MONK

Serial batch job submission

Make sure you have the required MONK modulefile loaded then create a batch submission script, for example:

#!/bin/bash
#$ -S /bin/bash
#$ -cwd             # Job will run from the current directory
#$ -V               # Job will inherit current environment settings

monk10a.out datsets=datsets.lis

Submit the jobscript using:

qsub scriptname

where scriptname is the name of your jobscript.

Parallel batch job submission

Make sure you have the required MONK modulefile loaded then create a batch submission script, for example:

#!/bin/bash
#$ -S /bin/bash
#$ -cwd             # Job will run from the current directory
#$ -V               # Job will inherit current environment settings
#$ -pe smp.pe 8     # Number of cores to use (max 24)
                    # Note: If you were previously running multi-node jobs
                    # using orte-12-ib.pe on either CSF or Redqueen
                    # please email its-ri-team@manchester.ac.uk for help.

mpirun -n $NSLOTS monk10a.out datsets=datsets.lis

Submit the jobscript using:

qsub scriptname

where scriptname is the name of your jobscript.

WIMS

Serial batch job submission

Please note that WIMS must be run on 12-core nodes. Even if you are using fewer 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 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:

For a single node (multicore job – i.e, between 2 and 12 cores):

#$ -pe smp.pe 8            # Number of cores (2-12)

then add one of the following to select 12-core nodes (to avoid the landing on a 16-core Ivybridge node):

#$ -l sandybridge

or

#$ -l westmere             # These nodes may be slower than the sandybridge nodes

If previously running a multi-node job please email its-ri-team@manchester.ac.uk.

Two complete examples are now given below.

Make sure you have the required WIMS modulefile loaded then create a batch submission script, for example:

#!/bin/bash
#$ -S /bin/bash
#$ -cwd             # Job will run from the current directory
#$ -V               # Job will inherit current environment settings
#$ -l sandybridge   # Job will land on a 12-core sandybridge node (we only use one core)

### Change this to select your required nuclear library
export LIBRARY=$ANSWERS_DATA/w10j312v1.dat

wims11a_dv10_64.out library=$LIBRARY input=./my_sim.txt output=./my_sim.out space=8000000

Submit the jobscript using:

qsub scriptname

where scriptname is the name of your jobscript.

Parallel batch job submission

Make sure you have the required WIMS mpi modulefile loaded then create a batch submission script, for example:

#!/bin/bash
#$ -S /bin/bash
#$ -cwd             # Job will run from the current directory
#$ -V               # Job will inherit current environment settings

### Single-node. You must run on 12-core nodes only, even if using fewer cores.
#$ -pe smp.pe 8     # Number of cores to use (max 12)
#$ -l sandybridge   # or use westmere (slower than sandybridge)


### Change this to select your required nuclear library
export LIBRARY=$ANSWERS_DATA/w10j312v1.dat

### You must specify the full path to the wims executable using 
### $WIMS_HOME/wims11a_dv10_64.out otherwise your job will fail
### if it tries to run the wecco executable as part of the job.

mpirun -n $NSLOTS $WIMS_HOME/wims11a_dv10_64.out library=$LIBRARY \
          input=./my_sim.txt output=./my_sim.out space=8000000

Submit the jobscript using:

qsub scriptname

where scriptname is the name of your jobscript.

Further info

• APP website

Updates

None.