Search the Community
Showing results for tags 'cl'.
Found 2 results
Question: When running a direct rainfall model using the TUFLOW HPC solver and applying an IL/CL using the materials layer, the results in the RFML map output are showing that the losses continue to accumulate after the rainfall has stopped i.e. for a 1 hour storm event, the cumulative loss continues to increase after the model time has passed the 1 hour mark. Is the model working, and am I able to use the other output results? Answer: Yes, the model is working and you can still use TUFLOW HPC to model direct rainfall with IL/CL applied using the materials layer. There is a bug in TUFLOW build 2017-09-AC in the RFML map output when running with the HPC solver that continues to report rainfall loss after the rainfall has ceased. This bug is confined to this map output only and does not affect the hydraulic computations or other outputs (depth, velocity, hazard etc). Please do not use the RFML output when using the HPC solver in TUFLOW build 2017-09-AC or earlier. This is not an issue when using the Classic solver.
Q: When using a Global Rainfall boundary (via the "Global Rainfall BC == " command) do the spatially varying losses via the materials file apply, or only the Global Rainfall losses ("Global Rainfall Continuing Loss == " and "Global Rainfall Initial Loss == " commands)? A: When using a Global Rainfall BC the approach is more simplistic than the one than used for a 2d_rf layer. No memory is allocated for spatial losses and the global rainfall losses are the only ones that apply. These global losses are subtracted from the rainfall before the simulation and each cell gets the same rainfall applied. Therefore: The global rainfall losses commands only apply to global rainfall boundaries and not to 2d_rf polygons. The material losses do not apply to global rainfall boundaries. We will issue an updated 2016-03-AE manual in the coming weeks and this behaviour has been clarified. For future versions we will likely; add some warnings if either of the above configurations is specified, we will also look at supporting spatial losses for global rainfall, but will likely make a new command for doing so, to keep the existing behaviour.