18.11.2012 Views

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>ASE</strong> <strong>Manual</strong>, <strong>Release</strong> 3.6.1.2828<br />

Arguments:<br />

Key- Description<br />

word<br />

directory The relative path where all input and output files will be placed. If this does not exist, it will be<br />

created. Existing directories will be moved to directory-TIMESTAMP unless<br />

self._rename_existing_dir is set to false.<br />

label The prefix of .param, .cell, .castep, etc. files.<br />

Additional Settings<br />

Internal Description<br />

Setting<br />

_castep_command (=castep): the actual shell command used to call CASTEP.<br />

_check_checkfile (=True): this makes write_param() only write a continue or reuse statement if the<br />

addressed .check or .castep_bin file exists in the directory.<br />

_copy_pspots (=False): if set to True the calculator will actually copy the needed pseudo-potential<br />

(*.usp) file, usually it will only create symlinks.<br />

_export_settings (=True): if this is set to True, all calculator internal settings shown here will be included<br />

in the .param in a comment line (#) and can be read again by merge_param. merge_param<br />

can be forced to ignore this directive using the optional argument<br />

ignore_internal_keys=True.<br />

_force_write (=True): this controls wether the *cell and *param will be overwritten.<br />

_prepare_input_only (=False): If set to True, the calculator will create *cell und *param file but not start the<br />

calculation itself. If this is used to prepare jobs locally and run on a remote cluster it is<br />

recommended to set _copy_pspots = True.<br />

_castep_pp_path (=’.’) : the place where the calculator will look for pseudo-potential files.<br />

_rename_existing_dir (=True) : when using a new instance of the calculator, this will move directories out of<br />

the way that would be overwritten otherwise, appending a date string.<br />

_set_atoms (=False) : setting this to True will overwrite any atoms object previously attached to the<br />

calculator when reading a .castep file. By de- fault, the read() function will only create a<br />

new atoms object if none has been attached and other- wise try to assign forces etc. based<br />

on the atom’s positions. _set_atoms=True could be necessary if one uses CASTEP’s<br />

internal geometry optimization (calc.param.task=’GeometryOptimization’)<br />

because then the positions get out of sync. Warning: this option is generally not<br />

recommended unless one knows one really needs it. There should never be any need, if<br />

CASTEP is used as a single-point calculator.<br />

_track_output(=False) : if set to true, the interface will append a number to the label on all input and<br />

output files, where n is the number of calls to this instance. Warning: this setting may consume<br />

a lot more disk space because of the additio- nal *check files.<br />

_try_reuse (=_track_output) : when setting this, the in- terface will try to fetch the reuse file<br />

from the previous run even if _track_output is True. By de- fault it is equal to<br />

_track_output, but may be overridden.<br />

Since this behavior may not always be desirable for single-point calculations. Regular<br />

reuse for e.g. a geometry-optimization can be achieved by setting calc.param.reuse<br />

= True.<br />

Special features:<br />

.dryrun_ok() Runs castep_command seed -dryrun in a temporary directory return True if all variables<br />

initialized ok. This is a fast way to catch errors in the input. Afterwards _kpoints_used is set.<br />

.merge_param() Takes a filename or filehandler of a .param file or CastepParam instance and merges it into<br />

the current calculator instance, overwriting current settings<br />

132 Chapter 7. Documentation for modules in <strong>ASE</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!