Override Defaults via Config File¶
Examples¶
Example 1: Basic prediction config¶
Generate Prediction Dataset¶
| configs/predict/custom_train/preprocess_1976_example.yaml | |
|---|---|
- Point to the config of the training model (relative to where this config file is placed).
- Point to the config of the training dataset (relative to where this config file is placed).
- This should be a list of date ranges you would want to generate predictions for.
Generate Predictions¶
| configs/predict/custom_train/1979-01-26.yaml | |
|---|---|
- Relative path to the Hydra config used to generate the trained model (relative to the prediction config file).
- You can define a list of dates for which to make predictions. This date has to exist in the prediction dataset being used.
- Relative path to the prediction dataset config file (relative to the path you are running the
canari_ml predictcommand from).
This can be run using:
Example 2: Combined prediction, postprocess and plotting config¶
You can also (optionally) enable the default /postprocess and /plot config files to the prediction config, which will allow you to use the same config file to generate the output netCDF, and plot the results.
| configs/predict/custom_train/1979-01-26_and_plot.yaml | |
|---|---|
This can be run using: