Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LIS Irrigation output log messages needed #398

Open
karsenau opened this issue Nov 4, 2019 · 1 comment
Open

LIS Irrigation output log messages needed #398

karsenau opened this issue Nov 4, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@karsenau
Copy link
Contributor

karsenau commented Nov 4, 2019

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:

  1. 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.

  2. 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.

@emkemp emkemp added the bug Something isn't working label Mar 5, 2020
@karsenau
Copy link
Contributor Author

karsenau commented Jul 16, 2024

Check to see if this was ever fixed ...

@jerlingi @hkato1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants