-
Notifications
You must be signed in to change notification settings - Fork 30
Myopic Implementation #518
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
Comments
Two continuing issues in myopic approach (all in
The only solution I've found to this is to re-add in a
Relevant code in https://github.com/lfreese/pypsa-usa/tree/issue-518 |
Problem 2 above was solved and has been pushed. Needed to be: |
@ktehranchi have you pushed your changes to the opts (the SAFE/SAFER) ones you discussed? If so, I'll pull those and add the sns_horizon to them so that they work with myopic. If those are still being developed, I think this might be ready for a pull request. It doesn't do quite as well in the full year snapshot recreating the perfect foresight as it did in a 2-3 day snapshot, so I'm not sure if we feel like that should preclude pulling this, or if that's reasonable. Figures here show examples of the difference in production and capacity additions between a 2030 myopic and 2030 perfect foresight. Config file attached. The key gaps in production are coming in with coal, OCGT, and CCGT, for example: But the profiles are looking quite similar. |
Feature Request
Develop a myopic implementation of foresight rather than perfect.
Suggested Solution
Solution is in progress, modifying planning_horizons
Additional Info
No response
The text was updated successfully, but these errors were encountered: