Check Calculation Errors¶
The Calculation Error Logs list every issue PyGREET could not resolve at calculation time, and the assumption it made instead. Use them to judge how much to trust a result before you report it.
PyGREET checks your model at several levels. It catches many issues early as validations and warnings while you edit an entity. Issues you do not address carry through to calculation time and appear as errors in the logs.
When PyGREET meets an issue it cannot resolve, such as a unit it cannot convert or a connection that was never set, it does not stop the run. It applies a documented fallback (set the value to zero, keep it as declared, or aggregate without conversion) and records what happened.
For an LCA, this makes your results traceable and transparent. Every value is accounted for, and any place where PyGREET made an assumption is visible instead of hidden in a number.
Open the Logs¶
An empty log means the calculation finished cleanly.

Read the Table¶
Each row is one issue PyGREET recorded.
| Column | Shows |
|---|---|
| Type | The category of the issue (see the next section). |
| Entity | The model where the issue occurred. Select it to open the entity and inspect the values. |
| Section | The part of the entity where the value lives (for example, Input, or Non-Combustion Emission & Waste), so you can go straight to it. |
| Message | A plain-language description that names the flow and units involved and the fallback PyGREET applied. |
Note
The discrepancy can be in the current entity or in the one that first declared a value. The message then names both sides. Use the Entity link to confirm which one to correct.
Error Types¶
| Type | Meaning | Fallback |
|---|---|---|
| Unit Conversion | An amount or factor could not be expressed in the unit a step required. | Value set to zero or kept as declared, depending on the step. |
| Elementary Flow Multiple Units | The same elementary flow was declared in conflicting units across processes. | Values aggregated without conversion. |
| Pathway Connection No Set | An input expecting an upstream source had no connection set. | Upstream contribution treated as zero. |
| Division By Zero | A quantity PyGREET divides by resolved to zero, so the result is undefined. This happens when a loss ratio (or moisture content) reaches 100%, or when a consumption, refueling/charging efficiency, lifetime VMT, or reference heating value is zero. | Value set to zero. |
Clear the Logs¶
The logs reflect the current state of your model. When you fix the underlying issue and the affected value recomputes cleanly, or you delete the value, its entry leaves the log automatically.
A cleared log means the run finished without assumptions. Use this as a final check before you export or cite results.