ISYM: Difference between revisions

From VASP Wiki
No edit summary
No edit summary
(8 intermediate revisions by 2 users not shown)
Line 7: Line 7:
For {{TAG|ISYM}}=-1 {{!}} 0, the use of symmetry is switched off.
For {{TAG|ISYM}}=-1 {{!}} 0, the use of symmetry is switched off.


For {{TAG|ISYM}}=2 a more efficient, memory conserving symmetrisation of the charge density is used (than for {{TAG|ISYM}}=1). This reduces memory requirements in particular for the parallel version.
For {{TAG|ISYM}}=2 a more efficient, memory conserving symmetrization of the charge density is used (than for {{TAG|ISYM}}=1). This reduces memory requirements in particular for the parallel version.


For {{TAG|ISYM}}=3, VASP does not directly symmetrize the charge density. Instead the charge density is constructed by applying the relevant symmetry operations to the orbitals at the '''k'''-points in the irreducible part of the Brillouin zone. This method of symmetrization is used when {{TAG|LHFCALC}}=.TRUE.
For {{TAG|ISYM}}=3, VASP does not directly symmetrize the charge density. Instead, the charge density is constructed by applying the relevant symmetry operations to the orbitals at the '''k'''-points in the irreducible part of the Brillouin zone. This method of symmetrization is used when {{TAG|LHFCALC}}=.TRUE.


For {{TAG|ISYM}}=0, VASP does not use symmetry, but it will assume that &Psi;<sub>'''k'''</sub>=&Psi;<sup>*</sup><sub>'''-k'''</sub> and reduces the sampling of the Brillouin zone accordingly. This value should be set for molecular dynamics, i.e. {{TAG|IBRION}}=0.  
For {{TAG|ISYM}}=0, VASP does not use symmetry, but it will assume that &Psi;<sub>'''k'''</sub>=&Psi;<sup>*</sup><sub>'''-k'''</sub> and reduces the sampling of the Brillouin zone accordingly. This value should be set for molecular dynamics, i.e. {{TAG|IBRION}}=0.  
Line 15: Line 15:
For {{TAG|ISYM}}=-1 the use of symmetry is switched off completely.
For {{TAG|ISYM}}=-1 the use of symmetry is switched off completely.
   
   
When the use of symmetry is switched on, VASP determines the point group symmetry and the space group consistent with the structure and initial velocities found on the {{FILE|POSCAR}} file, and the initial magnetic moments specified through the {{TAG|MAGMOM}} tag in the {{TAG|INCAR}} file. The {{TAG|SYMPREC}}-tag (VASP.4.4.4 and newer versions) determines by how much atomic positions may differ and still be judged to be equivalent by the symmetry detection algorithms. The default is 10<sup>-5</sup>, which is usually sufficiently large even if the {{FILE|POSCAR}} file has been generated with a single precision program. Increasing the {{TAG|SYMPREC}} tag means, that the positions in the {{FILE|POSCAR}} file can be less accurate. During the symmetry analysis, VASP determines
When the use of symmetry is switched on, VASP determines the point group symmetry and the space group consistent with the structure and initial velocities found on the {{FILE|POSCAR}} file (this is written out to the {{TAG|OUTCAR}} file for each {{TAG|NWRITE}} option), and the initial magnetic moments specified through the {{TAG|MAGMOM}} tag in the {{TAG|INCAR}} file. The {{TAG|SYMPREC}}-tag (VASP.4.4.4 and newer versions) determines by how much atomic positions may differ and still be judged to be equivalent by the symmetry detection algorithms. The default is 10<sup>-5</sup>, which is usually sufficiently large even if the {{FILE|POSCAR}} file has been generated with a single precision program. Increasing the {{TAG|SYMPREC}} tag means, that the positions in the {{FILE|POSCAR}} file can be less accurate. During the symmetry analysis, VASP determines


