gijsber

Hi @SouthEndMusic (@visr). I've been think a bit, to limit the complexity and the amount of data to be specified (decisions to be made by the modeller where he doesn't...

Let's try whether allocation can update the setpoints for control instead of setting the control actions itself.

I would recommend 'control_state_id' instead of 'control_id'

sounds good to me

Hi @Huite, I would agree that forward fill would be logical. My assumption is that all predictors for the allocation algorithm would be forward fill including the demand predictor

Primod creates the user demand nodes in database.gpkg and sets a default priority. The priority can be adjusted manually if needed in the gpkg. Once this is set, the resolution...

Priority paramneter is only required when use_allocation=true. If you do not use allocation, the priority parameter can be optional.

if you have a model with allocation active and user demand node without specifying priority, you should get a validation error

Hi @Fati-Mon, Wether it is convenient for the modeller or not is another question, but can you check whether the following provides the result you expect ?: [user_demand.Time( demand=[0.0, 0.0,...

Manual checks needed on: - [ ] adding nodes and edges - [ ] inspect and change the attributes for the tables - [ ] visualize the output in timeseries...