PyPSA / PyPSA/pypsa-usa

Use the VOM/FOM cost data at the build year of the existing power plants

Open
#715 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
148
Forks
55
Avg merge
2d 11h
Merged PRs (30d)
18

Description

Feature Request

Currently in add_electricity.py and add_extracomponents.py, we assign the VOM/FOM cost data of the planning year (say 2050) to the existing power plants. It would be better to change it to the build year (say 2010)? There could be a ~30% difference for gas power plants.

    attach_conventional_generators(
        n,
        costs,
        plants,
        conventional_carriers,
        extendable_carriers,
        params.conventional,
        renewable_carriers,
        conventional_inputs,
        unit_commitment=params.conventional["unit_commitment"],
        fuel_price=None,  # update fuel prices later
    )
    if snakemake.params.retirement == "economic":
        economic_retirement_gens = set(elec_config.get("conventional_carriers", None))
        split_retirement_gens(
            n,
            costs_dict[n.investment_periods[0]],
            economic_retirement_gens,
            economic=True,
        )
Suggested Solution

No response

Additional Info

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with add_electricity.py and add_extracomponents.py, then trace attach_conventional_generators and the economic-retirement split_retirement_gens call. Determine how existing plants' build years are represented and update the cost lookup so VOM/FOM uses those years rather than the planning year; done when both paths consistently apply build-year costs.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.