Add technology specific renewable profiles for different planning horizons #859
Conversation
|
I am not so happy with the build renewable profiles, because this takes rather a long time. Suggestions on how to improve performance here without adding new wildcards are welcome. |
| @@ -335,6 +346,29 @@ | |||
| **resource, | |||
| ) | |||
|
|
|||
| if year_dependent_techs and foresight != "overnight": | |||
| for key, techs in year_dependent_techs.items(): | |||
There was a problem hiding this comment.
year_dependent_techs would always be a dictionary with one entry, right? In this case, it would be better to
remove this for-loop.
Regarding performance, did you check that the number of iterations in this nested for-loop is the desired number? If yes, I don't think there is much you can gain in performance.
There was a problem hiding this comment.
year_dependent_techs would always be a dictionary with one entry, right? In this case, it would be better to
remove this for-loop.
correct, but the key can change depending whether we consider PV or wind to panel or turbine, respectively
Regarding performance, did you check that the number of iterations in this nested for-loop is the desired number?
yes, it only runs the function func once for every technology
|
superseded by #912 |
Closes # (if applicable).
Changes proposed in this Pull Request
Checklist
envs/environment.yaml.config.default.yaml.doc/configtables/*.csv.doc/release_notes.rstis added.