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
Currently, LIS can only generate daily irrigation output (i.e., not monthly) and only runs if irrigation is written out when irrigation is turned on (selected on in the MODEL_OUTPUT table).
No alerts are provided to the user who may set such options. The following two situations require alerts in LIS to the users, who need to run with irrigation turned on:
When irrigation is turned on in the LIS config file but not activated in the MODEL OUTPUT table, LIS simply crashes with no message given. Conditional statements need to be added to let user know.
Currently, LIS will run with the "Irrigation output interval:" set to "1mo" (monthly interval), but two issues are encountered: all 0's are written out and the month-date in the file naming convention is generated incorrectly. Also here, conditional statements are needed to ensure the user does not select this option, until a fix is implemented.
Finally, LIS irrigation documentation needs a couple of minor updates and additional details.
The text was updated successfully, but these errors were encountered:
Currently, LIS can only generate daily irrigation output (i.e., not monthly) and only runs if irrigation is written out when irrigation is turned on (selected on in the MODEL_OUTPUT table).
No alerts are provided to the user who may set such options. The following two situations require alerts in LIS to the users, who need to run with irrigation turned on:
When irrigation is turned on in the LIS config file but not activated in the MODEL OUTPUT table, LIS simply crashes with no message given. Conditional statements need to be added to let user know.
Currently, LIS will run with the "Irrigation output interval:" set to "1mo" (monthly interval), but two issues are encountered: all 0's are written out and the month-date in the file naming convention is generated incorrectly. Also here, conditional statements are needed to ensure the user does not select this option, until a fix is implemented.
Finally, LIS irrigation documentation needs a couple of minor updates and additional details.
The text was updated successfully, but these errors were encountered: