Some points to pay attention during RTC-Tools intergration into FEWS.
Forecast date
For rtcRTC-toolsTools, the start date startDate is the earliest timestamp present in a timeseries. This is possibly historical data. forecast date The forecastDate is the point from which the optimization/simulation starts. In most cases the start data startDate and the forecast date overlap forecastDate are equal. However, we have to leave the flexibility for the existence of historical information. (Say; say, for e.g.example, that the decision that you take now depends on what happened in the last 4 hours). In Delft-FEWS the users have a different concept for forecast date; the forecast date of a historical simulation typically is the end time of the simulation. In order to be able to trigger historical runsuse RTC-Tools for historical data too (i.e. data before the forecast date), without confusing the Delft-FEWS user the following be done is that , one can adapt usage of the forecastDate in the python Python script of the model , the forecast date is overwritten such that is becomes the start dateby overwriting the forecastDate with the startDate (therefore, bypassing the forecast date information from Delft-FEWS). That can be done as followingfollows in the pre() method:
def pre(self):
super().pre()
self.io.reference_datetime = self.timeseries_import.start_datetime
...
...