Skip to main content
Step 8: WOE Feature Stability Validation. The final transformation guardrail. Screens WOE-encoded features for temporal stability to ensure the encoding is robust across data folds.

Parameters

inputs : WoeStabilizerInput
Custom stability configuration. If None, resolves from ‘train.stable’, ‘test.clean’ and ‘features.encoded.woe’.
**kwargs : dict
Additional parameters passed to the WoeStabilizer worker.
Inputs full schema can be obtained by ctx.workers.woe_stabilizer.spec with main params:
inputs == None→pipeline data context
train_set != None→custom train data for woe_stabilizer training
test_set != None→custom test data for woe_stabilizer assessment view
woe_features != None→custom subset of woe encoded vars

Returns

WoeStabilizerWorker
The populated instance of WoeStabilizerWorker.
Populates attributes into the worker context:
model→ctx.workers.woe_stabilizer
inputs→ctx.workers.woe_stabilizer.spec
result→ctx.workers.woe_stabilizer.result
state→ctx.workers.woe_stabilizer.state
report→ctx.workers.woe_stabilizer.report
stats→ctx.workers.woe_stabilizer.stats
fitter→ctx.workers.woe_stabilizer.fitter
Registers data into the datasets context:
features→ctx.datasets.features.woe.stable
features→ctx.datasets.features.all.stable.target
features→ctx.datasets.features.num.stable.target
features→ctx.datasets.features.cat.stable.target
features→ctx.datasets.features.ixn.stable.target
dropped→ctx.datasets.features.woe.dropped.stable
dropped→ctx.datasets.features.all.dropped.stable.target
dropped→ctx.datasets.features.num.dropped.stable.target
dropped→ctx.datasets.features.cat.dropped.stable.target
dropped→ctx.datasets.features.ixn.dropped.stable.target
stats→ctx.datasets.stats.encoded.woe.stable

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:
Note that steps 0-3 can be run by ExecutionContext one-liner:
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 targets might be under testing (note that ‘target2’ and ‘time_var2’ must be present in the data):

Attributes

All worker attributes return None prior its execution.