The calculation engine
Provenance: checking a figure against its source
Every calculated row can be traced back to the publisher's file it came from: the release, the publisher's own row reference, the unit exactly as printed, and every publisher that was asked first.
On this page you'll learn
- What the provenance panel shows
- How a method-based figure differs from a factor-based one
- How to read the resolution trace
- Endpoint
calculated-emissions/{id}/provenance/- Shown in
- The provenance drawer on any calculated row
What it shows
Published beside stored
The factor as Slate used it, and the publisher's row as printed, including the unit string exactly as the publisher wrote it ("tonne.km") next to Slate's controlled code.
As published
Every extra value the publisher printed on that row (heat content, uncertainty, extra gases), labelled automatically so a new publisher's fields appear without code changes.
Release and GWP set
Which release answered, its file, and which GWP set was applied, if any.
Resolution trace
Every publisher asked and what each said, classified as boundary, configuration or data gap.
Unquantified gases
Any gas the method couldn't cost, with the reason and whether you can act on it.
A method is not a factor
Landfill methane, land carbon and manure N₂O come from a published model, not a factor row. Their provenance says method_driven and names the method release, because an empty "as published" panel would look like provenance gone missing.
Reading the trace
| Class | Means | Action |
|---|---|---|
| Boundary | The publisher doesn't cover this | None: moving on was correct |
| Configuration | No release is imported for this publisher or date | Import the release |
| Data gap | Should have resolved and didn't | Fix the mapping or the data |