Ridge / Regressor Layer
Ridge Regression: Linear regression with L2 regularization. This model solves a regression model where the loss function is the linear least squares function and regularization is given by the l2-norm.
Mathematical formulation: where:
- X is the feature matrix
- y is the target vector
- β are the coefficients
- α is the regularization strength
Key characteristics:
- Handles multicollinearity
- Prevents overfitting
- Shrinks coefficients
- Stable solutions
Advantages:
- Better generalization
- Numerical stability
- Handles correlated features
- Reduced variance
Common applications:
- Financial modeling
- Demand forecasting
- Scientific regression
- High-dimensional data
- Feature-rich models
Outputs:
- Predicted Table: Results with predictions
- Validation Results: Cross-validation metrics
- Test Metric: Hold-out performance
- Feature Importances: Regularized coefficients
SelectFeatures
[column, ...]Feature column selection for Ridge Regression:
Requirements:
-
Data properties:
- Numeric values
- Finite numbers
- Handled missing values
- Appropriate scaling
-
Preprocessing needs:
- Standardization recommended
- Outlier treatment
- Correlation analysis
- Feature engineering
-
Statistical considerations:
- Multicollinearity acceptable
- Linear relationships
- Feature importance
- Interaction effects
-
Quality checks:
- Scale compatibility
- Missing patterns
- Distribution analysis
- Correlation structure
Note: If empty, uses all numeric columns except target
SelectTarget
columnTarget column specification for Ridge Regression:
Requirements:
-
Data type:
- Numeric continuous
- No missing values
- Finite numbers
- Real-valued
-
Statistical properties:
- Normality preferred
- Constant variance
- Linear relationships
- Independence
-
Preprocessing:
- Scaling consideration
- Outlier treatment
- Distribution checks
- Transformation needs
-
Quality checks:
- Range verification
- Missing patterns
- Distribution shape
- Relationship linearity
Note: Must be a single numeric column
Params
oneofDefault configuration for Ridge Regression:
Core settings:
-
Regularization:
- Alpha = 1.0 (standard L2 penalty)
- Balanced regularization strength
-
Model structure:
- Intercept included
- Automatic solver selection
- Standard convergence (tol=1e-4)
-
Computation:
- Default iterations
- Optimal solver choice
- Unrestricted coefficients
Best suited for:
- Initial modeling
- Moderate multicollinearity
- Standard regression tasks
- General purpose use
Customizable parameters for Ridge Regression:
Parameter categories:
-
Model complexity:
- Regularization strength
- Intercept inclusion
- Coefficient constraints
-
Optimization:
- Solver selection
- Convergence control
- Iteration limits
-
Computation:
- Numerical precision
- Memory usage
- Random seed
Trade-offs:
- Bias vs variance
- Speed vs accuracy
- Memory vs computation
Alpha
f64L2 regularization strength:
Mathematical impact:
Effects:
- Controls coefficient shrinkage
- Manages overfitting
- Stabilizes solutions
- Handles collinearity
Typical values:
- Weak: 0.01-0.1
- Standard: 1.0
- Strong: 10.0-100.0
Selection guide:
- Higher: More regularization
- Lower: Less shrinkage
- Zero: Standard OLS
FitIntercept
boolIntercept calculation control:
Model forms: With intercept: Without intercept:
Effects when True:
- Centers predictions
- Accounts for bias
- Shifts regression plane
- Better general fit
Effects when False:
- Forces origin fitting
- No bias term
- Stricter linear model
- Domain-specific needs
MaxIter
u64Maximum iteration limit:
Solver-specific defaults:
- sparse_cg: scipy default
- sag/saga: 1000
- lbfgs: 15000
Impact:
- Convergence control
- Computation time
- Solution precision
- Resource usage
Guidelines:
- Increase for harder problems
- Monitor convergence
- Balance with tolerance
Tol
f64Convergence tolerance threshold:
Solver interpretations:
- Direct: Solution precision
- Iterative: Stopping criterion
Typical values:
- Strict: 1e-6 to 1e-5
- Standard: 1e-4
- Relaxed: 1e-3
Trade-offs:
- Precision vs speed
- Convergence vs iterations
- Resource usage
Solver
enumNumerical solvers for Ridge Regression:
Core problem:
Selection criteria:
- Dataset size
- Feature count
- Memory constraints
- Convergence needs
Trade-offs:
- Speed vs precision
- Memory vs computation
- Exact vs iterative
- Sparse vs dense
Automatic solver selection:
Decision factors:
- Data dimensionality
- Sparsity pattern
- Memory availability
- Problem size
Best for:
- General use
- Unknown data properties
- Initial modeling
- Automatic optimization
Direct solution using Cholesky decomposition:
Mathematical solution:
Characteristics:
- Exact solution
- Dense matrices
- Memory intensive
- Fast for small problems
Best for:
- Small datasets
- Dense features
- High precision needs
- When memory sufficient
Singular Value Decomposition solver:
Mathematical solution:
Properties:
- Numerically stable
- Handles ill-conditioning
- Dense computation
- Memory intensive
Best for:
- Ill-conditioned data
- Numerical stability needs
- Small-medium datasets
- High precision requirements
Conjugate Gradient iterative solver:
Iterative update: where is residual and is search direction
Features:
- Memory efficient
- Sparse matrices
- Iterative solution
- Large scale problems
Best for:
- Large sparse data
- Memory constraints
- When approximation acceptable
- Distributed computing
Stochastic Average Gradient descent:
Update rule: where is the stored gradient for sample i
Characteristics:
- Fast convergence
- Memory efficient
- Streaming capable
- Randomized updates
Best for:
- Large datasets
- Online learning
- Fast approximate solutions
- When memory limited
SAGA optimizer: Enhanced SAG variant:
Update rule: where is previous gradient for sample i
Improvements:
- Unbiased gradients
- Better convergence
- Variance reduction
- Adaptive steps
Best for:
- Large-scale problems
- Better convergence needs
- When stability important
- Modern optimization
Specialized least squares solver:
Solves the regularized problem:
Features:
- Iterative method
- Sparse friendly
- Regularization aware
- Efficient computation
Best for:
- Sparse problems
- Large datasets
- Regular structure
- Memory efficiency
Limited-memory BFGS optimizer:
Quasi-Newton update: where is step and is gradient difference
Properties:
- Quasi-Newton method
- Memory efficient
- Fast convergence
- Constraint handling
Best for:
- Positive coefficients
- Large-scale problems
- Limited memory settings
- Constrained optimization
RandomState
u64Random number generation seed:
Affects:
- SAG/SAGA solvers
- Data shuffling
- Stochastic processes
Usage:
- Fixed seed: Reproducibility
- Different seeds: Robustness
- Zero: System randomness
Best practices:
- Set for reproducibility
- Vary for stability checks
- Document chosen values
Hyperparameter optimization for Ridge Regression:
Search space organization:
-
Regularization:
- Alpha values
- Model complexity
- Stability control
-
Solver selection:
- Algorithm choice
- Computation method
- Resource usage
-
Convergence:
- Tolerance levels
- Iteration limits
- Precision control
Computational impact:
- Time: O(n_params * n_samples * n_features)
- Memory: O(n_features²) or O(n_samples)
- Storage: O(n_params * n_features)
Alpha
[f64, ...]Regularization strength search space:
Search strategies:
-
Logarithmic scale (recommended):
- [0.0001, 0.001, 0.01, 0.1, 1.0, 10.0]
- Covers wide range of regularization
- Common parameter space
-
Fine-tuning:
- [0.1, 0.3, 0.7, 1.0, 1.5]
- Around promising values
- Narrow, focused search
-
Problem-specific:
- High noise: [1.0, 10.0, 100.0]
- Low noise: [0.001, 0.01, 0.1]
- Based on domain knowledge
Impact analysis:
- Model complexity
- Coefficient shrinkage
- Prediction stability
- Generalization performance
FitIntercept
[bool, ...]Intercept inclusion search space:
Search options:
- Standard search:
- [true]: Default modeling
- [true, false]: Full comparison
Evaluation criteria:
- Prediction bias
- Model simplicity
- Domain constraints
- Performance metrics
Selection impact:
- Model flexibility
- Baseline predictions
- Error distribution
- Interpretation ease
MaxIter
[u64, ...]Maximum iterations search space:
Search patterns:
-
Conservative range:
- [100, 500, 1000]
- Standard problems
- Quick convergence
-
Extended search:
- [1000, 5000, 10000, 15000]
- Complex problems
- Difficult convergence
-
Solver-specific:
- SAG/SAGA: [1000, 2000, 5000]
- LBFGS: [10000, 15000, 20000]
- Based on algorithm needs
Considerations:
- Convergence behavior
- Computational resources
- Solution precision
- Time constraints
Tol
[f64, ...]Convergence tolerance search space:
Search ranges:
-
Standard scale:
- [1e-6, 1e-5, 1e-4, 1e-3]
- Covers common needs
- Balance precision/speed
-
High precision:
- [1e-8, 1e-7, 1e-6]
- Exact solutions
- Critical applications
-
Quick convergence:
- [1e-4, 1e-3, 1e-2]
- Faster solutions
- Approximate needs
Trade-offs:
- Precision vs speed
- Iterations needed
- Resource usage
- Solution quality
Solver
[enum, ...]Numerical solvers for Ridge Regression:
Core problem:
Selection criteria:
- Dataset size
- Feature count
- Memory constraints
- Convergence needs
Trade-offs:
- Speed vs precision
- Memory vs computation
- Exact vs iterative
- Sparse vs dense
Automatic solver selection:
Decision factors:
- Data dimensionality
- Sparsity pattern
- Memory availability
- Problem size
Best for:
- General use
- Unknown data properties
- Initial modeling
- Automatic optimization
Direct solution using Cholesky decomposition:
Mathematical solution:
Characteristics:
- Exact solution
- Dense matrices
- Memory intensive
- Fast for small problems
Best for:
- Small datasets
- Dense features
- High precision needs
- When memory sufficient
Singular Value Decomposition solver:
Mathematical solution:
Properties:
- Numerically stable
- Handles ill-conditioning
- Dense computation
- Memory intensive
Best for:
- Ill-conditioned data
- Numerical stability needs
- Small-medium datasets
- High precision requirements
Conjugate Gradient iterative solver:
Iterative update: where is residual and is search direction
Features:
- Memory efficient
- Sparse matrices
- Iterative solution
- Large scale problems
Best for:
- Large sparse data
- Memory constraints
- When approximation acceptable
- Distributed computing
Stochastic Average Gradient descent:
Update rule: where is the stored gradient for sample i
Characteristics:
- Fast convergence
- Memory efficient
- Streaming capable
- Randomized updates
Best for:
- Large datasets
- Online learning
- Fast approximate solutions
- When memory limited
SAGA optimizer: Enhanced SAG variant:
Update rule: where is previous gradient for sample i
Improvements:
- Unbiased gradients
- Better convergence
- Variance reduction
- Adaptive steps
Best for:
- Large-scale problems
- Better convergence needs
- When stability important
- Modern optimization
Specialized least squares solver:
Solves the regularized problem:
Features:
- Iterative method
- Sparse friendly
- Regularization aware
- Efficient computation
Best for:
- Sparse problems
- Large datasets
- Regular structure
- Memory efficiency
Limited-memory BFGS optimizer:
Quasi-Newton update: where is step and is gradient difference
Properties:
- Quasi-Newton method
- Memory efficient
- Fast convergence
- Constraint handling
Best for:
- Positive coefficients
- Large-scale problems
- Limited memory settings
- Constrained optimization
RandomState
u64Random seed configuration:
Usage patterns:
-
Development:
- Fixed seed
- Reproducible results
- Debug capability
-
Validation:
- Multiple seeds
- Stability testing
- Robustness checks
Best practices:
- Document seed values
- Test with different seeds
- Ensure reproducibility
- Consider randomization needs
RefitScore
enumRegression model evaluation metrics:
Purpose:
- Model performance evaluation
- Error measurement
- Quality assessment
- Model comparison
Selection criteria:
- Error distribution
- Scale sensitivity
- Domain requirements
- Business objectives
Model's native scoring method:
- Typically R² score
- Model-specific implementation
- Standard evaluation
- Quick assessment
Coefficient of determination (R²):
Formula:
Properties:
- Range: (-∞, 1]
- 1: Perfect prediction
- 0: Constant model
- Negative: Worse than mean
Best for:
- General performance
- Variance explanation
- Model comparison
- Standard reporting
Explained variance score:
Formula:
Properties:
- Range: (-∞, 1]
- Accounts for bias
- Variance focus
- Similar to R²
Best for:
- Variance analysis
- Bias assessment
- Model stability
Maximum absolute error:
Formula:
Properties:
- Worst case error
- Original scale
- Sensitive to outliers
- Upper error bound
Best for:
- Critical applications
- Error bounds
- Safety margins
- Risk assessment
Negative mean absolute error:
Formula:
Properties:
- Linear error scale
- Robust to outliers
- Original units
- Negated for optimization
Best for:
- Robust evaluation
- Interpretable errors
- Outlier presence
Negative mean squared error:
Formula:
Properties:
- Squared error scale
- Outlier sensitive
- Squared units
- Negated for optimization
Best for:
- Standard optimization
- Large error penalty
- Statistical analysis
Negative root mean squared error:
Formula:
Properties:
- Original scale
- Outlier sensitive
- Interpretable units
- Negated for optimization
Best for:
- Standard reporting
- Interpretable errors
- Model comparison
Negative mean squared logarithmic error:
Formula:
Properties:
- Relative error scale
- For positive values
- Sensitive to ratios
- Negated for optimization
Best for:
- Exponential growth
- Relative differences
- Positive predictions
Negative median absolute error:
Formula:
Properties:
- Highly robust
- Original scale
- Outlier resistant
- Negated for optimization
Best for:
- Robust evaluation
- Heavy-tailed errors
- Outlier presence
Negative Poisson deviance:
Formula:
Properties:
- For count data
- Non-negative values
- Poisson assumption
- Negated for optimization
Best for:
- Count prediction
- Event frequency
- Rate modeling
Negative Gamma deviance:
Formula:
Properties:
- For positive continuous data
- Constant CV assumption
- Relative errors
- Negated for optimization
Best for:
- Positive continuous data
- Multiplicative errors
- Financial modeling
Negative mean absolute percentage error:
Formula:
Properties:
- Percentage scale
- Scale independent
- For non-zero targets
- Negated for optimization
Best for:
- Relative performance
- Scale-free comparison
- Business metrics
D² score with absolute error:
Formula:
Properties:
- Range: (-∞, 1]
- Robust version of R²
- Linear error scale
- Outlier resistant
Best for:
- Robust evaluation
- Non-normal errors
- Alternative to R²
D² score with pinball loss:
Properties:
- Quantile focus
- Asymmetric errors
- Risk assessment
- Distribution modeling
Best for:
- Quantile regression
- Risk analysis
- Asymmetric costs
- Distribution tails
D² score with Tweedie deviance:
Properties:
- Compound Poisson-Gamma
- Flexible dispersion
- Mixed distributions
- Insurance modeling
Best for:
- Insurance claims
- Mixed continuous-discrete
- Compound distributions
- Specialized modeling
Split
oneofStandard train-test split configuration optimized for general classification tasks.
Configuration:
- Test size: 20% (0.2)
- Random seed: 98
- Shuffling: Enabled
- Stratification: Based on target distribution
Advantages:
- Preserves class distribution
- Provides reliable validation
- Suitable for most datasets
Best for:
- Medium to large datasets
- Independent observations
- Initial model evaluation
Splitting uses the ShuffleSplit strategy or StratifiedShuffleSplit strategy depending on the field stratified
. Note: If shuffle is false then stratified must be false.
Configurable train-test split parameters for specialized requirements. Allows fine-tuning of data division strategy for specific use cases or constraints.
Use cases:
- Time series data
- Grouped observations
- Specific train/test ratios
- Custom validation schemes
RandomState
u64Random seed for reproducible splits. Ensures:
- Consistent train/test sets
- Reproducible experiments
- Comparable model evaluations
Same seed guarantees identical splits across runs.
Shuffle
boolData shuffling before splitting. Effects:
- true: Randomizes order, better for i.i.d. data
- false: Maintains order, important for time series
When to disable:
- Time dependent data
- Sequential patterns
- Grouped observations
TrainSize
f64Proportion of data for training. Considerations:
- Larger (e.g., 0.8-0.9): Better model learning
- Smaller (e.g., 0.5-0.7): Better validation
Common splits:
- 0.8: Standard (80/20 split)
- 0.7: More validation emphasis
- 0.9: More training emphasis
Stratified
boolMaintain class distribution in splits. Important when:
- Classes are imbalanced
- Small classes present
- Representative splits needed
Requirements:
- Classification tasks only
- Cannot use with shuffle=false
- Sufficient samples per class
Cv
oneofStandard cross-validation configuration using stratified 3-fold splitting.
Configuration:
- Folds: 3
- Method: StratifiedKFold
- Stratification: Preserves class proportions
Advantages:
- Balanced evaluation
- Reasonable computation time
- Good for medium-sized datasets
Limitations:
- May be insufficient for small datasets
- Higher variance than larger fold counts
- May miss some data patterns
Configurable stratified k-fold cross-validation for specific validation requirements.
Features:
- Adjustable fold count with
NFolds
determining the number of splits. - Stratified sampling
- Preserved class distributions
Use cases:
- Small datasets (more folds)
- Large datasets (fewer folds)
- Detailed model evaluation
- Robust performance estimation
NFolds
u32Number of cross-validation folds. Guidelines:
- 3-5: Large datasets, faster training
- 5-10: Standard choice, good balance
- 10+: Small datasets, thorough evaluation
Trade-offs:
- More folds: Better evaluation, slower training
- Fewer folds: Faster training, higher variance
Must be at least 2.
K-fold cross-validation without stratification. Divides data into k consecutive folds for iterative validation.
Process:
- Splits data into k equal parts
- Each fold serves as validation once
- Remaining k-1 folds form training set
Use cases:
- Regression problems
- Large, balanced datasets
- When stratification unnecessary
- Continuous target variables
Limitations:
- May not preserve class distributions
- Less suitable for imbalanced data
- Can create biased splits with ordered data
NSplits
u32Number of folds for cross-validation. Selection guide: Recommended values:
- 5: Standard choice (default)
- 3: Large datasets/quick evaluation
- 10: Thorough evaluation/smaller datasets
Trade-offs:
- Higher values: More thorough, computationally expensive
- Lower values: Faster, potentially higher variance
Must be at least 2 for valid cross-validation.
RandomState
u64Random seed for fold generation when shuffling. Important for:
- Reproducible results
- Consistent fold assignments
- Benchmark comparisons
- Debugging and validation
Set specific value for reproducibility across runs.
Shuffle
boolWhether to shuffle data before splitting into folds. Effects:
- true: Randomized fold composition (recommended)
- false: Sequential splitting
Enable when:
- Data may have ordering
- Better fold independence needed
Disable for:
- Time series data
- Ordered observations
Stratified K-fold cross-validation maintaining class proportions across folds.
Key features:
- Preserves class distribution in each fold
- Handles imbalanced datasets
- Ensures representative splits
Best for:
- Classification problems
- Imbalanced class distributions
- When class proportions matter
Requirements:
- Classification tasks only
- Sufficient samples per class
- Categorical target variable
NSplits
u32Number of stratified folds. Guidelines: Typical values:
- 5: Standard for most cases
- 3: Quick evaluation/large datasets
- 10: Detailed evaluation/smaller datasets
Considerations:
- Must allow sufficient samples per class per fold
- Balance between stability and computation time
- Consider smallest class size when choosing
RandomState
u64Seed for reproducible stratified splits. Ensures:
- Consistent fold assignments
- Reproducible results
- Comparable experiments
- Systematic validation
Fixed seed guarantees identical stratified splits.
Shuffle
boolData shuffling before stratified splitting. Impact:
- true: Randomizes while maintaining stratification
- false: Maintains data order within strata
Use cases:
- true: Independent observations
- false: Grouped or sequential data
Class proportions maintained regardless of setting.
Random permutation cross-validator with independent sampling.
Characteristics:
- Random sampling for each split
- Independent train/test sets
- More flexible than K-fold
- Can have overlapping test sets
Advantages:
- Control over test size
- Fresh splits each iteration
- Good for large datasets
Limitations:
- Some samples might never be tested
- Others might be tested multiple times
- No guarantee of complete coverage
NSplits
u32Number of random splits to perform. Consider: Common values:
- 5: Standard evaluation
- 10: More thorough assessment
- 3: Quick estimates
Trade-offs:
- More splits: Better estimation, longer runtime
- Fewer splits: Faster, less stable estimates
Balance between computation and stability.
RandomState
u64Random seed for reproducible shuffling. Controls:
- Split randomization
- Sample selection
- Result reproducibility
Important for:
- Debugging
- Comparative studies
- Result verification
TestSize
f64Proportion of samples for test set. Guidelines: Common ratios:
- 0.2: Standard (80/20 split)
- 0.25: More validation emphasis
- 0.1: More training data
Considerations:
- Dataset size
- Model complexity
- Validation requirements
It must be between 0.0 and 1.0.
Stratified random permutation cross-validator combining shuffle-split with stratification.
Features:
- Maintains class proportions
- Random sampling within strata
- Independent splits
- Flexible test size
Ideal for:
- Imbalanced datasets
- Large-scale problems
- When class distributions matter
- Flexible validation schemes
NSplits
u32Number of stratified random splits. Guidelines: Recommended values:
- 5: Standard evaluation
- 10: Detailed analysis
- 3: Quick assessment
Consider:
- Sample size per class
- Computational resources
- Stability requirements
RandomState
u64Seed for reproducible stratified sampling. Ensures:
- Consistent class proportions
- Reproducible splits
- Comparable experiments
Critical for:
- Benchmarking
- Research studies
- Quality assurance
TestSize
f64Fraction of samples for stratified test set. Best practices: Common splits:
- 0.2: Balanced evaluation
- 0.3: More thorough testing
- 0.15: Preserve training size
Consider:
- Minority class size
- Overall dataset size
- Validation objectives
It must be between 0.0 and 1.0.
Time Series cross-validator. Provides train/test indices to split time series data samples that are observed at fixed time intervals, in train/test sets. It is a variation of k-fold which returns first k
folds as train set and the k + 1
th fold as test set. Note that unlike standard cross-validation methods, successive training sets are supersets of those that come before them. Also, it adds all surplus data to the first training partition, which is always used to train the model.
Key features:
- Maintains temporal dependence
- Expanding window approach
- Forward-chaining splits
- No future data leakage
Use cases:
- Sequential data
- Financial forecasting
- Temporal predictions
- Time-dependent patterns
Note: Training sets are supersets of previous iterations.
NSplits
u32Number of temporal splits. Considerations: Typical values:
- 5: Standard forward chaining
- 3: Limited historical data
- 10: Long time series
Impact:
- Affects training window growth
- Determines validation points
- Influences computational load
MaxTrainSize
u64Maximum size of training set. Should be strictly less than the number of samples. Applications:
- 0: Use all available past data
- >0: Rolling window of fixed size
Use cases:
- Limit historical relevance
- Control computational cost
- Handle concept drift
- Memory constraints
TestSize
u64Number of samples in each test set. When 0:
- Auto-calculated as n_samples/(n_splits+1)
- Ensures equal-sized test sets
Considerations:
- Forecast horizon
- Validation requirements
- Available future data
Gap
u64Number of samples to exclude from the end of each train set before the test set.Gap between train and test sets. Uses:
- Avoid data leakage
- Model forecast lag
- Buffer periods
Common scenarios:
- 0: Continuous prediction
- >0: Forward gap for realistic evaluation
- Match business forecasting needs