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
Dear all,
since we are working with a new Basin Office in Tanzania, the Rufiji Basin Water Office, we had to present the discharge technology on Friday. We went to an intake at Ruaha River to demonstrate the app. It was a rectangular lined furrow. The waterline setting was very nice and exact, but those were the velocities we measured: 0.36m/s, 0.34m/s, 0.33m/s, 0.36m/s, 0.49m/s, 0.3m/s. In this case, this meant a range from 200l/s to 300l/s.
Of course we were confronted with questions concerning the accuracy. How could this be improved?
Is it possible, that the app measures 8 or 12 seconds, so that the results get more stable?
Could the app give a range of discharge, something like 200-300l/s?
The fact, that the app gives a discharge with two places after the decimal point suggests that it is that exact. Instead of giving a discharge of 296.16, it could maybe just display 300?
Kind regards,
Timo
The text was updated successfully, but these errors were encountered:
Dear all,
since we are working with a new Basin Office in Tanzania, the Rufiji Basin Water Office, we had to present the discharge technology on Friday. We went to an intake at Ruaha River to demonstrate the app. It was a rectangular lined furrow. The waterline setting was very nice and exact, but those were the velocities we measured: 0.36m/s, 0.34m/s, 0.33m/s, 0.36m/s, 0.49m/s, 0.3m/s. In this case, this meant a range from 200l/s to 300l/s.
Of course we were confronted with questions concerning the accuracy. How could this be improved?
Is it possible, that the app measures 8 or 12 seconds, so that the results get more stable?
Could the app give a range of discharge, something like 200-300l/s?
The fact, that the app gives a discharge with two places after the decimal point suggests that it is that exact. Instead of giving a discharge of 296.16, it could maybe just display 300?
Kind regards,
Timo
The text was updated successfully, but these errors were encountered: