UTL-OBS¶
Structure of Blocks¶
FOR EACH SIMULATION
BEGIN OPTIONS
[DIGITS <digits>]
[PRINT_INPUT]
END OPTIONS
BEGIN CONTINUOUS FILEOUT <obs_output_file_name> [BINARY]
<obsname> <obstype> <id> [<id2>]
<obsname> <obstype> <id> [<id2>]
...
END CONTINUOUS
Explanation of Variables¶
Block: OPTIONS¶
digits
Keyword and an integer digits specifier used for conversion of simulated values to text on output. The default is 5 digits. When simulated values are written to a file specified as file type DATA in the Name File, the digits specifier controls the number of significant digits with which simulated values are written to the output file. The digits specifier has no effect on the number of significant digits with which the simulation time is written for continuous observations.PRINT_INPUT
keyword to indicate that the list of observation information will be written to the listing file immediately after it is read.
Block: CONTINUOUS¶
FILEOUT
keyword to specify that an output filename is expected next.obs_output_file_name
Name of a file to which simulated values corresponding to observations in the block are to be written. The file name can be an absolute or relative path name. A unique output file must be specified for each CONTINUOUS block. If the “BINARY” option is used, output is written in binary form. By convention, text output files have the extension “csv” (for “Comma-Separated Values”) and binary output files have the extension “bsv” (for “Binary Simulated Values”).BINARY
an optional keyword used to indicate that the output file should be written in binary (unformatted) form.obsname
string of 1 to 40 nonblank characters used to identify the observation. The identifier need not be unique; however, identification and post-processing of observations in the output files are facilitated if each observation is given a unique name.obstype
a string of characters used to identify the observation type.id
Text identifying cell where observation is located. For packages other than NPF, if boundary names are defined in the corresponding package input file, ID can be a boundary name. Otherwise ID is a cellid. If the model discretization is type DIS, cellid is three integers (layer, row, column). If the discretization is DISV, cellid is two integers (layer, cell number). If the discretization is DISU, cellid is one integer (node number).id2
Text identifying cell adjacent to cell identified by ID. The form of ID2 is as described for ID. ID2 is used for intercell-flow observations of a GWF model, for three observation types of the LAK Package, for two observation types of the MAW Package, and one observation type of the UZF Package.
Example Observation Input File¶
Example 1
BEGIN OPTIONS
DIGITS 10
PRINT_INPUT
END OPTIONS
BEGIN CONTINUOUS FILEOUT my_model.gwf.head.csv
# obsname obstype ID
L1 HEAD 1 51 51 # heads at lay 1 row 51 col 51
L2 HEAD 2 51 51 # heads at lay 2 row 51 col 51
END CONTINUOUS
BEGIN CONTINUOUS FILEOUT my_model.gwf.ddn.csv
# obsname obstype ID
L1ddn DRAWDOWN 1 51 51 # heads at lay 1 row 51 col 51
L2ddn DRAWDOWN 2 51 51 # heads at lay 2 row 51 col 51
END CONTINUOUS
BEGIN CONTINUOUS FILEOUT my_model.gwf.flow.csv
# obsname obstype ID ID1
L1rfflow FLOW-JA-FACE 1 51 51 1 51 52
L2rfflow FLOW-JA-FACE 2 51 51 2 51 52
L1-L2flow FLOW-JA-FACE 1 51 51 2 51 51
END CONTINUOUS
Example Observation Input File¶
Example 2
BEGIN OPTIONS
DIGITS 10
PRINT_INPUT
END OPTIONS
BEGIN CONTINUOUS FILEOUT my_model.gwt.conc.csv
# obsname obstype ID
L1 CONCENTRATION 1 51 51 # concs at lay 1 row 51 col 51
L2 CONCENTRATION 2 51 51 # concs at lay 2 row 51 col 51
END CONTINUOUS
BEGIN CONTINUOUS FILEOUT my_model.gwt.mflow.csv
# obsname obstype ID ID1
L1rfflow FLOW-JA-FACE 1 51 51 1 51 52
L2rfflow FLOW-JA-FACE 2 51 51 2 51 52
L1-L2flow FLOW-JA-FACE 1 51 51 2 51 51
END CONTINUOUS