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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Usage<br />

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

• The rhombohedral (or trigonal) lattices are not implemented. They will be implemented when the need<br />

arises (and if somebody can tell me the precise definition of the 4-number Miller indices - I only know that<br />

they are “almost the same as in hexagonal lattices”).<br />

• lattice.compounds<br />

Lattices with more than one element. These are mainly intended as examples allowing you to define new<br />

such lattices. Currenly, the following are defined<br />

– B1 = NaCl = Rocksalt<br />

– B2 = CsCl<br />

– B3 = ZnS = Zincblende<br />

– L1_2 = AuCu3<br />

– L1_0 = AuCu<br />

The lattice objects are called with a number of arguments specifying e.g. the size and orientation of the lattice.<br />

All arguments should be given as named arguments. At a minimum the symbol argument must be specified.<br />

symbol The element, specified by the atomic number (an integer) or by the atomic symbol (i.e. ‘Au’). For<br />

compounds, a tuple or list of elements should be given. This argument is mandatory.<br />

directions and/or miller: Specifies the orientation of the lattice as the Miller indices of the three basis<br />

vectors of the supercell (directions=...) and/or as the Miller indices of the three surfaces<br />

(miller=...). Normally, one will specify either three directions or three surfaces, but any combination<br />

that is both complete and consistent is allowed, e.g. two directions and two surface miller indices (this<br />

example is slightly redundant, and consistency will be checked). If only some directions/miller indices are<br />

specified, the remaining should be given as None. If you intend to generate a specific surface, and prefer to<br />

specify the miller indices of the unit cell basis (directions=...), it is a good idea to give the desired<br />

Miller index of the surface as well to allow the module to test for consistency. Example:<br />

>>> atoms = BodyCenteredCubic(directions=[[1,-1,0],[1,1,-1],[0,0,1]],<br />

... miller=[None, None, [1,1,2]], ...)<br />

If neither directions nor miller are specified, the default is directions=[[1,0,0],<br />

[0,1,0], [0,0,1]].<br />

size: A tuple of three numbers, defining how many times the fundamental repeat unit is repeated. Default:<br />

(1,1,1). Be aware that if high-index directions are specified, the fundamental repeat unit may be large.<br />

latticeconstant: The lattice constant. If no lattice constant is specified, one is extracted from<br />

<strong>ASE</strong>.ChemicalElements provided that the element actually has the crystal structure you are creating. Depending<br />

on the crystal structure, there will be more than one lattice constant, and they are specified by giving<br />

a dictionary or a tuple (a scalar for cubic lattices). Distances are given in Angstrom, angles in degrees.<br />

Structure Lattice constants Dictionary-keys<br />

Cubic a ‘a’<br />

Tetragonal (a, c) ‘a’, ‘c’ or ‘c/a’<br />

Orthorhombic (a, b, c) ‘a’, ‘b’ or ‘b/a’, ‘c’ or ‘c/a’<br />

Triclinic (a, b, c, α, β, γ) ‘a’, ‘b’ or ‘b/a’, ‘c’ or ‘c/a’, ‘alpha’, ‘beta’, ‘gamma’<br />

Monoclinic (a, b, c, alpha) ‘a’, ‘b’ or ‘b/a’, ‘c’ or ‘c/a’, ‘alpha’<br />

Hexagonal (a, c) ‘a’, ‘c’ or ‘c/a’<br />

Example:<br />

>>> atoms = Monoclinic( ... , latticeconstant={’a’: 3.06,<br />

... ’b/a’: 0.95, ’c/a’: 1.07, ’alpha’: 74})<br />

debug: Controls the amount of information printed. 0: no info is printed. 1 (the default): The indices of surfaces<br />

and unit cell vectors are printed. 2: Debugging info is printed.<br />

7.9. Creating atomic structures 95

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

Saved successfully!

Ooh no, something went wrong!