neqsim-benchmark-reference-data

Benchmark Reference Data

Every Standard and Comprehensive NeqSim task must compare its results against independent reference data before the numbers are reported. In practice that step gets rewritten in every benchmark notebook, with the reference values pasted in as bare literals, no citation, an invented tolerance, and no check that the reference is actually independent of the model being tested.

This skill supplies the parts that should not be rewritten: where the reference came from, whether it is allowed to be used as a benchmark here, how far the model may deviate before the comparison fails, and what the result block must look like so the report generator and the CI gate accept it.

It does not compute NeqSim results. It provides the other side of the comparison and the verdict.

When to Use

• A task is writing its XX_benchmark_validation.ipynb notebook.
• A benchmark_validation block must be produced for results.json.
• A property, critical constant, or saturation condition from a NeqSim fluid needs an independent, citable reference value.
• A number quoted in a report needs a traceable provenance chain from value to citation.
• An existing benchmark claim must be audited: is the reference independent, is the deviation larger than the reference's own uncertainty, are there enough points?

When Not to Use

• As a property engine. CoolProp and the anchor table are references, not the model — do not use them to produce the answer the task is asked for.
• For mixtures outside a reference formulation's validated range. The applicability gate will refuse, and it is right to refuse.
• As a substitute for measured data on the actual fluid. A reference EOS for a pure component does not validate a characterised reservoir fluid; it validates the pure-component limit of the model.
• To manufacture a PASS. Loosening the tolerance until a comparison passes is the failure mode this skill exists to make visible.

Inputs