GMS:Observations: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
No edit summary
Line 1: Line 1:
{{Infobox Calibration}}
{{Infobox Calibration}}
==Point Observations==
==Point Observations==
The primary type of field data used in a typical calibration exercise is point observations. Point observations represent values that are measured at some location in the field. Point observations generally correspond to water table elevations measured at observation wells. However, multiple observed values can be defined at each observation point. Observation points are managed in the Map module using the Coverage Setup dialog.
The primary type of field data used in a typical calibration exercise is point observations. Point observations represent values that are measured at some location in the field. Point observations generally correspond to water table elevations measured at observation wells. However, multiple observed values can be defined at each observation point. Observation points are managed in the Map module using the ''Coverage Setup'' dialog.


==Flow Observations==
==Flow Observations==
Line 18: Line 18:


===Group Weight Multipliers===
===Group Weight Multipliers===
In addition to the individual weight, a group weight can also be assigned. Group weights are assigned using the Group Weight section of the Observations dialog. This dialog is accessed by selecting the Observations command in the MODFLOW  menu.
In addition to the individual weight, a group weight can also be assigned. Group weights are assigned using the Group Weight section of the ''Observations'' dialog. This dialog is accessed by selecting the '''''Observations''''' command in the ''MODFLOW'' menu.


A group weight can be assigned to each of the following observation types:
A group weight can be assigned to each of the following observation types:
Line 47: Line 47:
{{template:Version GMS 8.0}}
{{template:Version GMS 8.0}}
===Export Trans. Obs.===
===Export Trans. Obs.===
Beginning with version 8.0, this button allows you to export a csv (comma separated values) file with transient observation data. This file can be loaded into excel to create plots of the transient observation values vs. the model computed values. An example of using this data is included in the [[GMS:Tutorials|MODFLOW- Managing Transient Data]] tutorial.
Beginning with version 8.0, this button allows you to export a *.csv (comma separated values) file with transient observation data. This file can be loaded into excel to create plots of the transient observation values vs. the model computed values. An example of using this data is included in the [[GMS:Tutorials|MODFLOW- Managing Transient Data]] tutorial.


==Confidence Interval and Standard Deviation==
==Confidence Interval and Standard Deviation==
Line 61: Line 61:
The standard deviation becomes important when using an inverse model.  The  weight assigned to each of the observations points is a function of the standard  deviation.  This weight is used in the objective function that the inverse model  tries to minimize.  An observation point with a small standard deviation will  have a greater influence on the objective function than a point with a large  standard deviation.
The standard deviation becomes important when using an inverse model.  The  weight assigned to each of the observations points is a function of the standard  deviation.  This weight is used in the objective function that the inverse model  tries to minimize.  An observation point with a small standard deviation will  have a greater influence on the objective function than a point with a large  standard deviation.


