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
Copy file name to clipboardExpand all lines: docs/sphinx/source/user_guide/storage.rst
+13-10Lines changed: 13 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -60,14 +60,17 @@ In order to work with time series pvlib relies on pandas and pytz to handle
60
60
time and time zones. See "Time and time zones" section for a brief
61
61
introduction.
62
62
63
-
Also, when dealing with storage systems and energy flow, you need to take into
63
+
Also, when dealing with storage systems and power flow, you need to take into
64
64
account the following conventions:
65
65
66
-
- Timestamps are associated to the beginning of the interval
66
+
- Timestamps are associated to the beginning of the interval, as opposed to
67
+
other pvlib series where timestamps are instantaneous
67
68
68
69
- The time series frequency needs to be well defined in the time series
69
70
70
-
- Values represent power throughout the interval, in W
71
+
- Values represent a constant power throughout the interval, in W (power flow
72
+
simplifies calculations if you want to be able to model different time step
73
+
lengths)
71
74
72
75
- Positive values represent power provided by the storage system (i.e.:
73
76
discharging), hence negative values represent power into the storage system
@@ -232,6 +235,9 @@ cycles:
232
235
@suppress
233
236
plt.close()
234
237
238
+
239
+
.. ipython:: python
240
+
235
241
@savefigsam_soc.png
236
242
results["SOC"].plot(ylabel="SOC (%)")
237
243
@suppress
@@ -241,10 +247,7 @@ cycles:
241
247
Power flow
242
248
----------
243
249
244
-
TODO: We are assuming power flow instead of energy flow in this module. Should we change that? It seems SAM works with power flow, maybe for a good reason? Or maybe it is more common? It seems to me like energy flow is more intuitive, but... :shrug: Or maybe we could rename it to "Power balance" instead of "Power flow" (and leave the flow for "Energy flow")
245
-
246
-
With pvlib you can simulate power/energy flow for different scenarios and use
247
-
cases.
250
+
With pvlib you can simulate power flow for different scenarios and use cases.
248
251
249
252
Self consumption
250
253
****************
@@ -302,7 +305,7 @@ self-consumption use case:
302
305
303
306
.. ipython:: python
304
307
305
-
from pvlib.flowimport self_consumption
308
+
from pvlib.powerflowimport self_consumption
306
309
307
310
power_flow = self_consumption(generation, load)
308
311
power_flow.head()
@@ -313,7 +316,7 @@ from grid to load/system:
313
316
314
317
.. ipython:: python
315
318
316
-
from pvlib.flowimport self_consumption
319
+
from pvlib.powerflowimport self_consumption
317
320
318
321
@savefigpower_flow_self_consumption_load.png
319
322
power_flow.groupby(power_flow.index.hour).mean()[["System to load", "Grid to load"]].plot.bar(stacked=True, xlabel="Hour", ylabel="Power (W)", title="Average power flow to load")
@@ -367,7 +370,7 @@ function:
367
370
368
371
.. ipython:: python
369
372
370
-
from pvlib.flowimport self_consumption_ac_battery
373
+
from pvlib.powerflowimport self_consumption_ac_battery
0 commit comments