Overfitting occurs when a digital predistorter (DPD) model becomes excessively complex relative to the true power amplifier (PA) nonlinearity, memorizing the specific training waveform's noise, thermal transients, and measurement artifacts instead of learning the generalizable inverse transfer function. This results in excellent performance metrics on the training dataset but catastrophic linearization failure when the predistorter encounters new modulation schemes, power levels, or signal bandwidths not present during coefficient estimation.
Glossary
Overfitting

What is Overfitting?
Overfitting is a modeling failure in digital predistortion where the predistorter learns noise and specific artifacts of the training data rather than the true underlying power amplifier nonlinearity, severely degrading generalization to unseen signals.
In indirect learning architectures (ILA) and direct learning architectures (DLA), overfitting is mitigated through Tikhonov regularization, cross-validation across diverse excitation signals, and limiting model complexity via memory polynomial order reduction. Engineers monitor the gap between training normalized mean squared error (NMSE) and validation NMSE as a primary diagnostic; a widening divergence indicates the model is fitting measurement noise rather than the true AM-AM/AM-PM distortion characteristics.
Key Characteristics of Overfitting in DPD
Overfitting in digital predistortion occurs when the model memorizes the training dataset's specific noise, measurement artifacts, and transient conditions rather than learning the true underlying power amplifier nonlinearity. This results in excellent training performance but catastrophic degradation when the predistorter encounters new signal conditions.
High Training NMSE, Poor Validation NMSE
The hallmark diagnostic of overfitting is a divergence between training and validation metrics. The predistorter achieves exceptionally low Normalized Mean Squared Error on the training dataset—often below -50 dB—but exhibits significantly worse performance on unseen test signals. This gap indicates the model has memorized specific training samples rather than learning the smooth, continuous PA transfer function. Engineers should monitor both metrics during coefficient estimation and halt training when validation error begins to rise while training error continues to decrease.
Excessive Model Complexity
Overfitting is directly correlated with model capacity exceeding the information content of the training data. Key indicators include:
- Memory polynomial order too high: Nonlinearity orders beyond 7-9 and memory depths exceeding 3-4 taps often fit noise
- Neural network over-parameterization: Hidden layers with hundreds of neurons when the PA's true nonlinearity requires far fewer parameters
- Volterra series kernel explosion: Including high-order cross-terms that capture spurious correlations rather than physical distortion mechanisms The parsimony principle applies: the simplest model that adequately captures the PA behavior generalizes best.
Sensitivity to Training Signal Characteristics
An overfit predistorter becomes brittle to changes in signal statistics that differ from the training waveform. Symptoms include:
- Peak-to-average power ratio dependency: Excellent linearization for the specific PAPR used during training, but degraded ACLR for signals with different crest factors
- Bandwidth configuration fragility: Performance collapses when signal bandwidth changes from the training condition
- Modulation scheme over-specialization: Predistorter tuned to 256-QAM fails on 64-QAM or OFDM waveforms with different subcarrier configurations This occurs because the model has learned spurious correlations between specific signal features and distortion products that don't generalize across modulation formats.
Noise Amplification and Coefficient Variance
Overfit DPD models exhibit excessively large or unstable coefficient magnitudes that amplify measurement noise rather than canceling distortion. Diagnostic signs include:
- Coefficient norm explosion: The L2 norm of the predistorter coefficient vector grows large as the model fits noise components
- High coefficient variance across training runs: Small changes in training data produce dramatically different coefficient sets
- Numerical ill-conditioning: The condition number of the regression matrix becomes extremely high, indicating the solution is sensitive to input perturbations Tikhonov regularization or ridge regression directly addresses this by penalizing large coefficient magnitudes, constraining the solution space to physically plausible values.
Poor Generalization Across Temperature and Aging
An overfit model captures the specific thermal state and aging condition of the PA during training rather than the invariant nonlinear behavior. This manifests as:
- Temperature drift failure: NMSE degrades significantly as the PA junction temperature changes from the training condition
- Aging compensation breakdown: Performance deteriorates over weeks or months as transistor characteristics shift
- Device-to-device variation sensitivity: A predistorter trained on one PA unit fails when deployed on another unit of the same model due to manufacturing tolerances Robust DPD requires training data that spans the expected operating envelope of temperature, frequency, and power levels, combined with online adaptation to track slow-varying changes.
Spectral Hole Artifacts
A distinctive signature of overfitting in frequency-domain analysis is the appearance of unnatural spectral nulls or holes in the linearized output spectrum. These artifacts occur because:
- The model has learned to cancel specific frequency components present in the training signal's distortion profile
- When a new signal with different spectral content is applied, the predistorter over-compensates at certain frequencies while under-compensating at others
- The resulting ACLR may appear acceptable in aggregate but exhibits non-uniform spectral regrowth that violates emission mask requirements at specific offsets Cross-validation across multiple signal realizations during training helps identify and prevent these frequency-selective overfitting artifacts.
Frequently Asked Questions
Addressing the critical failure mode where a digital predistorter memorizes training data noise instead of learning the true power amplifier nonlinearity, leading to degraded generalization on unseen signals.
Overfitting in digital predistortion is a modeling failure where the predistorter learns the specific noise, measurement artifacts, and idiosyncrasies of the training dataset rather than the true underlying power amplifier nonlinearity. This occurs when the model complexity—such as the number of Volterra series kernels or neural network parameters—exceeds what is necessary to capture the PA's actual behavioral characteristics. An overfitted DPD model will exhibit excellent performance metrics like Normalized Mean Squared Error (NMSE) on training data but will fail to generalize to new signal conditions, modulation schemes, or operating temperatures. The predistorter essentially memorizes the training waveform's specific distortion pattern, including thermal transients and measurement noise, producing spurious spectral regrowth when confronted with previously unseen signals. This is particularly dangerous in adaptive DPD systems where the model must maintain linearization performance across varying traffic patterns and environmental conditions.
Overfitting vs. Underfitting in DPD Models
Comparative analysis of overfitting and underfitting behaviors in digital predistortion coefficient estimation, including causes, detection metrics, and mitigation strategies.
| Characteristic | Overfitting | Underfitting | Optimal Fit |
|---|---|---|---|
Definition | Model learns noise and training-specific artifacts rather than true PA nonlinearity | Model fails to capture sufficient complexity of the PA transfer function | Model captures true underlying PA nonlinearity with minimal residual error |
NMSE on Training Data | Exceptionally low (< -45 dB) | High (> -30 dB) | Low and stable (-38 to -42 dB) |
NMSE on Validation Data | Significantly worse than training NMSE | Similar to training NMSE but poor overall | Consistent with training NMSE |
ACPR Improvement | Degrades on unseen signals | Minimal improvement (< 5 dB) | Consistent 15-25 dB improvement |
Model Complexity Indicator | Excessive polynomial order or neuron count relative to PA memory depth | Insufficient nonlinear order or memory taps | Matched to PA nonlinearity order and memory span |
Coefficient Magnitude Distribution | Large coefficient variance with extreme outlier values | Coefficients near zero or initialization values | Well-distributed coefficients with physical plausibility |
Generalization Across Signals | Poor performance on modulation schemes or bandwidths not in training set | Poor performance on all signals | Robust performance across diverse signal types |
Primary Cause | Excessive model capacity, insufficient training data diversity, or training SNR too high | Insufficient model order, truncated memory depth, or under-trained parameters | Appropriate model selection and representative training data |
Detection Method | Cross-validation with held-out signal types; monitor train/validation NMSE divergence | Monitor absolute NMSE floor; verify model order sufficiency via sweep | Cross-validation with consistent train/validation metrics |
Mitigation Strategy | Apply Tikhonov regularization, reduce model order, increase training data diversity, add noise injection | Increase polynomial order or memory depth, extend training iterations, verify basis function completeness | Maintain current architecture; implement monitoring for drift detection |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Understanding overfitting requires familiarity with the mathematical safeguards, training methodologies, and performance metrics used to ensure a predistorter generalizes beyond its training data.
Tikhonov Regularization
A stabilization technique that adds a penalty term to the least squares cost function to prevent overfitting. By constraining the magnitude of the DPD coefficients, it suppresses the model's sensitivity to noise in the observation path. This is mathematically equivalent to ridge regression and is essential when the condition number of the data matrix is high, indicating an ill-posed inverse problem.
Cross-Validation
A model selection framework that partitions the captured PA input-output data into distinct training and validation sets. The predistorter is trained on one subset and evaluated on the unseen hold-out set. A diverging NMSE between the training and validation errors is the primary diagnostic for overfitting, indicating the model is memorizing specific training artifacts rather than the true inverse nonlinearity.
Model Order Selection
The process of determining the optimal nonlinearity order and memory depth of a predistorter. Excessively high polynomial orders or deep memory taps allow the model to fit high-frequency noise, leading to poor generalization. Information criteria like AIC and MDL balance model fit against complexity, penalizing the addition of superfluous parameters that do not significantly improve the error.
Generalization Error
The true measure of a DPD model's performance, defined as the expected error on all possible signals, not just the training waveform. Overfitting is characterized by a low training error but a high generalization error. In practice, this manifests as excellent ACPR correction on the lab signal but degraded performance when the modulation scheme or channel configuration changes in the field.
Early Stopping
A regularization technique used in iterative SGD or RLS training where the coefficient update process is halted before convergence to the minimum of the training error. By monitoring the validation error during training, the algorithm stops when the validation error begins to increase, even if the training error is still decreasing. This prevents the model from entering the overfitting regime.
Data Diversity
The most fundamental defense against overfitting. Training a predistorter on a single-tone or narrowband signal will not capture the full dynamic nonlinearity of the PA. A robust model requires a training dataset that spans the expected operational envelope:
- Varying signal bandwidths
- Different PAPR distributions
- Multiple carrier configurations
- A range of average input power levels

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us