Decide where producer & consumer parameters e.g. priority for simulator ESDL will be defined

[lfse-slafleur]

Options:

• In ESDL
• In params_dict which is submitted as part of the workflow (Config options outside of ESDL)

Sam is currently investigating with Edwin.

[edwinmatthijssen]

Can you maybe write something about what kind of options you want when specifying a priority? Just one or two slides with some examples.

Should there a priority list? Can assets have the same priority? Is a priority a number? Can priorities be zero or negative (specifying not to take this asset into account for the time being)? And so on.

I think it relates to some of the things being discussed with @jimrojerTNO and @ewoudwerkman about MESIDO

[lfse-slafleur]

@samvanderzwan

[edwinmatthijssen]

I was supposing Sam would already receive it as being assigned to this issue? Doesn't that work like that?

[lfse-slafleur]

I was supposing Sam would already receive it as being assigned to this issue? Doesn't that work like that?

It should be! But considering I created the ticket I thought it may not have been very explicit to whom the question was directed so I thought I would make it explicit.

[jimrojerTNO]

Previously we decided to use marginal cost as the parameter for priority.

[edwinmatthijssen]

But this can change in future, or not? And "in future" could be "now" if there are more specific requirements for this. @jimrojerTNO, I don't fully understand what you mean with your comment. Are you proposing Sam should also just use marginal costs?

[jimrojerTNO]

Ewoud previously suggested that we use marginal cost for priority, my logic would be to be consistent with that and use it also for the simulator. If we decide to change it, we should also change it at our side.