You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of today, oemof in general is developed mostly focussing on local energy systems (e.g. with a granularity that allows resolving at least individual urban areas). So, your assumption that single installations play a role is indeed true. In a combined workflow, we rather try to answer the question on which of the available roofs PV installations should be installed (first). For most of the active devs, the overall potential on a global scale is not so much of interest.
As you have noticed, feedinlib has also been used in the openFRED project (and there are models using solph that optimise the national scale energy system). To my knowledge, this is currently not the focus of most of the oemof devs, so I do not really see that someone here would contribute to a more detailed comparison with atlite.
This project seems to have similar use cases as https://github.com/PyPSA/atlite
It would be very cool to have a summary of the similarities and differences on the README page.
Similarities:
Differences
I think the comparison here is also very interesting and would be very cool to compare the performance of the feedinlib towards atlite:
https://github.com/PyPSA/atlite/blob/master/examples/historic-comparison-germany.ipynb
Would be cool if others could complete the list of features/similarities/differences :)
The text was updated successfully, but these errors were encountered: