Least Squares (LS) Estimation is a batch coefficient extraction algorithm that determines the optimal complex-valued weights for a predistorter model by minimizing the sum of squared differences between the power amplifier's measured output and the model's predicted output. It solves the overdetermined system of linear equations y = Xw by finding the coefficient vector w that minimizes the Euclidean norm of the residual error vector.
Glossary
Least Squares (LS) Estimation

What is Least Squares (LS) Estimation?
The foundational mathematical optimization technique for determining the optimal predistorter coefficients by minimizing the sum of squared errors between observed and modeled data.
In digital predistortion, the LS solution is computed directly via the pseudo-inverse (w = (X^H X)^{-1} X^H y), where X is the basis function matrix constructed from input signal samples and y is the observed PA output. While computationally intensive due to the matrix inversion, LS provides the optimal unbiased estimate under the assumption of white Gaussian noise, making it the gold standard for offline model extraction and the benchmark against which adaptive algorithms like Recursive Least Squares (RLS) are measured.
Key Characteristics of LS Estimation
The foundational batch algorithm for solving the linear regression problem in digital predistortion, minimizing the squared error between observed and modeled PA output.
The Normal Equation Solution
LS estimation solves for the optimal coefficient vector w analytically using the Normal Equation: w = (XᴴX)⁻¹Xᴴy. This computes the projection of the observed output vector y onto the column space of the basis function matrix X. The solution is guaranteed to be the global minimum of the quadratic cost function, assuming XᴴX is invertible.
Batch Processing Paradigm
LS estimation operates on a complete captured data block rather than sample-by-sample. This batch nature provides excellent numerical stability for offline model extraction but makes it unsuitable for real-time tracking of rapidly changing PA characteristics. Typical block sizes range from 1,000 to 10,000 samples to capture the statistical distribution of the signal.
Numerical Conditioning Requirements
The matrix XᴴX must be well-conditioned for stable inversion. Ill-conditioning arises from highly correlated basis functions, leading to coefficient explosion and poor generalization. Techniques to address this include:
- Basis function orthogonalization
- Ridge regression (adding a regularization parameter λ)
- QR decomposition for direct solving without explicit inversion
Indirect Learning Architecture Application
In DPD, LS estimation is most commonly applied in the Indirect Learning Architecture (ILA). The algorithm identifies a postdistorter by swapping the input and output roles: the PA output becomes the model input, and the PA input becomes the desired response. The extracted postdistorter coefficients are then copied directly to the predistorter, assuming the PA inverse is sufficiently accurate.
Computational Complexity Profile
The dominant cost is the matrix inversion of XᴴX, which is an (M × M) matrix where M is the number of model coefficients. Complexity scales as O(M³) for direct inversion or O(M²) per iteration for iterative solvers. For a GMP model with 50 coefficients, this is trivial; for a full Volterra series with 500+ coefficients, it becomes a significant computational burden.
Relationship to QR Decomposition
For improved numerical stability, LS problems are often solved via QR decomposition rather than the Normal Equation. The basis matrix X is factored into an orthogonal matrix Q and an upper triangular matrix R. The coefficient vector is then found by back-substitution: Rw = Qᴴy. This avoids squaring the condition number, which occurs when forming XᴴX explicitly.
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.
Frequently Asked Questions
Clear answers to common questions about the mathematical engine behind digital predistortion coefficient extraction.
Least Squares (LS) estimation is a batch coefficient extraction algorithm that determines the optimal predistorter coefficients by minimizing the sum of squared errors between the power amplifier's measured output and the model's predicted output. In DPD systems, LS solves the inverse modeling problem: given a matrix of basis function outputs and a vector of observed PA input signals, it computes the complex-valued coefficient vector that minimizes the Euclidean norm of the error. The solution is obtained analytically via the normal equations w = (X^H X)^{-1} X^H y, where X is the basis function matrix, y is the target signal, and w is the coefficient vector. This closed-form solution makes LS the foundational algorithm for offline model extraction and initial coefficient estimation before adaptive tracking takes over.
Related Terms
Core algorithms and mathematical techniques used alongside or as alternatives to Least Squares for extracting optimal digital predistorter coefficients.
Basis Function Orthogonalization
A numerical conditioning process that transforms correlated polynomial basis functions into an orthogonal set before coefficient estimation. This dramatically improves the stability and convergence speed of the LS solution.
- Problem: Polynomial terms (x, x|x|², x|x|⁴...) are highly correlated, creating ill-conditioned normal equations
- Solution: Apply Gram-Schmidt, Löwdin, or eigenvalue-based orthogonalization to the basis matrix
- Result: The condition number of the observation matrix drops by orders of magnitude
- Trade-off: Adds a preprocessing step but enables reliable coefficient extraction at higher nonlinear orders
Principal Component Analysis (PCA) for DPD
A dimensionality reduction technique applied to the basis function matrix to identify and retain only the most significant principal components. PCA addresses multicollinearity in memory polynomial models before coefficient estimation.
- Method: Computes the eigendecomposition of the covariance matrix AᵀA, retaining components with the largest eigenvalues
- Dimension Reduction: Projects the original high-dimensional basis set onto a lower-dimensional subspace
- Noise Rejection: Discards components with small eigenvalues that primarily represent measurement noise
- Integration: Often combined with LS or ridge regression for the final coefficient estimation on the reduced basis set

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