You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/metrix.md
+20-2
Original file line number
Diff line number
Diff line change
@@ -233,14 +233,18 @@ If no generator is configured to be managed by Metrix, then all generators are i
233
233
Note that Metrix will take into account the Pmin and Pmax values of generators (which can be modified through the mapping script).
234
234
In the same way than most parameters, the value can be a fixed integer/float or a time series name.
235
235
236
+
Doctrine costs can be defined for postprocessing purpose (up and down redispatching and costs timeseries)
237
+
236
238
The syntax to define a managed generator is:
237
239
238
240
```groovy
239
241
generator(id) { // id of the generator which will be managed by Metrix
240
242
adequacyDownCosts 'ts_cost_down' // Cost of ramping down for the adequacy phase (here a time series name is used)
241
243
adequacyUpCosts 'ts_cost_up' // Cost of ramping up for the adequacy phase (here a time series name is used)
242
-
redispatchingDownCosts 10 // Cost of ramping down (preventive) for the OPF simulation (here a fixed value is used)
243
-
redispatchingUpCosts 100 // Cost of ramping up (preventive) for the OPF simulation (here a fixed value is used)
244
+
redispatchingDownCosts 10 // Cost of ramping down for the OPF simulation (here a fixed value is used)
245
+
redispatchingUpCosts 100 // Cost of ramping up for the OPF simulation (here a fixed value is used)
246
+
redispatchingDownDoctrineCosts 10 // Doctrine cost of ramping down for the OPF simulation (fixed value or time series name)
247
+
redispatchingUpDoctrineCosts 100 // Doctrine cost of ramping up for the OPF simulation (fixed value or time series name)
244
248
onContingencies 'a','b' // list of contingencies where Metrix can use this generator in (curative) remedial actions
245
249
}
246
250
```
@@ -301,6 +305,8 @@ for (g in network.generators) {
301
305
302
306
Similarly to generators, loads can be adjusted in the OPF simulation (in preventive and curative mode), but only as a decrease. The cost in preventive action is fixed (default 13000 €/MWh) and can be modified in the global parameters with the keyword `lossOfLoadCost`. We can also override this value for specific loads. The specified cost will automatically be weighted with the contingency probability (default : 10^-3). We can also limit the maximum percentage of load shedding (in preventive and curative mode).
303
307
308
+
Doctrine costs can be defined for postprocessing purpose (load shedding costs timeseries)
309
+
304
310
Here is the corresponding syntax:
305
311
```groovy
306
312
load(load_id) {
@@ -309,6 +315,8 @@ load(load_id) {
309
315
curativeSheddingPercentage 10 // optional shedding max percentage for curative actions
310
316
curativeSheddingCost 40 // optional cost for curative shedding action
311
317
onContingencies 'a', 'b' // optional contingency upon which curative action are operated
318
+
preventiveSheddingDoctrineCost 10000 // doctrine cost for preventive shedding action (fixed value or time series name)
319
+
curativeSheddingDoctrineCost 'ts_doctrine_cost' // doctrine cost for curative shedding action (fixed value or time series name)
312
320
}
313
321
```
314
322
@@ -348,6 +356,16 @@ Control types:
348
356
- `OPTIMIZED`: can optimize the p0 target in adequacy phase and preventive (and curative if contingencies were defined)
349
357
- `FIXED`: the target p0 is fixed
350
358
359
+
### Losses
360
+
361
+
Doctrine costs can be defined for postprocessing purpose (global losses cost time series)
362
+
363
+
```groovy
364
+
losses() {
365
+
costs 'ts_losses_cost' // Losses cost (fixed value or time series name)
366
+
}
367
+
```
368
+
351
369
### Monitored sections
352
370
353
371
It is possible to monitor a constraint on a weighted sum of a set of branch flows:
0 commit comments