How the library is checked

Inspect the published library inventory, the requirements used to check it, and the evidence attached to those requirements. The front page also includes recorded simulation cases.

Checking the published library snapshot…

A verification requirement identifies a claim, an aspect of that claim, and a checking method. The published scope is counted independently of the number of files or jobs. Requirement coverage is being loaded from the published snapshot.

Closure is derived from the evidence and publication records bound to the accepted revision, not from a job counter or a model’s presence in the catalogue. A check uses its declared method, observables, references and tolerances; structural inspection is distinct from simulation and from comparison with measured data. The current closure result is being loaded. Withdrawn or stale evidence cannot count as current coverage.

The method determines what a check can demonstrate:

• Structural checks inspect the declared subjects, connectors, parameters or composition. They do not establish numerical accuracy.
• Analytic checks compare declared observables with an independently computed relation or invariant, within the acceptance tolerances.
• Cross-code checks compare distinct implementations for the quantities and operating conditions stated by the check.
• Source-based checks require a traceable source, the applicable rights, the extracted quantities and the declared comparison. Published inputs alone are not an experimental validation target.

Coverage has a boundary. The table counts the published requirement scope, not every possible use of a model. Neither a catalogue entry nor a closed requirement implies plant qualification, licensing suitability or independent institutional reproduction. Consult the attached evidence for its operating range, method and limitations.

Capability assessments may describe interfaces, physics, geometry, operation and evidence separately. A maturity label and a current requirement closure answer different questions; neither is inferred from catalogue size.

Where an assessment is available, its scope and supporting evidence determine how it may be used.

Assessment metadata is being loaded. No maturity rating is assigned by this page.

Each row names a capability in the current scope. Each column is an assessment dimension. A cell gives requirements with current linked evidence out of the requirements tracked; “–” means none is tracked for that dimension. The shade is coverage, not a maturity rating. Select, focus or hover a row for its summary.

The package contains physics functions, fluid and material property packages, reusable components, integrated systems and example models. The accepted revision and inventory definition are being loaded.

Browse the examples present in the accepted library revision by domain or name. Presence in this catalogue is an inventory fact, not a claim that every example has been simulated successfully on the current revision.