Hydro clustering - UC CR 13 Bis #1164
hugo-antoine-rtei
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Work In Progress - I will add to this discussion in the coming days
The implementation of a clustered approach to hydro is key in order to:
Logic of the Change
The objective is to allow the definition of multiple reservoirs on a single area and have one single aggregated unit connected to each reservoir – no connected reservoirs at this stage, one reservoir per Hydro Valley. No time-series generation will be possible for hydro clusters. The hydro heuristic will be applied on each cluster separately (instead of each area, it will be each cluster).
1 - UI Change
1.1 - Inputs
The hydro clusters should be defined similarly to the Renewable and Thermal clusters. For ease of development and to ensure compatibility, the hydro clusters will be added as a new window inside Antares:
Note: This approach should probably be revisited down the road, with a switch like it was done for the renewable clusters.
Inside of that window, you will find on the left the list of each area, like for the renewable clusters or thermal windows, and on the right, two general tabs will be available, containing data applicable for all hydro clusters:
area_1.cluster_1 area_1.cluster_2 area_2.cluster_1 area_2.cluster_2
load_area_1 1 0.5 0 0
load_area_2 0 0.5 1 1
load_area_3 0 0 0 0
load_area_4 0 0 0 0
Once a hydro cluster is selected, the following tabs are available in the bottom of the Hydro Cluster List tab:
Note: Could be used in the future when we define more than one turbine unit per hydro cluster.
The following tabs are intentionally not re-used, as generation of inflows time-series for hydro clusters will not be available:
1.2 - Outputs
The logic used for thermal and renewable clusters can also be re-used. A separate tab, “Hydro clusters” will be created, to hold the “H. ROR”, “H. STOR”, “H. PUMP”, “H. LEV”, “H. INFL”, “H. OVFL”, “H. VAL”, and “H. COST” columns for each hydro cluster.
2 - File Storage
2.1 - Input files
Current way of storing data:
/hydro
⌞ allocation
⌞ .ini
⌞ common
⌞ capacity
⌞ creditmodulations_.txt
⌞ inflowPattern_.txt
⌞maxpower_.txt
⌞ reservoir_.txt
⌞ waterValue_.txt
⌞ prepro
Proposition to add a new folder inside input: hydroclusters:
/hydroclusters
Beta Was this translation helpful? Give feedback.
All reactions