Common Error Recipes¶
Use this page when you know the symptom but do not know which subcommand page to open first. For full details, keep Troubleshooting open in parallel.
Quick routing¶
Symptom |
Start here |
Then read |
|---|---|---|
Input & extraction |
||
Missing element columns / extraction aborts |
|
|
|
Regenerate all PDBs with the same prep tool + settings; re-run |
|
Charge & spin |
||
|
Set |
|
Energies/states look wrong after a run |
Re-check charge/multiplicity policy in CLI conventions |
|
Installation & environment |
||
UMA model 401/403 / gated-repo error ( |
|
|
|
|
|
|
Fix AmberTools availability first |
|
|
Rebuild native extension ( |
|
DMF mode import errors ( |
Install |
|
GPU & CUDA |
||
CUDA out-of-memory at runtime ( |
Shrink ML region ( |
|
CUDA/GPU runtime mismatch |
Verify |
|
Convergence |
||
TSOPT does not converge |
Reduce |
|
IRC does not terminate |
Reduce |
|
Optimizer stalls at flat energy (MLIP noise floor) |
Let |
|
Optimizer stalls at flat energy (MLIP noise floor) |
Tune |
|
Plotting |
||
Plot export failures |
Install Chrome runtime for Plotly export |
Recipe 1: Extraction fails before MEP starts¶
Signal:
Errors mention missing element symbols, atom-count mismatch, or empty pockets.
First checks:
Confirm all inputs are prepared with the same workflow and atom ordering is consistent.
Ensure element columns are present before running
extractorall.
Typical fix path:
Repair elements -> rerun extraction -> confirm pocket size and residue inclusion.
Recipe 2: Charge/spin validation fails¶
Signal:
If the log shows unexpected charges (e.g., protein charge is wrong, or total charge does not match expectations), review the charge resolution rules.
First checks:
Ensure total charge and multiplicity are physically correct for the target state.
If using residue maps, validate each residue key in
--ligand-charge.Verify the resolution rules in CLI Conventions when results look physically inconsistent.
Typical fix path:
Prefer explicit
-qand-mfor critical runs, then retry scan/path/tsopt.
Recipe 3: Build or environment blockers¶
Signal:
mm-parmtooling not found,hessian_ffimport failures, CUDA mismatch.
First checks:
Confirm required executables and Python extension modules exist in the active env.
Validate GPU visibility and PyTorch CUDA compatibility.
Typical fix path:
Repair toolchain/build first, then rerun with
--help-advancedto verify available options before full execution.
Recipe 4: Convergence and post-processing failures¶
Signal:
TSOPT stalls or IRC branches look unstable.
First checks:
First-order-saddle certification requires exactly one imaginary mode; inspect its displacement and IRC connectivity.
TSOPT: reduce
trust_radius/max_stepand increase its cycle limit.trust_maxdefaults to 0.10 bohr for RFO-family TS optimizers.IRC: reduce
--step-sizeand increase--max-cycles.Check whether the configured energy-plateau window is flat while force/step criteria remain unmet. The default fallback stops with
status: stalled; it does not declare convergence (see Troubleshooting).
Typical fix path:
Run a smaller diagnostic case, tune thresholds/step sizes, then scale back up.