-
-
Notifications
You must be signed in to change notification settings - Fork 48
Example behavior in a week
Jeroen ter Heerdt edited this page Jun 4, 2020
·
1 revision
This page provides insight into how this component should behave in certain weather conditions. With this you should be able to do a sanity check against your configuration and make sure everything is working correctly.
The scenario is as follows - we will look at several days, the precipitation and evapotranspiration for those days, the effects on the various calculations that this component makes and whether or not irrigation should be triggered. Note the values for precipitation and evapotranspiration are made up and are not representative of any real-life situation.
Initially, the bucket=0
, so the daily adjusted run time (ART)=0
as well.
-
P
: Precipitation -
Et
:Evapotranspiration -
Np
= Netto Precipitation (=P-Et
) -
B
= Bucket during the day -
D
= Daily Adjusted Run Time -
Bu
= Bucket after update (=B+Np
) -
Du
= Daily Adjusted Run Time after update (seconds)`
Day | P |
Et |
Np |
B |
D |
Bu |
Du |
Irrigation required |
---|---|---|---|---|---|---|---|---|
1 | 0.5 |
0.1 |
0.4 |
0 |
0 |
0.4 |
0 |
No |
2 | 0 |
0.6 |
-0.6 |
0.40 |
0 |
-0.2 |
180 |
Yes - bucket should be reset afterwards |
3 | 1 |
0.2 |
0.8 |
0 (reset) |
0 |
0.8 |
0 |
No |
4 | 0.2 |
0.4 |
-0.2 |
0.8 |
0 |
0.6 |
0 |
No |
5 | 0 |
1.5 |
-1.5 |
0.6 |
0 |
-0.9 |
600 |
Yes - bucket should be reset afterwards |
6 | 0 |
0.4 |
-0.4 |
0 (reset) |
0 |
-0.4 |
300 |
Yes - bucket should be reset afterwards |
7 | 0.5 |
0.2 |
0.3 |
0 (reset) |
0 |
0.3 |
0 |
No |