Output Directory Layout¶
This page lists the main files that the commands write, the default output directories, and where each file goes inside all. Each command page lists all of its files under Output files.
Filename conventions¶
Filename |
Written by |
Purpose |
|---|---|---|
|
|
The aggregate JSON result (see JSON Output Reference). |
|
per-stage and report commands with |
A copy of the command’s |
|
With |
The JSON result of one command or report, also written when the run ends without converging. |
|
CLI and Colab runs, once the output directory exists |
The command line (quoted for the shell) and the stdout/stderr printed while the command runs, including the lines that show how the run ended; the command’s page lists them (for example opt → Checking convergence). Help, version, and dry-run calls do not create it, nor do the commands without an output directory ( |
|
|
Text summary. The header gives |
|
|
Optimized geometry, the structure to pass to the next command; also written when the optimization does not converge. The |
|
|
Reaction path frames. The |
|
|
Reaction path frames (all images) and the highest-energy image (HEI). When file conversion is on, |
|
|
Energy profile of the minimum energy path (MEP): |
|
|
IRC (intrinsic reaction coordinate) trajectories (full path plus each branch), with a |
|
|
Ends of the two branches: the endpoint candidates to optimize with |
|
|
Vibrational mode listing. |
|
|
The ML region without and with the link hydrogens, as the DFT calculation sees it; |
|
commands with |
Copies of the outputs in the input format, written next to them: PDB for PDB/mmCIF input, plus a |
Default --out-dir¶
Subcommand |
Default |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
next to the input file (writes |
Set another directory with -o/--out-dir <path>. The preparation commands take file paths instead: extract takes one or more -o/--output <file> paths, mm-parm an -o/--out-prefix <prefix>, and define-layer an -o/--output <file>.
Standalone vs all¶
A standalone subcommand writes a flat result_<subcmd>/ directory, without segments/ or _work/. Inside all, each post-processing stage uses the same file layout under segments/seg_NN/ in ts/, irc/, freq/, and dft/.
path-search/path-optare laid out differently. Run standalone, they write the files in the table above toresult_path_search/orresult_path_opt/. Insideall, the MEP search runspath-optby default and the recursivepath-searchwith--refine-path; the raw output stays in_work/path_opt/or_work/path_search/, and only the MEP files (mep_trj.*,mep_plot.png,energy_diagram_MEP.png) are moved to the root.
The all tree has three parts: the deliverables at the root, segments/, and _work/. The tree below shows the main entries; all → Output files lists every file, including those inside seg_NN/, and the names of the energy diagrams:
result_all/
├─ summary.log · summary.json # run summary
├─ mep_trj.pdb · mep_trj.cif · mep_trj.xyz # MEP coordinates
├─ mep_plot.png · energy_diagram_MEP.png · energy_diagram_*_all.png · irc_plot_all.png
├─ ml_region.pdb # ML region (reusable with --model-pdb)
├─ mm_parm/ # Amber topology <input>.parm7 / .rst7 (reusable with --parm7)
├─ layered/ # full structures with the layers in the B-factors
├─ segments/
│ └─ seg_NN/ # one reaction step: seg_01, seg_02, ...
│ ├─ reactant.{pdb,cif,xyz} · ts.* · product.* # optimized R, TS, and P (--tsopt)
│ └─ ts/ · irc/ · endpoint_opt/ · freq/{R,TS,P}/ · dft/{R,TS,P}/ # per-stage working files (--tsopt / --thermo / --dft)
└─ _work/ # intermediate files, including the TS candidates (HEI)
├─ pockets/ · scan/
└─ path_opt/ # MEP search and hei_seg_NN.* (path_search/ with --refine-path)
In TS-only mode (one transition-state (TS) candidate given with --tsopt and no -s/--scan-lists) there is no MEP stage, so _work/path_opt/ is absent and the deliverables live under segments/seg_01/.
Notes¶
Runs that stop early: a run that stops at the argument or input checks, before its output directory is set up, may write none of the files above.
summary.json/result.jsonwithout--out-json: a successful per-stage run writes them only with--out-json. When a run stops on an exception after the output directory is set up, both are written even without the flag, with"execution_status": "failed"and an"error_type".--no-convert-filesinall: it cannot be combined with--tsopt,--thermo, or--dft.
See Also¶
all — the full
result_all/tree and the energy diagramsJSON Output Reference — keys of
summary.jsonandresult.json, with Python and jq examplesCommon options and selectors —
--out-dir,--convert-files, and exit codesTroubleshooting — common errors and fixes