pypsa-usa icon indicating copy to clipboard operation
pypsa-usa copied to clipboard

Nuclear Capital Cost is set to zero

Open trevorb1 opened this issue 1 year ago • 2 comments

Checklist

  • [X] I am using the current master branch
  • [X] I am running on an up-to-date pypsa-usa environment. Update via conda env update -f envs/environment.yaml

The Issue

I think with the switch to getting ATB data from PUDL, something happened with capital costs of nuclear and its not being brought in correctly. This is for a 2020 single period model run with technical retirement (which should not have nuclear as extendable, but in any case it should have correct costs). I have confirmed this is an issue for both electricity only and sector studies

image

Steps To Reproduce

No response

Expected Behavior

No response

Error Message

No response

Anything else?

No response

trevorb1 avatar Oct 28 '24 02:10 trevorb1

Nuclear in the 2024 ATB doesn't start until 2030. We could fix this by setting the minimum technology year to 2030 but that would unnecessarily restrict earlier planning horizon years:

    tech_year = snakemake.wildcards.year
    if int(tech_year) < 2030:
        logger.warning(
            "Minimum cost year supported is 2030, using 2030 expansion costs.",
        )
    years = range(2030, 2051)
    tech_year = min(years, key=lambda x: abs(x - int(tech_year)))

Other solutions could be:

  • query the tech year requested, and if it doesn't exist we search a year higher
  • use an earlier ATB for planning horizons pre 2024

ktehranchi avatar Nov 08 '24 01:11 ktehranchi

I guess your solution of query the tech year requested, and if it doesn't exist we search a year higher matches what we currently do for offshore wind? Can we just do this for nuclear as well?

https://github.com/PyPSA/pypsa-usa/blob/1dadca45acff5932c66e38c6adb1d09094ff7d16/workflow/scripts/build_cost_data.py#L274-L284

trevorb1 avatar Nov 20 '24 20:11 trevorb1