Jump to content
TUFLOW Forum

Pavlina Monhartova

Administrators
  • Content Count

    37
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About Pavlina Monhartova

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Ben, We haven't heard from any of our users about using github for TUFLOW control files. If you do try it, please let us know about your experience. Kind regards, Pavlina
  2. Hi Helen, Can you please send .tlf to support@tuflow.com so we have a bit more information about your model? Thank you. Kind regards, Pavlina
  3. Hi Jason, The increase in startup time might be insignificant for some models and to some extent noticeable for others depending on how the model is built. Keep in mind that this would only affect the initialisation run time for the first time when XF files are used (the default). We will consider if skipping the grids that doesn't fall within the refinement domain can be implemented for future releases. Thank you for the suggestion. Cheers, Pavlina
  4. Hi Bonnie, Surcharging manholes are not currently supported in TUFLOW, however they are on our development list to consider for future releases. Q pit with 1d_na user defined storage might be a reasonable workaround in the meantime. Is there a storage node in your current model? Cheers, Pavlina
  5. Hi Matthew, Well spotted. It seems the only option for grids is to output to -asc. I have added this on our development list. In the meantime, you can use asc_to_asc utility to convert created asc grids to the binary format. Cheers, Pavlina
  6. Thank you Peter for the suggestion, great advice. If you or Paul still have the model with CN points that doesn't work well with HPC, please send it to support@tuflow.com and we can investigate if it should work. Cheers, Pavlina
  7. Hi Josh, Could you please send a .tlf to support@tuflow.com so we have a bit more information? Thank you. Kind Regards, Pavlina
  8. Hi Josh, Recently we had model (not rain on grid) with similar behaviour and double precision was the fix. Due to not enough significant numbers in single precision there was a trickle flow remaining throughout the pipes. The rest of Peter's suggestions are also worth checking, e.g. 1D timestep and justification for the trickle flow, especially with your model being rain on grid. If you can't get to the bottom of this, please send the model to support@tuflow.com for investigation. Thank you. Kind Regards, Pavlina
  9. Hello everyone, Not having access to the Jabber I would provide some feedback here. Thanks Peter for your input. To add, virtual pipes could also be used to transfer water, same as pumps, it really depends what exactly are you trying to model and what data you have available. For Ezra, a way how to model a rainfall falling on buildings without the 1D error or 2D waterfall like effect would be to use 2d_sa_rf layer and Read GIS SA RF command. You will digitise a small polygon for each building on the ground where you expect the rainfall from the building to fall and assign appropriate attributes – Table 7-6 in the latest TUFLOW Manual. https://www.tuflow.com/Downloads.aspx Kind Regards, Pavlina
  10. Hi Abhishek, Thank you for the suggestion. It has been added to the TUFLOW development list to consider for future releases. Kind regards, Pavlina
  11. Hi Rvan Can you please email support@tuflow.com the model input files and the .tlf file, or if too large just the .tlf file to start with and we will help you solve the problem. In regards to the overlapping materials, the material polygon that is being read into TUFLOW last will set the material for the location where it is overlapping. For material polygons within one layer we recommend to remove the overlaps to be sure straight away which material is applied. Kind Regards, Pavlina
  12. Hi Richard, There are only two possible options available at the moment - classic or 1D weir as the global factor is not supported in HPC yet. Knowing that your HPC model is going to be large you might need to play with the 1D weir and conduct some sensitivity testing. Kind regards, Pavlina
  13. Hi Lucy, The depth to groundwater (DGW) isn't predefined with the -type switch within the TUFLOW_to_GIS utility such as depth, water level and velocity, however, there is a way how to convert these less common data types as well. XMDF files contain a number of scalar (s) and vector (v) datasets. For example, switch -s1 will convert the first scalar dataset. A summary of the available datasets is listed within the DOS window when TUFLOW_to_GIS is preprocessing results and the summary is unique for every XMDF. If you write "pause" at the end of the processing batch file, the DOS Window won't disappear and you can scroll through to find the summary and the number for the depth to groundwater dataset. Below snapshot shows an example of such summary and the Depth to groundwater output could be converter to ASC with -s6 switch. Please note that maximum and minimum is not available for the depth to groundwater output and switch -t<output time> will need to be specified to produce the output for a specific time. Kind regards, Pavlina
  14. Hi Melodea, The latest 2018-03-AE TUFLOW release is rounding up the third decimal space for form loss coefficient in the 2d_lfcsh layer. We already have a task created on our development list to increase the number of decimal spaces for future releases. Kind regards, Pavlina
  15. Hi Peter, Thank you for posting this. It isn't currently possible to do what you have described, however we already have this "super scenario" task on our development list for future releases. Please stay tuned. Kind Regards, Pavlina
×
×
  • Create New...