Jump to content
TUFLOW FV

Chris.Huxley

Administrators
  • Content Count

    13
  • Joined

  • Last visited

About Chris.Huxley

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1464 profile views
  1. Hi Yanti, 1. You're correct, _FLUX is for flow rate crossing each NS (eg. m3/s) and _MASS is the volume within the whole domain (eg. m3). 2. The discharges are already converted to m3/s. 3. The Flux output should be the output you are after. If not, you can calculate your nodestring cross-section characteristics from the _spatial_nodestring.csv log file. The file summarises the cell x,y coordinate, elevation and face length for each nodestring in the model. You will need to switch on "Echo spatial" in the simulation control file for this log file to be written. The file will be written to the log folder (i.e. not the output folder) Syntax Required: Echo spatial == 1 Module 3 of the TUFLOW FV tutorial models includes an example with this feature enabled: http://fvwiki.tuflow.com/index.php?title=Tutorial_Module03 Complete model files for this tutorial model can be downloaded from the TUFLOW website: http://www.tuflow.com/FV%20TutorialModel.aspx Hope this helps, Chris
  2. Syntax highlighting (colour coding) is an effective way to visually determine if the commands you are specifying in the simulation control file (*.fvc,*.fvm) are correct. A new UltraEdit TUFLOW FV template wordfile is available for download from the TUFLOW FV Utilities download website: http://www.tuflow.com/FV%20Utilities.aspx Instructions how to update UltraEdit with the wordfile are provided on the TUFLOW FV Wiki: http://fvwiki.tuflow.com/index.php?title=UltraEdit_Colour_Coding tuflowfv.uew
  3. Question: I wish to calibrate my model to a historic event. What is the best (most efficient) way to compare recorded results against model results? Answer: Here are a number of tips which may be useful during model calibration/validation: 1) Time Formatting: During calibration modelling it is often convenient to run simulations using isodate format. Isodate format uses date/time specifications to define the model simulation start and end time (instead of hours) Example Syntax: time format == ISODATE start time == 26/03/2010 16:30:00 end time == 01/04/2010 23:00:00 TUFLOW FV WIKI Examples: - Tutorial Module 3 for a worked model example: http://fvwiki.tuflow.com/index.php?title=Tutorial_Module03 - How to configure Excel to use isodate format correctly: http://fvwiki.tuflow.com/index.php?title=Boundary_Condition_Input_Format - How to configure the time settings in SMS to display the result time values correctly: http://fvwiki.tuflow.com/index.php?title=SMS_Tips#Changing_SMS_Time_Settings_.28Hours_to_Isodate.29 2) Point Result Output: Calibration typically requires comparison of model results to a time series of recorded data at a specific location. The output file will include the suffix, “POINTS.csv”: ("FMA2_Hydro_002_POINTS.csv" Example Syntax: output == points output points file == ..\GIS\Output_Points.csv !csv file containing list of point x,y coordinates output parameters == h !water level only output interval == 900. !seconds end output TUFLOW FV WIKI Examples: http://fvwiki.tuflow.com/index.php?title=Tutorial_Module03#Hydrodynamic_Simulation_Results 3) Peak Value Results: Calibration may require comparison of model results to a large number of recorded peak values (eg. flood debris marks) within a study area. This is best done using the model time series *dat or *netcdf results. TUFLOW FV currently doesn’t automatically output the maximum result values (this functionality will be included in the next software release), instead, a series of post processing steps are required to extract the peak/maximum values from the time series *dat or *netcdf results via Example Syntax: output == datv output parameters == h !water level only output interval == 900. !seconds end output TUFLOW FV WIKI Examples: - Extracting the maximum value using SMS: http://fvwiki.tuflow.com/index.php?title=SMS_Tips#Data_Calculations - Extracting the maximum value using TUFLOW Utilities: RES_to_RES: http://fvwiki.tuflow.com/index.php?title=RES_to_RES#Max TUFLOW_to_GIS: http://fvwiki.tuflow.com/index.php?title=TUFLOW_to_GIS#Converting_to_grids 4) Flux/Flow Rating: Model calibration sometimes requires comparison of model flows against recorded ratings. This is already addressed in the following forum post:
  4. Question: I need your help regarding TuflowFV output. I need to calculate flux (concentration/discharge) leaving estuary. So I need to know water velocity. I see there are Vx and Vy components. Are they for water or just above surface water? Answer: There are two elements to this question: 1) What do the Vx and Vy components represent? For a 2D simulation, the Vx and Vy results define the depth averaged flow velocity x,y contributions. 2) How to calculate flux? Modellers need not calculate these results from velocity and depth output. TUFLOW FV will automatically calculate and output flux results if the command "output == flux" is specified: output == flux output interval == 900. end output Flux for all model parameters (e.g. flow, salinity) across all nodestrings within the model will be output to a csv file (simulation name_FLUX.csv). Tutorial Module 3 (documented on the TUFLOW FV Wiki) includes a worked example of this output option (http://fvwiki.tuflow.com/index.php?title=Tutorial_Module03)
  5. Question: We sometime use results displayed in SMS for our report figures. Is there a way to save a display zoom or extent? Answer: Unfortunately not at the present time. A feature request has been submitted to the SMS development team. In the meantime, here is a workaround. 1. Right click on the map data layer in the project explorer and choose "New Coverage" 2. Change the type to something like "Observation" and name it something of your choice. i.e. "Extent 1" 3. Use the create feature arc tool to draw a box around the area of interest 4. You can then toggle the display off in the project explorer and right click on the newly created coverage and choose "Zoom to Coverage" 5. The area of interest will be displayed as shown below
  6. Question Is there a maximum allowable number of elements in a model? Answer There is no limitation on the model element count. Although there are no input limitations, there are some output constraints, depending how you intend to view/process your results. If you are relying on SMS to display your results, you will find that SMS cannot load *.dat results with a file size greater than 1.5GB. You can manage your output file size in a number of ways: Using SMS: Manage the number of output times (command: output interval == t (sec)) Use the TUFLOW Utility, Res_to_Res.exe to create a smaller dat file derived from a reduced time series of the larger *.dat results. Refer to RES_to_RES processing option “RANGE”: http://fvwiki.tuflow.com/index.php?title=RES_to_RES#Range Use output types which do not rely on SMS: command: output == netcdf command: output == points
  7. Question I would like to use the cell elevation input file command to overwrite the centre centre elevations in my model. Cell Elevation File == <cell elevation file (.csv), xytype, ztype> Is there an easy way to get a list of the cell IDs and the associated cell centre x,y co-ordinates? Answer Yes, you can use the echo spatial command to get this information. Echo spatial == 1 !(default == 0, off) This command will write a file to the log folder called '<run_name>_spatial_geo.csv'. The file contains a summary of the geometry data (cell ID, cell centre xy coordinates, elevation, material). The data from this echo file can easily be updated and used as a cell elevation file for future simulations.
  8. Manually specified head vs flow downstream boundaries can be applied using the bc type "HQ" bc == HQ, 1, ..\bc\HQ.csv bc header == level,flow end bc Note: TUFLOW FV uses the convention of negative for flow leaving the model and positive for flow entering the model. As such, flow values should be negative when specifying a HQ boundary at an outflow location (example 'HQ.csv' shown below). level , flow 0.00 , -0.00 1.00 , -10.0 2.00 , -20.0 2.50 , -40.0
  9. The ‘VanRijn04’ sediment transport option in TUFLOW FV is an implementation of the TRANSPOR program developed by Leo Van Rijn. Here are a few papers that describe the formulae which are used in the program: http://www.leovanrijn-sediment.com/papers/P3-2007a.pdf http://www.leovanrijn-sediment.com/papers/P3-2007b.pdf http://www.leovanrijn-sediment.com/papers/P3-2007c.pdf
  10. Question: TUFLOW FV seems to be writing corrupt dat file results. The simulation successfully runs to completion. My point time series hydrograph results look sensible, meanwhile the dat result files which I view in SMS don't make sense at all. It doesn't show any resemblance to a flood surface at all??? Is there an error in the output command which I am specifying? Output Dir == ..\output\ output == datv output parameters == h,v,d output interval == 900. end output Answer: Your out command are correct. I suspect the issue is caused by loading your dat results with the wrong geometry dataset (2dm). When SMS loads a dat file it checks for compatibility with the underlying geometry data (2dm) by comparing the number of nodes and elements in both datasets. If the datasets have the same number, it will load the data without an error message. However, the results in the dat file will only view correctly if the element/node numbering is the same as it was when the TUFLOW FV simulation was undertaken. Element numbering is altered if the mesh is renumbered "Nodestrings > Renumber...". Due to this, renumbering the 2dm file after your model simulation will make the geometry (2dm) and dat result file incompatible with one another. If you wish to view your results in SMS you will need to load them with the original 2dm geometry dataset that was referenced in the TUFLOW FV simulation (Geometry 2D == XXX.2dm ).
  11. Question: TUFLOW FV seems to be writing corrupt dat file results. The simulation successfully runs to completion. My point time series hydrograph results look sensible, meanwhile the dat result files which I view in SMS don't make sense at all. It doesn't show any resemblance to a flood surface at all??? Is there an error in the output command which I am specifying? Output Dir == ..\output\ output == datv output parameters == h,v,d output interval == 900. end output Answer: Your output commands are correct. I suspect the issue is caused by loading your dat results with the wrong geometry dataset (2dm). When SMS loads a dat file it checks for compatibility with the underlying geometry data (2dm) by comparing the number of nodes and elements in both datasets. If the datasets have the same number, it will load the data without an error message. However, the results in the dat file will only view correctly if the element/node numbering is the same as it was when the TUFLOW FV simulation was undertaken. Element numbering is altered if the mesh is renumbered "Nodestrings > Renumber...". Due to this, renumbering the 2dm file after your model simulation will make the geometry (2dm) and dat result file incompatible with one another. If you wish to view your results in SMS you will need to load them with the original 2dm geometry dataset that was referenced in the TUFLOW FV simulation (Geometry 2D == XXX.2dm ).
  12. Question: I have a hydrodynamic model which is using english units (ft). I specify this within the model control fil using the command: Units == English I would now like to upgrade the model by switching on sediment transport. Are the units supposed to be SI within the sediment control file? I am not sure if I should be consistent with the units or if I should use metric units for the sediment module? Answer: Unfortunately, TUFLOW FV currently doesn’t support Imperial/English units for the morphology module. This means your entire model (both the hydrodynamic and morphology components) will need to use SI units to assess sediment transport. We are planning to update the software in future releases to support morphology Imperial/English units and will keep you updated on these developments.
  13. The TUFLOW FV wiki lists the steps required to configure Excel to use the correct time/date isodate format. Details are also provided outlining how to update the default settings on your computer saving the need to make frmat changes each time Excel is opened. http://fvwiki.tuflow.com/index.php?title=Boundary_Condition_Input_Format
×
×
  • Create New...