Automatic estimation of availability - Autoschedule

The autoschedule action is intended for series that lack information about availability. This action is run by ConsoleUI and more on the arguments that can be passed to the ConsoleUI can be found in the documentation for ConsoleUI. The availability that is missing can reflect a monotonic increase of production capacity, e.g. the total wind power production for a region or country. Often, the exact installed capacity for such a series at each specific point in time is unknown. The autoschedule action automatically estimates the historical installed capacity and current maximum based on the historical measured values and saves the past periods with lower maximum capacity than the current as scheduled items in the schedule. The program first fetches the current maximum value from the models connected to the series and the end date for the last existing scheduled item for the series. It then runs through the historical measured values from this end date up to now and search for any values exceeding the current maximum. When it finds a higher value, the previous period together with the previous maximum is stored as a scheduled item. When all historic data is checked, the result will be a list of scheduled items together with a new maximum value which will be updated in all models connected to the series. If the model has any saved regression results in csv-files, these will be rescaled according to the ratio between the old and new maximum in case the /rescale parameter is set to true. The action can take a number of limits as parameter. These can be set in order to prevent the program from changing the maximum capacity due to erroneous spikes in the measured data. The limits are set as the maximum allowed increase and can be specified in both absolute as well as relative increase. If the limits set for individual series are exceeded, the changes are blocked and an error message is written to the status log data base. If certain spikes are instead to be ignored instead, set the /ignorevalues-parameter to some positive integer, reflecting the maximum number of ignored consecutive values. If the limits for the total increase of maximum capacity are exceeded a warning message is written.