Jump to content
TUFLOW Forum

Search the Community

Showing results for tags 'Direct Rainfall'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • About This Forum and Announcements
    • How to Use This Forum
    • Forum Feedback
    • Announcements
  • TUFLOW Modelling
    • 1D/2D Linking
    • 1D Domains
    • 2D/2D Linking
    • 2D/2D Nesting
    • 2D Domains
    • Boundaries
    • Documentation & Tutorial Model
    • Dongles/Licensing/Installation
    • Ideas / Suggestions / New Features
    • Mass Balance/Mass Error
    • MATH Errors & Simulation Failure
    • Restart Files
    • Post-Processing
    • Software/Hardware Requirements
    • Text Files (.tcf, .tgc, .tbc, .ecf)
    • Utilities
    • Miscellaneous
  • Other Software
    • ISIS-TUFLOW
    • MapInfo/Vertical Mapper
    • miTools
    • Other GIS/CAD
    • SMS
    • XP-SWMM2D
    • UltraEdit/Excel
    • TUFLOW Apps

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 9 results

  1. Hi all, I am running a direct rainfall model and I am trying to use PO lines to obtain hydrograph outputs at key locations in my model. When I first tried to use PO lines in my tcf it came up with the error 0046 - Time Series Output Interval not specified. I was able to fix this error by using the command Time Series Output Interval == 3600. The model runs, but without any rainfall entering the model. When I remove the PO lines but keep the Time Series Output Interval command the model still runs without rainfall. The model was running with rainfall before and when I remove the Time Series command. Also, the model I have that uses 2d_bc input hydrographs rather than 2d_rf layers seems to run fine with the PO and Time Series commands. I have attached my tcf. Thanks, Rhain Traralgon_Creek_m1_v01_r013_~e1~_~e2~.tcf
  2. Hi All, I am a engineering student doing some flood modelling for the West Gippsland CMA and I am experimenting with TUFLOW's Direct Rainfall modelling to see how viable it can be for rural catchment simulation.The issue is that in order to keep this flood study in line with the 2016 ARR I have to stochastically vary my rainfall data, meaning that I have to run a large suite simulation (roughly 70) that varies the rainfall data read by the 2d_rf layers. What I need help with is that I am struggling to find an efficient way to view and analyse the large set of data produced by this suite of simulations. I am trying to compare the results between each individual run to find which storm duration/temporal pattern combination generates the largest flood extent, depth of flood water, water velocity, etc. I am just wondering if anyone had any tips or tricks that they were happy to share with me. Thanks, Rhain
  3. Hi Admin, Do you have an example of model text files incorporating .tcf HPC, 1d (.ecf), IL (materials), direct rainfall? Thanks in advance
  4. Hi! I'm having some trouble getting it to rain in a model I've converted to HPC. It worked fine in classic, but when I add the lines below to the TCF, no water enters the model... Solution Scheme == HPC Hardware == GPU in the TLF it shows that it's still reading the hyetographs correctly, but for some reason the Vi column is full of zeroes. Any ideas? I thought maybe it didn't like the Global Rainfall BC command & tried it with a 2D_RF polygon but no luck. Similarly, I tried changing the PO layer to one without QS lines but still no luck not sure if it's related but the DOS window also contains a bunch of errors along the lines of "CUDA driver API error 0400". They occur all the way through but the run doesn't stop please help! Sam
  5. Hi! I'm having some trouble getting it to rain in a model I've converted to HPC. It worked fine in classic, but when I add the lines below to the TCF, no water enters the model... Solution Scheme == HPC Hardware == GPU in the TLF it shows that it's still reading the hyetographs correctly, but for some reason the Vi column is full of zeroes. Any ideas? I thought maybe it didn't like the Global Rainfall BC command & tried it with a 2D_RF polygon but no luck. Similarly, I tried changing the PO layer to one without QS lines but still no luck not sure if it's related but the DOS window also contains a bunch of errors along the lines of "CUDA driver API error 0400". They occur all the way through but the run doesn't stop please help! Sam Gin_09_05PC_2160m_post_HPC.tlf Gin_09_05PC_2160m_post_HPC.hpc.tlf
  6. Dear TUFLOW Users, Tutorial Model 8 - Direct Rainfall is now online and available for download. This module includes examples on the powerful depth-varying roughness feature in TUFLOW, hyetograph input methods, mass conservation considerations and also the differing approaches required when presenting and reviewing rainfall on grid results. Tutorial Model 8 forms part of a larger series of free tutorial models that users can download and run without a TUFLOW license. They are great for beginners or even those looking to use the latest modelling techniques. Follow these links to get started on the tutorial: http://wiki.tuflow.com/index.php?title=Tutorial_Module08 (Tutorial Wiki) http://www.tuflow.com/Tuflow%20Tutorial%20Models.aspx (Model and Data) Should you have any further queries please don't hesitate to send us an email at support@tuflow.com. Regards, The TUFLOW Team.
  7. Q: In the tmf file the Tuflow manual says that: The third and fourth numbers are optional and set the initial and continuing loss rates in mm and mm/h if using Read GIS RF. My understanding was that the 10mm in 3rd column of tmf will impact only the first non-zero value of the hyetograph. And if this is less than 10mm then only that first step will be removed (changed to 0) and that’s the end of initial loss story – the rest of the hyetograph will not be impacted by this 3rd column. Does Tuflow keep removing the rainfall until the 10mm loss is accumulated or does it just take 10mm from the first step and leave the rest alone? A: Good question! Tuflow takes the initial loss off the cumulative rainfall applied in your 2d_RF layer. So, it’s not just that first time step Firstly, Tuflow coverts the hyetograph to a flow to be applied per cell. You can see the gross values of this conversion in your .tlf (and below figure). This is before any removal of losses. The losses are then removed from the cumulative total on the cell, so that a total of (10mm* Cell area) of volume will be removed, using up those initial timesteps until this volume per cell is reached. Only after the losses are removed, the flow is applied to the cells (ie: the rainfall isn’t applied then losses are deducted after that.) Using your data I’ve made a test case below. In the second figure, the dark red dashes are the m3/s per cell that tuflow is applying as a part of the 2d_RF layer without losses (as reported in your .tlf) and the dark blue dashes are the m3/s per cell with losses. I’ve back calculated this from your information. You can see the loss volume in the difference at the start. The tail ends of both lines are the same as the loss has been removed. This is also confirmed in looking at the depth in the model at a cell, refer to the third figure. Thus, you can see that more than your initial timestep is used by the initial loss. At the moment, it is not clear to see what is exactly being applied after losses. However, in the forthcoming 2015 release there are new outputs for checking the rate and cumulative rainfall applied to each cell. So in the future, this kind of question will be more easily checked and visualised. I hope this helps, please let me know if you require more information. Thanks, Rachel
  8. Q: What is the direct rainfall approach and what is the difference between the 2d_rf and 2d_sa_rf layers? A: For both the direct rainfall and the SA RF approach the specified boundary is a rainfall hyetograph. The direct rainfall approach applies the rainfall hyetograph to active cells with the region. For the SA RF the rainfall hyetograph is converted to a flow (in m3/s or ft3/s using the area attributers in the GIS layer, this is described further below. For both types the input hyetograph must be in mm (or inches) versus hours. The first and last rainfall entries should be set to zero, otherwise these rainfall values are applied as a constant rainfall if the simulation starts before or extends beyond the first and last time values in the rainfall time-series. Each value represent the rainfall that falls per increment, for example in the table below between 0.0833 (5 minutes) and 0.1667 (10 minutes) a rainfall depth of 2.5mm is applied, as opposed to a cumulative depth or rainfall rate. A total of 16.5mm of rainfall is applied over a 30min period in the hyetograph below. Time Rainfall 0.0000 0.0 0.0833 0.0 0.1667 2.5 0.2500 5.4 0.3333 3.5 0.4167 5.1 0.5000 0.0 The rainfall (2d_rf) layer applies the rainfall hyetograph to all the active 2D cells, the attributes are: · Rainfall name · factor 1 · factor 2 Both of the factors are multipliers and can be used to modify the boundary. E.g. an f1 might be an area reduction factor and f2 a climate change factor. These are multiplication factors and should be set to 1 if no change is desired. If these are set to 0 no rainfall will be applied and you will get a warning to tell you that this has occurred. For the direct rainfall approach the losses can be specified in either the materials database (the can be varied based on the land-use or 2d_mat layer) or via a soils / infiltration layer. Note: using the double precision build of TUFLOW is recommended for direct rainfall models to ensure accuracy in small flows. The sa rf layer (2d_sa_rf) also uses a rainfall hyetograph, but the required attributes are: · Name · Catchment_Area · Rain_Gauge_Factor · IL · CL The catchment area, factor, IL and CL are used to convert the rainfall, to an inflow boundary (e.g. time - flow). This is then applied to the 2D cells using the source area inflow type (2d_sa). For the SA inflow the default approach (for the 2013 version) is to direct the flow initially to the lowest cell within the polygon and when multiple cells are wet the flow is then spread between wet cells with the flow being proportioned by the cell depth. To turn off the proportioning to depth use the .tcf file command: SA Proportion to Depth == OFF A minimum depth can also be set, below this depth the cell will receive no inflow: SA Minimum Depth == <minimum depth> Regards TUFLOW Support team
  9. 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
×
×
  • Create New...