-
Notifications
You must be signed in to change notification settings - Fork 8
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
Remove remains of the forecast feature #645
Conversation
a154f8f
to
0c196c0
Compare
0e3ca6d
to
b925269
Compare
* Move broadcast_techs out of quantities module * Update _inner_split * Fix trade model * Fix constraints tests * Fix demand_share tests * Fix quantities tests * Fix trade tests * Fix adhoc model * Rename broadcast_techs to broadcast_over_assets * Better docstring, rename argument * Delete filter_with_template * Remove `broadcast_over_assets` from `capacity_in_use` * Fix trade tests * Edit TODO * Remove foresight parameter * Update settings and documentation * Temporarily suppress test * Fix carbon budget framework * Revert change to settings * Update settings and documentation * Revert change to settings * Update results * Small changes to fix tests * Add warning about deprecated parameter * Clarify log messages * Better final message
6e19f4d
to
64b088e
Compare
64b088e
to
97929b6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I see there are no changes to any of the output files, so I guess forecast
was totally useless, right? Was forecast
the same as foresight
? Also, when we talk about investment year
, is that the current simulation year or the next one?
I think "forecast" and "foresight" mean the same thing (i.e. allowing agents to look forward into the future), although as long as I've been working on MUSE the I'm guessing maybe
The investment year is the next one on from the current year. E.g. agents in 2020 will make investments for 2025 based on information (demand, prices, technology parameters) they have about 2025 I actually think "current year" is a bit misleading as MUSE is really simulating a time window each iteration (i.e. 2020 to 2025), and has fully solved the system for that whole time window by the end of the iteration (not just the first/"current" year), so maybe "base year" or "planning year" would be clearer In MUSE2 this is simpler - only the current year, where agents plan and make investments in the same year |
This was originally used to allow agents to look beyond the investment year, but it wasn't working properly and I've had permission from Adam to remove this feature to help simplify the code. Most of the work was done in #631, but some remnants still remained which I couldn't get rid of until #657 as
agent.forecast_year
was being used in the outputs module.