The user must enter an interval (or standard deviation) and confidence in the [[GMS:Feature Objects#Feature Object Properties|Properties Dialog]]. Although these values are rarely quantified the following examples  may prove helpful.
The user must enter an interval (or standard deviation) and confidence in the [[GMS:Feature Objects#Feature Object Properties|''Properties'' Dialog]]. Although these values are rarely quantified the following examples  may prove helpful.


If the user had the following set of head measurements for one  observation well:
If the user had the following set of head measurements for one  observation well:

Revision as of 22:10, 17 May 2012

Calibration,
Parameters,
Stochastic Modeling
Calibration
Model Calibration
Automated Parameter Estimation
PEST Dialog
PEST
Run Options
Observations
MODFLOW-USG Observations
Plot Wizard
Calibration Targets
Parameters
Parameters
Parameter Dialog
Pilot Points
Multiplier Arrays for Parameters
Standard MODFLOW Parameters
Stochastic Modeling
Stochastic Modeling
Gaussian Field Generator
Risk Analysis Wizard
T-PROGS
v • e

Point Observations

The primary type of field data used in a typical calibration exercise is point observations. Point observations represent values that are measured at some location in the field. Point observations generally correspond to water table elevations measured at observation wells. However, multiple observed values can be defined at each observation point. Observation points are managed in the Map module using the Coverage Setup dialog.

Flow Observations

Flow observations represent gains or losses between aquifers and streams or reservoirs. In addition to point observations, flow observations are an essential part of a calibration exercise for a flow model. If calibration is attempted using point observations only, there may be many combinations of parameters such as hydraulic conductivity and recharge that will result in the same head distribution. Adding one or more flow observations serves to "pin down" the flow quantity resulting in a set of hydraulic conductivities and recharge values that are more likely to be unique.

While the point observation tools are model independent, GMS only supports flow observations for MODFLOW and FEMWATER. With MODFLOW, observed flows are assigned to selected arcs and polygons making up the MODFLOW conceptual model in the Map module. When a MODFLOW solution is imported, the computed flows are read for the arcs and polygons and compared with observed values.

With a FEMWATER simulation, observed values cannot be assigned to objects in the FEMWATER conceptual model. However, when a FEMWATER solution is imported, the computed flows on selected model boundaries can be automatically summed. Comparison of computed vs. observed flows must then be made manually.

Observation Weights

When performing automated parameter estimation, a set of head and flow observations are defined using points, arcs, and polygons in the Map module. When entering the point and flow observations, care should be taken when entering the calibration interval and confidence values. These values are used to determine the weights assigned to each observation in the inverse model. The weight is multiplied by the residual for the observation in the objective function. The weight that is sent to the inverse model input files by GMS is computed as

Note that GMS will automatically convert from an interval and a confidence to a standard deviation or you can directly enter the standard deviation.

Group Weight Multipliers

In addition to the individual weight, a group weight can also be assigned. Group weights are assigned using the Group Weight section of the Observations dialog. This dialog is accessed by selecting the Observations command in the MODFLOW menu.

A group weight can be assigned to each of the following observation types:

  1. Head observations.
  2. Constant head flow observations.
  3. River flow observations.
  4. General head flow observations.
  5. Drain flow observations.
  6. Stream flow observations.

Options 2-6 correspond to flow observations that are defined using the Observed flow rate option.

The default value for the group weights is 1.0. The default value can be changed to give a larger influence to a particular observation type. For example, if a particular model had sixteen head observations and one flux observation corresponding to a stream gage, a better solution may be obtained by increasing the flux group weight to give more weight to the stream gage measurement.

Observations Dialog

This dialog is used to manage which coverages that contain MODFLOW observation data will be applied to the current simulation. It is also used to apply group weights. You can only access this dialog when observations have been created using the Map Module in a MODFLOW conceptual model.

Group Weights

These weights can be used to emphasize (or deemphasize) a type of observation for the simulation.

Coverages

This spreadsheet allows you to choose which observation coverages will be used in the current simulation. This can be helpful if you have observations for a site from different times, but you only want to use one of the times.

Gnome globe current event.png
 This contains information about functionality available starting at GMS version 8.0.
The content may not apply to other versions.
GMS logo 40px.png

Export Trans. Obs.

Beginning with version 8.0, this button allows you to export a *.csv (comma separated values) file with transient observation data. This file can be loaded into excel to create plots of the transient observation values vs. the model computed values. An example of using this data is included in the MODFLOW- Managing Transient Data tutorial.

Confidence Interval and Standard Deviation

The interval and standard deviation are related by the following equation:

where sd is the standard deviation, CI is the confidence interval, and z is the the "z statistic" based on the specified confidence and the normal distribution. The user can enter an interval and confidence, and the standard deviation will be computed; or the user can enter a standard deviation and confidence, and the interval will be computed.

In practical terms entering an interval (or standard deviation) and confidence is an indication of how much error the user believes is associated with the observed value.

The standard deviation becomes important when using an inverse model. The weight assigned to each of the observations points is a function of the standard deviation. This weight is used in the objective function that the inverse model tries to minimize. An observation point with a small standard deviation will have a greater influence on the objective function than a point with a large standard deviation.

The user must enter an interval (or standard deviation) and confidence in the Properties Dialog. Although these values are rarely quantified the following examples may prove helpful.

If the user had the following set of head measurements for one observation well:

Date Head
May 10, 1998 55.0
July 10, 1998 50.5
September 5, 1998 48.6
November 15, 1998 49.1
February 2, 1999 50.8
March 12, 1999 54.0
April 1, 1999 57.2

The mean of the data is 52.17 and the standard deviation is 3.25. The user could enter this standard deviation and a confidence of 95%.

Many times the user does not have this much data available. Usually the user will only have one measured value. In this case the user must use engineering judgement to estimate an interval or standard deviation. For example, if I have a single head measurement of 45.7 ft and I believe that observation to be accurate to within a 1 foot. Then I would enter 1 foot as my interval.

See also


v • e
GMS – Groundwater Modeling System
Modules:2D Grid  •  2D Mesh  •  2D Scatter Point  •  3D Grid  •  3D Mesh  •  3D Scatter Point  •  Boreholes  •  GIS  •  Map  •  Solid  •  TINs  •  UGridsGMS Logo2.png
Models:FEFLOW  •  FEMWATER  •  HydroGeoSphere  •   MODAEM  •  MODFLOW  •  MODPATH  •  mod-PATH3DU  •  MT3DMS  •  MT3D-USGS  •  PEST  •  PHT3D  •  RT3D  •  SEAM3D  •  SEAWAT  •  SEEP2D  •  T-PROGS  •  ZONEBUDGET
Aquaveo
Retrieved from "https://www.xmswiki.com/index.php?title=GMS:Observations&oldid=37232"