I added three source gpkg files from https://maps.nrel.gov/psh to account for three durations of PHS (8hr, 10hr, 12hr). Each duration has a specific CAPEX and potential MW. The files are now uploaded in repo_data/psh but feel free to move to anywhere appropriate.
In add_extra_components.py, I now added the codes to add PHS to storageunits, if users select to add in the ["extendable_carriers"]["StorageUnit"]. The individual PHS resources are clustered based on the region clusters. Note that the annualized CAPEX is recalculated based on resource quality in the function.
One potential issue is, now in each cluster, there would be multiple classes of PHS since the CAPEX differences. The future improvement could be to re-aggregate all PHS classes for each cluster after solving.
Please feel free to ask me if there is any confusion!
Looks great! I think its a good thing that we have multiple classes of PHS after the clustering. We can just make sure to label them correctly in the results plots.
Closes #320.
Changes proposed in this Pull Request
I added three source gpkg files from https://maps.nrel.gov/psh to account for three durations of PHS (8hr, 10hr, 12hr). Each duration has a specific CAPEX and potential MW. The files are now uploaded in
repo_data/psh
but feel free to move to anywhere appropriate.In
add_extra_components.py
, I now added the codes to add PHS to storageunits, if users select to add in the ["extendable_carriers"]["StorageUnit"]. The individual PHS resources are clustered based on the region clusters. Note that the annualized CAPEX is recalculated based on resource quality in the function.One potential issue is, now in each cluster, there would be multiple classes of PHS since the CAPEX differences. The future improvement could be to re-aggregate all PHS classes for each cluster after solving.
Please feel free to ask me if there is any confusion!