ComplementNb / Classifier Layer
Complement Naive Bayes Classifier - The Complement Naive Bayes classifier was designed to correct the “severe assumptions” made by the standard Multinomial Naive Bayes classifier. It is particularly suited for imbalanced data sets.
Mathematical form: where:
- represents complement of class c
- represents features in document d
- Parameters estimated using weight normalization
Key characteristics:
- Better handling of imbalanced data
- Complement class estimation
- Weight normalization
- Robust feature handling
- Non-negative weights
Common applications:
- Text classification with imbalance
- Document categorization
- Rare category detection
- Uneven class distribution problems
- Multi-class classification
Outputs:
- Predicted Table: Input data with predictions
- Validation Results: Cross-validation metrics
- Test Metric: Test set performance
- ROC Curve Data: ROC analysis information
- Confusion Matrix: Classification breakdown
- Feature Importances: Feature weights
Note: Particularly effective when standard Multinomial NB performs poorly on imbalanced data
SelectFeatures
[column, ...]Feature columns for Complement Naive Bayes:
Requirements:
- Non-negative values
- Typically count/frequency data
- No missing values
- Meaningful for complement calculation
Preprocessing guidelines:
-
Feature representation:
- Term frequencies
- Count data
- Non-negative features
-
Feature engineering:
- Text vectorization
- Frequency extraction
- Domain-specific counts
-
Data quality:
- Handle missing values
- Ensure non-negativity
- Check feature relevance
If empty, uses all numeric columns except target.
SelectTarget
columnTarget column for classification:
Requirements:
- Categorical labels
- Multiple classes
- No missing values
- Properly encoded
Class characteristics:
- Handles imbalanced classes well
- Robust to rare categories
- Supports multi-class
- Complement-based estimation
Quality checks:
- Validate class distribution
- Check for rare classes
- Verify label consistency
- Monitor class frequencies
Params
oneofOptimized default configuration for Complement Naive Bayes:
Default settings:
- Alpha: 1.0 (Laplace smoothing)
- Force alpha: True (exact smoothing)
- Fit prior: True (learn priors)
- Norm: False (single normalization)
Best suited for:
- Imbalanced datasets
- Text classification
- Multi-class problems
- When standard NB fails
Provides robust baseline for imbalanced problems
Fine-grained control over Complement Naive Bayes parameters:
Parameter groups:
- Smoothing parameters
- Weight normalization
- Prior probability handling
- Numerical stability controls
Alpha
f64Additive smoothing parameter:
Effect:
Typical values:
- 1.0: Standard Laplace smoothing
- <1.0: Lighter smoothing
- >1.0: Stronger smoothing
Controls estimation stability
ForceAlpha
boolAlpha value enforcement:
Behavior:
- true: Use exact alpha value
- false: Minimum 1e-10 threshold
Important for numerical stability
FitPrior
boolPrior probability handling:
Note: Only affects single-class edge cases
Usually keep default (true) unless specific need
Norm
boolWhether or not a second normalization of the weights is performed.
Effect:
- true: Additional normalization step
- false: Standard weights
Can improve performance on some datasets
Exhaustive hyperparameter optimization for Bernoulli Naive Bayes:
Search process:
- Tests all parameter combinations
- Uses cross-validation for evaluation
- Optimizes specified scoring metric
- Returns best performing configuration
Key parameters:
- Smoothing parameters (alpha)
- Prior probability options
- Binarization threshold
Best practices:
- Start with broader ranges
- Focus on alpha and binarize
- Consider problem constraints
Alpha
[f64, ...]Smoothing parameter values to evaluate:
Common grids:
- Basic: [0.1, 1.0, 10.0]
- Fine-grained: [0.1, 0.5, 1.0, 2.0]
- Wide range: [0.01, 0.1, 1.0, 10.0]
Impact:
- Smaller: More sensitive to training data
- Larger: More conservative predictions
ForceAlpha
[bool, ...]Alpha enforcement options:
Combinations:
- [true]: Exact alpha values
- [false]: Minimum 1e-10 smoothing
- [true, false]: Compare both
Consider numerical stability needs
FitPrior
[bool, ...]Prior probability learning options:
Combinations:
- [true]: Learn from data
- [false]: Use uniform priors
- [true, false]: Compare both
Important for class imbalance
Binarize
[f64, ...]Binarization threshold values:
Common ranges:
- Standard: [0.0, 0.5, 1.0]
- Fine: [0.2, 0.4, 0.6, 0.8]
- With raw features: [0.0, 1.0, 5.0]
Critical when features not binary
RefitScore
enumPerformance metric for model evaluation:
Selection criteria:
- Default: Model's built-in scoring
- Accuracy: Overall correctness
- BalancedAccuracy: For imbalanced data
- LogLoss: Probability quality
- RocAuc: Threshold-independent
Choose based on:
- Class distribution
- Problem requirements
- Prediction type needed
Uses estimator's built-in scoring method:
For Bernoulli NB:
- Returns accuracy score
- Equal weight to all samples
- Fast computation
Best for:
- Quick evaluation
- Balanced datasets
- Initial testing
Standard classification accuracy score:
Formula:
Properties:
- Range: [0, 1]
- Perfect score: 1.0
- Baseline: max(class proportions)
Best for:
- Balanced classes
- Equal error costs
- Simple evaluation
Class-weighted accuracy score:
Formula:
Properties:
- Adjusts for class imbalance
- Range: [0, 1]
- Random baseline: 0.5
Best for:
- Imbalanced datasets
- When minority classes matter
- Uneven class distributions
Logarithmic loss (cross-entropy):
Formula:
Properties:
- Penalizes confident mistakes
- Range: [0, ∞)
- Perfect score: 0.0
Best for:
- Probability calibration
- When confidence matters
- Probabilistic predictions
Area Under Receiver Operating Characteristic Curve:
Properties:
- Threshold-independent
- Range: [0, 1]
- Random baseline: 0.5
- Perfect score: 1.0
Best for:
- Binary classification
- Threshold tuning
- Ranking evaluation
- Imbalanced datasets
Note: For multiclass, computes average ROC AUC
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