Overfitting occurs when a coefficient estimation algorithm learns the specific noise and measurement artifacts present in the training dataset instead of the true power amplifier behavioral model. The extracted digital predistortion coefficients produce excellent performance on the captured data but fail catastrophically when exposed to new, unseen signal conditions or modulation schemes.
Glossary
Overfitting

What is Overfitting?
Overfitting is a modeling failure where the extracted parameters fit the training data noise rather than the underlying system dynamics, resulting in poor generalization to new signals.
In indirect learning architectures, overfitting manifests as excessive model complexity relative to the information content of the training data. Mitigation strategies include applying a regularization parameter to the diagonal of the correlation matrix, employing early stopping during iterative training, and ensuring the training dataset spans sufficient signal diversity to capture the amplifier's true nonlinear dynamics rather than transient measurement noise.
Key Indicators of Overfitting
Overfitting in coefficient estimation manifests as a model that memorizes training data noise rather than learning the true power amplifier dynamics. The following indicators help engineers detect this failure mode before deployment.
Divergent Training vs. Validation Error
The most definitive signature of overfitting: training error (e.g., NMSE on the captured dataset) continues to decrease monotonically while validation error on a held-out signal begins to rise. This divergence indicates the model is fitting noise specific to the training capture rather than the underlying amplifier nonlinearity. Monitor both curves during iterative estimation and halt training when validation error reaches its minimum. For ILA architectures, validate on a separate signal realization with different peak-to-average power ratio statistics.
Coefficient Magnitude Explosion
Overfit models exhibit excessively large coefficient magnitudes, particularly in higher-order nonlinear terms. In memory polynomial models, coefficients for high-order kernels (e.g., 7th, 9th, 11th order) grow unbounded as the estimator attempts to fit noise fluctuations. This violates the principle of parsimony—a well-behaved power amplifier model should have smoothly decaying coefficient magnitudes with increasing nonlinearity order. Monitor the L2 norm of the coefficient vector during training; a sharp increase signals overfitting.
Poor ACLR on Unseen Signals
The operational test: apply the extracted predistorter to a new signal not present in the training set. An overfit DPD will show excellent Adjacent Channel Leakage Ratio (ACLR) on the training signal but degraded ACLR on any other waveform. This occurs because the predistorter has learned the specific spectral pattern of the training signal's noise rather than the amplifier's true distortion characteristic. Always validate with at least two distinct signal types (e.g., LTE and NR test models).
Ill-Conditioned Correlation Matrix
Overfitting is often preceded by numerical instability in the least squares solution. The condition number of the input correlation matrix R = X^H X grows large (typically > 10^8), indicating that the basis functions are nearly linearly dependent for the given training data. This ill-conditioning amplifies noise sensitivity. Mitigation requires Tikhonov regularization (ridge regression) by adding a diagonal loading term λI, where λ is selected via cross-validation or the L-curve criterion.
Spectral Noise Amplification
An overfit predistorter exhibits out-of-band noise amplification when driven with a clean signal. Analyze the predistorter output spectrum without the power amplifier in the loop: overfit models inject high-frequency noise components that were present in the training residuals. This is particularly visible in wideband DPD systems where the linearization bandwidth approaches the Nyquist rate. A properly regularized model should produce a smooth predistorter output spectrum without spurious noise peaks.
Sensitivity to Training Data Perturbations
A robust model should produce similar coefficient sets when trained on slightly different captures of the same amplifier. An overfit model shows high variance in extracted coefficients across repeated measurements under identical conditions. Quantify this by computing the coefficient standard deviation across multiple training runs with different noise realizations. Large variance in high-order terms indicates the estimator is fitting measurement noise rather than deterministic amplifier behavior.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about overfitting in coefficient estimation for digital predistortion systems.
Overfitting in digital predistortion is a modeling failure where the extracted DPD coefficients fit the noise and measurement artifacts in the training data rather than the true nonlinear dynamics of the power amplifier. This results in a coefficient set that performs well on the specific waveform used during training but fails to generalize to new signals, modulation schemes, or operating conditions. In the context of parameter extraction, overfitting occurs when the model complexity—such as the polynomial order or memory depth of a Volterra series—exceeds the information content of the training data. The model then captures stochastic variations, thermal transients, and quantization noise as if they were deterministic PA behaviors. The consequence is degraded Adjacent Channel Leakage Ratio (ACLR) and increased Error Vector Magnitude (EVM) when the predistorter encounters signals not present in the training set.
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.
Overfitting vs. Underfitting in DPD Models
Comparative analysis of overfitting and underfitting failure modes in digital predistortion coefficient estimation, including causes, detection methods, and remediation strategies.
| Characteristic | Overfitting | Underfitting | Optimal Fit |
|---|---|---|---|
Definition | Model captures noise and measurement artifacts rather than true PA nonlinear dynamics | Model lacks sufficient complexity to represent the underlying PA transfer function | Model captures true PA nonlinearity and memory effects while rejecting noise |
Training NMSE | < -45 dB |
| -35 to -42 dB |
Validation NMSE |
|
| -34 to -40 dB |
NMSE Gap (Train vs. Validation) |
| < 3 dB | 2-5 dB |
ACLR Improvement (Validation) | Degraded or unstable | Minimal (< 5 dB) | 12-18 dB typical |
Spectral Regrowth at Band Edges | Erratic, non-physical spikes | Uniform residual regrowth | Smooth, controlled suppression |
Coefficient Magnitude Distribution | Large, oscillating values; high variance | Small, near-zero values | Moderate, smoothly decaying magnitudes |
Condition Number Sensitivity | Extremely sensitive; solution unstable | Insensitive; model too rigid | Stable within regularization bounds |
Primary Cause | Excessive model order, insufficient regularization, noisy training data | Insufficient nonlinearity order, missing memory depth, under-parameterization | Appropriate model complexity with proper regularization |
Detection Method | Cross-validation with held-out signal types; monitor train/validation NMSE divergence | Residual error analysis; check for structured patterns in error signal | Consistent performance across multiple signal types and power levels |
Remediation Strategy | Increase regularization parameter; reduce polynomial order; apply early stopping; use more diverse training data | Increase nonlinearity order; add memory taps; incorporate cross-terms; switch to GMP structure | Maintain current configuration; implement online adaptation for drift compensation |
Typical Occurrence | High-order GMP models with dense coefficient grids trained on single-tone test signals | Low-order memoryless polynomial models applied to wideband GaN Doherty PAs | Properly regularized GMP models with memory depth matched to PA time constants |
Related Terms
Understanding overfitting requires familiarity with the core tradeoffs and techniques that govern a model's ability to generalize from training data to unseen signals.
Bias-Variance Tradeoff
The fundamental tension between a model's ability to fit training data accurately (low bias) and its ability to generalize to unseen data (low variance). Overfitting represents a high-variance state where the model captures noise rather than the underlying signal. The total error is the sum of bias², variance, and irreducible error.
Regularization Parameter
A scalar added to the diagonal of the correlation matrix to improve numerical stability and prevent overfitting when solving ill-conditioned least squares problems. In DPD coefficient estimation, Tikhonov regularization penalizes large coefficient magnitudes, constraining the model complexity and improving generalization to new signal bandwidths.
Early Stopping
A regularization technique where an iterative optimization algorithm is halted before full convergence to prevent the model from fitting noise in the training data. In online training for DPD, monitoring the error on a validation signal set and stopping when it begins to increase is a practical defense against overfitting.
Model Extraction Techniques
The methods for extracting power amplifier behavioral models from measurements, which directly influence overfitting risk. Offline training on a single static capture can lead to overfitting if the excitation signal lacks sufficient diversity. Online training continuously adapts, reducing the gap between training and operational data distributions.
Condition Number
The ratio of the largest to smallest singular value of a matrix, quantifying the sensitivity of the solution of a linear system to small perturbations in the input data. A high condition number indicates an ill-conditioned estimation problem where the extracted coefficients are highly sensitive to noise, a primary cause of overfitting in Least Squares estimation.
Misadjustment
The normalized difference between the steady-state mean squared error of an adaptive filter and the minimum mean squared error achievable by the optimal Wiener filter. In LMS and RLS algorithms, excess misadjustment can be a symptom of tracking noise rather than the true system dynamics, analogous to overfitting in batch-trained models.

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