Feat/optional training start

[Flix6x]

Description

• Stop relying on start-date to be set by the user
• Stop relying on end-date to be set by the user
• Start testing the ForecasterParametersSchema directly to validate derivation of timing parameters
• Added changelog item in documentation/changelog.rst

Look & Feel

possible to run forecasting cli command without start_date or end_date:

Examples:

• flexmeasures add forecasts --sensor 20 --start-date "2025-01-01T00:00:00+01"
• flexmeasures add forecasts --sensor 20 --end-date "2025-01-15T00:00:00+01"
• flexmeasures add forecasts --sensor 20

How to test

pytest flexmeasures/data/schemas/tests/test_forecasting.py

...

Further Improvements

• Clarify train-period vs max-training-window in cli.data_add.train_predict_pipeline (and for our first example in forecasting.rst we should mention train-period rather than max-training-window).
• Rename def train_predict_pipeline -> def add_forecast

[read-the-docs-community]

Documentation build overview

📚 flexmeasures | 🛠️ Build #31315929 | 📁 Comparing f53173b against latest (0904e02)

🔍 Preview build

Show files changed (4 files in total): 📝 4 modified | ➕ 0 added | ➖ 0 deleted

File	Status
changelog.html	📝 modified
_autosummary/flexmeasures.api.v3_0.sensors.html	📝 modified
api/v3_0.html	📝 modified
features/forecasting.html	📝 modified

[BelhsanHmida]

The Duration object has a method for shifting with respect to another datetime. But you should try it out for cases like 31 January plus P1M, and 31 March minus P1M. For our use case in these timing parameters we'd probably prefer picking the next or preceding date, respectively, over raising an error.

i created this issue for this: #1970