*the Bravais lattice type of the supercell,
*the Bravais lattice type of the supercell,
*the point group symmetry and the space group of the supercell with basis (static and dynamic) - and prints the names of the group (space group: only 'family'),
*the point group symmetry and the space group of the supercell with basis (static and dynamic) - and prints the names of the group (space group: only 'family'),
*the type of the generating elementary (primitive) cell if the supercell is a non-primitive cell,
*the type of the generating elementary (primitive) cell if the supercell is a non-primitive cell,
*all 'trivial non-trivial' translations (= trivial translations of the generating elementary cell within the supercell) -- needed for symmetrisation of the charge,
*all 'trivial non-trivial' translations (= trivial translations of the generating elementary cell within the supercell) -- needed for symmetrization of the charge,
*the symmetry-irreducible set of k-points if automatic k-mesh generation was used and additionally the symmetry-irreducible set of tetrahedra if the tetrahedron method was chosen together with the automatic k-mesh generation and of course also the corresponding weights ('symmetry degeneracy'),
*the symmetry-irreducible set of k-points if automatic k-mesh generation was used and additionally the symmetry-irreducible set of tetrahedra if the tetrahedron method was chosen together with the automatic k-mesh generation and of course also the corresponding weights ('symmetry degeneracy'),
*and tables marking and connecting symmetry equivalent ions.
*and tables marking and connecting symmetry equivalent ions.
Line 26: Line 26:
The symmetry analysis is done in four steps:
The symmetry analysis is done in four steps:
*First the point group symmetry of the lattice (as supplied by the user) is determined.
*First the point group symmetry of the lattice (as supplied by the user) is determined.
*Then tests are performed, whether the basis breaks symmetry. Accordingly these symmetry operations are removed.
*Then tests are performed, on whether the basis breaks the symmetry. Accordingly, these symmetry operations are removed.
*The initial velocities are checked for symmetry breaking.
*The initial velocities are checked for symmetry breaking.
*Finally, it is checked whether {{TAG|MAGMOM}} breaks the symmetry. Correspondingly the magnetic symmetry group is determined.
*Finally, it is checked whether {{TAG|MAGMOM}} breaks the symmetry. Correspondingly the magnetic symmetry group is determined.
Line 36: Line 36:
*The stress tensor according to the determined space group
*The stress tensor according to the determined space group


Why is symmetrisation necessary: Within LDA the symmetry of the supercell and the charge density are always the same. This symmetry is broken, because a symmetry-irreducible set of '''k'''-points is used for the calculation. To restore the correct charge density and the correct forces it is necessary to symmetrise these quantities.
Why is symmetrization necessary: Within LDA the symmetry of the supercell and the charge density is always the same. This symmetry is broken because a symmetry-irreducible set of '''k''' points is used for the calculation. To restore the correct charge density and the correct forces it is necessary to symmetrize these quantities.


It must be stressed that VASP does not determine the symmetry elements of the primitive cell. If the supercell has a lower symmetry than the primitive cell only the lower symmetry of the supercell is used in the calculation. In this case one should not expect that forces that should be zero according to symmetry will be precisely zero in actual calculations. The symmetry of the primitive cell is in fact broken in several places in VASP:
It must be stressed that VASP does not determine the symmetry elements of the primitive cell. If the supercell has a lower symmetry than the primitive cell only the lower symmetry of the supercell is used in the calculation. In this case, one should not expect that forces that should be zero according to symmetry will be precisely zero in actual calculations. The symmetry of the primitive cell is in fact broken in several places in VASP:


*Local potential:
*Local potential:
:In reciprocal space, the potential ''V''('''G''') should be zero, if '''G''' is not a reciprocal lattice vector of the primitive cell. For {{TAG|PREC}}=Medium, this is not guaranteed due to "aliasing" or wrap around and the charge density (and therefore the Hartree potential) might violate this point. But even for {{TAG|PREC}}=High, small errors are introduced, because the exchange correlation potential is calculated in real space.
:In reciprocal space, the potential ''V''('''G''') should be zero, if '''G''' is not a reciprocal lattice vector of the primitive cell. For {{TAG|PREC}}=Medium, this is not guaranteed due to "aliasing" or wrap around and the charge density (and therefore the Hartree potential) might violate this point. But even for {{TAG|PREC}}=High, small errors are introduced, because the exchange-correlation potential is calculated in real space.


*'''k'''-points:
*'''k'''-points:
:In most cases, the automatic '''k'''-point grid does not have the symmetry of the primitive cell.
:In most cases, the automatic '''k'''-point grid does not have the symmetry of the primitive cell.
{{NB|tip|If symmetry is switched on then {{TAG|NWRITE}}{{=}}3 writes out the symmetry operations to the {{TAG|OUTCAR}} file.}}
== Related tags and articles ==
{{TAG|OUTCAR}}, {{TAG|IALGO}}, {{TAG|IBRION}}, {{TAG|MDALGO}}, {{TAG|ISIF}}, {{TAG|NWRITE}}


{{sc|ISYM|Examples|Examples that use this tag}}
{{sc|ISYM|Examples|Examples that use this tag}}
----
----
[[The_VASP_Manual|Contents]]


