new
New Features!
Backend updates
2.50.00: Expanded interiors model; address DB issues; misc. bugfixes and updates
This minor release contains a greatly expanded and enriched interiors model as well as updates to how we handle DB connections. There are a few minor bugs we are aware of and working to address ASAP, noted below.
Expand Interiors Model
To support some enterprise API users, we are expanding how interiors modeling is performed in the application. The alternate schema for the
interiors
object is a list of spaces
, each of which is a collection of takeoffs
(and some overall descriptive data.). The takeoffs are all tagged to an
id
field. Acceptable entries for the id
field can be queried with a GET request to /api/interiors/assemblies/list
. To get the full description of a particular assembly, pass that id
in a GET request to api/interiors/assembly
Address DB Issues
In the past week, we have had intermittent issues with how we are sharing database connections across Lambda executions. To solve this, we are performing health checks and retries w/ backoff when the database is not behaving as expected. This appears to have addressed the issue in development environment. While this will make finicky requests slower, we prefer the occasional slow request to the same frequency of failures.
Misc. Updates
In addition to the above, we made a variety of small updates -
- Previously, there were occasional errors with very small (< 10 m2) floor areas; these have been addressed.
- C.Scale no longer counts D1 recycling potential from waste generated on the jobsite during construction. Certifications are mostly silent on this topic, but this updates hews close to general guidance on reporting D1 emissions separately.
- Emission summaries throughout the response object are now only A-C emissions (as relevant).
- Solar PV now has a separate includeparameter
- In category_by_stages, construction activities is now broken out into its own category
- The first year of any embodied carbon timeseries data now includes A4 and A5p3 emissions in addition to A1–A3. This ensures consistency and improves alignment with the category_by_stagesresponse object.