v4.0.5

What's Changed

• Flip slope when deserializing legacy hdd_only models

Full Changelog: v4.0.4...v4.0.5

v4.0.4

What's Changed

• Fix issues with legacy model deserialization

Full Changelog: v4.0.3...v4.0.4

v4.0.3

What's Changed

• Move masking behavior for rows with missing temperature from reporting dataclass to prediction output
• Add disqualification check to billing model predict()

Full Changelog: v4.0.2...v4.0.3

v4.0.2

What's Changed

• Point test data to correct branch
• Fix issues with datetimeindex

Full Changelog: v4.0.1...v4.0.2

v4.0.1

What's Changed

• Correct dataframe input behavior and final row temperature aggregation
• Remove unnecessary datetime normalization in order to respect hour of day
• Convert timestamps in certain warnings to strings to allow serialization
• Allow configuration of segment_type in HourlyModel wrapper

Full Changelog: v4.0.0...v4.0.1

v4.0.0

What's Changed

• Update daily model methods, API, and serialization
• Provide new API for hourly model to match daily syntax and prepare for future additions
• Add baseline and reporting dataclasses to support compliant initialization of meter and temperature data

Full Changelog: v3.2.0...v4.0.0

OpenEEmeter v1.0.0 Release notes

Welcome to the OpenEEmeter. This fully documented and supported release provides libraries for calculating monthly and daily weather-normalized metered energy savings. It reflects the official guidance of the CalTRACK methods specification and can be used to generate CalTRACK compliant savings estimates.

This official release of the OpenEEmeter is designed for analysts who want to quickly calculate weather-normalized metered energy savings. An enhanced data formatter and loader along with standard outputs have allowed us to deprecate the ETL library and Datastore application associated with the alpha releases of the OpenEEmeter.

You may download and use the OpenEEmeter with no restrictions or licensing fees. You can run meters locally, deploy it on your own servers, or wrap it into a larger application. We’d love to hear about your ideas for using it.

While the OpenEEmeter is generally pretty amazing, there are some things that it can’t do yet. We’re counting on Elon Musk for most of those things. In the meantime, feel free to let us know how we can improve it.