Skip to main content
Step 2: Feature Temporal Stability. Analyzes features for temporal stationarity to prevent data leakage and overfitting. It filters the ‘clean’ feature set down to a ‘stable’ set.

Parameters

inputs : FeStabilizerInput
Custom stability configuration. If None, resolves from ‘.clean’ state.
is_target : bool
If True, performs stability check on the target variable instead of features (skips registration of result datasets). Defaults to False.
**kwargs : dict
Additional parameters passed to the FeatureStabilizer worker.
Inputs full schema can be obtained by ctx.workers.fe_stabilizer.spec with main params:
inputs == None→pipeline data context
train_set != None→custom train data for fe_stabilizer training and feature temporal cleaning
test_set != None→custom test data might be provided to obtain temporal view and stats
num_features != None→optional subset of numerical features
cat_features != None→optional subset of categorical features

Returns

FeatureStabilizerWorker
The populated instance of FeatureStabilizerWorker.
Populates attributes into the worker context:
model→ctx.workers.fe_stabilizer
inputs→ctx.workers.fe_stabilizer.spec
result→ctx.workers.fe_stabilizer.result
state→ctx.workers.fe_stabilizer.state
report→ctx.workers.fe_stabilizer.report
stats→ctx.workers.fe_stabilizer.stats
fitter→ctx.workers.fe_stabilizer.fitter
Registers data into the datasets context:
features→ctx.datasets.features.all.stable.dist
features→ctx.datasets.features.num.stable.dist
features→ctx.datasets.features.cat.stable.dist
dropped→ctx.datasets.features.all.dropped.stable.dist
dropped→ctx.datasets.features.num.dropped.stable.dist
dropped→ctx.datasets.features.cat.dropped.stable.dist
stats→ctx.datasets.stats.stable.features

Examples

Defining the Project Context (Control Plane) & Project Scope:

Worker → Model → Fitter

Accessing worker’s inputs schema → parameters & types (shown in the display output):
Accessing model’s fitter options and schema → parameters & types (shown in the display output):
Executing workers with defaults → auto provided by the context:
Once worker has been executed, thus its main model has been built, we have access to all populated attributes.
View to model report of executed worker:

Model → Fitter

Once worker has been executed, we can obtain internal fitter state and its parametrization (shown in the display output):
The fitted fitter provides all populated attributes.
Direct choice and parametrization of internal fitter:
In the experimenting phase, when various time variables might be under testing (note that ‘time_var2’ must be present in the data):

Attributes

All worker attributes return None prior its execution.