freq¶
Compute vibrational frequencies and thermochemistry (ZPE, Gibbs energy, etc.) using an MLIP backend (UMA by default; -b/--backend also supports ORB, MACE, AIMNet2). Use it when full vibrational analysis is required — for example, to confirm that a stationary point is a true minimum with no imaginary frequencies, or that a TS has exactly one — or when thermochemistry corrections (ZPE, Gibbs energy) are needed. When VRAM permits, --hessian-calc-mode Analytical speeds up Hessian evaluation. Imaginary frequencies appear as negative values.
Examples¶
Minimal run with explicit charge and spin:
# Minimal run with explicit charge and spin
pdb2reaction freq -i ts_or_min.pdb -q 0 -m 1 --out-dir ./result_freq
PHVA with link freezing and dump thermo payload:
# PHVA with link freezing and dump thermo payload
pdb2reaction freq -i ts_or_min.pdb -q 0 -m 1 --freeze-links --dump --out-dir ./result_freq_phva
Analytical Hessian mode on VRAM-rich nodes:
# Analytical Hessian mode on VRAM-rich nodes
pdb2reaction freq -i ts_or_min.pdb -q 0 -m 1 \
--hessian-calc-mode Analytical --out-dir ./result_freq_analytical
Workflow¶
Geometry loading & freeze handling: structures are read via
pysisyphus.helpers.geom_loader. For PDB inputs,--freeze-linksdetects cap hydrogens and freezes their parent atoms, then merges the resulting indices withgeom.freeze_atoms; the merged list is echoed and propagated to the MLIP backend and PHVA.MLIP backend:
--hessian-calc-modeselects analytical or finite-difference Hessians. The MLIP backend may return a partial (active) Hessian block whenever atoms are frozen. For Hessian evaluation modes, see Hessian evaluation mode.PHVA & TR projection: with frozen atoms, eigenanalysis occurs inside the active subspace, where translation/rotation modes are projected out. Both 3N×3N and active-block Hessians are accepted, and frequencies are reported in cm⁻¹ (negatives = imaginary).
Mode export:
--max-writelimits how many modes are animated. Modes are sorted by value (or absolute value with--sort abs). The sinusoidal animation amplitude (--amplitude-ang) and frame count (--n-frames) match the YAML defaults._trj.xyzanimations are produced for every input;.pdbanimations are written only when a PDB template exists and--convert-filesremains enabled (ASE conversion is used as a fallback).Thermochemistry: if
thermoanalysisis installed, a QRRHO-like summary (EE, ZPE, E/H/G corrections, heat capacities, entropies) is printed using PHVA frequencies. CLI pressure in atm is converted internally to Pa. When--dump, athermoanalysis.yamlsnapshot is also written.Performance: the implementation minimizes GPU memory usage by keeping a single Hessian resident.
Outputs¶
out_dir/ (default:./result_freq/)
├─ mode_XXXX_±freqcm-1_trj.xyz # Per-mode animations
├─ mode_XXXX_±freqcm-1.pdb # Only when a PDB template exists and conversion is enabled
├─ frequencies_cm-1.txt # Full frequency list using the selected sort order
└─ thermoanalysis.yaml # Present when `thermoanalysis` is importable and --dump is True
Console blocks summarizing resolved
geom,calc,freq, and thermochemistry settings.
Exit codes¶
See Exit codes in CLI Conventions.
CLI options¶
The tables below cover the options that need explanation; the full flag list is in the generated command reference — do not hand-duplicate it here.
Option |
Description |
Default |
|---|---|---|
|
Structure file accepted by |
Required |
|
Total charge. When omitted, charge can be inferred from |
Required unless a |
|
Either a scalar integer (e.g., |
None |
|
MLIP predictor parallelism (workers > 1 disables analytic Hessians). See workers > 1 disables analytical Hessians (UMA backend) for diagnostic notes. |
|
|
Workers per node, forwarded to the parallel predictor. |
|
|
Spin multiplicity (2S+1). |
|
|
PDB input (or XYZ/GJF with |
|
|
Comma-separated 1-based atom indices to freeze explicitly (e.g., |
None |
|
Number of modes to export. |
|
|
Mode animation amplitude (Å). |
|
|
Frames per mode animation. |
|
|
Mode ordering: |
|
|
Output directory. |
|
|
Thermochemistry temperature (K). |
|
|
Thermochemistry pressure (atm). On the CLI this flag is |
|
|
Write |
|
|
MLIP Hessian mode ( |
|
|
Toggle XYZ/TRJ → PDB companions when a PDB template is available (GJF is not written). |
|
|
Reference PDB topology to use when the input is XYZ/GJF (keeps XYZ coordinates). |
None |
|
Base YAML configuration applied before explicit CLI options. |
None |
|
Print resolved YAML layers/config and continue. |
|
|
Write a machine-readable |
|
|
MLIP backend. |
|
|
Implicit solvent name for xTB correction (e.g. |
|
|
xTB solvent model. |
|
|
Validate and print execution plan without running frequency analysis. |
|
YAML configuration¶
The geom, calc, freq, and thermo sections are unchanged from the canonical definitions in YAML Reference: see geom, calc, freq, and thermo. freq automatically sets calc.return_partial_hessian = true (PHVA) by default; YAML can override.
The only freq-specific default that differs from the canonical block is the output directory:
freq:
out_dir: ./result_freq/ # freq default
Notes¶
tsoptalready includes an imaginary-frequency check, so a separatefreqrun is mainly for thermochemistry or detailed mode inspection.A properly converged first-order saddle point (TS) is expected to have exactly one imaginary frequency (detection cutoff
hessian_dimer.neg_freq_thresh_cm, default 5 cm⁻¹).Imaginary frequencies are reported as negative values in cm⁻¹.
freqprints how many were detected and dumps details when--dump.--hessian-calc-modefollows the standard precedence (defaults < config < explicit CLI); an explicit CLI--hessian-calc-modevalue takes precedence overcalc.hessian_calc_modein the config YAML.
See Also¶
tsopt — Optimize TS candidates (includes imaginary-frequency check; follow with IRC for endpoint validation)
irc — IRC from TS (freq is often run on IRC endpoints for thermochemistry)
dft — Single-point DFT for higher-level energy refinement
all — End-to-end workflow with
--thermoYAML Reference — Full
freqandthermoconfiguration optionsGlossary — Definitions of ZPE, Gibbs Energy, Enthalpy, Entropy
Common Error Recipes — Symptom-first failure routing
Troubleshooting — Detailed fixes for common failure modes