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
{{ message }}
This repository has been archived by the owner on Oct 13, 2022. It is now read-only.
When a rain file has very small rain values (<0.000) RMevents_sample counts it in the rain event and doesn't start counting its interevent period. No rain gage equipment can measure rain amounts that small, rain files with values that small have some other sort of problem. Nonetheless, we could prevent the problem by having RMevents_sample round the rain values to 3 decimals before the ieHr step.
This did the trick in a script prior to running RMevents_sample:
#round rain data to omit rows with very small rain values
precip$rain <- round(precip$rain, digits = 3)
The text was updated successfully, but these errors were encountered:
This issue has to do with the quality of data in the input file. My preference would be to leave it to the user to check data quality before using it in Rainmaker rather than having a fix for bad data within the script.
For this and other data fixes users keep running into - perhaps an enhancement would be a data scrubbing function/workflow to test and ensure data are ready for the 'real' rainmaker, as opposed to writing steps within rainmaker functions to catch these edge cases.
When a rain file has very small rain values (<0.000) RMevents_sample counts it in the rain event and doesn't start counting its interevent period. No rain gage equipment can measure rain amounts that small, rain files with values that small have some other sort of problem. Nonetheless, we could prevent the problem by having RMevents_sample round the rain values to 3 decimals before the ieHr step.
This did the trick in a script prior to running RMevents_sample:
#round rain data to omit rows with very small rain values
precip$rain <- round(precip$rain, digits = 3)
The text was updated successfully, but these errors were encountered: