Open nesnoj opened 6 months ago
Don't know if I fully understand the question. For django-oemof it is no problem to update profiles on runtime, BUT as we want to use TSAM aggregated timeseries, timeseries have to be aggregated and stored in DP beforehand. We could have multiple DPs prepared and select DP for simulation depending on user settings, if this helps? Don't know how many DPs we need in this case?!
I see, so the only option seems to be adding separate pvground... components incl. profiles to the esys. Which would require adjusting the mapping between backend and sim
You are right - but this would be a small change IMO (one extra line or something). As you can see #117 I have to revisit EE calculation anyway. But @srhbrnds has to rerun TSAM for us as well.
Currently we use
sequences/solar-pv_ground_profile
from oemof datapackage for all PV ground. However, a different timeseries forpv_ground_vertical_bifacial
needs to be integrated (forpv_ground_elevated
the existingsolar-pv_ground_profile
is ok).@henhuy Do we need separate components for PV ground in the esys or can we overlay both timeseries on-the-fly (weighted)?