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

Made changes to tools.costs related to base year and first year of modeling #186

Merged
merged 11 commits into from
Apr 25, 2024

Commits on Apr 24, 2024

  1. Configuration menu
    Copy the full SHA
    8bcef12 View commit details
    Browse the repository at this point in the history
  2. Change default fom_rate to zero

    By default, do not allow for the growth of fixed O&M costs (per vintage) over time
    
    I also had to force the `config.fom_rate` in the equation to a float, otherwise I received this error:
    
    ``ValueError: Integers to negative integer powers are not allowed.``
    measrainsey committed Apr 24, 2024
    Configuration menu
    Copy the full SHA
    cd13b21 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    e127036 View commit details
    Browse the repository at this point in the history
  4. Change decay to start at config.base_year instead of config.y0

    Instead of projecting cost reductions starting at the model start year (`y0`), I've now changed the tool to start projecting at the base year (`base_year`). If `base_year` is greater than `y0` (which is 2020), the base year cost is held constant from `y0` to `base_year`.
    measrainsey committed Apr 24, 2024
    Configuration menu
    Copy the full SHA
    9fa19eb View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    17e1b72 View commit details
    Browse the repository at this point in the history
  6. Edit the cost assumptions for select CCS technologies

    We were seeing instances where the costs of certain CCS technologies were becoming lower than their non-CCS counterparts.
    
    As a fix for now, I am manually changing the input assumptions for these technologies so that:
    1) the CCS and non-CCS counterparts are mapped to the same WEO technologies (and therefore use the same regional differentiation)
    2) the CCS technologies follow the same cost reduction narratives as their non-CCS counterparts
    measrainsey committed Apr 24, 2024
    Configuration menu
    Copy the full SHA
    7a54a9d View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    e43ad94 View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    9781258 View commit details
    Browse the repository at this point in the history
  9. Configuration menu
    Copy the full SHA
    8fc96cd View commit details
    Browse the repository at this point in the history
  10. Add #186 to doc/whatsnew

    measrainsey committed Apr 24, 2024
    Configuration menu
    Copy the full SHA
    c2e1893 View commit details
    Browse the repository at this point in the history
  11. Update doc/whatsnew

    measrainsey committed Apr 24, 2024
    Configuration menu
    Copy the full SHA
    48ccf0b View commit details
    Browse the repository at this point in the history