Custom Extensions#
macroforecast supports custom work by accepting ordinary Python callables at
the stage that owns the behavior. There is no separate custom registry and no
YAML wrapper requirement. A custom function must return the same object shape
that the next stage already expects.
Use this section when a built-in loader, cleaning step, feature transform, model, search rule, diagnostic, or artifact is not enough.
Pages#
Page |
Use it for |
|---|---|
End-to-end custom workflow and stage-local design rule. |
|
In-memory panels, custom CSV/Parquet loaders, frequency and metadata contracts. |
|
Direct preprocessing callables and runner-safe custom preprocessing steps. |
|
Direct custom feature transforms and fitted feature-spec steps. |
|
User estimators, fit return objects, model specs, model ensembles, and search spaces. |
|
Custom sample policies, hyperparameter search algorithms, and forecast combinations. |
|
Custom scalar metrics, custom forecast-comparison tests, and custom evaluation slices. |
|
Custom model interpretation, feature diagnostics, and forecast diagnostics. |
|
Saving custom tables, dictionaries, notes, diagnostics, and manifests. |
Flow Contract#
Stage |
Custom entry point |
Must return |
|---|---|---|
Data |
|
|
Preprocessing |
|
|
Feature engineering |
|
Feature |
Models |
|
|
Windows and selection |
|
|
Forecasting |
|
|
Evaluation and tests |
callable metric, |
Metric columns, |
Interpretation and analysis |
|
Schema-tagged |
Output |
|
Files plus |