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

Make Iteration Structure #12

Closed
Ethan-Russell opened this issue Oct 7, 2022 · 6 comments · Fixed by #86
Closed

Make Iteration Structure #12

Ethan-Russell opened this issue Oct 7, 2022 · 6 comments · Fixed by #86
Assignees
Milestone

Comments

@Ethan-Russell
Copy link
Member

No description provided.

@Ethan-Russell Ethan-Russell added this to the Core Model milestone Oct 7, 2022
@Ethan-Russell
Copy link
Member Author

Ethan-Russell commented Dec 27, 2022

Make 2 examples to prove functionality of this interface:

  • Simple, just iterates once for the config file
  • More complex, does a check of some condition to see if it should iterate, changes something between iterations.

@Ethan-Russell Ethan-Russell self-assigned this Dec 27, 2022
@Ethan-Russell
Copy link
Member Author

resolved by #53

@Ethan-Russell
Copy link
Member Author

The only remaining task would be:

  • Make a sequential iteration.

@Ethan-Russell
Copy link
Member Author

Sequential Simulations:

We need to save a new gen sheet. This should include:

  • Original values for most columns (not scaled by hourly/yearly adjustments)
  • Retirements
  • Keep pcap_built
  • Retire any capacity below a threshold
  • Keep generators that will have been retired with unpaid CAPEX costs.

In MATLAB E4ST, we are using accrual accounting rather than cash accounting.

CAPEX could make sense to do cash accounting. FOM, VOM, and fuel costs are expenses incurred in each year.

We would need to be very careful in multi-year CAPEX and ITC accounting - we couldn't interpolate, but would have to do some sort of cost-averaging across years.

Likewise if we do build rates, we will need to change them depending on how many years we do between simulations.

There is an advantage of accrual accounting for CAPEX - we stop simulating the future. If we count the cost of building new things in the year that they happen, we would be showing the investment cost up front, when much of the benefit is years into the future.

Another idea from Dan - calculate investments as a lump sum. Then apportion the lump-sum investment cost (and lump-sum subsidies) over the years, possibly using a depreciation rate.

@Ethan-Russell
Copy link
Member Author

Leaning towards going forward with accrual accounting to avoid the need to do excessive conversions. The optimization requires us to use accrual accounting CAPEX numbers already. As long as we are doing accrual in our reporting, we need to track past capex independently from what retires.

Would be nice to include lump-sum accounting for CAPEX as an option for results.

@Ethan-Russell
Copy link
Member Author

Also FOM should be changed to be $/MW/yr

This was referenced Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant