XML schema for lattices and graphs - lattices

XML Schema for Lattices and Graphs

XML Schema for Lattices

Lattices are created by replicating a unit cell through translation by integer multiples of the basic vectors of the lattice, as shown here in two dimensions:

A 2d lattice

We propose to describe such a lattice by an (optional) name and the dimensionality of the lattice, both given as attributes:

  <LATTICE name="2D" dimension="2"/>

Additionally we can specify the cartesian coordinates of the basis vectors of the lattice. For above lattice this would be:

  <LATTICE name="2D" dimension="2">
    <BASIS>
      <VECTOR>   1 0 </VECTOR>
      <VECTOR> 0.5 1 </VECTOR>
    </BASIS>
  </LATTICE>

Basis vectors can also be specified in a symbolic and parametrized way, such as:

  <LATTICE name="2D" dimension="2">
    <PARAMETER name="a" default="1"/>
    <PARAMETER name="b" default="1"/>
    <PARAMETER name="phi" default="Pi/2"/>
    <BASIS>
      <VECTOR>   a 0 </VECTOR>
      <VECTOR> b*sin(phi) b*cos(phi) </VECTOR>
    </BASIS>
  </LATTICE>

Finite lattices

Finite extent

Most (but not all) computer simulations do not work on the infinite lattice presented above, but instead on a finite part of the lattice, that we call finite lattice. There are many ways in which such a finite lattice can be defined. Any finite subset of a lattice is a finite lattice, the possibilities are infinite. To start with we define the most widespread lattice fo finite extent, where a cell is translated at most a finite number of times in any direction, e.g. a square, rectangular, cubic or hypercubic lattice, where we specify the extent in any of the dimensions.
A 5x3 lattice

  <FINITELATTICE name="5x3">
    <LATTICE name="2D" dimension="2"/>
    <EXTENT dimension="1" size="5"/>
    <EXTENT dimension="2" size="3"/>
  </FINITELATTICE>

If the dimension attribute is omitted, the extent is assumed to apply to all dimensions, e.g. a cubic lattice
of linear size 4 would be:

  <FINITELATTICE>
    <LATTICE dimension="3"/>
    <EXTENT size="4"/>
  </FINITELATTICE>

Not all dimensions need to be finite, and an infinite strip of width two can be specified as
A strip of width 2

  <FINITELATTICE name="strip">
    <LATTICE name="2D" dimension="2"/>
    <EXTENT dimension="2" size="2"/>
  </FINITELATTICE>

In many applications the exact extent is not constant, but an input parameter specified by the user. We can again use a PARAMETER element to specify the extent. For an L x 2 strip this is:

  <FINITELATTICE>
    <LATTICE name="2D" dimension="2"/>
    <PARAMETER name="L"/>
    <EXTENT dimension="1" size="L"/>
    <EXTENT dimension="2" size="2"/>
  </FINITELATTICE>

If we want to have a strip of size L x W, with a default value of 2 for the width in case that W is not specified we provide both a

size

and a parameter attribute:

  <FINITELATTICE>
    <LATTICE name="2D" dimension="2"/>
    <PARAMETER name="L" />
    <PARAMETER name="W" default="2" />
    <EXTENT dimension="1" size="L" />
    <EXTENT dimension="2" size="W" />
  </FINITELATTICE>

Finally, it is often the case that we consider a square (or cubic) lattice of the same extent L in all dimensions, unless we specifically provide other dimensions (e.g. W for the width or H for the height). This can be described as:

  <FINITELATTICE>
    <LATTICE name="3D" dimension="3"/>
    <PARAMETER name="L" />
    <PARAMETER name="W" default="L" />    
    <PARAMETER name="H" default="W" />
    <EXTENT dimension="1" size="L" />
    <EXTENT dimension="2" size="W" />
    <EXTENT dimension="2" size="H" />
  </FINITELATTICE>

The first defined parameter spcifies the dimension. Thus in only L is specified by the user, we get a n LxLxL cube, if L and W are specified an LxWxW block. If L and H are specified we get an LxLxH block and if all of L, W and H are defined we get an LxWxH block.

Boundary conditions

For finite lattices in addition to the extent the boundary conditions need to be specifed. Widely used boundary conditions are:

open:the lattice has open edges, and the boundary cells do not have any neighbor on one or more sides
periodic: the lattice is assumed to be periodic, i.e. moving out of the lattice on one side, one reenters the lattice on the opposite side. The right neighbor of the rightmost cell is the left-most, and the upper neighbor of the uppermost cell is the lowest cell. For a two-dimensional lattice this looks like a torus.

For these two types of boundary conditions we have defined a BOUNDARY element, with a type attribute that can take either of these values. E.g. for a periodic L x L square lattice:

  <FINITELATTICE>
    <LATTICE name="2D" dimension="2"/>
    <EXTENT size="L" />
    <BOUNDARY type="periodic" />
  </FINITELATTICE>

Or for a strip that is periodic in the long and open in the short direction:

  <FINITELATTICE name="strip">
    <LATTICE name="strip" dimension="2"/>
    <PARAMETER name="W" default="2" />
    <EXTENT dimension=1 size="L" />
    <EXTENT dimension=2 size="W" />
    <BOUNDARY dimension="1" type="periodic" />
    <BOUNDARY dimension="2" type="open" />
  </FINITELATTICE>

Alternatively, if the boundary condition is to be defined at run-time, again a PARAMETER element can be specified to denote the name of the parameter that will determine the boundary condition and optionally provide a default value:

  <FINITELATTICE>
    <LATTICE name="cube" dimension="3"/>
    <PARAMETER name="BC" default="periodic" />
    <EXTENT size="L" />
    <BOUNDARY type="BC" />
  </FINITELATTICE>

This will specify a cubic lattice with boundary conditions given by the parameter BC, and periodic boundary conditions as default.

Referencing lattices

Instead of defining a lattice every time, we can also refer to a previously defined lattice. E.g. instead of defining

  <FINITELATTICE name = "finite tilted 2D">
    <LATTICE name="tilted 2D" dimension="2">
      <BASIS>
        <VECTOR>   1 0 </VECTOR>
        <VECTOR> 0.5 1 </VECTOR>
      </BASIS>
    </LATTICE>
    <PARAMETER name="BC" default="periodic" />
    <EXTENT dimension="1" size="L" />
    <EXTENT dimension="2" size="W" />
    <BOUNDARY type="BC" />
  </FINITELATTICE>

we can first define the infinite lattice:

  <LATTICE name="tilted 2D" dimension="2"
    <BASIS>
      <VECTOR>   1  0 </VECTOR>
      <VECTOR> 0.5, 1 </VECTOR>
    </BASIS>
  </LATTICE>

And then every time we define a finite sublattice refer to this lattice by using a ref attribute in the lattice element instead of repeating the definition:

  <FINITELATTICE name = "finite tilted 2D">
    <LATTICE ref="tilted 2D">
    <PARAMETER name="BC" default="periodic" />
    <EXTENT dimension="1" size="L" />
    <EXTENT dimension="2" size="W" />
    <BOUNDARY type="BC" />
  </FINITELATTICE>

We envision that a library of common lattices will be built up rapidly.

Related software

C++ concepts and traits types for lattices can be found in the ALPS library at alps.comp-phys.org

Extensions and open questions

Topics to be discussed, and possible extensions include:

symmetries and space groups of the lattice
other shapes of finite lattices
other special boundary conditions

We encourage your comments and ideas .

Back to XML in Compuational Physics