Demand Response

[DEUCE1957]

This feature request relates to the PR #661 and discussions with @BDonnot. It is meant to act as a roadmap for implementing Demand Response (DR) in Grid2Op. Discussion / suggestions are welcome.

• Fully Flexible Load (current implementation in Demand Response #661), load that can be reduced / increased up to its max load size (meant to represent the 'fuse' size of the load) with no implications for its future use. This is the most flexible option, but not entirely realistic.
• Curtailable Load: Load that can only be decreased, in its discrete form this could also be used to represent load shedding. There is no need to compensate for the reduction later.
• Deferrable Load: Load that can be delayed to a future timestep. Could represent EV charging or Heat Pumps.
• Moveable Load: Load that can be reconnected at a different location, usually to represent topology changes at lower voltages. This can be used to represent the relationship between the TSO and DSO, where the former might request the DSO to 'move' a load to reduce congestion.

[BDonnot]

Hello

Fully Flexible Load (current implementation in #661), load that can be reduced / increased up to its max load size (meant to represent the 'fuse' size of the load) with no implications for its future use. This is the most flexible option, but not entirely realistic.

Your implementation is a first step and a really interesting one :-)

It shows demand response can be implemented with grid2op which is really nice.

What I meant in the PR is that it would be better (in my opinion) to have load shedding modeled as a ratio and not as a MW / MVAr additive amount.

Indeed, having ratio would allow to resolve all the issues I had I believe.

Is that what you meant by "curtailable load" ?

Deferrable load and moveable load are another type of "demand response" and could be implemented later on I think.