Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize NREL mappings #122

Open
trevorb1 opened this issue Feb 4, 2022 · 1 comment
Open

Standardize NREL mappings #122

trevorb1 opened this issue Feb 4, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@trevorb1
Copy link
Member

trevorb1 commented Feb 4, 2022

We use the NREL dataset in multiple places throughout the code base (such as in costs and capacity factor). We include a mapping dictionary to match our technology naming to NREL technology scenarios...

technology = {
'COA':['Coal', 'IGCCHighCF'] ,
'COC':['Coal', 'CCS30HighCF'] ,
'HYD':['Hydropower', 'NPD4'] ,
'CCG': ['NaturalGas','CCHighCF'],
'CTG': ['NaturalGas','CTHighCF'],
'WND': ['LandbasedWind','LTRG4'],
'SPV': ['UtilityPV','KansasCity'],
'URN': ['Nuclear'],
'BIO': ['Biopower','Dedicated'],
}

We should create a solution where we specify this at a global level (such as the config.yaml file, but Im not sure it really belongs there), so they never become mismatched.

@trevorb1 trevorb1 added the enhancement New feature or request label Feb 4, 2022
@trevorb1
Copy link
Member Author

trevorb1 commented Feb 4, 2022

Oh I just saw we have constants in the functions.py file ! May want to move them to a constants.py file or something

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant