Difference between revisions of "ORCA 2016"

From HPC users
Jump to navigationJump to search
Line 29: Line 29:


For this reason, you have to create a jobscript for your tasks.
For this reason, you have to create a jobscript for your tasks.
=== Serial run ===
=== Serial run ===


Line 84: Line 85:
# all other files are created in <tt>$TMPDIR</tt>, which is automatically deleted after the job; if additional files need to be saved, they need to be copied (not yet implemented in the job script)
# all other files are created in <tt>$TMPDIR</tt>, which is automatically deleted after the job; if additional files need to be saved, they need to be copied (not yet implemented in the job script)


 
=== Parallel run ===
 
 
 
 
 
 
<!-- You have to prepare a jobscript and an inputfile for your ORCA job.
An example ORCA-job could look like this:
 
#SBATCH --partition=carl.p
#SBATCH --time=1-00:00:00
#SBATCH --mem=2G
#SBATCH --job-name ORCA-TEST
#SBATCH --output=slurm-%j.out
#SBATCH --error=slurm-%j.err
module load ORCA
MODEL=TiF3
ORCAEXE=`which orca`
$ORCAEXE ${MODEL}.inp > ${MODEL}.out
 
The first 5 lines are meant for SLURM. In the first line configuring the time needed for the job. Please be as accurate as possible but keep in mind that the job will fail if, e.g. the time is set to 1 hour but the job actually needs 5 hours. Second line defines the memory. For this job 2G (2Gb) should be enough. After that, we need to name our job, our example job is named "ORCA-TEST". The following two lines are defining the output- and the errorfile. Without adding these two lines, the output and errors will be saved into a single file.-->


== Documentation ==
== Documentation ==


The full documentation of the most recent version of ORCA (currently 4.0.0) can be found [https://orcaforum.cec.mpg.de/OrcaManual.pdf here] (PDF viewer required).
The full documentation of the most recent version of ORCA (currently 4.0.0) can be found [https://orcaforum.cec.mpg.de/OrcaManual.pdf here] (PDF viewer required).

Revision as of 07:47, 22 March 2017

Introduction

The program ORCA is a modern electronic structure program package that is able to carry out geometry optimizations and to predict a large number of spectroscopic parameters at different levels of theory. Besides the use of Hartee Fock theory, density functional theory (DFT) and semiempirical methods, high level ab initio quantum chemical methods, based on the configuration interaction and coupled cluster methods, are included into ORCA to an increasing degree.

For more details please refer the offical home of ORCA where you can also find a thorough documentation on using the program. Note that ORCA is free of charge for non-commercial use and by using ORCA on the cluster you are accepting the ORCA license. In particular, any scientific work using ORCA should at least cite

F. Neese: The ORCA program system (WIREs Comput Mol Sci 2012, 2: 73-78)

as well as other related works as apropriate.

Below, a short introduction to using ORCA on the cluster is given.

Installed version

The currently installed versions of ORCA are 3.0.3 and 4.0.0:

You can always check that out by yourself, you only need to use the command "module av ORCA":

$ module av ORCA

------------------------ /cm/shared/uniol/modules/chem -------------------------
   ORCA/3.0.3    ORCA/4.0.0 (D)

  Where:
   D:  Default Module

Using ORCA on the HPC cluster

Since there many people working with the HPC cluster, its important that everyone has an equal chance to do so. Therefore, every job should be processed by SLURM.

For this reason, you have to create a jobscript for your tasks.

Serial run

#!/bin/bash 

#SBATCH --partition=carl.p
#SBATCH --time=1-00:00:00
#SBATCH --mem=2G 
#SBATCH --job-name ORCA-SERIAL-TEST
#SBATCH --output=orca-serial-test-%j.out
#SBATCH --error=orca-serial-test-%j.err 

module load ORCA

MODEL=TiF3

ORCAEXE=`which orca`

$ORCAEXE ${MODEL}.inp > ${MODEL}.out

#preparing $TMPDIR for run by copying file
for ext in $INPUTEXT
do
   if [ -e $MODEL.$ext ]
   then
      echo "Copying $MODEL.$ext to TMPDIR"
      cp $MODEL.$ext $TMPDIR/${MODEL}_${JOB_ID}.$ext
   fi
done

#change to $TMPDIR for running ORCA
cd $TMPDIR
 
#run ORCA
$ORCAEXE ${MODEL}_${JOB_ID}.inp > $WORK/${MODEL}_${JOB_ID}.out
 
#saving files from $TMPDIR
for ext in $OUTPUTEXT
do
   if [ -e ${MODEL}_${JOB_ID}.$ext ]
   then
      echo "Copying $MODEL.$ext to $WORK"
      cp ${MODEL}_${JOB_ID}.$ext $WORK
   fi
done

The job script requires additional input files for ORCA, in this case TiF3.inp and TiF3.xyz and all three files have to be placed in the same directory. Note: all downloads have to be unzipped first.

Once the job script and your input files are ready, a job can be submitted as usual with the command:

sbatch orca_serial_test.job

The job script works roughly in the following way

  1. the ORCA module is loaded and the name of the model is set (must be identical to the name of the .inp file)
  2. all input files (identified by the model name and given extensions) are copied to $TMPDIR, more files can be included by adding their extensions to the variable INPUTEXT
  3. the directory is changed to $TMPDIR and the run is started, a log file for the run (extension .out) is written to the directory from where the job was submitted
  4. all other files are created in $TMPDIR, which is automatically deleted after the job; if additional files need to be saved, they need to be copied (not yet implemented in the job script)

Parallel run

Documentation

The full documentation of the most recent version of ORCA (currently 4.0.0) can be found here (PDF viewer required).