- name
- hpc-vasp
- description
- Build, review, debug, and automate VASP first-principles workflows. Use when working with VASP input sets such as INCAR, POSCAR, KPOINTS, and POTCAR; when choosing SCF, relaxation, static, DOS, or band-structure stages; or when fixing convergence, symmetry, cutoff, and k-point issues.
HPC VASP
Treat VASP as a staged workflow built around a coherent four-file input set.
Start
- Read
references/input-set-manual.mdbefore creating or editing a VASP run directory. - Read
references/stage-and-parameter-matrix.mdwhen mapping SCF, relaxation, static, DOS, and band workflows to INCAR and KPOINTS choices. - Read
references/pseudopotential-kpoints-and-convergence.mdwhen choosing POTCAR, k-point density, smearing, and electronic controls. - Read
references/cluster-execution-playbook.mdwhen staging a VASP workflow for scheduler-backed cluster execution. - Read
references/error-recovery.mdwhen VASP parsing, SCF, ionic relaxation, or post-processing setup fails.
Additional References
Load these on demand:
references/poscar-species-and-structure.mdfor species ordering, coordinate modes, and cell interpretationreferences/restarts-spin-and-wavefunction-files.mdfor restart logic, spin setup, and charge or wavefunction handoffreferences/dos-and-band-workflows.mdfor static, DOS, and band-structure stage sequencingreferences/incar-tag-matrix.mdfor stage-to-tag and electronic-class-to-smearing tablesreferences/workflow-handoff-matrix.mdfor stage artifacts and restart-file handoff tablesreferences/error-pattern-dictionary.mdfor structured SCF, ionic, and handoff failure signaturesreferences/cluster-execution-playbook.mdfor stage handoff, resource-shape discipline, and restart policy on clusters
Reusable Templates
Use assets/templates/ when a concrete starting input is needed, especially:
INCAR_relaxINCAR_staticKPOINTS_gammaINCAR_bandsKPOINTS_mp_6x6x6POSCAR_sivasp-standard-slurm.sh
Guardrails
- Do not mix POTCAR datasets casually across elements or workflow stages.
- Do not copy INCAR tags from unrelated systems without checking metallic versus insulating behavior.
- Do not run DOS or bands workflows before the geometry and ground-state setup are trustworthy.
- Do not guess VASP tags from Quantum ESPRESSO or other DFT codes.
Outputs
Summarize:
- workflow stage
- INCAR intent
- KPOINTS strategy
- POTCAR and species assumptions
- expected key outputs and next stage