FlexMeasures 0.12.2

FlexMeasures 0.12.2

This is a patch release in the 0.12.x series and includes some regression fixes. We recommend that all users upgrade to this version.

See our changelog for a list of all the changes.

FlexMeasures 0.12.1

FlexMeasures 0.12.1

This is a patch release in the 0.12.x series and includes some regression fixes. We recommend that all users upgrade to this version.

See our changelog for a list of all the changes.

v0.12: Replay, custom scheduling

.. warning:: After upgrading to flexmeasures==0.12, users of API versions 1.0, 1.1, 1.2, 1.3 and 2.0 will receive "Deprecation" and "Sunset" response headers, and warnings are logged for FlexMeasures hosts whenever users call API endpoints in these deprecated API versions.
The relevant endpoints are planned to become unresponsive in flexmeasures==0.13.

.. warning:: Upgrading to this version requires running flexmeasures db upgrade (you can create a backup first with flexmeasures db-ops dump).

.. note:: Read more on these features on the FlexMeasures blog <http://flexmeasures.io/012-replay-custom-scheduling/>__.

New features

• Hit the replay button to visually replay what happened, available on the sensor and asset pages [see PR #463 <http://www.github.com/FlexMeasures/flexmeasures/pull/463>_ and PR #560 <http://www.github.com/FlexMeasures/flexmeasures/pull/560>_]
• Ability to provide your own custom scheduling function [see PR #505 <http://www.github.com/FlexMeasures/flexmeasures/pull/505>_]
• Visually distinguish forecasts/schedules (dashed lines) from measurements (solid lines), and expand the tooltip with timing info regarding the forecast/schedule horizon or measurement lag [see PR #503 <http://www.github.com/FlexMeasures/flexmeasures/pull/503>_]
• The asset page also allows to show sensor data from other assets that belong to the same account [see PR #500 <http://www.github.com/FlexMeasures/flexmeasures/pull/500>_]
• The CLI command flexmeasures monitor latest-login supports to check if (bot) users who are expected to contact FlexMeasures regularly (e.g. to send data) fail to do so [see PR #541 <http://www.github.com/FlexMeasures/flexmeasures/pull/541>_]
• The CLI command flexmeasures show beliefs supports showing beliefs data in a custom resolution and/or timezone, and also saving the shown beliefs data to a CSV file [see PR #519 <http://www.github.com/FlexMeasures/flexmeasures/pull/519>_]
• Improved import of time series data from CSV file: 1) drop duplicate records with warning, 2) allow configuring which column contains explicit recording times for each data point (use case: import forecasts) [see PR #501 <http://www.github.com/FlexMeasures/flexmeasures/pull/501>], 3) localize timezone naive data, 4) support reading in datetime and timedelta values, 5) remove rows with NaN values, and 6) filter by values in specific columns [see PR #521 <http://www.github.com/FlexMeasures/flexmeasures/pull/521>]
• Filter data by source in the API endpoint /sensors/data (GET) [see PR #543 <http://www.github.com/FlexMeasures/flexmeasures/pull/543>_]
• Allow posting null values to /sensors/data (POST) to correctly space time series that include missing values (the missing values are not stored) [see PR #549 <http://www.github.com/FlexMeasures/flexmeasures/pull/549>_]
• Allow setting a custom planning horizon when calling /sensors/<id>/schedules/trigger (POST), using the new duration field [see PR #568 <http://www.github.com/FlexMeasures/flexmeasures/pull/568>_]
• New resampling functionality for instantaneous sensor data: 1) flexmeasures show beliefs can now handle showing (and saving) instantaneous sensor data and non-instantaneous sensor data together, and 2) the API endpoint /sensors/data (GET) now allows fetching instantaneous sensor data in a custom frequency, by using the "resolution" field [see PR #542 <http://www.github.com/FlexMeasures/flexmeasures/pull/542>_]

Bugfixes

• The CLI command flexmeasures show beliefs now supports plotting time series data that includes NaN values, and provides better support for plotting multiple sensors that do not share the same unit [see PR #516 <http://www.github.com/FlexMeasures/flexmeasures/pull/516>_ and PR #539 <http://www.github.com/FlexMeasures/flexmeasures/pull/539>_]
• Fixed JSON wrapping of return message for /sensors/data (GET) [see PR #543 <http://www.github.com/FlexMeasures/flexmeasures/pull/543>_]
• Consistent CLI/UI support for asset lat/lng positions up to 7 decimal places (previously the UI rounded to 4 decimal places, whereas the CLI allowed more than 4) [see PR #522 <http://www.github.com/FlexMeasures/flexmeasures/pull/522>_]
• Stop trimming the planning window in response to price availability, which is a problem when SoC targets occur outside of the available price window, by making a simplistic assumption about future prices [see PR #538 <http://www.github.com/FlexMeasures/flexmeasures/pull/538>_]
• Faster loading of initial charts and calendar date selection [see PR #533 <http://www.github.com/FlexMeasures/flexmeasures/pull/533>_]

Infrastructure / Support

• Reduce size of Docker image (from 2GB to 1.4GB) [see PR #512 <http://www.github.com/FlexMeasures/flexmeasures/pull/512>_]
• Allow extra requirements to be freshly installed when running docker-compose up [see PR #528 <http://www.github.com/FlexMeasures/flexmeasures/pull/528>_]
• Remove bokeh dependency and obsolete UI views [see PR #476 <http://www.github.com/FlexMeasures/flexmeasures/pull/476>_]
• Fix flexmeasures db-ops dump and flexmeasures db-ops restore not working in docker containers [see PR #530 <http://www.github.com/FlexMeasures/flexmeasures/pull/530>] and incorrectly reporting a success when pg_dump and pg_restore are not installed [see PR #526 <http://www.github.com/FlexMeasures/flexmeasures/pull/526>]
• Plugins can save BeliefsSeries, too, instead of just BeliefsDataFrames [see PR #523 <http://www.github.com/FlexMeasures/flexmeasures/pull/523>_]
• Improve documentation and code w.r.t. storage flexibility modelling ― prepare for handling other schedulers & merge battery and car charging schedulers [see PR #511 <http://www.github.com/FlexMeasures/flexmeasures/pull/511>, PR #537 <http://www.github.com/FlexMeasures/flexmeasures/pull/537> and PR #566 <http://www.github.com/FlexMeasures/flexmeasures/pull/566>_]
• Revised strategy for removing unchanged beliefs when saving data: retain the oldest measurement (ex-post belief), too [see PR #518 <http://www.github.com/FlexMeasures/flexmeasures/pull/518>_]
• Scheduling test for maximizing self-consumption, and improved time series db queries for fixed tariffs (and other long-term constants) [see PR #532 <http://www.github.com/FlexMeasures/flexmeasures/pull/532>_]
• Clean up table formatting for flexmeasures show CLI commands [see PR #540 <http://www.github.com/FlexMeasures/flexmeasures/pull/540>_]
• Add "Deprecation" and "Sunset" response headers for API users of deprecated API versions, and log warnings for FlexMeasures hosts when users still use them [see PR #554 <http://www.github.com/FlexMeasures/flexmeasures/pull/554>_ and PR #565 <http://www.github.com/FlexMeasures/flexmeasures/pull/565>_]
• Explain how to avoid potential SMTPRecipientsRefused errors when using FlexMeasures in combination with a mail server [see PR #558 <http://www.github.com/FlexMeasures/flexmeasures/pull/558>_]
• Set a limit to the allowed planning window for API users, using the FLEXMEASURES_MAX_PLANNING_HORIZON setting [see PR #568 <http://www.github.com/FlexMeasures/flexmeasures/pull/568>_]

.. warning:: The API endpoint ([POST] /sensors/(id)/schedules/trigger <api/v3_0.html#post--api-v3_0-sensors-(id)-schedules-trigger>_) to make new schedules will (in v0.13) sunset the storage flexibility parameters (they move to the flex-model parameter group), as well as the parameters describing other sensors (they move to flex-context).

.. warning:: The CLI command flexmeasures monitor tasks has been deprecated (it's being renamed to flexmeasures monitor last-run). The old name will be sunset in version 0.13.

.. warning:: The CLI command flexmeasures add schedule has been renamed to flexmeasures add schedule for-storage. The old name will be sunset in version 0.13.

FlexMeasures 0.11.3

FlexMeasures 0.11.3

This is a patch release in the 0.11.x series and includes some regression fixes. We recommend that all users upgrade to this version.

See our changelog for a list of all the changes.

FlexMeasures 0.11.2

FlexMeasures 0.11.2

This is a patch release in the 0.11.x series and includes some regression fixes. We recommend that all users upgrade to this version.

See our changelog for a list of all the changes.

FlexMeasures 0.11.1

FlexMeasures 0.11.1

This is a patch release in the 0.11.x series and includes some regression fixes. We recommend that all users upgrade to this version.

See our changelog for a list of all the changes.

v0.11: Better data views

Version v0.11 of FlexMeasures adds much more useful data views, which are also customizable.
In addition, we completed the Docker-compose stack to include background job workers. This is very useful for developers.

New features

• The asset page now shows the most relevant sensor data for the asset [see PR #449 <http://www.github.com/FlexMeasures/flexmeasures/pull/449>_]
• Individual sensor charts show available annotations [see PR #428 <http://www.github.com/FlexMeasures/flexmeasures/pull/428>_]
• New API options to further customize the optimization context for scheduling, including the ability to use different prices for consumption and production (feed-in) [see PR #451 <http://www.github.com/FlexMeasures/flexmeasures/pull/451>_]
• Admins can group assets by account on dashboard & assets page [see PR #461 <http://www.github.com/FlexMeasures/flexmeasures/pull/461>_]
• Collapsible side-panel (hover/swipe) used for date selection on sensor charts, and various styling improvements [see PR #447 <http://www.github.com/FlexMeasures/flexmeasures/pull/447>_ and PR #448 <http://www.github.com/FlexMeasures/flexmeasures/pull/448>_]
• Add CLI command flexmeasures jobs show-queues [see PR #455 <http://www.github.com/FlexMeasures/flexmeasures/pull/455>_]
• Switched from 12-hour AM/PM to 24-hour clock notation for time series chart axis labels [see PR #446 <http://www.github.com/FlexMeasures/flexmeasures/pull/446>_]
• Get data in a given resolution [see PR #458 <http://www.github.com/FlexMeasures/flexmeasures/pull/458>_]

.. note:: Read more on these features on the FlexMeasures blog <http://flexmeasures.io/011-better-data-views/>__.

Bugfixes

• Do not fail asset page if entity addresses cannot be built [see PR #457 <http://www.github.com/FlexMeasures/flexmeasures/pull/457>_]
• Asynchronous reloading of a chart's dataset relies on that chart already having been embedded [see PR #472 <http://www.github.com/FlexMeasures/flexmeasures/pull/472>_]
• Time scale axes in sensor data charts now match the requested date range, rather than stopping at the edge of the available data [see PR #449 <http://www.github.com/FlexMeasures/flexmeasures/pull/449>_]
• The docker-based tutorial now works with UI on all platforms (port 5000 did not expose on MacOS) [see PR #465 <http://www.github.com/FlexMeasures/flexmeasures/pull/465>_]
• Fix interpretation of scheduling results in toy tutorial [see PR #466 <http://www.github.com/FlexMeasures/flexmeasures/pull/466>_ and PR #475 <http://www.github.com/FlexMeasures/flexmeasures/pull/475>_]
• Avoid formatting datetime.timedelta durations as nominal ISO durations [see PR #459 <http://www.github.com/FlexMeasures/flexmeasures/pull/459>_]
• Account admins cannot add assets to other accounts anymore; and they are shown a button for asset creation in UI [see PR #488 <http://www.github.com/FlexMeasures/flexmeasures/pull/488>_]

Infrastructure / Support

• Docker compose stack now with Redis worker queue [see PR #455 <http://www.github.com/FlexMeasures/flexmeasures/pull/455>_]
• Allow access tokens to be passed as env vars as well [see PR #443 <http://www.github.com/FlexMeasures/flexmeasures/pull/443>_]
• Queue workers can get initialised without a custom name and name collisions are handled [see PR #455 <http://www.github.com/FlexMeasures/flexmeasures/pull/455>_]
• New API endpoint to get public assets [see PR #461 <http://www.github.com/FlexMeasures/flexmeasures/pull/461>_]
• Allow editing an asset's JSON attributes through the UI [see PR #474 <http://www.github.com/FlexMeasures/flexmeasures/pull/474>_]
• Allow a custom message when monitoring latest run of tasks [see PR #489 <http://www.github.com/FlexMeasures/flexmeasures/pull/489>_]

FlexMeasures 0.10.1

FlexMeasures 0.10.1

This is a patch release in the 0.10.x series and includes some regression fixes. We recommend that all users upgrade to this version.

See our changelog for a list of all the changes.

Dockerization & Styling

New features

• New design for FlexMeasures' UI back office [see PR #425 <http://www.github.com/FlexMeasures/flexmeasures/pull/425>_]
• Improve legibility of chart axes [see PR #413 <http://www.github.com/FlexMeasures/flexmeasures/pull/413>_]
• API provides health readiness check at /api/v3_0/health/ready [see PR #416 <http://www.github.com/FlexMeasures/flexmeasures/pull/416>_]

.. note:: Read more on these features on the FlexMeasures blog <http://flexmeasures.io/010-docker-styling/>__.

Bugfixes

• Fix small problems in support for the admin-reader role & role-based authorization [see PR #422 <http://www.github.com/FlexMeasures/flexmeasures/pull/422>_]

Infrastructure / Support

• Dockerfile to run FlexMeasures in container; also docker-compose file [see PR #416 <http://www.github.com/FlexMeasures/flexmeasures/pull/416>_]
• Unit conversion prefers shorter units in general [see PR #415 <http://www.github.com/FlexMeasures/flexmeasures/pull/415>_]
• Shorter CI builds in Github Actions by caching Python environment [see PR #361 <http://www.github.com/FlexMeasures/flexmeasures/pull/361>_]
• Allow to filter data by source using a tuple instead of a list [see PR #421 <http://www.github.com/FlexMeasures/flexmeasures/pull/421>_]

FlexMeasures 0.9.4

This is a patch release in the 0.9.x series and includes some regression fixes. We recommend that all users upgrade to this version.

See our changelog for a list of all the changes.