FlexMeasures / flexmeasures / 19737548276

74%

Build Type

push

github

Committed by web-flow

Commit Message

Feat: improve UX of running forecasters with different configuration (#1834)

* feat: add success message

Signed-off-by: F.N. Claessen <felix@seita.nl>

* fix: max training period should lead to the most recent period in the original training window, instead of the oldest period

Signed-off-by: F.N. Claessen <felix@seita.nl>

* docs: missing punctuation

Signed-off-by: F.N. Claessen <felix@seita.nl>

* feat: warn in case forecaster made no forecasts

Signed-off-by: F.N. Claessen <felix@seita.nl>

* feat: if name, type, model and version are equal, keep the data source with the highest ID, as this will represent the most recently added data source, which has the most up-to-date data_generator config

Signed-off-by: F.N. Claessen <felix@seita.nl>

* feat: do not create a new source with every change in start_date and end_date

Signed-off-by: F.N. Claessen <felix@seita.nl>

* docs: explain why the as_job parameter is not part of the data_generator config

Signed-off-by: F.N. Claessen <felix@seita.nl>

* feat: let charts show all versions of data sources

Signed-off-by: F.N. Claessen <felix@seita.nl>

* feat: only show all versions on sensor charts, and not on asset charts, as a way to balance reflecting the time series in the db (in the sensor chart), and showing what's relevant (in the asset chart)

Signed-off-by: F.N. Claessen <felix@seita.nl>

* Revert "feat: do not create a new source with every change in start_date and end_date"; reason: rather than the start_date (after applying the max-training-period) and end_date, we should be saving the start_date (before applying the max-training-period) and max-training-period.

This reverts commit e8a5a0a96.

* Revert "feat: warn in case forecaster made no forecasts"; reason: the compute method doesn't return any results yet

This reverts commit 73902022c.

* feat: move the override of the original start-date to outside the schema, so that the da... (continued)

Run Details

1374 of 2015 branches covered (68.19%)

Branch coverage included in aggregate %.

10 of 11 new or added lines in 4 files covered. (90.91%)

2 existing lines in 2 files now uncovered.

10114 of 13617 relevant lines covered (74.27%)

5.94 hits per line