/software/

TESSERA · FEM SOFTWARE · IN DEVELOPMENT

General-purpose finite element analysis, built to be checked.

Tessera is the finite element platform we are building at BadgerMecX — a solver for real engineering models, starting with structures and growing into the physics we already run for clients. The difference is not a feature list: verification, reproducibility and the working behind a result are part of the product.

Verification-firstRuns in the browserBuilt by engineers who run analyses

WHY WE ARE BUILDING IT

The analysis is the easy part.

We run analyses for a living. The hard part is almost never the solver — it is showing, months later and to someone else, that the result can be trusted.

01Results without a paper trailA number comes out of a black box. Showing a reviewer why it is right means redoing the work by hand.
02Verification is left to youThe vendor validates the software; nobody validates your model, your mesh or your settings — and that is where the risk sits.
03A run cannot be repeatedSix months later the version has moved, the settings are gone and the result cannot be reproduced exactly.
04Licences shape the workSeat cost decides who is allowed to open and check the model; the file format decides whether you can ever leave.
05Setup takes longer than the analysisInstalls, versions, drivers and a licence server before the first run.
06Reports are rebuilt by handNumbers are copied into a document and the link back to the run that produced them is lost.

THE PROGRAM

What it looks like today.

Mesh Quality
Mesh Quality The quality window reads the mesh before anything is solved: aspect ratio, Jacobian ratio and skewness, each as a histogram with its minimum, mean and maximum. Clicking a bar selects those elements in the model, so a bad number is a place you can look at rather than a figure in a table. The convergence study runs on the same mesh and reports whether the result has stopped moving.
Contacts
Contacts Contacts are found automatically when a multi-part shape is meshed. Instead of a list of names to choose from, the panel asks two questions — can they come apart, and can they slide on each other — and the answer picks the type. The selected contact is drawn on the model: side A orange, side B cyan, the rest of the assembly translucent. Reach and gap are set per contact, and the panel says how many nodes were tied.
General View Screen
General View Screen One window: model tree, toolbar, result and legend. Every result keeps its own clamp, so changing the scale on displacement leaves the von Mises scale where it was. The capture panel on the right exports the figure at report size with a transparent background, and the charts on the view go into the image where they sit on screen. The console at the top keeps the command log — the answer to "how did you get this result".

HOW WE ARE BUILDING IT

Rules we hold ourselves to.

  1. 01
    Verification is part of the releaseA solver goes out only with its verification set: closed-form solutions, standard benchmarks and hand calculations, published next to it. A release that fails one does not ship.Re-run on every deploy.
  2. 02
    Every run is reproducibleThe engine version, the inputs, the mesh and the assumptions travel with the result, so the same run can be repeated months later by someone else.Reports carry the engine version.
  3. 03
    The working stays visibleWhere a result can be shown step by step, it is: the formulation, the substituted values and the checks behind the number — next to it, not in a help page.
  4. 04
    Your models stay yoursDocumented, open formats in and out. Export is not a paid feature and leaving must always be possible.
  5. 05
    Web-native and scriptableRuns in the browser, scales to the cloud for heavy runs, and anything the interface can do the API can do.
  6. 06
    Built by the people running the analysesWe use it on our own consultancy work before anyone else does. If it does not survive a real deadline and a real reviewer, it is not ready.
  7. 07
    Limits are statedWhere a model is outside its range of validity the software says so, instead of returning a confident number.

WHERE WE WILL BE DIFFERENT

The things we refuse to compromise on.

We do not compare ourselves to any named product — we state what we hold ourselves to.

Verification is part of the product Every solver ships with the reference cases it must reproduce, published with it and re-run on each release.
USUALLY
A validation manual, separate from your model
TESSERA
Published with the solver, re-run on every release
Reproducible runs Version, inputs, mesh and assumptions are stored with the result, so an analysis can be reproduced exactly and defended later.
USUALLY
Version, settings and inputs scattered across files
TESSERA
Version-stamped, repeatable run
The working, not just the number For everything we can show step by step, the formulation and the substituted values sit next to the result.
USUALLY
A number out of a black box
TESSERA
Result plus the working behind it
Your models stay portable Documented, open input and output formats, with export included.
USUALLY
Proprietary formats; export as an upsell
TESSERA
Open formats, export included
No install, no licence server The browser is the workstation; heavy runs move to the cloud without changing the model. The API does everything the interface does.
USUALLY
Local install, drivers, licence server
TESSERA
Browser and API from day one
Checking a model is not a licence decision Reviewing someone else's model should never be blocked by a seat count.
USUALLY
Per-seat licences decide who may check

WHO IS BUILDING IT

Engineers who run these analyses for a living.

We run finite element and flow analysis as consultancy work — structural FEA, CFD, vibration and NVH, thermal and acoustics — from concept validation to regulatory approval, for [XX] years. Tessera exists because we keep hitting the same walls in our own projects, and because we already know what a result has to survive: a client, an independent reviewer and an approval body.

What we do for clients →

SCOPE

What it will do, and where each part stands.

running todayin buildplanned
running Solver core & verification suite The element library, the linear solver and the reference cases every release must reproduce. Runs behind the public calculators
running Linear statics Frames and trusses today; plates, shells and solids next. 2D frames live: C-05
running Sections, members and stability Section properties, beams, buckling and member behaviour from first principles. Live: C-01, C-03, C-04
running Loads & design checks Code loads and combinations, then member and connection checks with the clause shown. Wind load live: C-10
running Mesh & geometry Import, clean up, mesh and mesh-convergence control.
build Modal & dynamics Natural frequencies, response spectrum and transient analysis.
build Nonlinear & contact Large displacement, material nonlinearity and contact.
running Thermal Steady-state and transient conduction with convection and radiation boundaries.
running Results & reporting Diagrams, tables and a report that carries the version stamp.
planned Performance Sparse direct and iterative solvers, parallel and cloud runs.
planned API & automation Drive the solver from a script: parametric studies and optimisation.

ROADMAP

Stages, not dates.

A stage goes live when its release condition is met — not when a date arrives.

  1. Stage 1 Solver core and verification suite The element library, the linear solver and the test set it must pass on every release. The free calculators run on it in public. RELEASE CONDITIONEvery engine reproduces its reference set before release.
  2. Stage 2 Workspace: models, runs and reports Save a model, keep the run history, export a version-stamped report. RELEASE CONDITIONProven on our own client jobs first.
  3. Stage 3 2D structural models in the browser Build the model in the interface, run the linear solver on it, read the results in the same place. RELEASE CONDITIONA published benchmark set reproduced against reference solutions.
  4. Stage 4 3D frames, plates and shells Full 3D structural modelling with meshing and convergence control. RELEASE CONDITIONValidation against reference models and independent cross-checks.
  5. Stage 5 Dynamics and nonlinear Modal analysis, response spectra, large displacement, plasticity and contact. RELEASE CONDITIONLiterature benchmarks reproduced within a stated tolerance.
  6. Stage 6 Open API and automation Everything the interface can do, from a script. RELEASE CONDITIONIdentical results through the API and the interface.

WHILE WE BUILD

Free calculators, open to everyone.

Small, single-purpose tools we publish for free. They run on the same solver core and the same verification suite, and they need no account.

What do you analyse?