Skip to content

1.4 Access, units and file anatomy

The inputs on this page are educational templates that have not been executed for this course. Use an authorized installation, verify version-specific options and establish your own convergence.

1.4.1 Before spending a compute allocation

This course follows a two-atom, nonmagnetic diamond-silicon cell using semilocal PBE density-functional theory. You need a legitimate VASP installation and authorized PBE Si PAW data. Ask your institutional administrator which executable, module and MPI launcher are supported. A publicly downloadable tutorial does not grant redistribution rights to VASP or POTCAR. Do not upload restricted potential contents to a public repository or teaching archive. Share your own geometry and settings, dataset identifiers and permitted hashes instead. Official POTCAR documentation; NSC installation and access guide.

Confirm that you can create directories and inspect plain text, know the batch-queue rules, and can identify the exact Si potential release and variant. Run production parallel calculations on allocated compute nodes. Keep each question in a separate directory: 01-static, 02-cutoff/e400, 03-kmesh/k08, 04-relax, 05-scf, 06-bands and 07-dos. A clear directory dependency prevents a postprocessing run from overwriting its parent density.

1.4.2 Four files, four responsibilities

File Meaning Check before accepting the run
POSCAR Lattice, atom counts and coordinates Visualize periodic neighbors; verify distances and volume
INCAR Physical model and numerical instructions Compare requested tags with effective values echoed in OUTCAR
KPOINTS Integration mesh or plotting path Inspect IBZKPT and actual point count
POTCAR Authorized PAW datasets in species order Verify potential labels, valence data, release and ENMAX

This course uses an explicit KPOINTS file to make sampling auditable; VASP can also generate meshes through KSPACING. POSCAR species counts and POTCAR block ordering determine which data describe each atom. Merely editing an element label cannot repair a mismatched potential. For multiple species, concatenate only authorized datasets in the same intended ordering and record that order. POSCAR format; KPOINTS format.

1.4.3 Read outputs by purpose

OUTCAR is the detailed log and OSZICAR the compact iteration record. CONTCAR contains the output structure. CHGCAR stores density and PAW-related information for supported restarts and postprocessing; WAVECAR stores wavefunctions. They are not interchangeable. Use vasprun.xml, or vaspout.h5 on builds that support it, for structured analysis. EIGENVAL, DOSCAR and PROCAR support electronic-structure analysis when the corresponding information was written. Never assume that an output filename alone proves that the run finished or that the contents match a new geometry. OUTCAR; OSZICAR; CHGCAR.

1.4.4 Units and normalization

Use eV for ENCUT, SIGMA and electronic energy thresholds, Å for lattice lengths, and eV/Å for forces. OUTCAR's stress line labeled in kB uses kilobar: \(1\ \mathrm{kbar}=0.1\ \mathrm{GPa}\). It does not refer to Boltzmann's constant. Positive diagonal stress in VASP corresponds to compression; do not transfer another code's sign convention without checking. ISIF stress convention.

Total energy belongs to the simulated cell. For this two-atom primitive cell, an energy difference per atom is \(\Delta E_{\mathrm{atom}}=(E_2-E_1)/2\) for calculations with the same composition and compatible settings. A raw cell energy from this model is not directly comparable to an eight-atom conventional-cell energy. Comparisons also require a common potential family, functional and documented energy convention.

1.4.5 Exercise and deliverable

Write a one-page run manifest listing version/build, approved executable, system and atom count, authorized dataset identity, target observable and proposed convergence tolerance. Identify what will be shared publicly and what must stay within the license. Explain why a statement such as “the energy is −X eV” is incomplete without the cell, method, normalization and reference. This exercise needs no calculation; its output is the manifest and a directory plan.


Previous:Course overview · Next:First bulk-silicon single point