Configuration System#
Enerzyme workflows are composed from YAML sections. Different commands read different subsets; some sections override training defaults at inference time.
Section index#
Section |
Used by |
Reference config |
|---|---|---|
|
train, predict, extract, collect |
|
|
train; loaded from model dir at infer |
|
|
train; partial use in predict/extract |
|
|
train, predict |
|
|
simulate |
|
|
simulate |
all sim YAMLs |
|
extract |
|
|
annotate |
|
|
annotate |
|
Training artifacts#
After enerzyme train -c train.yaml -o out/:
out/config.yaml— resolved configuration (use as-mcfor predict/simulate)out/FFxx/orout/FFxx_suffix/— model checkpoints (best/,last/)out/processed_dataset_<hash>/— preprocessed HDF5 cacheout/logs/— training logs
Override rules at inference#
Predict (enerzyme predict -c pred.yaml -m model_dir -mc train.yaml):
-coverridesDatahub(test path, features) andMetric-mcsuppliesModelhuband default transforms/neighbor list consistencyNeighbor list and transform settings should match training unless you know the effect
Simulate (enerzyme simulate -c sim.yaml -m model_dir -mc train.yaml):
-csuppliesSimulationandSystem-mcsupplies model architecture andDatahubtransforms for the ASE calculatorOptional
-cp(calculator patch) and-pp(PLUMED patch) add external plugins
Extract — combines predict-style Datahub with Extractor radii and reference molecule.
Annotate — Supplier + QMDriver only; independent of Modelhub.
Legacy vs current schema#
Older configs use a flat Datahub with compression:; current configs use compressed: and optional datasets: for multi-dataset training. Both layouts are still accepted; new projects should follow enerzyme/config/train.yaml.
Splitter configs similarly support:
Old:
parts: [training, validation]+ratios: [...]New:
parts: [{name, dataset, ratio}, ...]for multi-dataset splits
See /user_guide/data/splitting.