Jump to content
TUFLOW FV

Ian.Teakle@bmtwbm.com.au

Administrators
  • Content Count

    4
  • Joined

  • Last visited

About Ian.Teakle@bmtwbm.com.au

  • Rank
    Expert

Profile Information

  • Gender
    Male
  • Location
    Brisbane

Recent Profile Visitors

1087 profile views
  1. The TUFLOW FV Linux installation is as follows: 1. Download and install codemeter service http://www.wibu.com/downloads-user-software.html >> rpm -ivh CodeMeter64-5.10.1224-501.x86_64.rpm 2. Install tuflowfv, e.g. >> rpm -ivh --nodeps --prefix=<installdir> tuflowfv-dev-1.x86_64.rpm 3. Set PATH and LD_LIBRARY_PATH environment variables, e.g. >> PATH=<installdir>/bin:$PATH >> LD_LIBRARY_PATH=<installdir>/lib:$LD_LIBRARY_PATH 3. Run tuflowfv >> tuflowfv If the installation was successful then you should be able to hit enter when prompted for the input file and the license availability information will be output to the screen:
  2. The TUFLOW FV 2014-01 Release is now available for download from: www.tuflow.com/FV%20Latest%20Release.aspx. The 2014-01 release notes can be downloaded from: www.tuflow.com/Download/TUFLOW_FV/ReleaseNotes/FV-Release-Notes%202014.01.pdf
  3. The control file excerpt provided below contains some examples of how flow regulation structures (e.g. weirs, culverts, sluice gates etc.) can be "controlled". Three alternatives are illustrated: 1. Controlling the flow with a timeseries, e.g. historic gate operation is known and can be specified directly (as a timeseries). 2. Controlling the flow with a "Sample Rule" e.g. gate operation is tied to water level monitoring (within the model domain). 3. Controlling the flow with a "Target Rule" e.g. gate operation is tied water level monitoring (within the model domain) and a target water level timeseries. ! Timeseries Controlled Structure structure == nodestring, 1 flux function == matrix ! hQh matrix flux file == hQh.csv ! hQh matrix file control == timeseries ! structure fraction open specified by input timeseries control parameter == fraction_open control update dt == 1. ! hr control file == ..\..\bcs\pump\AQUIS_pump_inflow_control_tseries.csv ! csv file with column headers "TIME", "FRACTION_OPEN" max opening increment == 0.1 ! maximum change in structure fraction open (per update timestep) end structure ! Sample Rule Controlled Structure structure == nodestring, 1 flux function == matrix ! hQh matrix flux file == hQh.csv ! hQh matrix file control == sample_rule ! structure control type control parameter == fraction_open ! structure fraction open specified by water level monitoring and associated rule control update dt == 1. ! HR control file == control_rule.csv ! csv file with column headers "SAMPLE_VALUE", "FRACTION_OPEN" sample type == WL ! sampling parameter (water level) sample point == 364352., 8139574. ! sampling location sample dt == 0.1 ! hr max opening increment == 0.1 ! maximum change in structure fraction open (per update timestep) end structure ! Target Rule Controlled Structure structure == nodestring, 1 flux function == matrix ! hQh matrix flux file == hQh.csv ! hQh matrix file control == target_rule ! structure fraction open specified by water level monitoring, target water level timeseries and associated rule control parameter == fraction_open control update dt == 1. ! HR target file == target_wl.csv ! csv file with column headers "TIME", "TARGET_VALUE" control file == control_rule.csv ! csv file with column headers "TARGET_DEFICIT","FRACTION_OPEN" sample type == WL ! sampling parameter (water level) sample point == 364352., 8139574. ! sampling location sample dt == 0.1 ! hr max opening increment == 0.1 ! maximum change in structure fraction open (per update timestep) end structure
  4. Thanks RAM There are a few vertical coordinate type options for specifying the vertical distribution for a QC boundary condition, as detailed below. Firstly, the default if no vertical distribution is specified is for a depth averaged inflow. The basic bc control block syntax is: bc == QC, x, y, bc_tsfile bc header == … vertical coordinate type == height ! other vertical coordinate options are <depth; elevation; sigma> vertical distribution == vdistrfil.csv end bc The vertical coordinate type can be DEPTH (below surface), HEIGHT (above sea bed), ELEVATION or SIGMA (0. at surface and 1. at seabed). The vdistrfil.csv should have one column with the heading equivalent to the specified vertical coordinate type (e.g. HEIGHT) and one column with the heading WEIGHT. The units of WEIGHT don’t matter as the distribution gets normalised.
×
×
  • Create New...