Status: Needs Review
This page has not been reviewed for accuracy and completeness. Content may be outdated or contain errors.
Configuration Groups¶
Hydra config groups keep current experiments modular and composable.
Current Group Layout¶
configs/
├── data/
├── pipeline/
│ ├── anomaly/
│ └── sam3/
├── plugins/
├── training/
└── trainrun/
Standard Trainrun Composition¶
# @package _global_
defaults:
- /pipeline/anomaly/rx@pipeline: rx_statistical
- /data@data: lentils
- /training@training: default
- _self_
name: rx_demo
output_dir: ./outputs/${name}
Pipeline Group¶
Current pipeline families:
configs/pipeline/anomaly/rx/configs/pipeline/anomaly/deep_svdd/configs/pipeline/anomaly/adaclip/configs/pipeline/sam3/
Override example:
Data Group¶
Use configs/data/ for dataset paths, IDs, and loader settings.
Example:
data:
cu3s_file_path: data/Lentils/Lentils_000.cu3s
annotation_json_path: data/Lentils/Lentils_000.json
train_ids: [0, 2, 3]
val_ids: [1, 5]
test_ids: [1, 5]
batch_size: 2
Training Group¶
Use configs/training/ for trainer and optimizer settings.
Example:
Plugin Group¶
Use the narrow manifest required by the workflow:
configs/plugins/adaclip.yamlconfigs/plugins/bytetrack.yamlconfigs/plugins/deepeiou.yamlconfigs/plugins/detr.yamlconfigs/plugins/sam3.yamlconfigs/plugins/trackeval.yamlconfigs/plugins/ultralytics.yaml
Each plugin ships its own plugins.yaml manifest; reference the ones you need from your config. The full list of plugin-supplied nodes lives in the Nodes catalog.