RunMat for aerospace engineering

Reduce flight and test data, qualify hardware against vibration and shock, and run structural and thermal simulations, in one MATLAB-language tool your team works in together.

Talk to us

Write math in the language your engineers already know

MATLAB is the working language of aerospace analysis. Flight-test reduction, guidance and control, loads post-processing and Monte Carlo work are written in it, and engineering schools teach it, so the engineers you have and the ones you hire already know it.

RunMat runs MATLAB-language code as it is, in the same project as your simulation studies. Existing scripts keep working, and new work starts without retraining anyone.

Migration guideSignal processing

flight-attitude.m
% Kalman filter, state x = [pitch; gyro bias].
F = [1 -dt; 0 1]; B = [dt; 0]; H = [1 0];
Q = diag([1e-4 1e-6]); R = 2.5^2;
x = [accel(1); 0]; P = diag([10 1]);
est = zeros(n, 1); integ = zeros(n, 1); integ(1) = accel(1);
for k = 2:n
x = F * x + B * gyro(k); % predict with the gyro
P = F * P * F' + Q;
K = P * H' / (H * P * H' + R); % correct with the accelerometer
x = x + K * (accel(k) - H * x);
P = (eye(2) - K * H) * P;
est(k) = x(1);
integ(k) = integ(k-1) + gyro(k) * dt; % gyro alone, for comparison
end
Terminal
$ runmat flight-attitude.m
pitch error (RMS), Kalman estimate: 0.16 deg
gyro alone 15.47 deg, accelerometer alone 2.50 deg

Run multiphysics simulations defined in text

Most simulation tools capture setup as hundreds of choices made through menus and dialogs, saved in a project file that only the tool can open. In RunMat the whole intent of a study, its geometry, materials, loads and the analyses it chains, is a short text file with the units written in.

Text can be read, compared line by line, reused across a program and rerun years later. It is also what AI models write well: a model can set up a study from a description, and RunMat checks units, regions and the analysis chain before anything runs.

This study heats an avionics box, carries the temperature into its structure and solves the vibration modes the heat shifts, all on one mesh.

Simulation in RunMatThermal

avionics-box-heated-modes.fea
study heated_modes {
geometry = geometry.box
mesh = mesh.box
model = model.operating
analysis heat { thermal steady {} retain heated }
analysis preload after analysis.heat {
thermomechanical preload { temperature = analysis.heat.state.heated }
}
analysis modes after analysis.preload {
structural prestressed_modal {
prestress = analysis.preload.state.geometric_stiffness
modes = 6
}
}
}

Design the vehicle where you analyze it

Model parts and assemblies in RunMat MCAD, with each dimension as an input in the part file. Change an input and the part regenerates, and its assemblies and drawings update from it.

Studies on a part rerun on the new geometry with their setup in place, so each design change gets its stress and modal check in one project. Avionics boards are laid out in RunMat ECAD, in the project that holds the airframe.

RunMat MCADRunMat ECAD

RunMat MCAD on the camera drone: RunMat Agent is asked for a landing-gear skid, asks which way the skids run, then builds two carbon-fiber tubes on four aluminum clamp-legs and reports 27.2 mm ground clearance and a 36.2° tip-over angle. The view turns to show the gear from below. The cursor then sketches a rectangle on the hinge mount's top face, extrudes a 3 mm boss, and opens the part's source, where the new sketch1 and extrude1 code is selected.
0:00 / 0:00
Example: a camera drone in RunMat MCAD. RunMat Agent adds landing gear with 27.2 mm ground clearance and a 36.2° tip-over angle, then a boss is sketched and extruded on the hinge mount and its new code appears in the part's source.

A deterministic engine designed for AI models to use in controlled loops

RunMat is a deterministic engine: the same study or script gives the same result every time. It is designed for AI models to use in a controlled loop, for work like the analyses on this page.

The model writes the study. RunMat checks its units, regions and analysis chain and sends any error back for the model to fix, then solves it. The model reports the result and how it was computed, and every number in that answer came from RunMat, so it can go in a qualification report.

Use Claude Code, Codex, any MCP client or the agent built into RunMat, on the model your company already uses.

AI integrations

Works withClaude CodeCodexAny MCP client

AI modelSets up and interpretsRunMatChecks and runs the studystudyerrors and results
  1. ModelWrites cantilever.fea
  2. RunMatline 28: traction must be force per area, found N
  3. ModelFixes the load unit: N → Pa
  4. RunMatSolved · tip deflection 0.199 mm, beam theory 0.200 mm
  5. ModelReports the results and how they were computed

Work together, live, in multiplayer

Analysts, test engineers, leads and suppliers open the same project at once. Everyone sees each other's edits and cursors, and can point at the same peak on a plot or the same spot on a 3D result, as it happens.

Reviews happen on the result itself instead of over email and screen shares, and every run is shared with the inputs and software version that produced it, ready for the certification file.

Scale from one computer to large clusters

Anything you write, MATLAB-language scripts and simulation studies alike, runs on a laptop, across every core, on the GPU or across a cluster you own, without being rewritten.

Sweep a design over hundreds of studies or run thousands of Monte Carlo cases in parallel, and collect the results in the same script.

Parallel

% 200 bracket thicknesses, one study each, across the cluster
t = 2 + 4 * (0:199) / 199;            % mm
f1 = zeros(1, 200);
parfor k = 1:200
    f1(k) = first_mode(fea.run(bracket_study(t(k))));
end
LaptopRemote serverLARGE CLUSTER

Keep controlled work inside your network

The desktop, server and workers can run fully offline on your machines, which makes ITAR-aligned private deployment possible under enterprise contract. The source of the runtime and solver is public, so your security team can read what runs.

Defense and controlled programs

Examples

Shelf vibration spectra at takeoff, climb and cruise against the qualification limit, rendered by RunMat

Flight-test vibration against its limit

Welch spectra of three test points against the GEVS limit.

Pitch from accelerometer tilt, gyro integration and a Kalman estimate against the reference, rendered by RunMat

Pitch from IMU data

A Kalman filter on a drifting gyro and a noisy accelerometer.

GEVS input spectrum and the response of a 180 Hz mode, rendered by RunMat

Random vibration of one mode

Miles' equation against the integrated response at 180 Hz.

Shock response spectrum of a decaying multi-tone transient against its peak input, rendered by RunMat

Shock response spectrum

A pyroshock-like transient through 60 Q = 10 oscillators.

Impact points of 4,000 dispersed trajectories with a 3-sigma ellipse, rendered by RunMat

Impact footprint

4,000 dispersed trajectories and their 3-sigma ellipse.

Board and case temperatures of an avionics unit over a three-hour flight against the board limit, rendered by RunMat

Avionics temperature through a flight

A two-mass thermal model of a board and its case, with ode45.

What RunMat does not do

  • Block-diagram modeling like Simulink, and code generation for flight software
  • DO-178C or DO-330 tool qualification
  • Coupled loads analysis with a launch vehicle, flutter and aeroelasticity
  • Compressible or turbulent flow
  • Fatigue, large deformation, contact and bolted joints

Start here

  1. 01

    Open the flight-test example in your browser. No account needed.

  2. 02

    Run three of your own scripts and compare their run times.

  3. 03

    Talk to us about your team, your programs and where it runs.

Defense and controlled programsStructural simulationSignal processingParallel computing