Irrigation planning system
Through a simulated irrigation planning system, combined with soil moisture simulation and planning optimization, an irrigation plan that minimizes water loss is generated, which solves the water loss and efficiency problems in the existing irrigation planning and achieves efficient irrigation management.
Patent Information
- Application Number
- CN202010767479.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-09-05
- Filing Date
- 2020-08-03
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2040-08-03
AI Technical Summary
Existing irrigation planning methods cannot effectively reduce water-related losses, such as the waste of water penetration into non-root areas, pesticides and fertilizers, and energy waste, and rely on inaccurate environmental data input.
Using a simulation-based irrigation planning system, combined with a soil moisture simulator and planning optimizer, generate an irrigation plan that minimizes water loss through an iterative process, considering the interaction between surface, vegetation and atmosphere, and optimizing according to customized constraints and weather forecasts Watering rate and time.
It realizes minimizing water penetration within the depth layer of the root area, reducing water-related losses, improving irrigation efficiency, and meeting user-specific irrigation needs and constraints.
Smart Images

Figure CN112446580B_ABST
Abstract
Description
Background Art
[0001] The present disclosure relates to irrigation, and more particularly, to developing irrigation plans.
[0002] Irrigation can include providing water to various types of vegetation. Irrigation planning can include determining the amount of water to be provided and the intervals at which the water is to be provided. Summary of the invention
[0003] According to an embodiment of the present disclosure, a computer-implemented method may include: obtaining irrigation data by an irrigation planning system. The method may further include obtaining a first watering rate set by the irrigation planning system. The method may further include generating a first soil moisture estimate set and a second soil moisture estimate set by the irrigation planning system. The first soil moisture estimate set and the second soil moisture estimate set are based at least in part on the irrigation data. The method may further include obtaining a custom constraint by the irrigation planning system. The method may further include making a first determination by the irrigation planning system that the first soil moisture estimate set satisfies the custom constraint. The method may further include obtaining a humidity reference value by the irrigation planning system in response to making the first determination. The humidity reference value may be based at least in part on the second soil moisture estimate set. The method may further include making a second determination by the irrigation planning system that the humidity reference value exceeds a first threshold. The method may further include generating an irrigation plan by the irrigation planning system in response to making the second determination.
[0004] The present invention also includes systems and computer program products corresponding to the above methods.
[0005] The above summary is not intended to describe each illustrated embodiment or every implementation of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The accompanying drawings included in this application are incorporated into the specification and form a part of the specification. They illustrate embodiments of the present disclosure and are used to explain the principles of the present disclosure together with the specification. The accompanying drawings are only illustrations of certain embodiments and do not limit the present disclosure.
[0007] Figure 1 An example computing environment with an irrigation scheduling system according to an embodiment of the present disclosure is depicted.
[0008] Figure 2 A flow chart of an example method for generating an irrigation plan according to an embodiment of the present disclosure is depicted.
[0009] Figure 3 An example system block diagram of an irrigation planning system according to an embodiment of the present disclosure is depicted.
[0010] Figure 4Depicted are representative major components of a computer system that may be used in accordance with embodiments of the present disclosure.
[0011] Figure 5 A cloud computing environment according to an embodiment of the present disclosure is depicted.
[0012] Figure 6 Abstract model layers according to an embodiment of the present disclosure are depicted.
[0013] Although the present invention is subject to various modifications and alternative forms, the details thereof have been shown in the drawings by way of example and will be described in detail. However, it should be understood that it is not intended to limit the present invention to the specific embodiments described. On the contrary, it is intended to cover all modifications, equivalents and alternative forms that fall within the spirit and scope of the present invention. DETAILED DESCRIPTION
[0014] Aspects of the present disclosure relate to irrigation planning; more particularly, aspects relate to customized, efficient irrigation planning. Although the present disclosure is not necessarily limited to such applications, various aspects of the present disclosure may be understood by discussing various examples using this context.
[0015] High irrigation costs and limited access to freshwater resources can provide a strong incentive to irrigate efficiently. In addition, inefficient irrigation can result in various water-related losses, such as unnecessary water infiltration beyond the root zone depth layer (e.g., the area below the surface from which plants can absorb water from the soil); leaching of pesticides, fertilizers, and herbicides; and energy wasted on irrigation. (In this disclosure, "surface" can refer to the surface of land or soil components on which vegetation is planted.) Irrigation plans can specify the amount of water to be allocated to vegetation and the time intervals for such allocations; however, such plans may not be designed to minimize water-related losses. In addition, the effectiveness of methods used to generate irrigation plans may be limited by data inputs and / or approximations that do not accurately represent relevant environmental conditions.
[0016] To address these and other issues, embodiments of the present disclosure include an irrigation planning system that generates an irrigation plan that can minimize water-related losses. In some embodiments, an irrigation plan may include one or more of a watering rate set, an irrigation time period, one or more irrigation time increments, an irrigation date, and an irrigation time of day. In some embodiments, an irrigation planning system may generate an irrigation plan using simulation-based optimization. In some embodiments, an irrigation planning system may consider the interaction between surfaces, vegetation, and the atmosphere when generating an irrigation plan. For example, in some embodiments, an irrigation planning system may include a soil moisture simulator that may generate a soil moisture estimate based at least in part on inputs such as precipitation rate, ambient temperature, relative humidity, and solar radiation. In some embodiments, an irrigation planning system may include a planning optimizer that may generate an irrigation plan based at least in part on a soil moisture estimate from a soil moisture simulator and a custom constraint set. (In the present disclosure, a "set" may include one or more items; therefore, a "set" of custom constraints may include one or more custom constraints). In some embodiments, a custom constraint set may include one or more user-specific restrictions. For example, in some embodiments, a user of an irrigation planning system may need to irrigate crops on Tuesday morning because irrigation equipment will be disabled for maintenance on Tuesday afternoon. In addition, in this example, the weather forecast for Tuesday may include precipitation. In this example, a user may input custom constraints into the irrigation planning system for irrigation on Tuesday mornings. Further, in this example, the irrigation planning system may generate an irrigation plan that minimizes water-related losses while taking into account the custom constraints for irrigation on Tuesday mornings. Also, in this example, the irrigation planning system may obtain weather forecasts and take into account expected precipitation when generating the irrigation plan.
[0017] In some embodiments, an irrigation planning system may implement an iterative process between a soil moisture simulator and a plan optimizer to generate an irrigation plan that can reduce water infiltration in a predetermined area below the surface. For example, in some embodiments, such an iterative process may include an irrigation planning system that obtains an initial set of watering rates (e.g., a set of flow rate values for delivering irrigation water to vegetation). In this example, the initial set of watering rates may include a stored set of watering rates from a previous irrigation plan, and may take into account predicted rainfall during the planned irrigation time. Further, in this example, the irrigation planning system may use the initial set of watering rates to perform an iterative calculation cycle until the irrigation planning system determines that a threshold has been exceeded. In addition, in this example, the irrigation planning system may generate an irrigation plan that includes a final set of watering rates.
[0018] For example, a soil moisture simulator of an irrigation planning system may obtain irrigation data that includes an initial set of watering rates, altitude information, vegetation data, and meteorological parameters. Continuing with this example, the soil moisture simulator may use the obtained irrigation data to generate a set of soil moisture estimates at a depth layer (e.g., an area below the surface, such as an area extending from 0.15 m below the surface to 0.75 m below the surface). Further, in this example, the soil moisture simulator may send the set of soil moisture estimates to the planning optimizer. In addition, in this example, the planning optimizer may generate an adjusted set of watering rates based on the set of soil moisture estimates and the obtained set of custom constraints (e.g., a minimum required soil moisture for a certain vegetation, a specific amount of water available for irrigation, a specific amount of power available for pumping irrigation water, etc.). In addition, in this example, the planning optimizer may send the set of adjusted watering rates to the soil moisture simulator, and the soil moisture simulator may generate an updated set of soil moisture estimates based on the set of adjusted watering rates and the obtained irrigation data. In this example, the irrigation planning system can continue an iterative process in which the soil moisture simulator sends an updated set of soil moisture estimates to the planning optimizer and the planning optimizer sends an adjusted set of watering rates to the soil moisture simulator until the irrigation planning system determines that one or more thresholds have been exceeded.
[0019] For example, in some embodiments, the irrigation planning system can utilize a defined root zone depth layer (e.g., an area where a crop set below the surface can absorb water from the soil). In this example, the root zone depth layer can be defined as an area extending from 0.15m below the surface to 0.75m below the surface. Further in this example, the irrigation planning system can utilize the definition of the remaining area depth layer (e.g., an area below the root zone depth layer, the presence of moisture from the infiltrated irrigation water indicates wasted irrigation water). In this example, the remaining area depth layer can be defined as an area extending from 0.75m below the surface to 1.5m below the surface. Further, in this example, the irrigation planning system can define a threshold as a function that can indicate when a set of watering rates corresponds to a minimum rate of infiltrated water entering the remaining area depth layer. In addition, in this example, the irrigation planning system can continue the above iterative process until the soil moisture simulator generates a set of soil moisture estimates that exceeds the threshold. In addition, in this example, when the irrigation planning system determines that the threshold has been exceeded, the planning optimizer can generate a final set of watering rates. In addition, in this example, the irrigation planning system can include a final set of watering rates in the irrigation plan.
[0020] Turning to the attached figure, Figure 1An example computing environment 100 is shown, which includes a computing device 110, a server 120, an IoT device 130, an irrigation device 160, and an irrigation planning system 150, which can exchange data via a network 140. In some embodiments, the computing environment 100 may include multiple of at least one of the computing device 110, the server 120, the IoT device 130, the irrigation device 160, the irrigation planning system 150, and the network 140. In some embodiments, one or more of the computing device 110, the server 120, the IoT device 130, the irrigation device 160, the irrigation planning system 150, and the network 140 may include a computer system, such as a computer system for Figure 4 A computer system 401 is described.
[0021] Return to reference Figure 1 In some embodiments, the irrigation planning system 150 may be a discrete computer system. In some embodiments, the irrigation planning system 150 may be a computer program or application implemented on a processor of a computer system. For example, in some embodiments, the irrigation planning system 150 may be a computer program installed on the computing device 110. In some embodiments, the computing device 110 may include a device such as a desktop computer, a tablet computer, a laptop computer, or a smartphone. In some embodiments, the computing device 110 and / or the server 120 may obtain, store, and / or process data for the irrigation planning system 150. For example, in some embodiments, one or more of the computing device 110 and the server 120 may obtain, store, and / or process custom constraints and / or irrigation data, such as information about Figure 3 In some embodiments, the IoT device 130 may include one or more sensors, such as a precipitation sensor, a temperature sensor, and a barometer. In some embodiments, the IoT device 130 may include: one or more devices configured to obtain irrigation data, such as information about Figure 3 In some embodiments, the irrigation equipment 160 may include one or more irrigation equipment, such as a collection of sprinkler devices configured to distribute water according to an irrigation plan generated by the irrigation planning system 150. In some embodiments, the network 140 may be a wide area network (WAN), a local area network (LAN), the Internet, or an intranet. In some embodiments, the network 140 may be connected to a network. Figure 5 The cloud computing environment 50 described in is substantially similar or identical.
[0022] Figure 2 1 is a flow chart showing an exemplary method 200 for generating an irrigation plan according to an embodiment of the present disclosure. The method 200 may be performed by an irrigation planning system, such as a Figure 1 Irrigation planning system 150 described or related Figure 3 Irrigation planning system 335 is described.
[0023] Return to reference Figure 2 In step 210, the irrigation planning system may obtain irrigation data. In some embodiments, the irrigation data may include one or more types of irrigation data, such as Figure 3 The irrigation data 370 described above may include soil moisture (SM) and soil temperature (ST). In some embodiments, the irrigation data may further include time-dependent meteorological parameters such as precipitation rate (PR). t ), atmospheric temperature (T t ), atmospheric pressure (P t ), relative humidity (RH t ), wind field (W t ) and solar radiation (SR t )(where superscript t represents a time value). In some embodiments, the irrigation planning system may obtain irrigation data intermittently so that the irrigation planning system can take into account changing conditions, such as changing meteorological parameters. In some embodiments, the irrigation data may include a time-dependent watering rate (WR t In some embodiments, the watering rate may be the volume flow rate (e.g., 40 m / s during the first hour) used to deliver irrigation water to the vegetation during the time interval (t). 3 / Hour).
[0024] In some embodiments, at step 210, the irrigation planning system may obtain a watering rate set (eg, WR t =[WR 0 ,WR 1 ,…WR N ], where the superscript t represents a time value, such as the Nth hour or the Nth day). For example, in some embodiments, the irrigation planning system can obtain the initial set of watering rates from a storage location, such as a computing device, that stores a set of watering rates from a previously generated irrigation plan. In some embodiments, the irrigation planning system can obtain the initial set of watering rates from a user via a computing device, such as computing device 110.
[0025] In step 215, the irrigation planning system can obtain a set of customized constraints. In some embodiments, the irrigation planning system can obtain a set of customized constraints from, for example, Figure 1 A remote server such as server 120 or Figure 1The computing device of the user of the computing device 110 obtains the customized constraint set. In some embodiments, the customized constraint set may include a threshold value, such as a minimum required soil moisture at a root zone depth layer for a particular crop. In some embodiments, the irrigation planning system may calculate such a minimum required soil moisture according to the following equation: B*=FC*(1-cc)+cc*WP, where B* is the minimum required soil moisture at the root zone depth layer for a particular crop; FC is the field capacity of the soil; cc is the crop coefficient for the particular crop; and WP is the wilting point for the particular crop. In some embodiments, the irrigation planning system may obtain the minimum required soil moisture at the root zone depth layer by calculating B* based on the values of FC, cc, and WP obtained by the irrigation planning system from a remote server or a computing device of the user. In some embodiments, the irrigation planning system may obtain the minimum required soil moisture at the root zone depth layer from an external source such as a remote server.
[0026] In some embodiments, the customized set of constraints may include user-specific constraints based at least in part on available time and / or available resources. For example, in some embodiments, the customized set of constraints may include an irrigation time period, such as a five-hour time period, during which irrigation may be performed. In some embodiments, the customized set of constraints may include a volumetric flow rate, such as a maximum volumetric flow rate for delivering irrigation water based on available irrigation equipment. By obtaining the customized set of constraints, the irrigation planning system may customize the irrigation plan to take into account one or more user-specific constraints; thus, in some embodiments, the irrigation planning system may address specific irrigation needs with improved accuracy.
[0027] In step 220, the irrigation planning system may generate one or more sets of soil moisture estimates based at least in part on the obtained irrigation data (e.g., the irrigation data obtained in step 210). For example, in some embodiments, the irrigation planning system may generate a set of soil moisture estimates based at least in part on the set of watering rates; thus, the set of soil moisture estimates may correspond to the set of watering rates. In some embodiments, each soil moisture estimate in the set of soil moisture estimates may include an approximation of the amount of water present in a unit amount of soil at a depth layer (e.g., a soil area below the surface). For example, in some embodiments, a soil moisture estimate of 10% may indicate that water accounts for 10% of the mass of a cubic meter of soil at the depth layer. By generating one or more sets of soil moisture estimates based at least in part on the obtained irrigation data, the irrigation planning system may take into account the interaction between the surface, vegetation, and atmosphere. For example, in some embodiments, the irrigation planning system may estimate the amount of irrigation water that may reach the soil depth in combination with evaporation (e.g., by evaporation from the soil and / or by transpiration from the vegetation) that may occur in combination with the soil, vegetation, and meteorological parameters involved.
[0028] In some embodiments, in step 220, the irrigation planning system may generate a set of soil moisture estimates at a root zone depth layer based at least in part on the set of watering rates. In some embodiments, the root zone depth layer may be an area below the surface where plants can absorb water from the soil. In some embodiments, the root zone depth layer may correspond to a particular type of vegetation. For example, in some embodiments, a first crop such as corn may have a root zone depth layer extending from 0.1 m below the surface to 0.8 m below the surface. In another example, in some embodiments, a second crop such as wheat may have a root zone depth layer extending from 0.1 m below the surface to 0.5 m below the surface.
[0029] In some embodiments, in step 220, the irrigation planning system can generate a set of soil moisture estimates at a remaining zone depth layer based at least in part on the set of watering rates. In some embodiments, the remaining zone depth layer can be a depth layer below the root zone depth layer where the presence of moisture from the infiltrated irrigation water indicates wasted irrigation water. Continuing with the example of the root zone depth layer for the corn crop discussed above, the corresponding remaining zone depth layer can extend to 0.8 m below the surface (e.g., from 0.8 m below the surface to 1.5 m below the surface).
[0030] In some embodiments, at step 220, the irrigation planning system may generate a set of soil moisture estimates (eg, SM t =[SM 0 ,SM 1 ,…SM N ], where the superscript t represents a time value, such as the Nth hour or the Nth day), the set of soil moisture estimates being based at least in part on an initial set of watering rates or an adjusted set of watering rates (discussed in further detail below). In some embodiments, step 220 may include the irrigation planning system obtaining soil temperature as a function of depth and / or time. In some embodiments, step 220 may include the irrigation planning system calculating evapotranspiration at a particular time. In some embodiments, step 220 may include an irrigation planning system generating one or more sets of updated soil moisture estimates in response to obtaining one or more sets of adjusted watering rates (see step 240 below). In some embodiments, step 220 may include an irrigation planning system generating one or more updated soil moisture estimates in response to obtaining changed irrigation data, such as changed meteorological parameters.
[0031] In step 225, the irrigation planning system can determine whether one or more customized constraints are satisfied and proceed based on whether one or more customized constraints are satisfied. For example, in some embodiments, the irrigation planning system can compare one or more soil moisture estimates at the root zone depth layer to the minimum required soil moisture (B*) at the root zone depth layer to ensure that the one or more soil moisture estimates exceed the minimum required soil moisture. In some embodiments, if the one or more soil moisture estimates do not exceed the minimum required soil moisture, the irrigation planning system can proceed to step 240 (discussed further below). In some embodiments, if the one or more soil moisture estimates exceed the minimum required soil moisture, the customized constraints can be satisfied and the irrigation planning system can proceed to step 230.
[0032] In some embodiments, the set of customized constraints may include a maximum watering rate, such as a maximum watering rate for a user's irrigation equipment. In these embodiments, the irrigation planning system may compare the set of watering rates to the maximum watering rate to determine whether the maximum watering rate is exceeded. In some embodiments, if one or more watering rates in the set of watering rates exceed the maximum watering rate, the irrigation planning system may adjust the set of watering rates in step 240 (discussed further below). In some embodiments, if no watering rate in the set of watering rates exceeds the maximum watering rate, the customized constraints may be satisfied and the irrigation planning system may proceed to step 230.
[0033] In some embodiments, the custom constraint set may include an irrigation time period during which irrigation may occur. For example, in some embodiments, a user may input a maximum irrigation time period into the irrigation planning system. In these embodiments, the irrigation planning system may compare the irrigation time period of the watering rate set with the maximum irrigation time period to determine whether the irrigation time period of the watering rate set exceeds the maximum irrigation time period. For example, a watering rate set may have an irrigation time period of 3 hours (e.g., WR t =[WR 0 ,WR 1 ,WR 2 ], where WR 0 Indicates the watering rate from 0-1 hour; WR 1 Indicates the watering rate from 1-2 hours; WR 2 In this example, if the custom constraint set includes a maximum irrigation period of 3 hours or more, the irrigation planning system can proceed to step 230 because the custom constraints will be satisfied. However, in this example, if the custom constraint set includes a maximum irrigation period of less than three hours, the irrigation planning system can proceed to step 240 to adjust the watering rate set (discussed further below).
[0034] In step 230, the irrigation planning system may obtain a moisture reference value. In some embodiments, the moisture reference value may include a soil moisture estimate as a function of depth and / or time. In some embodiments, the moisture reference value may indicate a change in soil moisture at depth over a period of time. In some embodiments, the moisture reference value may be based on a set of soil moisture estimates; thus, the moisture reference value may correspond to a set of soil moisture estimates.
[0035] For example, in some embodiments, the humidity reference value may include the total water loss (f(WR t )). In some embodiments, the irrigation planning system can calculate the total water consumption loss based on the set of soil moisture estimates according to the following formula:
[0036] in:
[0037] is the soil moisture estimate at time (t) in the depth layer (d') of the remaining area;
[0038] is the soil moisture estimate at a subsequent time (t+1) of the remaining area depth layer (d'); N represents the Nth time; and Δt is the time difference. In this example, the total water loss may indicate the penetration of water into the remaining area depth layer. As described in further detail below, the irrigation planning system may generate a minimum total water loss, which may correspond to a minimum penetration of water into the remaining area depth layer. In some embodiments, the moisture reference value may include the difference between the two total water losses.
[0039] In step 235, the irrigation planning system may determine whether one or more thresholds are exceeded. For example, in some embodiments, the irrigation planning system may determine whether the total water consumption loss exceeds a predetermined threshold. In some embodiments, the irrigation planning system may determine whether the difference between the first total water consumption loss and the second total water consumption loss exceeds a predetermined threshold. In some embodiments, the predetermined threshold may be selected by a user. In some embodiments, the predetermined threshold may be selected by the irrigation planning system based on its analysis of previously generated irrigation plans and / or machine learning techniques. In some embodiments, if one or more thresholds are not exceeded, the irrigation planning system may proceed to step 240. In some embodiments, if one or more thresholds are exceeded, the irrigation planning system may proceed to step 245.
[0040] In some embodiments, the predetermined threshold in step 235 may be applied to one or more total water loss calculated by the irrigation planning system. In an example where the predetermined threshold may be applied to one total water loss calculated by the irrigation planning system, the irrigation planning system may obtain an initial watering rate set in step 210. Continuing with this example, in step 220, the irrigation planning system may generate a first set of soil moisture estimates at the remaining area depth layer based at least in part on the initial watering rate set; thus, the first set of soil moisture estimates may correspond to the initial watering rate set. Continuing with this example, in step 230, the irrigation planning system may calculate a first total water loss based on the first set of soil moisture estimates; thus, the first total water loss may correspond to the first set of soil moisture estimates and the initial watering rate set. Continuing with this example, a user may input a maximum threshold for the first total water loss into the irrigation planning system. Continuing with this example, in step 235, the irrigation planning system may compare the first total water loss to the maximum threshold, and if the first total water loss is greater than the maximum threshold, proceed to step 240. Continuing with this example, if the first total water consumption loss is less than the maximum threshold, the irrigation planning system may proceed to step 245 .
[0041] In some embodiments, the predetermined threshold in step 235 may apply to more than one total water consumption loss. For example, in some embodiments, the irrigation planning system may generate a first total water consumption loss and a second total water consumption loss. In this example, the irrigation planning system may compare the difference between the first total water consumption loss and the second total water consumption loss to the predetermined threshold. For example, in some embodiments, the predetermined threshold may be 0.00005, and the predetermined threshold may be exceeded when the difference between the first total water consumption loss and the second total water consumption loss is less than 0.00005. In some embodiments, the irrigation planning system may compare the predetermined threshold to the percentage change between the first total water consumption loss and the second total water consumption loss. In some embodiments, the predetermined threshold may be selected so that the predetermined threshold is exceeded when the first total water consumption loss and the second total water consumption loss are approximately equal (e.g., have an absolute difference that may be less than about 0.01; have a percentage change that may be less than about 0.01%; etc.).
[0042] In some embodiments, in step 235, the irrigation planning system determining that the threshold is exceeded may indicate at least one of: an optimal criterion has been reached; water infiltration into the remaining area depth layer is minimized; and water-related losses are minimized.
[0043] In step 240, the irrigation planning system may obtain a set of watering rates and generate an adjusted set of watering rates. In some embodiments, the obtained set of watering rates may be a set of watering rates corresponding to the custom constraints that were not satisfied in step 225. In some embodiments, the irrigation planning system may continue the iterative process of generating the adjusted set of watering rates in step 240 until the custom set of constraints is satisfied in step 225 (e.g., the irrigation planning system may repeat steps 220, 225, and 240 until the custom set of constraints is satisfied). In some embodiments, the obtained set of watering rates may be a set of watering rates corresponding to a threshold that was not exceeded in step 235. In some embodiments, the irrigation planning system may continue the iterative process of generating the adjusted set of watering rates in step 240 until the threshold is exceeded in step 235 (e.g., the irrigation planning system may repeat steps 220 to 240 until the threshold is exceeded).
[0044] In some embodiments, in step 240, the set of watering rates between consecutive iterations may be adjusted by a planning optimizer (e.g., planning optimizer 350, discussed further below) in conjunction with a soil moisture simulator (e.g., soil moisture simulator 340, discussed further below). For example, in some embodiments, the soil moisture simulator may automatically output a standardized adjustment to the watering rate to be applied to the set of watering rates for the first iteration. In this example, the planning optimizer may find the correct ratio to be multiplied by the standardized adjustment by scanning the range of ratios within the minimum and maximum values, so that adding the multiplied adjustment to the set of watering rates for the first iteration can minimize the total water consumption loss. In some embodiments, the set of watering rates between consecutive iterations may be adjusted by the planning optimizer without the need to perform standardized adjustments to the watering rates from the soil moisture simulator. For example, in some embodiments, the planning optimizer may design candidate adjustment rates via a methodical increment / decrement process applied to each watering rate in the set of watering rates. The planning optimizer may then add each candidate adjustment rate to the set of watering rates for the first iteration to generate an adjusted set of watering rates.
[0045] In some embodiments, the irrigation planning system may generate an adjusted watering rate set by manipulating (e.g., adding / removing, increasing / decreasing, etc.) one or more watering rates in the obtained watering rate set. For example, if the custom constraint set requires a 3-hour irrigation period, and the obtained watering rate set includes a 5-hour irrigation period, then in step 240, the irrigation planning system may reduce the irrigation period of the obtained watering rate set from five hours to three hours to obtain an adjusted watering rate set. In some embodiments, the irrigation planning system may generate an adjusted watering rate set by manipulating the irrigation time increments of one or more watering rates. For example, a watering rate set having three, one-hour watering rates has a three-hour irrigation period and an one-hour irrigation time increment. In this example, the watering rate set may be manipulated in step 240 so that the resulting adjusted watering rate set may have two 1-hour watering rates and two 0.5-hour watering rates. In this example, the adjusted watering rate set has a three-hour irrigation period, a first irrigation time increment of one hour, and a second irrigation time increment of one and a half hours. In some embodiments, the irrigation planning system may determine how to manipulate the obtained set of watering rates based on its analysis of previously generated irrigation plans and / or machine learning techniques.
[0046] If the irrigation planning system determines in step 235 that the threshold is exceeded, then in step 245, the irrigation planning system can output the irrigation plan. In some embodiments, step 245 can include transmitting the irrigation plan to a controller of the irrigation equipment, such as a controller of the irrigation equipment. Figure 1 The irrigation device 160 discussed. In some embodiments, the irrigation plan may include the final adjusted watering rate set generated in step 240. For example, in some embodiments, the irrigation planning system may continue the iterative process for five times before it determines in step 235 that the threshold is exceeded. In this example, the fifth adjusted watering rate set generated in step 240 may be the final adjusted watering rate set. In some embodiments, the irrigation plan may include an initial watering rate set that satisfies the custom constraints in step 225 and exceeds the threshold in step 235. In some embodiments, the irrigation plan may include one or more of a watering rate set, an irrigation time period, one or more irrigation time increments, an irrigation date, and an irrigation time of day. In some embodiments, the watering rate set included in the irrigation plan may minimize water-related losses during irrigation.
[0047] Figure 3An example system block diagram 300 of an irrigation planning system 335 according to an embodiment of the present disclosure is shown. The irrigation planning system 335 may include one or more processors and / or neural networks. In some embodiments, the irrigation planning system 335 may include a computer system, such as a computer system ... Figure 4 Described computer system 401. Reference back to Figure 3 In some embodiments, the irrigation planning system 335 may obtain one or more types of irrigation data 370. In some embodiments, the irrigation data may include location data 305, meteorological parameters 310, terrain data 315, depth layer data 320, initial conditions 325, and soil / vegetation data 330. In some embodiments, the irrigation data 370 may be obtained from one or more sources, such as a user's data input device, a collection of sensors, and one or more local or remote computer systems.
[0048] In some embodiments, the location data 305 may include geographic location information, such as global positioning system coordinates. In some embodiments, the meteorological parameters 310 may include time-dependent meteorological parameters, such as precipitation rate, temperature, relative humidity, solar radiation, atmospheric pressure, and wind speed and direction. In some embodiments, the meteorological parameters may include expected meteorological parameters from a weather forecast. In some embodiments, the terrain data 315 may include information about the slope of the altitude and terrain. In some embodiments, the depth layer data 320 may include a depth layer definition, such as the depth of the upper and lower boundaries of the root zone depth layer defining a specific crop. In some embodiments, the depth layer data 320 may include the depth of the remaining area depth layer defining. In some embodiments, the initial conditions 325 may include an initial irrigation data estimate input by a user, such as a user's guess at an initial watering rate set. In some embodiments, the initial conditions 325 may include irrigation data or an irrigation plan previously obtained by an irrigation planning system 335. In some embodiments, the soil / vegetation data 330 may include information such as soil and vegetation types and properties. In some embodiments, soil / vegetation data 330 may include at least one of minimum required soil moisture (B*) at the root zone depth layer for a particular crop; field capacity (FC) of the soil; crop coefficient (cc) for a particular crop; and wilting point (WP) for a particular crop. In some embodiments, soil / vegetation data 330 may include information such as optimal (e.g., preferred or beneficial) irrigation conditions for vegetation (e.g., a specific time and / or date, and a set of watering rates that may correspond to profitable crop yields).
[0049] In some embodiments, the irrigation planning system 335 may include a soil moisture simulator 340. In some embodiments, the soil moisture simulator 340 may perform Figure 2At least one of steps 210, 215, and 220 discussed. In some embodiments, the soil moisture simulator 340 can be a submodule of the irrigation planning system 335. In some embodiments, the soil moisture simulator 340 can obtain one or more types of irrigation data 370 and generate one or more model outputs 345 based on the one or more types of irrigation data 370. In some embodiments, the model outputs 345 can include at least one set of soil moisture estimates according to time and depth; or at least one type of irrigation data 370. Soil temperature estimates according to time and depth; and evapotranspiration values according to time. In some embodiments, the soil moisture simulator can send one or more model outputs 345 to the planning optimizer 350.
[0050] In some embodiments, the plan optimizer 350 may perform a reference Figure 2 One or more of steps 215, 225, 230, 235, 240, and 245 discussed. In some embodiments, the planning optimizer 350 can obtain one or more model outputs 345 from the soil moisture simulator 340. In some embodiments, the planning optimizer 350 can obtain a customized constraint set 360 from a source (e.g., a user input device, a data storage location, etc.). In some embodiments, the customized constraint set 360 can include constraints such as irrigation time periods, threshold amounts of irrigation water, specific times and / or dates for irrigation, specific soil moisture based on time and depth, and a threshold flow rate for providing irrigation water. In some embodiments, the customized constraint set 360 can include at least one of a minimum required soil moisture (B*) at a root zone depth layer for a specific crop; a field capacity (FC) of the soil; a crop coefficient (cc) for a specific crop; and a wilting point (WP) for a specific crop. In some embodiments, the customized constraint set 360 can include thresholds, such as regarding Figure 2 One or more thresholds discussed in step 235 of .
[0051] In some embodiments, the plan optimizer 350 may generate an adjusted set of watering rates 355 based at least in part on the model outputs 345 and / or the custom constraints 360. In some embodiments, the plan optimizer 350 may send the adjusted set of watering rates 355 to the soil moisture simulator 340. In some embodiments, the irrigation planning system 335 may implement an iterative process between the soil moisture simulator 340 and the plan optimizer 350 to generate the irrigation plan 365. In these embodiments, the soil moisture simulator 340 may send the model outputs 345 to the plan optimizer 350 in a loop, and the plan optimizer 350 may send the adjusted set of watering rates 355 to the soil moisture simulator 340 in a loop until the set of model outputs 345 satisfies the custom constraints 360.
[0052] In some embodiments, the irrigation plan 365 generated by the irrigation planning system 335 can provide a unique set of watering rates that accurately accounts for ambient conditions and custom constraints while minimizing water-related losses. Thus, in some embodiments, the irrigation planning system 335 can provide an irrigation plan 365 that is specifically customized to the user's irrigation requirements. In some embodiments, the irrigation plan 365 generated by the irrigation planning system 335 can be output to irrigation equipment, such as a Figure 1 Irrigation equipment 160 discussed.
[0053] Figure 4 Depicted are representative major components of an exemplary computer system 401 that can be used in accordance with embodiments of the present disclosure. The specific components depicted are presented for purposes of example only and are not necessarily the only such variations. Computer system 401 may include processor 410, memory 420, input / output interface (also referred to herein as I / O or I / O interface) 430, and main bus 440. Main bus 440 may provide communication paths for other components of computer system 401. In some embodiments, main bus 440 may be connected to other components, such as a dedicated digital signal processor (not shown).
[0054] The processor 410 of the computer system 401 may be composed of one or more CPUs 412. The processor 410 may also include one or more memory buffers or caches (not shown) that provide temporary storage of instructions and data for the CPU 412. The CPU 412 may execute instructions on inputs provided from the cache or memory 420 and output the results to the cache or memory 420. The CPU 412 may include one or more circuits that are configured to perform one or more methods consistent with embodiments of the present disclosure. In some embodiments, the computer system 401 may include multiple processors 410 that are typical of relatively large systems. However, in other embodiments, the computer system 401 may be a single processor with a single CPU 412.
[0055] The memory 420 of the computer system 401 may include a memory controller 422 and one or more memory modules (not shown) for temporary or permanent storage of data. In some embodiments, the memory 420 may include a random access semiconductor memory, a storage device, or a storage medium (volatile or non-volatile) for storing data and programs. The memory controller 422 may communicate with the processor 410 to facilitate the storage and retrieval of information in the memory module. The memory controller 422 may communicate with the I / O interface 430 to facilitate the storage and retrieval of inputs or outputs in the memory module. In some embodiments, the memory module may be a dual in-line memory module.
[0056] The I / O interface 430 may include an I / O bus 450, a terminal interface 452, a storage interface 454, an I / O device interface 456, and a network interface 458. The I / O interface 430 may connect the main bus 440 to the I / O bus 450. The I / O interface 430 may direct instructions and data from the processor 410 and the memory 420 to the various interfaces of the I / O bus 450. The I / O interface 430 may also direct instructions and data from the various interfaces of the I / O bus 450 to the processor 410 and the memory 420. The various interfaces may include a terminal interface 452, a storage interface 454, an I / O device interface 456, and a network interface 458. In some embodiments, the various interfaces may include a subset of the above interfaces (for example, an embedded computer system in an industrial application may not include a terminal interface 452 and a storage interface 454).
[0057] Logic modules throughout computer system 401 - including but not limited to memory 420, processor 410, and I / O interface 430 - can communicate failures of one or more components and changes to one or more components to a hypervisor or operating system (not depicted). The hypervisor or operating system can allocate the various resources available in computer system 401 and keep track of the location of data in memory 420 and the location of processes assigned to various CPUs 412. In embodiments that combine or rearrange elements, various aspects of the functionality of the logic modules can be merged or reallocated. These changes will be apparent to those skilled in the art.
[0058] It is understood in advance that although the present disclosure includes detailed descriptions about cloud computing, the implementation of the teachings recorded herein is not limited to a cloud computing environment. Instead, embodiments of the present invention can be implemented in conjunction with any other type of computing environment now known or later developed.
[0059] Cloud computing is a service delivery model for convenient, on-demand network access to a shared pool of configurable computing resources. Configurable computing resources are resources that can be quickly deployed and released with minimal management cost or interaction with the service provider, such as networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services. This cloud model can include at least five characteristics, at least three service models, and at least four deployment models.
[0060] Features include:
[0061] On-demand self-service: Cloud consumers can unilaterally and automatically deploy computing capabilities such as server time and network storage on demand without human interaction with the service provider.
[0062] Broad network access: Computing power can be accessed over the network through standard mechanisms that facilitate the use of the cloud through different types of thin-client or thick-client platforms (e.g., mobile phones, laptops, personal digital assistants (PDAs)).
[0063] Resource pool: The computing resources of the provider are grouped into resource pools and serve multiple consumers through a multi-tenant model, where different physical and virtual resources are dynamically allocated and reallocated on demand. Generally, consumers cannot control or even know the exact location of the provided resources, but can specify the location (such as country, state or data center) at a higher level of abstraction, so it is location-independent.
[0064] Rapid elasticity: The ability to quickly and elastically (sometimes automatically) deploy computing power to scale up quickly, and quickly release it to scale down quickly. To consumers, the computing power available for deployment often appears to be unlimited, and any amount of computing power can be accessed at any time.
[0065] Measurable services: Cloud systems automatically control and optimize resource usage by leveraging metering capabilities at a level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency to both service providers and consumers.
[0066] The service model is as follows:
[0067] Software as a Service (SaaS): The capability provided to consumers is to use the provider's applications running on a cloud infrastructure. Applications can be accessed from a variety of client devices through a thin client interface such as a web browser (e.g., web-based email). Aside from limited user-specific application configuration settings, consumers neither manage nor control the underlying cloud infrastructure including networks, servers, operating systems, storage, or even individual application capabilities.
[0068] Platform as a Service (PaaS): The capability provided to consumers is to deploy applications created or acquired by consumers on the cloud infrastructure, which are created using programming languages and tools supported by the provider. Consumers neither manage nor control the underlying cloud infrastructure including networks, servers, operating systems or storage, but have control over the applications they deploy and may also have control over the configuration of the application hosting environment.
[0069] Infrastructure as a Service (IaaS): The capabilities provided to consumers are processing, storage, network, and other basic computing resources on which consumers can deploy and run arbitrary software including operating systems and applications. Consumers neither manage nor control the underlying cloud infrastructure, but have control over the operating system, storage, and applications they deploy, and may have limited control over selected network components (such as host firewalls).
[0070] The deployment model is as follows:
[0071] Private Cloud: Cloud infrastructure is run solely for an organization. The cloud infrastructure can be managed by the organization or a third party and can exist inside or outside the organization.
[0072] Community Cloud: A cloud infrastructure is shared by several organizations and supports a specific community with common interests (e.g., mission, security requirements, policies, and compliance considerations). A community cloud can be managed by multiple organizations within the community or by a third party and can exist inside or outside the community.
[0073] Public cloud: Cloud infrastructure is provided to the public or to large industry groups and is owned by an organization that sells cloud services.
[0074] Hybrid cloud: A cloud infrastructure consisting of two or more clouds (private, community or public) in a deployment model that remain distinct entities but are bound together by standardized or proprietary technologies (such as cloud burst sharing for load balancing between clouds) that enable data and application portability.
[0075] Cloud computing environments are service-oriented, focusing on statelessness, low coupling, modularity, and semantic interoperability. At the core of cloud computing is an infrastructure consisting of a network of interconnected nodes.
[0076] Reference now Figure 5 , depicts an illustrative cloud computing environment 50. As shown, the cloud computing environment 50 includes one or more cloud computing nodes 10, with which local computing devices used by cloud consumers can communicate, such as, for example, personal digital assistants (PDAs) or cellular phones 54A, desktop computers 54B, laptop computers 54C, and / or automotive computer systems 54N. The nodes 10 can communicate with each other. They can be physically or virtually grouped in one or more networks (not shown), such as the private, community, public, or hybrid clouds described above, or a combination thereof. This allows the cloud computing environment 50 to provide infrastructure, platforms, and / or software as a service for which cloud consumers do not need to maintain resources on local computing devices. It should be understood that Figure 5The types of computing devices 54A-N shown are intended to be exemplary only, and computing node 10 and cloud computing environment 50 may communicate with any type of computerized device over any type of network and / or addressable connection (eg, using a Web browser).
[0077] Reference now Figure 6 , showing the cloud computing environment 50 ( Figure 5 ) provides a set of functional abstraction layers. It should be understood in advance that Figure 6 The components, layers and functions shown in are intended to be illustrative only, and embodiments of the present invention are not limited thereto. As shown, the following layers and corresponding functions are provided:
[0078] The hardware and software layer 60 includes hardware and software components. Examples of hardware components include: host 61; server 62 based on RISC (Reduced Instruction Set Computer) architecture; server 63; blade server 64; storage device 65; network and network components 66. Examples of software components include: network application server software 67 and database software 68. The virtualization layer 70 provides an abstraction layer from which examples of virtual entities can be provided: virtual server 71; virtual storage 72; virtual network 73, including virtual private network; virtual application and operating system 74; and virtual client 75.
[0079] The virtualization layer 70 provides an abstraction layer that can provide examples of the following virtual entities: virtual servers 71 , virtual storage 72 , virtual networks 73 (including virtual private networks), virtual applications and operating systems 74 , and virtual clients 75 .
[0080] In one example, the management layer 80 may provide the following functions: Resource provisioning function 81: providing dynamic acquisition of computing resources and other resources for performing tasks in a cloud computing environment; Metering and pricing function 82: tracking the cost of resource usage within the cloud computing environment and providing bills and invoices for this purpose. In one example, the resource may include an application software license. Security function: providing identity authentication for cloud consumers and tasks, and providing protection for data and other resources. User portal function 83: providing access to the cloud computing environment for consumers and system administrators. Service level management function 84: providing allocation and management of cloud computing resources to meet the required service levels. Service level agreement (SLA) planning and fulfillment function 85: providing pre-arrangement and provision for future demand for cloud computing resources predicted according to the SLA.
[0081] The workload layer 90 provides examples of functionality that can take advantage of a cloud computing environment. Examples of workloads and functionality that can be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom instruction delivery 93; data analytics processing 94; transaction processing 95; and irrigation scheduling logic 96.
[0082] As discussed in more detail herein, it is contemplated that some or all of the operations of some embodiments of the methods described herein may be performed in an alternate order or may not be performed at all; furthermore, multiple operations may occur concurrently or as internal parts of a larger process.
[0083] The present invention may be a system, a method and / or a computer program product. The computer program product may include one or more computer-readable storage media having computer-readable program instructions thereon for causing a processor to perform aspects of the present invention.
[0084] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media (a non-exhaustive list) include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium is not to be interpreted as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through a wire.
[0085] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.
[0086] The computer-readable program instructions for performing the operation of the present invention may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of the following: one or more programming languages, including object-oriented programming languages, such as Smalltalk, C++, etc.; and conventional process programming languages, such as "C" programming language or similar programming languages. The computer-readable program instructions may be executed entirely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (for example, by using the Internet of an Internet service provider). In some embodiments, an electronic circuit including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) may execute a computer-readable program instruction to personalize the electronic circuit by utilizing the state information of the computer-readable program instructions, so as to perform aspects of the present invention.
[0087] Various aspects of the present invention are described herein with reference to the flow charts and / or block diagrams of the methods, devices (systems) and computer program products according to embodiments of the present invention. It should be understood that each box of the flow chart and / or block diagram and the combination of each box in the flow chart and / or block diagram can be implemented by computer-readable program instructions.
[0088] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0089] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0090] Flowcharts and block diagrams in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention.In this regard, each square block in the flow chart or block diagram can represent a module, a fragment or a part of an instruction, which includes one or more executable instructions for realizing the specified logical function.In some alternative embodiments, the function indicated in the square block may not occur in the order indicated in the figure.For example, two boxes of continuous display can actually be completed as a step, in a partially or entirely overlapping manner at the same time, substantially simultaneously executed, or these boxes can sometimes depend on the participating functions to be executed in the opposite order.It should also be noted that each square block of the block diagram and / or flow chart and the combination of the square blocks of the block diagram and / or flow chart can be realized by a system based on hardware for a specific purpose of performing a specified function or action or performing a combination of hardware and computer instructions for a specific purpose.
[0091] The description of various embodiments of the present disclosure has been presented for illustrative purposes, but is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein are selected to explain the principles of the embodiments, practical applications of technologies found in the marketplace or technical improvements, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.
Claims
1. A computer-implemented method comprising: Obtain irrigation data from the irrigation planning system; Obtaining a first watering rate set by the irrigation planning system; generating, by the irrigation planning system, a first set of soil moisture estimates and a second set of soil moisture estimates, wherein the first set of soil moisture estimates and the second set of soil moisture estimates are based at least in part on the irrigation data, the first set of soil moisture estimates comprising soil moisture estimates at a root zone depth layer and the second set of soil moisture estimates comprising soil moisture estimates at a remaining zone depth layer, the remaining zone depth layer being below the root zone depth layer; obtaining, by the irrigation planning system, customized constraints; making, by the irrigation planning system, a first determination that the first set of soil moisture estimates satisfies the customized constraints; obtaining, by the irrigation planning system in response to making the first determination, a moisture reference value, wherein the moisture reference value is based at least in part on the second set of soil moisture estimates, wherein the moisture reference value is obtained by calculating a difference between a first soil moisture estimate at the remaining area depth layer at a first time and a second soil moisture estimate at the remaining area depth layer at a second time; making a second determination, by the irrigation planning system, that the humidity reference value exceeds a first threshold; as well as An irrigation plan is generated by the irrigation planning system in response to making the second determination. 2 . The computer-implemented method of claim 1 , wherein the custom constraint is a minimum required soil moisture at the root zone depth layer.
3. The computer-implemented method of claim 1 , further comprising obtaining a second custom constraint, Wherein the first set of watering rates satisfies the second customized constraint.
4. The computer-implemented method of claim 1 , wherein generating the first set of watering rates comprises: Generate a set of adjusted watering rates.
5. An irrigation planning system, comprising: processor; as well as A memory in communication with the processor, the memory containing program instructions which, when executed by the processor, are configured to cause the processor to perform the steps of the method according to any one of claims 1 to 4.
6. A computer program product, comprising a computer-readable storage medium having program instructions embodied therewith, the program instructions being executable by a computer to cause the computer to perform the steps of the method according to any one of claims 1 to 4.
7. A computing device comprising means for performing the steps of the method according to any one of claims 1 to 4.
