{"id":2338,"date":"2019-02-21T09:09:02","date_gmt":"2019-02-21T09:09:02","guid":{"rendered":"http:\/\/ri.itservices.manchester.ac.uk\/csf3\/?page_id=2338"},"modified":"2025-06-19T18:03:12","modified_gmt":"2025-06-19T17:03:12","slug":"mopac","status":"publish","type":"page","link":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/software\/applications\/mopac\/","title":{"rendered":"mopac"},"content":{"rendered":"

Overview<\/h2>\n

MOPAC is a semiempirical quantum chemistry software package for the prediction of chemical properties and modeling of chemical reactions.<\/p>\n

Version 2016-18.08 is available.<\/p>\n

Restrictions on use<\/h2>\n

All users must agree to abide by the MOPAC End User Agreement<\/a>.<\/p>\n

MOPAC is for academic, not for profit use only.<\/p>\n

All users must cite their use of the software in publications. The correct citation to use is given at the start of the output file of every job.<\/p>\n

You must be in the mopac<\/code> group to access it. Please contact us<\/a> to be added to the group.<\/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

To load the modulefile use this command:<\/p>\n

\r\nmodule load apps\/binapps\/mopac\/2016-64bit-18.08\r\n<\/pre>\n
Running the application<\/h2>\n
Please do not run MOPAC on the login node. Jobs should be submitted to the compute nodes via batch.<\/p>\n
Serial batch job submission<\/h3>\n
Make sure you have the modulefile loaded then create a batch submission script, for example:<\/p>\n
#!\/bin\/bash --login\r\n#$ -cwd             # Job will run from the current directory\r\n\r\nmodule load apps\/binapps\/mopac\/2016-64bit-18.08\r\n\r\nMOPAC2016.exe mydataset\r\n\r\n<\/pre>\n
where mydataset<\/code> is replaced with the name of your .mop<\/code>, .arc<\/code>, or .dat<\/code> without the suffix.<\/p>\n
Submit the jobscript using:<\/p>\n
qsub scriptname<\/em><\/pre>\n
where scriptname<\/code> is the name of your jobscript.<\/p>\n
Parallel batch job submission<\/h3>\n
MOPAC2016 can run in threaded mode; see the documentation<\/a>. E.g. for four threads:<\/p>\n
#!\/bin\/bash --login\r\n#$ -pe smp.pe 4\r\n\r\nmodule load apps\/binapps\/mopac\/2016-64bit-18.08\r\n\r\nexport OMP_NUM_THREADS=$NSLOTS\r\n\r\nMOPAC2016.exe mydataset\r\n<\/pre>\n
where mydataset<\/em> is replaced with the name of your .mop<\/code>, .arc<\/code>, or .dat<\/code> without the suffix.<\/p>\n
Submit the jobscript using:<\/p>\n
qsub scriptname<\/code><\/pre>\n
where scriptname<\/code> is the name of your jobscript.<\/p>\n
Serial (1-core) Interactive Jobs<\/h3>\n
To schedule a serial interactive job run the following command on the login node<\/strong> (not in a jobscript):<\/p>\n
\r\nqrsh -l short\r\n<\/pre>\n
This will log you in to a compute node where you can run Mopac in an interactive manner. Please note you will still need to use the module<\/code> command to set up applications as usual. Interactive sessions are limited to 1 hour.<\/p>\n
Parallel (multi-core) Interactive Jobs<\/h3>\n
To schedule a multi-core interactive job run the following command on the login node:<\/p>\n
\r\nqrsh -l short -pe smp.pe 2\r\n                         #\r\n                         # Number of cores\r\n<\/pre>\n
You will be logged in to a compute node where you can run Mopac in an interactive manner and will have access to 2 CPU cores (in this example) and 4GB per core. You should ensure any applications you run use only the number of cores reserved for you. Please note you will still need to use the module<\/code> command to set up applications as usual as well setting the following variable export OMP_NUM_THREADS=$NSLOTS<\/code> . Interactive sessions are limited to 1 hour.<\/p>\n
Further info<\/h2>\n