Search the Community
Showing results for tags 'RF'.
Found 2 results
I put this command in my TBC file: Read GIS SA All RF == gis\2d_sa_rf_LT_FutureTCD_001_R.shp ! Future Town Centre Development TUFLOW stopped without giving me an error. Here is the final lines of the TLF: Found database line: ARR2016_Urban,ARR2016_URBAN.csv,Time_0180M,01pct_0180M_01,,,,, ...Array size from xf file: 58 Opening GIS Layer: R:\PROJECTS\XXX\Modelling\TUFLOW\model\gis\2d_sa_rf_LT_FutureTCD_001_R.shp GIS Layer assigned ID of 2 1 DBF Fields (Name [#/Type/Length]): Name [1/C/100] Reading: R:\PROJECTS\1XXX\Modelling\TUFLOW\model\gis\2d_sa_rf_LT_FutureTCD_001_R.shp I found the problem was only 1 Attribute in the 2d_sa GIS fle instead of the required 5. But it should stop with an error message. The same behaviour is exhibited whether I use HPC or Classic. Regards Tina
Q: I have a TUFLOW GPU simulation which I am using “Read RowCol RF == <layer.mid>” to vary my rainfall factors (f1 and f2) on a cell by cell basis. However, when I review the results it would appear that the multiplication factors are not being used (or used as 1). A: As background for other readers, to gradually vary direct rainfall across your code in both TUFLOW classic and GPU area, you can use the: Read RowCol RF == <gis_layer> command and alter the f1 and f2 scaling factors. The hyetograph weights are multiplied together before being applied to the rainfall. When running TUFLOW GPU, the GPU module performs a check that these are within a valid range, currently this range is 0 – 1.The range limit is applied in the GPU to limit the amount of memory required and maintain accuracy of resolution. If the factors are in the range 0 – 1 they are used as expected. However, if these are outside the range the following error occurs in the log file: Adding hydrograph weight layer 1 ... ERROR: Hydrograph weight data not in range [0..1] If the error above is generated, the simulation then discards the weighting factors and proceeds, however, the results should be treated as suspect and not used. Currently, if this occurs the message is logged to the .gpu.tlf file, however, the simulation is not stopped. It is likely the for a future release that we will force the simulation to stop. TUFLOW classic allows the these weighting factors to add to more than 1, whereas, the GPU solver is capped as 1. To maintain consistency with TUFLOW classic, this capped weighting limit is currently under review within the GPU module, we will ensure that should this change then users will be notified. In the interim, to use weighing factors greater than 1 for a TFULOW GPU simulation, you will need to modify the rainfall boundary so that the f1 factors are less than 1. E.g. multiply the rainfall boundary by 2 and divide the factors by 2 so that they are less than 1. For future releases, we have been enhancing TUFLOW to support a wider range of rainfall boundaries (e.g. as a series of radar images). As part of this we are also adding more outputs. We will be including added the following, to make it easier to track rainfall on a cell by cell basis: · Rainfall rate (output as mm/hr) · Cumulative rainfall (output as mm) Regards TUFLOW Support Team