Category:Molecular Dynamics: Difference between revisions
No edit summary |
No edit summary |
||
Line 5: | Line 5: | ||
The input files for standard molecular dynamics runs are the same as for other calculational methods. However additionally to the structural data the {{TAG|POSCAR}} file can contain the initial velocities as a separate block. It can also contain the input on which atomic positions should be constrained or not. | The input files for standard molecular dynamics runs are the same as for other calculational methods. However additionally to the structural data the {{TAG|POSCAR}} file can contain the initial velocities as a separate block. It can also contain the input on which atomic positions should be constrained or not. | ||
Constrained and bias molecular dynamics also require an additional input file, the {{TAG|ICONST}} file. This file specifies the collective variables. The ({{TAG|ICONST}}) file is also required for the monitoring of geometric parameters. | Constrained and bias molecular dynamics ({{TAG|Constrained molecular dynamics}}, {{TAG|Metadynamics}} and {{TAG|Biased molecular dynamics}}) also require an additional input file, the {{TAG|ICONST}} file. This file specifies the collective variables. The ({{TAG|ICONST}}) file is also required for the monitoring of geometric parameters ([[MDALGO#Monitoring geometric parameters|Monitoring geometric parameters]]). | ||
Besides the main output files {{TAG|OUTCAR}} and {{TAG|OSZICAR}} | Besides the main output files, {{TAG|OUTCAR}} and {{TAG|OSZICAR}}, the {{TAG|XDATCAR}} is an important output file. It contains the trajectory of the MD. The {{TAG|REPORT}} file is important for molecular dynamics runs where the {{TAG|ICONST}} file was used. | ||
== Theory == | == Theory == | ||
*Ensembles: [[:Category:Ensembles|Ensembles]]. | *Ensembles: [[:Category:Ensembles|Ensembles]]. |
Revision as of 17:34, 5 June 2019
To get an idea about what basically molecular dynamics is and what the main contents are we refer the reader to references [1] and [2]. After understanding the theory behind molecular dynamics we refer the reader to Molecular dynamics calculations, which describes how to run standard molecular dynamics simulations. Every advanced molecular dynamics method builds on the knowledge in that tutorial and should be ideally only viewed after understanding the basics.
Important files
The input files for standard molecular dynamics runs are the same as for other calculational methods. However additionally to the structural data the POSCAR file can contain the initial velocities as a separate block. It can also contain the input on which atomic positions should be constrained or not.
Constrained and bias molecular dynamics (Constrained molecular dynamics, Metadynamics and Biased molecular dynamics) also require an additional input file, the ICONST file. This file specifies the collective variables. The (ICONST) file is also required for the monitoring of geometric parameters (Monitoring geometric parameters).
Besides the main output files, OUTCAR and OSZICAR, the XDATCAR is an important output file. It contains the trajectory of the MD. The REPORT file is important for molecular dynamics runs where the ICONST file was used.
Theory
- Ensembles: Ensembles.
- Thermostats: Thermostats.
- Interface pinning: Interface pinning calculations.
- Constrained molecular dynamics: Constrained molecular dynamics.
- Metadynamics: Metadynamics.
- Biased molecular dynamics: Biased molecular dynamics.
- Slow-growth approach: Slow-growth approach.
How to
- Basic molecular dynamics calculations: Molecular dynamics calculations.
- Ensembles: Ensembles.
- Thermostats: Thermostats.
- Interface pinning: Interface pinning calculations.
- Constrained molecular dynamics: Constrained molecular dynamics.
- Metadynamics: Metadynamics.
- Biased molecular dynamics: Biased molecular dynamics.
- Slow-growth approach: Slow-growth approach.
- Monitoring of geometric parameters: Monitoring geometric parameters.
Compilation
IMPORTANT NOTE: The simulation methods described in this section are included in VASP as of version 5.2.12, and require VASP to be compiled with the cpp flag -Dtbdyn that should be included in the corresponding line of makefile, as for instance in the following example:
CPP = $(CPP_) -DHOST=\"IFC9_fftw\" \ -Dkind8 -DNGXhalf -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc \ -Dtbdyn
This category currently contains no pages or media.