4.2.1. Dirac¶

4.2.1.1.1. Input¶

Input files for DIRAC are organized using blocks and subblocks with three level hierarchy. On the top level there are blocks (indicated by keywords starting with **) which can contain keys (starting with .) or subblocks (starting with *), which in turn can contain more keys. This structure can be easily reflected with tree-like Settings objects. In general, the preparation process is quite similar to SCMJob, however, there are a few nuances. The details are explained below.

• Each key present on the top level of myjob.settings.input is translated to a block. Values of those keys should be Settings instances. The block DIRAC is always printed as the first one, all other are ordered lexicographically (this behavior can be changed with DiracJob._top class attribute).

• In each block various keys and subblocks can be present. Subblocks are indicated by nested Settings instances, all other values are interpreted as keys.

• An empty value of a key can be obtained by setting its value to True.

• An empty block or subblock can be obtained with an empty Settings instance.

• If the value of a key is a list, each element of this list will be printed in a separate line.

• All keywords are written to the input file with upper case, values remain unchanged.

• Many DIRAC keywords contain spaces (for example WAVE FUNCTION or LINEAR RESPONSE) and thus cannot be used with convenient dot notation. Usual bracket notation has to be used in those cases (see Dot notation).

• Some subblocks follow the special requirement - they need to be “enabled” by presence of the corresponding keyword in the parent block. For example, in **HAMILTONIAN block a subblock *FDE can be used to specify frozen density embedding parameters, but this subblock is taken into account only if a key .FDE is present in **HAMILTONIAN. This introduces a problem, since you cannot store two entries with the same name in Settings:

  #sets the .FDE key on the top level of HAMILOTNIAN block
  myjob.setting.input.hamiltonian.fde = True
  #sets the *FDE subblock in the HAMILTONIAN block, but overwrites the key .FDE defined above
  myjob.setting.input.hamiltonian.fde.frdens = 'value2'
  

  To solve this problem a special “enabler” key _en can be used inside the subblock. If such a key is present, the parent block of this subblock will be enriched with corresponding key and value:

  #sets the .FDE key on the top level of HAMILOTNIAN block, its value can be set just like any other key
  myjob.setting.input.hamiltonian.fde._en = True
  #sets the "proper" contents of *FDE subblock.
  myjob.setting.input.hamiltonian.fde.frdens = 'value2'
  

4.2.1.1.2. Runscript¶

Calculations with DIRAC are executed using a start script called pam. This script accepts a range of option flags adjusting various technical aspects of calculation, including input and geometry files. You can type pam -h in you command line for details.

A runscript calling pam is automatically generated by PLAMS. Its contents are based on myjob.settings.runscript branch and follow general rules described in Contents of job settings. Besides that, the subbranch myjob.settings.runscript.pam is used to store option flags. Every key-value pair present there is transformed to --key=value flag appended to pam execution command. Following the usual convention, True represents an “empty value” (to get flags like --key) and list can be used for keys with multiple values (--key="val1 val2 val3").

Initially, when an instance of DiracJob is created, the following pam options are set by default:

self.settings.runscript.pam.noarch = True
self.settings.runscript.pam.get = ['DFCOEF', 'GRIDOUT', 'dirac.xml']

Their role is to obtain from DIRAC scratch space all the files produced by your calculation (they can be later discarded with Cleaning job folder if not needed) and prevent creating a .tgz archive out of them (to allow PLAMS to process them). These two default flags can be changed or removed if needed, but this can hinder some Results functionalities, so make sure to know what you are doing.

You don’t need to manually set mandatory inp and mol flags, they are added automatically just before the runscript is generated. If, for some reason, you don’t want to use automatic molecule handling and wish to provide a geometry file by yourself, all you need to do is to set mol entry in myjob.settings.runscript.pam with the path of your geometry file. PLAMS will then ignore geometry stored in myjob.molecule and use the supplied path.