KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesComputing Rank, Kernel and ImageEngineering · Engineering MathematicsLesson 655/883← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIComputing Rank, Kernel and Image

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Modules, Vector Spaces and Matrices

Computing Rank, Kernel and Image

Extracting rank, kernel basis and image basis from an echelon form, and the applications to polynomial factorisation.

Page KV-MATH-0428Reading time 4 minReviewed 2026-08-07Author Kevin Jogin

Executive summary

Once a matrix is in echelon form, rank, kernel and image are all read off directly. The kernel basis comes from the free columns, one basis vector per free column.

Berlekamp's factorisation algorithm is exactly a kernel computation, which is why this machinery appears in a number theory collection.

Learning objectives

  1. Extract rank, kernel and image from echelon form.
  2. Construct an explicit kernel basis.
  3. Connect the computation to polynomial factorisation.

01Reading off the invariants

  1. Rank

    The number of pivots in the echelon form.

  2. Image basis

    The pivot columns of the original matrix, not of the reduced one.

  3. Kernel dimension

    The number of free columns, equal to n minus the rank.

  4. Kernel basis

    One vector per free column: set that free variable to 1, all other free variables to 0, and back-substitute for the pivot variables.

Caution
The image basis must be taken from the original matrix columns, not the reduced ones. Row operations preserve the kernel and the column dependencies but change the column space itself.
rank + nullity = number of columns

02Constructing the kernel basis

Algorithm

Kernel basis from reduced echelon form

Inputmatrix A over a field
Outputa basis for the kernel of A
  1. Reduce A to reduced row echelon form, recording pivot columns.
  2. Identify the free columns as those without a pivot.
  3. For each free column j:
  4.   Create a vector v with vⱼ = 1 and all other free coordinates 0.
  5.   For each pivot row, set the corresponding pivot coordinate to the negative of the entry in column j.
  6.   Add v to the basis.
  7. Return the collection of vectors.
Cost  O(n³) for the reduction, O(n²) per basis vector

The resulting vectors are independent by construction, since each has a 1 in a coordinate where the others have 0, and there are exactly as many as the nullity — so they form a basis.

03Application to polynomial factorisation

Berlekamp's algorithm factors a squarefree polynomial over a finite field by computing the kernel of a specific linear map, the Berlekamp map.

Theorem

Berlekamp's key fact

For a squarefree polynomial f over F_q, the dimension of the kernel of the map v ↦ v^q − v on F_q[X]/(f) equals the number of irreducible factors of f.

So the number of factors is a nullity, computable by elimination before any factor is found. Each non-trivial kernel element then splits f by taking gcds.

  • Count factors first

    The rank computation reveals how many factors exist, which tells the algorithm when it is finished.

  • Split using kernel elements

    Each kernel element v gives gcd(f, v − c) for constants c, and these gcds separate the factors.

  • Cost

    Building the matrix dominates; the elimination is on a matrix of size the degree of f.

Note
This is a good illustration of the value of abstraction. Polynomial factorisation looks like a problem about polynomials, and the algorithm turns it into a rank computation — a completely different kind of question with well-understood algorithms.

04Frequently asked questions

Why take image basis columns from the original matrix?

Because row operations change the column space. They preserve which sets of columns are dependent, so the pivot positions identify an independent set, but the actual vectors must come from the original.

Is the kernel basis unique?

No. Any basis of the kernel is valid, and different elimination orders give different bases. The construction above gives a canonical one relative to the choice of free columns.

How large is the Berlekamp matrix?

Its size is the degree of the polynomial, so factoring a degree-n polynomial costs O(n³) field operations for the elimination. For high degrees the Cantor-Zassenhaus method is preferred, being roughly quadratic.

Related pages

  • Solving Systems of Linear Equations
  • Berlekamp's Factorization Algorithm
  • Gaussian Elimination

Sources and method

Structural reference: Victor Shoup, A Computational Introduction to Number Theory and Algebra, Version 1, Cambridge University Press, 2005 — book pages 328-331.

This page carries the durable method layer only: definitions, constructions, algorithms, complexity results and selection criteria, authored originally for KEVOS. No text is transcribed or paraphrased from the source, and no numeric tables or benchmark data are reproduced — these are routed to live authoritative sources instead.

