tuflow support 0 Report post Posted July 6, 2016 We have recently become aware of an issue affecting TUFLOW GPU simulations using the new gridded rainfall inputs. If the map output interval exceeds the interval in the rainfall grids, then the applied rainfall boundary condition is not updated. Choosing a map output interval that matches or divides into the boundary rainfall data interval will alleviate the issue. For example, if the gridded rainfall has a grid every 30 minutes, a Map Output Interval of 30, 15 or 10 minutes will all work. It is also important that the start map output time matches the gridded rainfall input start time. This will occur by default, though may be altered if a user defined Start Map Output time is specified. This does not affect TUFLOW “classic” simulations and the issue will be corrected in the 2016-03-AB release which will be available within the next month. If you're concerned about large file sizes resulting from your map output interval being reduced to fit your rainfall data interval you can use an output zone. For example with a 10 minute rainfall interval an output zone can be defined with an output interval of 10 minutes and the entire model output can be 1 hour. Again this work-around will only be required until the 2016-03-AB release. The 2016-03-AA release has the option to output the instantaneous rainfall rate and cumulative rainfall can be output with the RFR and RFC output types respectively. These can be used to cross-check the results. For example to output the depth, levels, velocities, rainfall rate and cumulative rainfall the .tcf command would be: Map Output Data Types == d h V RFR RFC Please contact support@tuflow.com if you have any queries relating to the above. Regards TUFLOW Support Team Quote Share this post Link to post Share on other sites
tuflow support 0 Report post Posted August 9, 2016 Just an update to the above post, we are in the final stages of testing for a 2016-03-AB update, which will hopefully be available shortly. Also a word of caution about the work around above, if the boundary update interval is rounded number e.g. 5min / 60min per hour = 0.0833, then rounding in the grid time may also cause the boundary not to be updated and the rainfall rate / cumulative rainfall outputs (as described above should be used to confirm the rainfall depth applied). Quote Share this post Link to post Share on other sites
par 0 Report post Posted August 16, 2016 An update to the 2016 version of TUFLOW (2016-03-AB) has been released. This addresses the above issue and all GPU models using the 2016 release should move to this build. Please see the following forum post for more information and download links: Quote Share this post Link to post Share on other sites