ASE Manual Release 3.6.1.2825 CAMd - CampOS Wiki
ASE Manual Release 3.6.1.2825 CAMd - CampOS Wiki
ASE Manual Release 3.6.1.2825 CAMd - CampOS Wiki
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>ASE</strong> <strong>Manual</strong>, <strong>Release</strong> 3.6.1.2828<br />
Note: Only Monkhorst-Pack and Gamma-centered k-point sampling are supported for restart at the moment.<br />
Some INCAR parameters may not be implemented for restart yet. Please report any problems to the <strong>ASE</strong> mailing<br />
list.<br />
The restart parameter can be used , as the name suggest to continue a job from where a previous calculation<br />
finished. Furthermore, it can be used to extract data from an already performed calculation. For example, to get the<br />
total potential energy of the sodium chloride molecule in the previous section, without performing any additional<br />
calculations, in the directory of the previous calculation do:<br />
>>> calc = Vasp(restart=True)<br />
>>> atoms = calc.get_atoms()<br />
>>> atoms.get_potential_energy()<br />
-4.7386889999999999<br />
FHI-aims<br />
Introduction<br />
FHI-aims is a all-electron full-potential density functional theory code using a numeric local orbital basis set. This<br />
interface provides all that should be required to run FHI-aims from within <strong>ASE</strong>.<br />
Running the Calculator<br />
The default initialization command for the FHI-aims calculator is<br />
class FHI-aims.Aims(output_template = ‘aims’, track_output = False)<br />
In order to run a calculation, you have to ensure that at least the following str variables are specified, either in<br />
the initialization or as shell variables:<br />
key- description<br />
word<br />
run_command The full command required to run FHI-aims from a shell, including anything to do with an MPI<br />
wrapper script and the number of tasks. An alternative way to set this command is via the shell<br />
variable AIMS_COMMAND, which is checked upon initialization and when starting a run.<br />
species_dir Directory where the species defaults are located that should be used. Can also be specified with<br />
the system variable AIMS_SPECIES_DIR.<br />
xc The minimal physical specification: what kind of calculation should be done.<br />
In addition, you might want to specify at least one of self-consistency accuracy commands (see below) in order to<br />
avoid an excessively long calculation.<br />
Two general options might come in useful to postprocess the output:<br />
keyword description<br />
output_template Base name for the output, in case the calculator is called multiple times within a single<br />
script.<br />
track_output True/False - if True all the output files will be kept, while the number of calls to the<br />
calculator is encoded in the output file name.<br />
List of keywords<br />
This is a non-exclusive list of keywords for the control.in file that can be addresses from within <strong>ASE</strong>. The<br />
meaning for these keywords is exactly the same as in FHI-aims, please refer to its manual for help on their use.<br />
One thing that should be mentioned is that keywords with more than one option have been implemented as lists, eg.<br />
k_grid=(12,12,12) or relativistic=(’atomic_zora’,’scalar’). In those cases, specifying a<br />
single string containing all the options is also possible.<br />
124 Chapter 7. Documentation for modules in <strong>ASE</strong>