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

Separate period_realized #58

Closed
jkiviluo opened this issue May 27, 2023 · 1 comment
Closed

Separate period_realized #58

jkiviluo opened this issue May 27, 2023 · 1 comment
Assignees
Labels
bug Something isn't working high priority Things to do as soon as possible

Comments

@jkiviluo
Copy link
Member

jkiviluo commented May 27, 2023

Period_realized needs to distinguish between investment solves and dispatch solves. Investment decisions are to be realized from investment solves and other decisions from the dispatch solves (when dispatch solve is performed). There needs to be consideration of other 'realizations' too, like using storage value from higher level solve in a lower level solve.

jkiviluo added a commit that referenced this issue May 27, 2023
When using investments with a horizon of investments that were to be overwritten by the following solves, those investments in the horizon were included as invested capacity in the next solve. This is now removed. However, an issue remains when this is used in conjunction with dispatch runs, since it depends on realized_periods (#58).
@jkiviluo jkiviluo added the bug Something isn't working label May 27, 2023
@jkiviluo jkiviluo self-assigned this Jun 1, 2023
@jkiviluo jkiviluo changed the title Seperate period_realized Separate period_realized Jun 2, 2023
@jkiviluo jkiviluo added the high priority Things to do as soon as possible label Jun 11, 2023
@jkiviluo
Copy link
Member Author

This has been implemented with 10d7e48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working high priority Things to do as soon as possible
Projects
None yet
Development

No branches or pull requests

1 participant