- Most model validation is done by a model’s own authors, on cases they chose. Regulators now say plainly that calibration evidence is not validation evidence.
- When teams have predicted an experiment blind, results have scattered. In the first Sandia Fracture Challenge, one team in 13 stayed within experimental scatter on every numerical quantity.
- Fields that score predictions blind, in public and repeatedly, improve and earn trust. Protein structure prediction is the clearest case.
- Battery models are often anchored in narrower conditions than the ones where decisions are made, and each ageing test can take months. That is where a sealed, running record pays off.
What validation usually means
The textbook definition asks a lot. The AIAA’s 1998 guide defines validation as “the process of determining the degree to which a model is an accurate representation of the real world from the perspective of the intended uses of the model.”1 Two phrases carry the weight: the real world, and intended uses.
In practice, the evidence that a model is fit for a purpose usually arrives as a validation report written by the people who built it, on cases they selected, sometimes against the same data its parameters were fitted to. None of that implies bad faith. It is how the work gets done when there is no shared record.
Regulators have started to draw the line explicitly. In its 2023 guidance on computational models in medical device submissions, the US FDA interprets validation “as comparison against data that is independent of the data used to create the model”, and states that calibration “is not considered validation”. Its advice is direct: “Be cautious not to present or confuse calibration evidence as/with validation evidence.”2
02What happens when the answer is hidden
The cleanest test of a model is a prediction made before the result exists. Several engineering communities have run exactly that experiment on themselves.
The Sandia Fracture Challenge
In mid-summer 2012, Sandia National Laboratories set out to test a gap its organisers named directly: methods in computational mechanics “are rarely validated against problems with an unknown outcome.” Teams were asked to predict how a specimen of a common commercial engineering alloy would tear: the force and crack opening at first cracking, the path the crack would take, and the force and opening when it started to grow again. Thirteen teams from 22 institutions submitted predictions before the experimental results were released.3
Nearly every team predicted the first-crack force within experimental scatter, and every team picked one of the two crack paths seen in the tests. Further into the failure, agreement fell apart. The organisers reported “a striking lack of consistency across research groups” and called for “additional blind prediction-based assessments.”3
| Quantity predicted | Share of teams | Teams |
|---|---|---|
| Crack path matched one seen in the tests | 13 of 13 teams | 13/13 |
| Force when the crack grew again, within scatter | 7 of 13 teams | 7/13 |
| Crack opening when the crack grew again, within scatter | 1 of 13 teams | 1/13 |
| Within scatter on every numerical quantity | 1 of 13 teams | 1/13 |
They got them. The second challenge, issued in 2014, drew 14 teams. Its authors found the predictions “more consistent and in line with the experimental results than in previous challenges”, though four teams still predicted the wrong crack path in at least one loading case.4 By the third, 21 teams took part and “all blind predictions identified the nominal crack path and initiation location correctly”, an improvement the authors credit to the “adoption of best practices from previous Challenges.”5
The Drag Prediction Workshops
Aerodynamics saw the same pattern. At the first AIAA CFD Drag Prediction Workshop in 2001, 18 participants using 14 codes computed the drag of the same wing-body configuration. For a single flight condition, the results spanned “a range of over 270 counts in the drag data, which is quite unacceptable.”6 A later review of the series put the industry’s goal at ±1 drag count, and notes that the fourth workshop was run as a blind test.7
03What blind scoring built
Protein structure prediction shows where this can lead. Since 1994, CASP, the Critical Assessment of protein Structure Prediction, has run every two years. Participants receive the sequences of proteins whose structures have just been determined but are kept secret, submit predictions, and have them scored. Its organisers describe the core of the exercise as “rigorous blind testing of methods and evaluation of the results by independent assessors.”8
At the fourteenth round, in 2020, AlphaFold2 reached a median score of 92.4 GDT across all targets, where a score of around 90 is informally considered competitive with experimental methods.9 The Nobel committee later wrote that when CASP’s organisers evaluated those results, “they understood that biochemistry’s 50-year-old challenge was over.” In 2024, Demis Hassabis and John Jumper shared half of the Nobel Prize in Chemistry for protein structure prediction.10
The model was remarkable. The reason the field believed it was the format: predictions made before the answer was public, scored by independent assessors, the same way every round.
Why batteries need it now
Battery and materials teams face the same question with three complications.
Each check is slow
“Long battery lifetime entails delayed feedback of performance, often many months to years,” as Severson and colleagues put it in 2019.11 Attia and colleagues made the same point a year later: “conducting even a single experiment to evaluate lifetime can take months to years.” Their closed-loop method found high-lifetime fast-charging protocols among 224 candidates in 16 days, compared with over 500 days for an exhaustive search without early prediction.12 Every test that confirms or refutes a model is expensive, so the record of those tests is worth keeping.
Behaviour shifts with conditions
In the same 2019 study, 124 commercial LFP/graphite cells of a single model, cycled in a 30 °C chamber under 72 fast-charging policies, lasted anywhere from 150 to 2,300 cycles.11 The conditions that matter most to a product decision, such as fast charging, cold operation and late life, are where behaviour moves fastest.
Models are anchored narrowly
Physics-based models are often parameterised in a narrow window. A commonly used parameter set for the LG M50 21700 cell, with an NMC811 positive electrode and a graphite-SiOx negative electrode, was validated against discharge and relaxation voltage profiles at room temperature.13 It ships with PyBaMM as “Chen2020”.14 Reviews are direct about what happens beyond a model’s window: equivalent circuit models cannot “operate outside the regime in which they are parameterised”, and the single particle model’s “accuracy decreases as the C-rate increases”.15 One comparison against experimental data found that “the predictability of the DFN model deteriorates when trying to predict the voltage response at low state of charge”.16
Inputs are uncertain too. A 2022 review of parameterisation found that “experimentally obtained exchange current densities vary by several orders of magnitude”.17 Degradation predictions can change shape, not just size: for the same LG M50 cell, raising a single cracking-rate parameter moves the predicted capacity fade from quasi-linear to a knee and then to sudden failure, though the authors note this matters only if such values occur in practice.18
Put together, the conditions where decisions are made are often where models are least anchored, and checking them takes months. That combination is where a sealed, running record earns its keep.
05What the standards already ask for
None of this is new to standards bodies. ASME V&V 40-2018 sets out a framework in which the credibility a model needs should be “commensurate with the degree to which the computational model is relied on as evidence” and with “the consequences of that decision being incorrect”.19 It ties credibility to a context of use, “a statement that defines the specific role and scope of the computational model used to address the question of interest.”2
NASA-STD-7009, published as a standard in 2008 and revised in 2016 and 2024, was developed in response to NASA’s 2004 report on applying the findings of the Columbia accident investigation across the agency. It defines credibility as “the quality to elicit belief or trust in M&S results”, and assesses it through factors that include validation, uncertainty characterisation and results robustness.20
The standards describe what credible evidence looks like. What they leave to each team is the record itself: where predictions are kept, how they are dated, and who can check them later.
06A lesson from pre-registration
Science met a similar problem in how results were reported, and addressed part of it by changing the order of events. Registered Reports, launched at the journal Cortex in 2013, review a study’s question and methods before the results exist.21 In the Center for Open Science’s words, “peer review occurs prior to observing the outcomes of the research.” More than 300 journals have used the format, either as a regular option or in a special issue.22
The principle carries over directly. Commit to the prediction and its uncertainty first. Score it after. Keep both.
07What a track record needs
From the challenges, the standards and the reporting reforms, five requirements follow.
- Sealed before the outcome. The prediction, its interval and the test conditions are fixed and timestamped before the result exists, and cannot change afterwards.
- Scored on the model’s own terms. Each prediction is judged against the interval its model stated, so calibration is visible: a model that claims 90% should contain about 90% of outcomes.
- Mapped to where it was tested. Results are tracked across the operating envelope, so validated regions are kept apart from extrapolation. This is the context of use, made concrete.
- Kept over time. Versions, parameter sets and drift stay on the record, and a claim of fitness lapses when the evidence does.
- Independent of any one vendor. Like CASP’s assessors, whoever keeps the record should have no stake in which model wins.
How Lilienthal puts this into practice
Lilienthal is our implementation of these requirements for teams that run several models against the same lab program. The screens below are from the product, shown with sample data from a fictional cell program.