PowerGenome
PowerGenome copied to clipboard
PowerGenome
A tool to quickly and easily create inputs for power systems models
There is an existing resource in EIA called "Nuclear". Also, there is a resource in ATB called "Nuclear" and the technology detail is "*". I can not tag these resources...
There are so many logs being written to console that it is hard to read or distinguish them. Some might be important, but most are better suited for coming back...
For new technologies specified in the additional_tech.csv file, it appears that PowerGenome defaults to a Cap_size of 1 MW in the output files. Could this be updated to reflect inputs...
Went through all .py files in /powergenome to ensure column names didn't have spaces and used _ instead.
Many dataframe column names were originally set to match GenX requirements, so they don't use the snake case convention that is generally followed elsewhere in the project. These should be...
The straight calculation of investment costs can't handle a WACC of 0. ``` PowerGenome/powergenome/nrelatb.py:738: RuntimeWarning: invalid value encountered in double_scalars / (np.exp(wacc * cap_rec_years) - 1) ``` I encountered this...
The code always clusters existing units, which makes it hard to get all of the units for dispatch modeling. Change settings/code to bypass clustering.
Based on feedback from GenX user, there is an issue when Cap_Size is greater than 1 and Commit = 0.
Related to #63. Is there any need to distinguish fossil resources by build year? I could see a benefit to mapping existing/new-build resources to a common set of names and...
I will be adding new resource cluster data for wind profiles by hub height (100m, 120m, etc) so that larger turbines can be built in later planning periods. This means...
Metadata
Owner
Metadata
A tool to quickly and easily create inputs for power systems models