Author: Kevin Jogin. Last reviewed 2026-08-07.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Computing Rank, Kernel and Image. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to turn a compact mathematical statement into a usable chain of definitions, claims, examples and checks. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Treat Computing Rank, Kernel and Image as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—kernel, basis, rank, image, echelon—should be made explicit before any proof or computation begins. Record the ambient set or structure, the permitted operations and the equality or equivalence relation in use. A compact theorem often changes meaning when the base field, finiteness condition, commutativity assumption or direction of an action changes.

For a proof, write the hypotheses as a checklist and mark the line at which each one is used. For a computation, state the representation of the input, the arithmetic model, the termination condition and the output invariant. For a classification problem, distinguish existence from uniqueness and distinguish an object from its representation. These separations prevent a correct local calculation from being mistaken for the general result.

A useful worked example should be small enough to inspect completely but rich enough to exercise the main mechanism. Compute the result in two ways where practical: symbolically and by substitution, structurally and numerically, or directly and through a normal form. Then include one near-miss example in which a hypothesis fails. The contrast explains why the theorem is shaped as it is and gives the reader a diagnostic pattern for later problems.

Verification is part of the mathematics. Check domains and codomains, substitute proposed solutions, test identity and zero cases, compare dimensions or cardinalities, and confirm that maps respect the required operations. In numerical work, report precision, conditioning and a residual rather than digits alone. In algorithmic work, separate mathematical correctness from implementation complexity and resource limits.

Step-by-step operating method

  1. Fix the setting. State the objects, ambient structure, notation and assumptions before manipulating symbols.
  2. Separate claims. Distinguish definitions, hypotheses, conclusions, equivalent conditions and consequences.
  3. Choose a method. Select proof, construction, calculation or algorithm according to the question actually asked.
  4. Work a small case. Use the smallest non-trivial example to expose the mechanism and test edge behaviour.
  5. Verify independently. Substitute back, check invariants, test boundary cases or use an alternative derivation.

Worked-example protocol

Illustrative method—not a source theorem. Start with a small admissible input and list the definitions it must satisfy. Carry out each transformation on a separate line, citing the property that permits it. Preserve exact values until approximation is necessary. At the end, verify the output against the original definition and one invariant such as dimension, degree, determinant, order, norm or residual. Then alter one hypothesis and observe which step ceases to be valid. This protocol creates a reusable example without inventing a theorem-specific numerical answer.

StageRecordQuality check
InputObjects, domain, notation, assumptionsEvery symbol is defined
MethodPermitted operation or cited result at each stepAll hypotheses hold
OutputExact result and representationCorrect type, domain and form
VerificationSubstitution, invariant or alternative derivationIndependent agreement
Boundary testZero, identity, degenerate or failed hypothesisScope is understood

Common failure modes and recovery actions

1. Watch for

Using a theorem without checking every hypothesis.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Treating a suggestive example as a proof of the general case.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Changing notation or conventions part-way through an argument.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Hiding a division-by-zero, convergence, finiteness or commutativity assumption.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Reporting a computed result without a residual, substitution or structural check.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

  • Can every symbol be traced to a definition or prior result?
  • Which hypothesis does each major step use?
  • Does the method cover zero, identity, degenerate and boundary cases?
  • Can the conclusion be checked by a second representation or calculation?
  • Are mandatory requirements distinguished from recommendations and illustrative values?
  • Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
  • Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
  • Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Computing Rank, Kernel and Image?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which assumption about kernel would change the result most if it proved false?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What evidence would allow an independent reviewer to reproduce or challenge the conclusion?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which boundary, exception or failure case has not yet been tested?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What must be handed over, monitored or reviewed after the immediate work is complete?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Authoritative references and use notes

The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.

  • MIT OpenCourseWare — Number Theory I — Massachusetts Institute of Technology. Used for algebraic and analytic number theory. Accessed 2026-08-13.
  • MIT OpenCourseWare — Algebra I — Massachusetts Institute of Technology. Used for groups, vector spaces, linear transformations and linear groups. Accessed 2026-08-13.

Continue learning

Gaussian EliminationGuide · Engineering MathematicsNEXT LESSON →Solving Systems of Linear EquationsGuide · Engineering MathematicsThe Inverse of a MatrixGuide · Engineering MathematicsAlgebras over a RingGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®