This patch release contains miscellaneous small improvements, most notably richer descriptive fields in the
carbon_intensities
response object and a preliminary version of the updated response schema. Component Descriptions
In the
carbon_intensities
response object, we've added a component_description
field to each item describing the material or assembly in some details. Occasionally, these are obvious (woodlumber is lumber) but sometimes less so (especially for assemblies which include many subassemblies, such as interiors). Aliasing
refurb_pc
to replacement_fraction
This is a non-breaking name change to create closer correspondence between the language we use in the API and how the LCA calculation is actually performed. We updated this name since we are counting B4 replacements and not B5 refurbishment. The choice of phrase here was determined in consultation with the Tally team to better align our language with theirs.
Time series bug fix
In some cases, A1-A3 emissions in building reuse scenarios were being incorrectly calculated in the time series object only. This bug fix addresses this issue, and includes additional unit tests to check for correspondence between the first year of the time series and A1-A3 emissions in the
category_by_stages
object. Validation bug fix for
percent_conditioned_area
We were seeing a bug where users entered 0% conditioned area and were still seeing operational emissions present. This was due to the 0 being validated as a null value and then reset to 100%. In this update, we treat null-ish 0 and null values differently.
Remove duplicate D2 emissions
In cases where users inputted solar pv, D2 emissions were being double counted in
category_by_stages
as they appeared in both pv_array
and operational_energy
. This was ultimately a terminology issue, and we've corrected these results so that D2 emissions would only be present in operational_energy
.Experimental response schema
The current
calculation
response schema is getting long in the tooth. The structure of this schema evolved over time and, as the capabilities of the API have evolved, the schema's structure has shown itself to be a limitation. Additionally, we need to make space in the schema to work towards reconciling our BIM-based, BoM-based, and predictive models into a single calculation structure. To preview the updated schema (still in development), set the top-level param
use_updated_schema
to true
.