[[Category:INCAR]]
[[Category:INCAR tag]][[Category:Electronic minimization]][[Category:Symmetry]][[Category:Memory]]

Revision as of 08:57, 20 October 2023

ISYM = -1 | 0 | 1 | 2 | 3 

Default: ISYM = 1 if VASP runs with USPPs
= 3 if LHFCALC=.TRUE.
= 2 else

Description: ISYM determines the way VASP treats symmetry.


ISYM=1 | 2 | 3, switches on the use of symmetry. For ISYM=-1 | 0, the use of symmetry is switched off.

For ISYM=2 a more efficient, memory conserving symmetrization of the charge density is used (than for ISYM=1). This reduces memory requirements in particular for the parallel version.

For ISYM=3, VASP does not directly symmetrize the charge density. Instead, the charge density is constructed by applying the relevant symmetry operations to the orbitals at the k-points in the irreducible part of the Brillouin zone. This method of symmetrization is used when LHFCALC=.TRUE.

For ISYM=0, VASP does not use symmetry, but it will assume that Ψk*-k and reduces the sampling of the Brillouin zone accordingly. This value should be set for molecular dynamics, i.e. IBRION=0.

For ISYM=-1 the use of symmetry is switched off completely.

When the use of symmetry is switched on, VASP determines the point group symmetry and the space group consistent with the structure and initial velocities found on the POSCAR file (this is written out to the OUTCAR file for each NWRITE option), and the initial magnetic moments specified through the MAGMOM tag in the INCAR file. The SYMPREC-tag (VASP.4.4.4 and newer versions) determines by how much atomic positions may differ and still be judged to be equivalent by the symmetry detection algorithms. The default is 10-5, which is usually sufficiently large even if the POSCAR file has been generated with a single precision program. Increasing the SYMPREC tag means, that the positions in the POSCAR file can be less accurate. During the symmetry analysis, VASP determines

  • the Bravais lattice type of the supercell,
  • the point group symmetry and the space group of the supercell with basis (static and dynamic) - and prints the names of the group (space group: only 'family'),
  • the type of the generating elementary (primitive) cell if the supercell is a non-primitive cell,
  • all 'trivial non-trivial' translations (= trivial translations of the generating elementary cell within the supercell) -- needed for symmetrization of the charge,
  • the symmetry-irreducible set of k-points if automatic k-mesh generation was used and additionally the symmetry-irreducible set of tetrahedra if the tetrahedron method was chosen together with the automatic k-mesh generation and of course also the corresponding weights ('symmetry degeneracy'),
  • and tables marking and connecting symmetry equivalent ions.

The symmetry analysis is done in four steps:

  • First the point group symmetry of the lattice (as supplied by the user) is determined.
  • Then tests are performed, on whether the basis breaks the symmetry. Accordingly, these symmetry operations are removed.
  • The initial velocities are checked for symmetry breaking.
  • Finally, it is checked whether MAGMOM breaks the symmetry. Correspondingly the magnetic symmetry group is determined.

The program symmetrizes automatically:

  • The total charge density according to the determined space group
  • The forces on the ions according to the determined space group.
  • The stress tensor according to the determined space group

Why is symmetrization necessary: Within LDA the symmetry of the supercell and the charge density is always the same. This symmetry is broken because a symmetry-irreducible set of k points is used for the calculation. To restore the correct charge density and the correct forces it is necessary to symmetrize these quantities.

It must be stressed that VASP does not determine the symmetry elements of the primitive cell. If the supercell has a lower symmetry than the primitive cell only the lower symmetry of the supercell is used in the calculation. In this case, one should not expect that forces that should be zero according to symmetry will be precisely zero in actual calculations. The symmetry of the primitive cell is in fact broken in several places in VASP:

  • Local potential:
In reciprocal space, the potential V(G) should be zero, if G is not a reciprocal lattice vector of the primitive cell. For PREC=Medium, this is not guaranteed due to "aliasing" or wrap around and the charge density (and therefore the Hartree potential) might violate this point. But even for PREC=High, small errors are introduced, because the exchange-correlation potential is calculated in real space.
  • k-points:
In most cases, the automatic k-point grid does not have the symmetry of the primitive cell.


Tip: If symmetry is switched on then NWRITE=3 writes out the symmetry operations to the OUTCAR file.

Related tags and articles

OUTCAR, IALGO, IBRION, MDALGO, ISIF, NWRITE

Examples that use this tag