Home / Verification
Verification
How TensorNode is checked, with summary counts. The detailed record is kept by TensorNode and is not published.
96modules tested
454code paths
823reference cases
5,200checked values
The method
- Independent reference cases. Each module is run against worked examples calculated separately, and the result of every output value is compared with the reference within a tight tolerance.
- Every code path. The same module is tested in each code system it supports, so a US, Canadian or European path is not assumed to behave like the Australian one.
- Review of the working. The clause references, factors, limits and equations of each module are reviewed against the standard; each finding is recorded and closed with the module changed or the limitation stated.
- Analysis checks. The FEA engine is compared with closed-form solutions and with an independent open-source solver on exported models.
- Every release. The suite runs before each release, and the counts here come from that run.
Counts
| Code system | Code paths tested | Reference cases | Checked values |
|---|---|---|---|
| Australia and New Zealand | 96 | 275 | 1,500 |
| United States | 180 | 190 | 1,457 |
| Canada | 89 | 176 | 1,272 |
| Europe | 89 | 182 | 971 |
Verify a report
Reports made in TensorNode carry a verification code. Open the app, choose About, then Verify a report, and enter the code to confirm that the report was made by TensorNode and has not been changed. Open TensorNode.
Calculation tools support the work of a qualified engineer. The engineer remains responsible for the design and for checking that a result suits the project. See the Terms.