Send the acquisition export from a single firing. You get back the same descriptive and diagnostic analysis a commercial programme receives — every derived parameter, every flag, with the derivation shown and documents you can attach to a report or a defence.
A university team is not a small company. The campaign is shorter, the people are the same people who built the hardware, and the result has to hold up in front of a reviewer who was never at the stand.
Two or three firings in a semester, sometimes one. Each run has to yield everything it can, because there is rarely a next month to repeat it in.
The people who designed the engine are the people who run the stand and then process the data — in the same weeks they have coursework and exams.
A spreadsheet per run and a script someone wrote two years ago and graduated. Results are hard to reproduce and harder to compare across the series.
A supervisor, a defence, a jury reading it years later. A number needs its derivation attached — not a chart that looked convincing at the time.
Not a trimmed demo version. The same computation core, the same reports, the same traceability — applied to one of your firings, at no cost, with no integration work on your side.
That is the whole list. If a channel is missing or a calibration cannot be confirmed, we say which parameters that makes unavailable rather than filling the gap.
A finished analysis of your own firing is teaching material — a hard start classified from a chamber-pressure trace, with the reasoning visible enough for a student to argue with it.
A campaign processed by one consistent method gives a term of defensible topics: stability in the steady-state window, chill-down as a precursor, repeatability across the series.
Team members work inside the same record an engineer would use, which is closer to how propulsion work is actually done than a spreadsheet inherited from last year's team.
Write to us and mark it as an academic request — tell us the team, the engine and roughly when it was fired.