Skip to content

model-artifacts.md

Latest commit

 

History

History
93 lines (68 loc) · 4.34 KB

model-artifacts.md

File metadata and controls

93 lines (68 loc) · 4.34 KB
Raw

DeePMD model artifacts for inference

Read this reference when the model is a training checkpoint, its extension is .pt2, or the correct backend/export path is unclear.

Identify the artifact

A suffix identifies a serialization/backend route, not necessarily a model family. In particular, both DPA3 and DPA4 training checkpoints use .pt. Never classify a .pt checkpoint from its filename alone. Inspect its stored model configuration when needed:

dp --pt show model.pt descriptor fitting-net type-map
Artifact Typical role Inference guidance
.pb TensorFlow frozen model Load with DeepPot or use dp test.
.pth Conventional PyTorch frozen model Load with DeepPot or use dp test.
.pt PyTorch training checkpoint Inspect before use. DPA4 supports eager Python evaluation and embedding extraction from a checkpoint; deployment normally uses a frozen artifact.
.pt2 AOTInductor deployment archive Use supported inference paths in a compatible runtime; the suffix alone does not imply descriptor hooks, portability, or multi-rank support.

Backend selection for inference is normally determined from the model artifact. Do not add a backend flag merely from the assumed model family.

DPA4/SeZM

DPA4/SeZM supports Python evaluation from its .pt checkpoint, but a .pt2 archive is the normal frozen deployment artifact. Freeze with:

dp --pt freeze -c model.ckpt.pt -o frozen_model

The command writes frozen_model.pt2 for a detected DPA4/SeZM checkpoint. For a multi-task checkpoint, select the head during export with --head SELECTED_BRANCH; the resulting .pt2 is already single-head. Evaluate the archive with:

from deepmd.infer import DeepPot

model = DeepPot("frozen_model.pt2")
energy, force, virial = model.eval(coord, cell, atype)

For labeled data:

dp test -m frozen_model.pt2 -s /path/to/system -n 30

DeepPot.eval on DPA4/SeZM .pt2 archives is covered for energy, force, virial, atomic energy, and atomic virial. dp test uses the same model dispatch. Both require an installed DeePMD-kit/PyTorch runtime compatible with the compiled archive.

Check that atype follows the model type_map and that coordinates/cells use the units and shapes documented by DeepPot.

Descriptors and DPA4 embeddings

Descriptor evaluation is conditional for .pt2. It requires an archive that contains the serialized model.json; metadata-only archives can run the main DeepPot.eval path but raise NotImplementedError for eval_descriptor. In particular, do not run dp eval-desc on a DPA4 .pt2 produced by the dp --pt freeze command above, because that export is metadata-only. Use a supported checkpoint or verify the archive contents and backend first.

DPA4 additionally exposes model embeddings from a training checkpoint:

dp embed -m model.ckpt.pt -s /path/to/system -o embedding.hdf5

dp embed supports the DPA4/SeZM .pt checkpoint and does not support .pt2.

Validation

  • Confirm that the artifact exists and can be loaded in the target environment.
  • Inspect the stored descriptor when .pt could mean DPA3 or DPA4.
  • Confirm the type map before constructing atype.
  • Run a small finite energy/force/virial evaluation before a large batch.
  • Treat .pt2 as a compiled deployment artifact, not a portable checkpoint. Export and validate it with a device and toolchain compatible with the final Python, C++, or LAMMPS runtime.

References