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
Benchmarks: new GenX LP benchmarks without UC (#131)
based on the GenX benchmarks on the jump-highs
platform, I added here a few LP GenX benchmarks removing Unit
commitment.
---------
Co-authored-by: Siddharth Krishna <siddharth-krishna@users.noreply.github.com>
Short description: This is a one-year example which contains 15 zones. This example includes transmission expansion, a CO2 emissions constraint and unit commitment for conventional generators.
40
+
# genx-elec_trex_co2_uc:
41
+
# Short description: This is a one-year example which contains 15 zones. This example includes transmission expansion, a CO2 emissions constraint and unit commitment for conventional generators.
42
+
# Model name: GenX
43
+
# Version:
44
+
# Technique: MILP
45
+
# Kind of problem: Infrastructure
46
+
# Sectors: Power
47
+
# Time horizon: Single period (1 year)
48
+
# MILP features: Unit commitment
49
+
# Sizes:
50
+
# - Name: 15-168h
51
+
# Size: R
52
+
# URL:
53
+
# Temporal resolution: 168
54
+
# Spatial resolution: 15
55
+
# N. of constraints:
56
+
# N. of continuous variables:
57
+
# N. of integer variables:
58
+
# N. of binary variables:
59
+
genx-elec_trex_uc:
60
+
Short description: This is 30 days example which contains 15 zones. This example includes transmission expansion and unit commitment for conventional generators.
Short description: This is a one-year example which contains 15 zones. This example includes transmission expansion and unit commitment for conventional generators.
Short description: This is a one-year example which contains 15 zones. This example includes a CO2 emissions constraint and unit commitment for conventional generators.
# Short description: This is a one-year example which contains 15 zones. This example includes a CO2 emissions constraint and unit commitment for conventional generators.
99
+
# Model name: GenX
100
+
# Version:
101
+
# Technique: MILP
102
+
# Kind of problem: Infrastructure
103
+
# Sectors: Power
104
+
# Time horizon: Single period (1 year)
105
+
# MILP features: Unit commitment
106
+
# Sizes:
107
+
# - Name: 15-168h
108
+
# Size: R
109
+
# URL:
110
+
# Temporal resolution: 168
111
+
# Spatial resolution: 15
112
+
# N. of constraints:
113
+
# N. of continuous variables:
114
+
# N. of integer variables:
115
+
# N. of binary variables:
116
+
# genx-15-zones_elec_uc:
117
+
# Short description: This is a one-year example which contains 15 zones. This example includes unit commitment for conventional generators.
Copy file name to clipboardExpand all lines: benchmarks/genx-extended/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,5 +12,5 @@
12
12
The abovementioned workflow takes advantage of the content of the `GenX.jl/case_for_oet/TDR_Results` folder for inputs clustered according to a time resolution of 168 h (as reported in `GenX.jl/case_for_oet/settings/time_domain_reduction_settings.yml`)
13
13
Whenever the temporal resolution of the model requires changes one should adopt a simple workflow:
14
14
- If already present, the `TDR_Results` folder should be deleted (or its name should be modified)
15
-
- The TimestepsPerRepPeriod entry in `GenX.jl/case_for_oet/settings/time_domain_reduction_settings.yml` should be adjusted according to the desired temporal resolution (e.g. 1 for hourly resolution, 24 for daily resolution, 168 for weekly resolution, etc.). For more information, follow the [GenX project Guide](https://genxproject.github.io/GenX.jl/dev/User_Guide/TDR_input/)
15
+
- The TimestepsPerRepPeriod entry in `GenX.jl/case_for_oet/settings/time_domain_reduction_settings.yml` should be adjusted according to the desired temporal resolution (e.g. 1 for hourly resolution, 24 for daily resolution - the `genx-elec_trex_uc` benchmark only runs with such resolution - 168 for weekly resolution, etc.). For more information, follow the [GenX project Guide](https://genxproject.github.io/GenX.jl/dev/User_Guide/TDR_input/)
16
16
- The model can be run using again and a new `TDR_Results` folder will generated according to the new temporal resolution
0 commit comments