Turn forecasting algorithm on by default for electricity storage

[mabijkerk]

If capacity is installed for electricity storage technologies, users will not see any behaviour when the default willingness to pay and willingness to accept are both lower than the minimum electricity price in a year. This is quite often the case for blank scenarios.

Users therefore first have to check the hourly electricity price and then determine sensible setting for the willingness to pay and willingness to accept. It can be unclear that these steps are required.

The forecasting algorithm should be therefore turned on by default. Even though its behaviour is less transparent, it will show immediate - and rather optimal - results. Advanced users can then read more about the forecasting algorithm on the documentation, or turn on the price-sensitive behaviour.

Notifying @DorinevanderVlies

[github-actions[bot]]

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.

[mabijkerk]

For optimizing storage to be turned on, the storage decay has to be turned off. See for example the settings_enable_storage_optimisation_energy_flexibility_mv_batteries_electricity input statement:

- query =
  IF(
    EQUALS(USER_INPUT(), 1.0),
    -> {
      UPDATE(V(energy_flexibility_mv_batteries_electricity, storage), decay, 0.0);
      UPDATE(V(energy_flexibility_mv_batteries_electricity, merit_order), subtype, optimizing_storage);
    },
    -> {}
  )

For us to turn on optimizing storage in the starting situation, we would have to set merit_order.subtype to optimizing_storage and storage.decay to 0.0 in the node file. This difficulty in this is that ETSource then no longer knows what the storage decay was originally.

I see three possible solutions to this:

1. Do nothing: leave the price-based mechanism on by default. This does however not solve this issue
2. Put the storage decay value into the input statement: instead of updating the decay to 0.0 when the toggle is turned on, it would update the decay to the actual value when the toggle is turned off. Typically we do however not store node attributes in inputs and it would not be transparant to do so now
3. Assume storage decay is 0.0 for all technologies: this would be a potential (temporary) solution, until storage decay is factored into the forecasting algorithm

@antw I'm interested to know if, in your opinion, I've missed any straightforward solutions.