|
| 1 | +# # [Multi-period OPF](@id mpopf_demo) |
| 2 | + |
| 3 | +# The multi-period (MP) OPF can also be modeled in ExaModelsPower with a number of user-specified adjustments, including storage. |
| 4 | + |
| 5 | +# Some of the models in this portion of the tutorial involve using external files. While we provide the necessary code to access these additional files, you may view them __[here](https://github.com/mit-shin-group/multi-period-opf-data)__ as well. |
| 6 | +# We will start with the simplest way to model the MPOPF, which also does not require the user to have any data already downloaded. Instead, the user specifies a demand curve for the system. The demand curve is a vector of ratios from 0 to 1 which indicate the scaling of demand compared to the demand indicated by the static OPF file. In this model of the MPOPF, every consuming bus has the same scaling in power demand for each point in time. A corrective action ratio, which limits the ramp rate of generators, can also be inputted. It is set to 0.1 as a default. The adjustable coordinate system and backend that were present for the static OPF are also available for all MPOPF models. |
| 7 | +using ExaModelsPower, CUDA, MadNLP, MadNLPGPU, ExaModels |
| 8 | +model, vars, cons = mpopf_model( |
| 9 | + "pglib_opf_case118_ieee.m", # static network data |
| 10 | + [.64, .60, .58, .56, .56, .58, .64, .76, .87, .95, .99, 1.0, .99, 1.0, 1.0, |
| 11 | + .97, .96, .96, .93, .92, .92, .93, .87, .72, .64], #Demand curve |
| 12 | + backend = CUDABackend(), |
| 13 | + corrective_action_ratio = 0.3 |
| 14 | +) |
| 15 | +result = madnlp(model; tol=1e-6) |
| 16 | + |
| 17 | +# If the user would like to provide more complex demand profiles, they can provide their own input files. The number of rows in each input file should match the number of buses in the static OPF datafile, and the number of columns will dictate the number of time periods in the MP model. |
| 18 | +# First, download the example load profile datafiles. |
| 19 | +using Downloads |
| 20 | + |
| 21 | +#Define URLs for Pd and Qd data files (raw or raw GitHub links) |
| 22 | +pd_url = "https://raw.githubusercontent.com/mit-shin-group/multi-period-opf-data/refs/heads/main/halfhour_30.Pd" |
| 23 | +qd_url = "https://raw.githubusercontent.com/mit-shin-group/multi-period-opf-data/refs/heads/main/halfhour_30.Qd" |
| 24 | + |
| 25 | +#Define local paths to temporarily store the files |
| 26 | +pd_file = "halfhour_30.Pd" |
| 27 | +qd_file = "halfhour_30.Qd" |
| 28 | + |
| 29 | +#Download the files if they don't already exist |
| 30 | +if !isfile(pd_file) |
| 31 | + Downloads.download(pd_url, pd_file) |
| 32 | +end |
| 33 | + |
| 34 | +if !isfile(qd_file) |
| 35 | + Downloads.download(qd_url, qd_file); |
| 36 | +end |
| 37 | + |
| 38 | +# Next, build the MPOPF model, providing the dynamic load data instead of a demand curve as input. |
| 39 | +#Run your model |
| 40 | +model, vars, cons = mpopf_model( |
| 41 | + "pglib_opf_case30_ieee.m", # static network data (assumed local or already handled) |
| 42 | + pd_file, # dynamic load data (Pd) |
| 43 | + qd_file; # dynamic load data (Qd) |
| 44 | + backend = CUDABackend() |
| 45 | +) |
| 46 | + |
| 47 | +#Solve |
| 48 | +result = madnlp(model; tol=1e-6) |
| 49 | + |
| 50 | +## MPOPF with storage |
| 51 | +# The MPOPF model can also be constructed with storage considerations. We model storage using the model proposed in __[Geth, Coffrin, Fobes 2020](https://arxiv.org/pdf/2004.14768)__. This requires inputting a modified datafile containing storage parameters. When modeling MPOPF with storage, all of the aforementioned tuneable parameters are still available. We also allow the user to specify whether or not to model the charging/discharging complementarity constraint. This is set to false by default to avoid potential numerical error. |
| 52 | + |
| 53 | +#First, we download the modified datafile with storage parameters included. |
| 54 | +#Define URL for the main datafile |
| 55 | +stor_url = "https://raw.githubusercontent.com/mit-shin-group/multi-period-opf-data/refs/heads/main/pglib_opf_case30_ieee_mod.m" |
| 56 | + |
| 57 | +#Define local path to temporarily store the file |
| 58 | +stor_file = "pglib_opf_case30_ieee_mod.m" |
| 59 | + |
| 60 | +#Download the file if it doesn't already exist |
| 61 | +if !isfile(stor_file) |
| 62 | + Downloads.download(stor_url, stor_file); |
| 63 | +end |
| 64 | + |
| 65 | +# Generate the model with your modified datafile. If the datafile contains storage parameters, ExaModelsPower will automatically recognize it and include the additional necessary constraints. |
| 66 | +model, vars, cons = mpopf_model( |
| 67 | + stor_file, # static network data with storage parameters |
| 68 | + pd_file, # dynamic load data (Pd) |
| 69 | + qd_file; # dynamic load data (Qd) |
| 70 | + backend = CUDABackend(), |
| 71 | + storage_complementarity_constraint = false |
| 72 | +) |
| 73 | +result = madnlp(model; tol=1e-6) |
| 74 | +result.objective |
| 75 | + |
| 76 | +# ExaModelsPower also provides a secondary option to avoid dealing with complementarity constraints. The user can specify a function that computesloss in battery level as a smooth function of discharge rate and the storage devices thermal rating parameter. We provide an arbitrary example function to demonstrate the modeling capability. |
| 77 | + |
| 78 | +function example_function(d, srating) |
| 79 | + return d + .2/srating*d^2 |
| 80 | +end; |
| 81 | + |
| 82 | +# ExaModelsPower will automatically adjust the necessary constraints if one of the inputs provided is a function. |
| 83 | +model, vars, cons = mpopf_model( |
| 84 | + stor_file, # static network data with storage parameters |
| 85 | + pd_file, # dynamic load data (Pd) |
| 86 | + qd_file, # dynamic load data (Qd) |
| 87 | + example_function; # discharge function |
| 88 | + backend = CUDABackend(), |
| 89 | + storage_complementarity_constraint = false |
| 90 | +) |
| 91 | +result = madnlp(model; tol=1e-6) |
| 92 | +result.objective |
| 93 | + |
| 94 | +# Despite the example discharge function being generated somewhat arbitrarily, the resultant objective values remain quite close for both the smooth and piecewise charge/discharge functions. |
| 95 | + |
0 commit comments