Read MI Table Links == <.mif/.mid_file> 50
Read Materials File == 51
Relative Resistance == [ {RELATIVE} | MATERIAL ] 51
S Channel Approach == [ PRE 2004-06-AA ] 51
Storage Above Structure Obvert == [ {CHANNEL WIDTH} | ] 51
Trim XZ Profiles == [ ON | {OFF} ] 52
XS Database == 52
[ BG | CS | NA | VG ].... ! Fixed Field Flags 60
BG Data == 60
CS Data == 60
NA Data == 61
VG Data == 61
Read MI IWL == <.mif/.mid_file> 69
Set IWL == 69
BC Database == <.csv_file> 77
BC Event Name == 77
BC Event Text == 78
EB Data == 78
Read MI BC == <.mif/.mid_file> 78
Cell Size == 9
Grid Size (N,M) == , 9
Grid Size (X,Y) == , 9
Orientation == , 9
Orientation Angle == 10
Origin == , 10
Read MI Location == <.mif/.mid_file> 10
Read TGA == <.tga_file> 18
Read TGF == <.tgf_file> 18
External Bndy == , , , 27
Read MI [ MAT | IWL | CnM | FRIC | WrF | FLC ] == 28
Read MI Code [ {} | BC ] == 28
Read MID [ CODE | MAT | IWL | CnM | FRIC | WrF | FLC ] == 28
Read MID Grid == 29
Set [ CODE | MAT | IWL | CnM | FRIC | WrF ] == 29
Write MI Domain == <.mif/.mid_file> 29
Write MI Grid == <.mif/.mid_file> 29
Allow Dangling Z Lines == [ ON | {OFF} ] 38
Default Land Z == 38
Interpolate ZC [ {} | ALL ] [ {} | LOWER ] 38
Interpolate [ ZHC | ZUVC ] [ {} | ALL ] [ {} | AFTER ] 39
Pause When Polyline Does Not Find Zpt == [ ON | {OFF} ] 39
Read MI Z Line [ {} | RIDGE or MAX | GULLY or MIN | HX ] [ {} | CC ] [ {} | THICK ] [ {} | ADD ] == 40
Read MI Zpts [ {} | ADD | MAX | MIN ] == 41
Read MID Zpts [ {} | ADD | MAX | MIN ] == 41
Set Zpt == 42
Write MI Zpts == 42
ZC == MIN(ZU,ZV) 42
Read File == 51
Stop 51
BC Database == <.csv_file> 9
BC Event Name == 9
BC Event Text == 10
Global Rainfall Area Factor == [ {1.0} | ] 10
Global Rainfall BC == 10
Global Rainfall Continuing Loss == [ {0} | ] 10
Global Rainfall Initial Loss == [ {0} | ] 10
Read MI BC == <.mif/.mid_file> 10
Read MI SA [ {} | Rainfall ] == <.mif/.mid_file> 11
Unused HX and SX Connections == [ {ERROR} | WARNING ] 11
Adjust Head at Estry Interface == [ {ON} | ON VARIABLE | OFF ]
(Optional)
If set to “ON”, lowers the head supplied by ESTRY to TUFLOW by the dynamic head. ESTRY, being a quasi-2D model calculates a static water level, whilst TUFLOW calculates an actual water level. Testing by Syme (1991) demonstrates that for stability reasons this option should be used. The adjustment by a dynamic head is averaged across the 2D/1D interface.
The “ON VARIABLE” option, adjusts the water level on a cell by cell basis. Usually less stable than the “ON” option.
The “OFF” option disables any head adjustment – not recommended.
Check Inside Grid == [ {ERROR} | WARNING | OFF ]
(Optional. Incorporated Build 2005-05-AN)
By default, some layers, such as the 2d_bc and 2d_po layers, must have all of their objects fall within the 2D domain they are associated with, otherwise an ERROR is issued and the simulation stops. Should it be required that this check be switched off, set to either WARNING (a WARNING is issued and will be included in the _messages.mif file) or OFF (no checks are made). The treatment of objects that fall partly inside a 2D domain should be cross-checked viewing the check files and results as to how they were treated.
(Optional)
Undocumented feature.
Null Cell Checks == [ ON | {OFF} ]
(Optional. Incorporated Build 2001-08-AE)
Switches on and off the checks that ensure null cells occur on one side of an external boundary. A TUFLOW simulation prior to Build 2001-08-AE will not proceed unless a null cell occurs on one side of an external boundary cell (this was traditionally used to indicate the inactive side of the boundary line). Setting this to OFF (the default) allows ESTRY models to be inserted through the 2D domain with no need to specify null cells (eg. a 1D creek flowing through a 2D floodplain). It also allows land cells, instead of null cells, to be specified against a boundary on the inactive side.
Note: Prior to Build 2001-08-AE models were checked for the null cells along boundaries. For models prior to this build, you may need to set this flag.
Oblique Boundary Alignment == [ {NEAREST TO LINE} | CENTRE TO CENTRE ]
(Optional)
Build 2004-01-AA changed the method used for assigning boundary cells (Code 2) along a 2d_bc line to be commensurate with the method used for 3D breaklines (see Read MI Z Line). Prior to this build, a 2d_bc line segment was shifted so that each end of the line segment was located at the centre of the nearest 2D cell. This approach is a hangover from earlier versions of TUFLOW when data was entered in on a cell reference basis. This approach will not necessarily choose the cell nearest to the line, and would choose different cells than that using Read MI Z Line. For example, this was of a particular nuisance where 2D HX lines are used to link 1D and 2D domains along a levee defined by a 3D breakline. The CC option in Read MI Z Line was introduced to minimise this issue.
The default from Build 2004-01-AA onwards is to choose boundary cells nearest the digitised line. For backward compatibility, the original approach can be used by specifying this command with the CENTRE TO CENTRE option.
However, it is recommended that the new approach be that used. If upgrading old models to this new approach, any Read MI Z Line command using the CC option needs to have the CC removed.
Oblique Boundary Method == [ {ON} | ON METHOD 2 | OFF ]
(Optional)
If set to “ON”, applies Oblique Boundary Method 1 as documented in Syme (1991). This offers substantial improvements in model stability along boundaries not parallel or at 45 to the X and Y axes of the grid. Using this method, boundaries and 2D/1D interfaces can be orientated at any angle.
“ON METHOD 2” activates Oblique Boundary Method 2 in Syme (1991). This method does not perform as well as Method 1 and is not recommended.
The “OFF” option disables any Oblique Boundary Methods.
Unused HX and SX Connections == [ {ERROR} | WARNING ]
(Optional)
If set to “ERROR”, the default, any unconnected or redundant CN objects in 2d_bc layers are treated as an ERROR. This error is typically due to a CN object not being snapped to a HX or SX object in the same 2d_bc layer, or the use of two CN objects at either end of a SX line (only one CN object is required to connect a SX line, thereby making the other one redundant). This error check was incorporated in Build 2003 06 AC. For backward compatibility, set to “WARNING” so that TUFLOW continues to run, but only issues a WARNING. It is not recommended that the WARNING option be used other than for backward compatibility.
Dostları ilə paylaş: | 
