XMS Wiki - http://wikis.aquaveo.com/xms/ - Recent changes [en]

User:Backlink22tr

2012-05-19T00:01:34Z

New user account

GMS:Conductance

2012-05-18T22:56:41Z

← Older revision		Revision as of 22:56, 18 May 2012
(2 intermediate revisions not shown)
Line 7:		Line 7:
	Darcy's law states:		Darcy's law states:

-	~~<!--~~[[Image:eq_cond1.gif]]~~-->~~	+	{{only in print\| [[Image:eq_cond1.gif\|frame]]}}
-	<math>\ Q=kiA</math>	+	{{hide in print\| <math>\ Q=kiA</math>}}

File:Eq cond7.gif

2012-05-18T22:50:11Z

uploaded a new version of "[[File:Eq cond7.gif]]"

File:Eq cond6.gif

2012-05-18T22:48:56Z

uploaded a new version of "[[File:Eq cond6.gif]]"

File:Eq cond5.gif

2012-05-18T22:30:28Z

uploaded a new version of "[[File:Eq cond5.gif]]"

File:Eq cond4.gif

2012-05-18T22:30:01Z

uploaded a new version of "[[File:Eq cond4.gif]]"

File:Eq cond3.gif

2012-05-18T21:49:21Z

uploaded a new version of "[[File:Eq cond3.gif]]"

File:Eq cond2.gif

2012-05-18T21:37:15Z

uploaded a new version of "[[File:Eq cond2.gif]]"

File:Eq cond1.gif

2012-05-18T21:31:58Z

uploaded a new version of "[[File:Eq cond1.gif]]"

User:DinaYbarra9

2012-05-18T21:12:52Z

New user account

GMS:Conductance

2012-05-18T21:07:33Z

← Older revision		Revision as of 21:07, 18 May 2012
Line 11:		Line 11:


-	where ''Q'' is the flow rate, ''k'' is the hydraulic conductivity, i represents the hydraulic gradient, and A represents the gross cross-sectional area of flow. Darcy's law can also be expressed as:	+	where ''Q'' is the flow rate, ''k'' is the hydraulic conductivity, ''i'' represents the hydraulic gradient, and ''A'' represents the gross cross-sectional area of flow. Darcy's law can also be expressed as:

	<!--[[Image:eq_cond2.gif]]-->		<!--[[Image:eq_cond2.gif]]-->
Line 48:		Line 48:


-	Where t is the thickness of the material and w is the width of the material along the length of the arc. When GMS applies the boundary condition from the arc to the grid cell, it automatically multiplies the entered value of conductance by the length of the arc that intersects the cell to create an accurate conductance value for the cell.	+	Where ''t'' is the thickness of the material and ''w'' is the width of the material along the length of the arc. When GMS applies the boundary condition from the arc to the grid cell, it automatically multiplies the entered value of conductance by the length of the arc that intersects the cell to create an accurate conductance value for the cell.

	=== Polygons ===		=== Polygons ===
Line 57:		Line 57:


-	Where t is the thickness of the material. When GMS converts the stress from a polygon to a grid cell, it automatically multiplies the entered value of conductance by the area of the cell that is covered by the polygon to create an appropriate conductance value for the cell. This restores the dimensional accuracy to the expression for conductance.	+	Where ''t'' is the thickness of the material. When GMS converts the stress from a polygon to a grid cell, it automatically multiplies the entered value of conductance by the area of the cell that is covered by the polygon to create an appropriate conductance value for the cell. This restores the dimensional accuracy to the expression for conductance.

	===Points===		===Points===
Line 63:		Line 63:

	===Parameter Factors===		===Parameter Factors===
-	Beginning with GMS version 7.0, the Well, Drain, River, General head, and Stream boundary conditions have a parameter factor field that is associated with each boundary condition. The parameter factor is used with the parameter value to compute the final value of conductance for a given boundary condition (or in the case of the well package the final Q value). The parameter factor is automatically set by GMS when doing the ''Map->MODFLOW'' command. This value will be set to the length of the arc in the cell or the area of the polygon in the cell associated with the boundary condition; for a point feature the factor is set to 1.0.	+	Beginning with GMS version 7.0, the Well, Drain, River, General head, and Stream boundary conditions have a parameter factor field that is associated with each boundary condition. The parameter factor is used with the parameter value to compute the final value of conductance for a given boundary condition (or in the case of the well package the final Q value). The parameter factor is automatically set by GMS when doing the '''''Map->MODFLOW''''' command. This value will be set to the length of the arc in the cell or the area of the polygon in the cell associated with the boundary condition; for a point feature the factor is set to 1.0.

	{{Navbox GMS}}		{{Navbox GMS}}

	[[Category:MODFLOW]]		[[Category:MODFLOW]]

GMS:Bugfixes GMS

2012-05-18T17:27:16Z

GMS:Data Set Files

2012-05-18T17:24:25Z

← Older revision		Revision as of 17:24, 18 May 2012
Line 1:		Line 1:
	==ASCII Data Set Files==		==ASCII Data Set Files==
-	Data sets can be stored to either ASCII or binary files. The default format is binary. Data sets can be saved in ASCII format by right clicking on the data set in the [[GMS:The GMS Screen\|Project Explorer]] and selecting the '''Export''' command from the pop up menu. For both file formats, multiple data sets can be stored in a single file and both scalar and vector data sets can be saved to the same file. The file format is identical for 2D and 3D data sets.	+	Data sets can be stored to either ASCII or binary files. The default format is binary. Data sets can be saved in ASCII format by right clicking on the data set in the [[GMS:The GMS Screen\|Project Explorer]] and selecting the '''''Export''''' command from the pop up menu. For both file formats, multiple data sets can be stored in a single file and both scalar and vector data sets can be saved to the same file. The file format is identical for 2D and 3D data sets.

	For scalar data set files, one value is listed per vertex, cell, node, or scatter point. The points are listed sequentially in ascending order according to the ids of the nodes, points, vertices, or cells. For vector data set files, one set of XYZ vector components is listed per vertex, cell, node, or scatter point. If necessary, a set of status flags can be included in the file. If the status flag is false (0), the corresponding item (node, cell, etc.) is inactive. If status flags are not included in the file, it is assumed that all items are active.		For scalar data set files, one value is listed per vertex, cell, node, or scatter point. The points are listed sequentially in ascending order according to the ids of the nodes, points, vertices, or cells. For vector data set files, one set of XYZ vector components is listed per vertex, cell, node, or scatter point. If necessary, a set of status flags can be included in the file. If the status flag is false (0), the corresponding item (node, cell, etc.) is inactive. If status flags are not included in the file, it is assumed that all items are active.

KMZ files

2012-05-18T17:19:51Z

How To Export - Screen Capture:

← Older revision		Revision as of 17:19, 18 May 2012
Line 11:		Line 11:
	== How To Export - Screen Capture ==		== How To Export - Screen Capture ==
	* You must be in plan view before you can export a KMZ file.		* You must be in plan view before you can export a KMZ file.
-	* You can export a KMZ file by using the standard ''File\|Save As'' dialog and selecting either the '''Google Earth© Raster KMZ File (.kmz)''' or '''Google Earth© Vector KMZ File (.kmz)''' option in the ''Save as type'' field.	+	* You can export a KMZ file by using the standard ''File\|Save As'' dialog and selecting either the '''Google Earth© Raster KMZ File (.kmz)''' or '''Google Earth© Vector KMZ File (.kmz)''' option in the '''Save as type''' field.
	* To specify a resolution higher than the screen resolution:		* To specify a resolution higher than the screen resolution:
-	** GMS - Select the ''Options'' button in the ''Save As'' dialog.	+	** GMS - Select the '''Options''' button in the ''Save As'' dialog.
	** SMS - Change the copy to clipboard scale factor in the [[SMS:Preferences\|Preferences dialog]]		** SMS - Change the copy to clipboard scale factor in the [[SMS:Preferences\|Preferences dialog]]

Registering an Image

2012-05-18T17:17:12Z

SMS Point Conversion:

← Older revision		Revision as of 17:17, 18 May 2012
(2 intermediate revisions not shown)
Line 1:		Line 1:
	<!-- THIS IS A SHARED PAGE, SO PLEASE DON'T PUT LINKS TO PROGRAM SPECIFIC PAGES UNLESS THEY ARE SPECIFIED AS SUCH -->		<!-- THIS IS A SHARED PAGE, SO PLEASE DON'T PUT LINKS TO PROGRAM SPECIFIC PAGES UNLESS THEY ARE SPECIFIED AS SUCH -->
-	If an image file is not geo-referenced then the user must define the coordinate system of the image. The register dialog allows the user to specify the coordinate system for the image. When an image is opened, if the image is not self-referenced, XMS attempts to find world file with the same name as the image (.wld or .jpgw extension). If neither of these is found, the register dialog opens.	+	If an image file is not geo-referenced then the user must define the coordinate system of the image. The register dialog allows the user to specify the coordinate system for the image. When an image is opened, if the image is not self-referenced, XMS attempts to find world file with the same name as the image (.wld or .jpgw extension). If neither of these is found, the register dialog opens.

	== What is Image Registration? ==		== What is Image Registration? ==
Line 10:		Line 10:
	An image is registered using the Register Image dialog. The main feature of the Register Image dialog is a large window in which the image is displayed. Two or three points (shown by "+" symbols) are also displayed in the window. These points are used to identify locations with known real world coordinates. The real world coordinates (X,Y) and image coordinates (U,V) of the registration points are listed in edit fields below the image. The points are moved to the desired locations on the image by dragging the points using the tools described below. Once the points are located, the real world coordinates can be entered in the corresponding edit fields. The dialog contains the following options:		An image is registered using the Register Image dialog. The main feature of the Register Image dialog is a large window in which the image is displayed. Two or three points (shown by "+" symbols) are also displayed in the window. These points are used to identify locations with known real world coordinates. The real world coordinates (X,Y) and image coordinates (U,V) of the registration points are listed in edit fields below the image. The points are moved to the desired locations on the image by dragging the points using the tools described below. Once the points are located, the real world coordinates can be entered in the corresponding edit fields. The dialog contains the following options:
	* '''2 point or 3 point registration''' - Two point registration rotates and uniformly scales an image. Three point registration allows for non-uniform scaling to account for some parallax.		* '''2 point or 3 point registration''' - Two point registration rotates and uniformly scales an image. Three point registration allows for non-uniform scaling to account for some parallax.
-	* '''Import World File''' - Used to import a TIFF world file (.tfw). A TIFF world file has the information needed to set the (X,Y) and (U,V) coordinates in order to place the image in the correct world coordinates.	+	* '''Import World File''' - Used to import a TIFF world file (*.tfw). A TIFF world file has the information needed to set the (X,Y) and (U,V) coordinates in order to place the image in the correct world coordinates.
	* '''Image name''' - Used to associate a name with the file. This name will appear in the project explorer.		* '''Image name''' - Used to associate a name with the file. This name will appear in the project explorer.

Line 38:		Line 38:
	==Import World File==		==Import World File==
	<!-- THIS IS A SHARED PAGE, SO PLEASE DON'T PUT LINKS TO PROGRAM SPECIFIC PAGES UNLESS THEY ARE SPECIFIED AS SUCH -->		<!-- THIS IS A SHARED PAGE, SO PLEASE DON'T PUT LINKS TO PROGRAM SPECIFIC PAGES UNLESS THEY ARE SPECIFIED AS SUCH -->
-	The Import World File button can be used to automatically define the registration data. A world file is a special file associated with a previously registered image that is exported from [http://www.esri.com/software/arcview/ ArcView®] or [http://www.esri.com/software/arcgis/arcinfo/ Arc/Info®]. The file contains registration data that can be used to register the image.	+	The '''Import World File''' button can be used to automatically define the registration data. A world file is a special file associated with a previously registered image that is exported from [http://www.esri.com/software/arcview/ ArcView®] or [http://www.esri.com/software/arcgis/arcinfo/ Arc/Info®]. The file contains registration data that can be used to register the image.

	==Saving/Reading Image Registration Data==		==Saving/Reading Image Registration Data==
Line 54:		Line 54:
	=== SMS Point Conversion ===		=== SMS Point Conversion ===
	<!-- THIS IS A SHARED PAGE, SO PLEASE DON'T PUT LINKS TO PROGRAM SPECIFIC PAGES UNLESS THEY ARE SPECIFIED AS SUCH -->		<!-- THIS IS A SHARED PAGE, SO PLEASE DON'T PUT LINKS TO PROGRAM SPECIFIC PAGES UNLESS THEY ARE SPECIFIED AS SUCH -->
-	The [[Single Point Conversion]] command in the '''Edit''' menu can be helpful if you need to convert between any two coordinate systems. You should perform this conversion and record the locations in the correct coordinate system prior to entering the registration dialog.	+	The [[Single Point Conversion]] command in the ''Edit'' menu can be helpful if you need to convert between any two coordinate systems. You should perform this conversion and record the locations in the correct coordinate system prior to entering the registration dialog.

-	An alternative approach is to convert the coordinate system after importing by right clicking on the image in the [[GMS:Project Explorer\|Project Explorer]] and choosing ''Coordinate Conversion'' from the right click menu.	+	An alternative approach is to convert the coordinate system after importing by right clicking on the image in the [[GMS:Project Explorer\|Project Explorer]] and choosing '''''Coordinate Conversion''''' from the right click menu.

	=== WMS Point Conversion ===		=== WMS Point Conversion ===

GMS:Exporting Non-native GMS Files

2012-05-18T17:14:54Z

← Older revision		Revision as of 17:14, 18 May 2012
Line 5:		Line 5:
	== Exporting through Save Dialog ==		== Exporting through Save Dialog ==

-	The file types that can be exported are shown in the table below. To export a particular file type, the file filter corresponding to that file type should be selected in the Save dialog.	+	The file types that can be exported are shown in the table below. To export a particular file type, the file filter corresponding to that file type should be selected in the ''Save'' dialog.

	{\| class="wikitable"		{\| class="wikitable"
Line 29:		Line 29:
	== Exporting from the Project Explorer ==		== Exporting from the Project Explorer ==

-	Item in the [[GMS:The GMS Screen\|Project Explorer]] can be exported to different formats by right-clicking on an item and selecting the Export command. The table below lists the file formats that will be shown depending on the type of [[GMS:Project Explorer\|Project Explorer]] object selected:	+	Item in the [[GMS:The GMS Screen\|Project Explorer]] can be exported to different formats by right-clicking on an item and selecting the '''''Export''''' command. The table below lists the file formats that will be shown depending on the type of [[GMS:Project Explorer\|Project Explorer]] object selected:

	{\| class="wikitable"		{\| class="wikitable"
Line 40:		Line 40:
	\|DXF/DWG		\|DXF/DWG
	\|<center>.dxf, .dwg</center>		\|<center>.dxf, .dwg</center>
-	\|Saves the current CAD data to a dxf or dwg file. You can convert your GMS data to CAD data by using the Data->CAD command in the CAD menu in the Map module.	+	\|Saves the current CAD data to a dxf or dwg file. You can convert your GMS data to CAD data by using the '''''Data->CAD''''' command in the CAD menu in the Map module.
	\|-		\|-
	\|Boreholes		\|Boreholes

Import from Web

2012-05-18T17:12:15Z

← Older revision		Revision as of 17:12, 18 May 2012
Line 1:		Line 1:
-	The ''Import from Web'' feature allows you to connect to the internet to download free data - images, elevation data etc. If you have an internet connection, this is an easy and convenient way to acquire this type of data.	+	The Import from Web feature allows you to connect to the internet to download free data - images, elevation data etc. If you have an internet connection, this is an easy and convenient way to acquire this type of data.
	The data is made available for free by various entities who provide [http://en.wikipedia.org/wiki/Web_service web services]. Each XMS programs has a number of available data types they can retrieve.		The data is made available for free by various entities who provide [http://en.wikipedia.org/wiki/Web_service web services]. Each XMS programs has a number of available data types they can retrieve.

Line 30:		Line 30:
	\|}		\|}

-	This feature is found via the ''File\|Import from Web'' command. This command results in the following series of dialogs.	+	This feature is found via the '''''File\|Import from Web''''' command. This command results in the following series of dialogs.

	<!-- I specify an 80% scaling on all the dialog images. I think the dialogs look way to big otherwise. Unfortunately there's no easy way to do that in MediaWiki so I have to just calculate what 80% of the width is in pixels. -->		<!-- I specify an 80% scaling on all the dialog images. I think the dialogs look way to big otherwise. Unfortunately there's no easy way to do that in MediaWiki so I have to just calculate what 80% of the width is in pixels. -->
	#'''Warning'''		#'''Warning'''
-	#:If your current coordinate system is 'Local', you will get the following warning dialog. The data that will be downloaded is georeferenced so your project coordinate system must be something other than 'Local'. Selecting ''OK'' will change the current coordinate system.	+	#:If your current coordinate system is "Local", you will get the following warning dialog. The data that will be downloaded is georeferenced so your project coordinate system must be something other than 'Local'. Selecting '''OK''' will change the current coordinate system.
	#:[[Image:ImportFromWeb-CurrentCoordSystemWarning.png\|center\|400px\|''Warning about Local Coordinate Systems'']]		#:[[Image:ImportFromWeb-CurrentCoordSystemWarning.png\|center\|400px\|''Warning about Local Coordinate Systems'']]
	#'''Virtual Earth Map Locator'''		#'''Virtual Earth Map Locator'''

GMS:Import From Database

2012-05-18T17:10:38Z

← Older revision		Revision as of 17:10, 18 May 2012
Line 1:		Line 1:
-	The ~~'''~~Database Import Wizard~~'''~~ allows users to access data stored in a database and import it. The wizard is invoked by selecting the '''Import from Database''' command from the '''File''' menu. The data types that can be imported by the '''Database Import Wizard''' are the same data types that are supported by the [[GMS:Text Import Wizard\|Text Import Wizard]].	+	The "Database Import Wizard" allows users to access data stored in a database and import it. The wizard is invoked by selecting the '''''Import from Database''''' command from the ''File'' menu. The data types that can be imported by the '''Database Import Wizard''' are the same data types that are supported by the [[GMS:Text Import Wizard\|"Text Import Wizard"]].

-	The '''Database Import Wizard''' has four steps:	+	The ''Database Import Wizard'' has four steps:
	== Step 1 - Connecting to a Database ==		== Step 1 - Connecting to a Database ==
	Step 1 of the wizard lets you set up a connection to a database. To connect to a database either on the same computer or on a network press the '''Connect to Database''' button. Once a database connection is created, a path to the database and the different tables in the database are displayed. When a table is selected its columns are displayed along with the number of rows in that table.		Step 1 of the wizard lets you set up a connection to a database. To connect to a database either on the same computer or on a network press the '''Connect to Database''' button. Once a database connection is created, a path to the database and the different tables in the database are displayed. When a table is selected its columns are displayed along with the number of rows in that table.

Shapefiles

2012-05-18T17:08:58Z

← Older revision		Revision as of 17:08, 18 May 2012
Line 1:		Line 1:
	One of the most common methods for creating feature objects is to import a shapefile. The concept of a shapefile was established by [http://www.esri.com/ Environmental Systems Research Institute (ESRI)] in their ArcView® program and it has become the defacto standard for sharing GIS vector data (points, lines, and polygons).		One of the most common methods for creating feature objects is to import a shapefile. The concept of a shapefile was established by [http://www.esri.com/ Environmental Systems Research Institute (ESRI)] in their ArcView® program and it has become the defacto standard for sharing GIS vector data (points, lines, and polygons).

-	A shape file is actually comprised of three or more files. The primary file is the .shp and it contains the geometric information (coordinates and if necessary connectivity of the points, lines, polygons). The .dbf file is a standard database file and stores the attributes of the feature objects. Finally, there will be a .shx file which is an indexing file. There may be a few other files that accompany the shapefile and so you should always move them around together if you are copying or moving them to a new directory.	+	A shape file is actually comprised of three or more files. The primary file is the .shp and it contains the geometric information (coordinates and if necessary connectivity of the points, lines, polygons). The .dbf file is a standard database file and stores the attributes of the feature objects. Finally, there will be a *.shx file which is an indexing file. There may be a few other files that accompany the shapefile and so you should always move them around together if you are copying or moving them to a new directory.

	Only one "theme" or type of feature can exist in a shapefile. For example you cannot store points and polygons in the shapefile, or boundaries and so you may be required to import multiple files.		Only one "theme" or type of feature can exist in a shapefile. For example you cannot store points and polygons in the shapefile, or boundaries and so you may be required to import multiple files.

GMS:Importing/Exporting Shapefiles

2012-05-18T17:07:36Z

Observation Coverage:

← Older revision		Revision as of 17:07, 18 May 2012
(3 intermediate revisions not shown)
Line 17:		Line 17:

	==Importing Shapefiles==		==Importing Shapefiles==
-	Shapefiles are imported to GMS using '''Open''' command in the '''File''' menu and selecting the *.shp extension. A dialog comes up that prompts the user whether to import the shapefile as a scatter set or feature objects.	+	Shapefiles are imported to GMS using '''''Open''''' command in the ''File'' menu and selecting the *.shp extension. A dialog comes up that prompts the user whether to import the shapefile as a scatter set or feature objects.

-	If the scatter set option is selected and the file must is a point file, the points are imported. If the option selected is Feature Objects, the Map Shapefile Properties Dialog appears. The list of coverage attributes in the top right portion of the dialog are the properties for the current GMS coverage type. The list of database fields in the top left portion of the dialog are the properties that GMS found in the specified shapefile. The bottom portion of the dialog shows how the shapefile properties will be mapped to the GMS coverage properties. GMS will attempt to automatically set up the mapping by looking for shapefile attribute names that match the names of the GMS coverage properties. The user can manually change the attribute mapping using the Map and Unmap buttons. Database fields that are not mapped will be ignored by GMS.	+	If the scatter set option is selected and the file must is a point file, the points are imported. If the option selected is Feature Objects, the ''Map Shapefile Properties'' Dialog appears. The list of coverage attributes in the top right portion of the dialog are the properties for the current GMS coverage type. The list of database fields in the top left portion of the dialog are the properties that GMS found in the specified shapefile. The bottom portion of the dialog shows how the shapefile properties will be mapped to the GMS coverage properties. GMS will attempt to automatically set up the mapping by looking for shapefile attribute names that match the names of the GMS coverage properties. The user can manually change the attribute mapping using the '''Map''' and '''Unmap''' buttons. Database fields that are not mapped will be ignored by GMS.

	The order for importing is first polygons, then arcs, then points. For example, when importing both an arc and a node shapefile, it is important to import the arc shapefile first. The properties that a node can have depend on the arcs it is attached to so GMS must find the arcs attached to nodes being imported. The points on the arcs need to be nodes and not vertices for GMS to match them up. That is, the points on the arcs that correspond with the points being imported in the point shapefile must be nodes, not vertices. Even if they're in the exact same location, GMS won't match them up if they're vertices, only if they're nodes.		The order for importing is first polygons, then arcs, then points. For example, when importing both an arc and a node shapefile, it is important to import the arc shapefile first. The properties that a node can have depend on the arcs it is attached to so GMS must find the arcs attached to nodes being imported. The points on the arcs need to be nodes and not vertices for GMS to match them up. That is, the points on the arcs that correspond with the points being imported in the point shapefile must be nodes, not vertices. Even if they're in the exact same location, GMS won't match them up if they're vertices, only if they're nodes.
Line 26:		Line 26:

	==Exporting Shapefiles==		==Exporting Shapefiles==
-	GMS feature objects are saved to shapefiles by right-clicking a coverage in the Project Explorer and using the '''Export''' command. Saving shapefiles brings up the Export Shapefile dialog. The Export Shapefile dialog shows the path and filename where the shapefile will be saved. In GMS, a single coverage can contain points, nodes, arcs and polygons. Shapefiles, however, can only contain one type of attribute. Thus, GMS can export up to three shapefiles depending on the type of objects in the GMS coverage. For example, if the GMS coverage contains arcs, points and nodes, the user can export the arcs to one shapefile and the points and nodes to a separate point shapefile. The user can control which shapefiles GMS will create when more than one is possible. The names for the shapefiles come from the prefix listed at the top of the dialog, appended with "_pts" for the point shapefile, "_arcs" for the arc shapefile, and "_polys" for the polygon shapefile.	+	GMS feature objects are saved to shapefiles by right-clicking a coverage in the Project Explorer and using the '''''Export''''' command. Saving shapefiles brings up the Export Shapefile dialog. The ''Export Shapefile'' dialog shows the path and filename where the shapefile will be saved. In GMS, a single coverage can contain points, nodes, arcs and polygons. Shapefiles, however, can only contain one type of attribute. Thus, GMS can export up to three shapefiles depending on the type of objects in the GMS coverage. For example, if the GMS coverage contains arcs, points and nodes, the user can export the arcs to one shapefile and the points and nodes to a separate point shapefile. The user can control which shapefiles GMS will create when more than one is possible. The names for the shapefiles come from the prefix listed at the top of the dialog, appended with "_pts" for the point shapefile, "_arcs" for the arc shapefile, and "_polys" for the polygon shapefile.

	The Export Shapefile dialog allows the user to specify the format of fields containing floating point numbers in the shapefile. The total width of the field and the number of digits to the right of the decimal can be specified. All float fields in the shapefile will be formatted according to these settings.		The Export Shapefile dialog allows the user to specify the format of fields containing floating point numbers in the shapefile. The total width of the field and the number of digits to the right of the decimal can be specified. All float fields in the shapefile will be formatted according to these settings.
Line 122:		Line 122:
	===MODFLOW/MT3D Areal Coverage===		===MODFLOW/MT3D Areal Coverage===

-	The fields exported for MODFLOW/MT3D layer coverages depend on what properties are defined for the polygons. They also depend on which flow package (LPF, BCF or HUF) is selected in the Coverage Properties dialog. Similarly when importing GMS looks for the appropriate fields based on the selected flow package.	+	The fields exported for MODFLOW/MT3D layer coverages depend on what properties are defined for the polygons. They also depend on which flow package (LPF, BCF or HUF) is selected in the ''Coverage Properties'' dialog. Similarly when importing GMS looks for the appropriate fields based on the selected flow package.

	The following table lists the attributes that go with each flow package.		The following table lists the attributes that go with each flow package.
Line 177:		Line 177:
	===Observation Coverage===		===Observation Coverage===

-	When importing shapefiles into an observation coverage, information should exist in the Int (interval) and Conf (confidence) fields, or in the Stdev (standard deviation) field but not both. The confidence value should be an integer between 0 and 100 (ie 95 means 95% confidence). GMS will assign default values if there is any information missing.	+	When importing shapefiles into an observation coverage, information should exist in the Int (interval) and Conf (confidence) fields, or in the Stdev (standard deviation) field but not both. The confidence value should be an integer between 0 and 100 (i.e., 95 means 95% confidence). GMS will assign default values if there is any information missing.

	{\| border="1" cellpadding="2"		{\| border="1" cellpadding="2"
Line 192:		Line 192:
	\|}		\|}
	''Point Properties for Observation Coverage.''		''Point Properties for Observation Coverage.''
-

	==See also==		==See also==

GMS:Importing/Exporting GIS Grids

2012-05-18T17:02:21Z

← Older revision		Revision as of 17:02, 18 May 2012
Line 2:		Line 2:

	=== Importing ===		=== Importing ===
-	Grids are imported using the '''Open''' command in the '''File''' menu.	+	Grids are imported using the '''''Open''''' command in the ''File'' menu.

	With GRASS and ARC/INFO grid files, the grid and the attributes are saved to a single file. When a grid file is imported, GMS constructs the grid, and then reads in the attribute matrix as a [[GMS:Data Sets\|data set]].		With GRASS and ARC/INFO grid files, the grid and the attributes are saved to a single file. When a grid file is imported, GMS constructs the grid, and then reads in the attribute matrix as a [[GMS:Data Sets\|data set]].
Line 8:		Line 8:
	When a grid in GRASS or ARC/INFO contains multiple attributes (data sets), each attribute is written to a separate grid file. In such cases, it is possible to read in one instance of the grid file to create a grid with a single data set, and then read in the other grids as extra data sets on the first grid. This can be accomplished as follows:		When a grid in GRASS or ARC/INFO contains multiple attributes (data sets), each attribute is written to a separate grid file. In such cases, it is possible to read in one instance of the grid file to create a grid with a single data set, and then read in the other grids as extra data sets on the first grid. This can be accomplished as follows:

-	#Select the Open command from the File menu.	+	#Select the '''''Open''''' command from the ''File'' menu.
	#Choose either the GRASS or ARC/INFO file filter.		#Choose either the GRASS or ARC/INFO file filter.
	#Select the grid file.		#Select the grid file.
-	#Select the OK button.	+	#Select the '''OK''' button.

	At this point, the first grid file is imported resulting in a grid with a single data set. For the additional data sets, steps 1-5 are repeated but now GMS will detect that there is already a 2D grid in memory that matches the grid being imported and will ask whether you want to replace the existing grid, or add the new grid as a data set of the existing grid.		At this point, the first grid file is imported resulting in a grid with a single data set. For the additional data sets, steps 1-5 are repeated but now GMS will detect that there is already a 2D grid in memory that matches the grid being imported and will ask whether you want to replace the existing grid, or add the new grid as a data set of the existing grid.

	===Exporting===		===Exporting===
-	Grids can be exported from GMS in the GRASS or ARC/INFO format by right-clicking on the grid in the [[GMS:Project Explorer\|Project Explorer]] and selecting the Export menu command. Only grids with equal row heights and equal column widths can be exported. When a grid is exported, the grid and the active data set are written to the GIS file. If multiple data sets are associated with the grid, each data set should be made the active data set and the grid should be exported repeatedly so that each data set is written to a separate grid file.	+	Grids can be exported from GMS in the GRASS or ARC/INFO format by right-clicking on the grid in the [[GMS:Project Explorer\|Project Explorer]] and selecting the '''''Export''''' menu command. Only grids with equal row heights and equal column widths can be exported. When a grid is exported, the grid and the active data set are written to the GIS file. If multiple data sets are associated with the grid, each data set should be made the active data set and the grid should be exported repeatedly so that each data set is written to a separate grid file.

GMS:Importing USGS DEMs

2012-05-18T17:00:14Z

GMS:Importing/Exporting CAD Data

2012-05-18T16:58:36Z

← Older revision		Revision as of 16:58, 18 May 2012
Line 7:		Line 7:
	GMS data can be exported to a DWG or DXF file that can then be read into a CAD package. If there is CAD data in memory when a GMS project is saved, GMS creates a new DWG file from the CAD data. The file is put in the same folder with the other project files and named using the project prefix.		GMS data can be exported to a DWG or DXF file that can then be read into a CAD package. If there is CAD data in memory when a GMS project is saved, GMS creates a new DWG file from the CAD data. The file is put in the same folder with the other project files and named using the project prefix.

-	Any CAD data in memory can be exported by right-clicking the CAD folder in the Project Explorer and selecting the '''''Export''''' command. The DWG/DXF Filename dialog will appear, and you can select either the DWG of DXF file types to save the CAD data. GMS objects must first be converted to CAD data before CAD data can be exported. To convert GMS data to CAD data, use the [[GMS:CAD Options\|Convert To CAD]] command in the Display Menu.	+	Any CAD data in memory can be exported by right-clicking the CAD folder in the Project Explorer and selecting the '''''Export''''' command. The ''DWG/DXF Filename'' dialog will appear, and you can select either the DWG of DXF file types to save the CAD data. GMS objects must first be converted to CAD data before CAD data can be exported. To convert GMS data to CAD data, use the [[GMS:CAD Options\|'''''Convert To CAD''''']] command in the ''Display'' Menu.

	==See also==		==See also==

GMS:Text Import Wizard Supported File Formats

2012-05-18T16:57:31Z

Transient point data:

← Older revision		Revision as of 16:57, 18 May 2012
(One intermediate revision not shown)
Line 2:		Line 2:

	== 2D scatter points ==		== 2D scatter points ==
-	This will create new scatter points in a new [[GMS:2D_Scatter_Point_Module\|2D scatter set]]. Optionally the imported points can be filtered using the filter options available by selecting the Filter Options button.	+	This will create new scatter points in a new [[GMS:2D_Scatter_Point_Module\|2D scatter set]]. Optionally the imported points can be filtered using the filter options available by selecting the '''Filter Options''' button.

	{\|class="wikitable"		{\|class="wikitable"
Line 272:		Line 272:

	== Transient point data ==		== Transient point data ==
-	This creates new time series [[XY_Series_Editor\|curve]] data on existing [[GMS:Feature_Objects#Points\|feature points]] similar to the [[#Pumping data\|Pumping data]] option above. This option is more generic than the [[#Pumping data\|Pumping data]] option, however, because it will work with feature points of any type and any attribute (that can be transient) of that feature point. The imported data is matched to the existing points by name or by XY location. Data for more than one attribute can be imported at the same time. The attributes of the active coverage are listed as available fields that can be mapped.	+	This creates new time series [[XY_Series_Editor\|curve]] data on existing [[GMS:Feature_Objects#Points\|feature points]] similar to the [[#Pumping data\|"Pumping data"]] option above. This option is more generic than the [[#Pumping data\|"Pumping data"]] option, however, because it will work with feature points of any type and any attribute (that can be transient) of that feature point. The imported data is matched to the existing points by name or by XY location. Data for more than one attribute can be imported at the same time. The attributes of the active coverage are listed as available fields that can be mapped.

	{\| class="wikitable"		{\| class="wikitable"

GMS:Text Import Wizard

2012-05-18T16:55:54Z

← Older revision		Revision as of 16:55, 18 May 2012
Line 1:		Line 1:
-	GMS can import many files generated by other software in their native format. Refer to [[GMS:Importing Non-native GMS Files\|Importing Non-native GMS Files]] for a list. For files that are not included in the list, GMS provides the '''Text Import Wizard'''.	+	GMS can import many files generated by other software in their native format. Refer to [[GMS:Importing Non-native GMS Files\|Importing Non-native GMS Files]] for a list. For files that are not included in the list, GMS provides the ''Text Import Wizard''.

-	The '''Text Import Wizard''' enables users to import many different types of data into GMS. The Text Import Wizard is initialized by selecting a *.txt file in the '''Open''' command from the '''File''' menu. The wizard has two steps.	+	The ''Text Import Wizard'' enables users to import many different types of data into GMS. The Text Import Wizard is initialized by selecting a *.txt file in the '''''Open''''' command from the ''File'' menu. The wizard has two steps.
	== Step 1 – Delimiting Columns ==		== Step 1 – Delimiting Columns ==

-	The first step in the wizard allows users to delimit the data into columns. Two options exist to delimit the data.	+	The first step in the wizard allows users to delimit the data into columns. Two options exist to delimit the data: '''Delimited''', '''Fixed Width'''.
-		+
-	Delimited	+
-		+
-	Fixed Width	+

	For the Delimited option, typical delimiters are included as well as an option for users to specify a delimiter. Columns can also be specified with a fixed width by clicking on the ruler bar or the window with the data. Break lines can be dragged, and they can be deleted by double-clicking on the break line or dragging them off the screen. The user can specify the starting row the data will be imported at. If your data has a row of headings, you can indicate such and GMS will use the headings in the next step to determine what kind of data each column represents.		For the Delimited option, typical delimiters are included as well as an option for users to specify a delimiter. Columns can also be specified with a fixed width by clicking on the ruler bar or the window with the data. Break lines can be dragged, and they can be deleted by double-clicking on the break line or dragging them off the screen. The user can specify the starting row the data will be imported at. If your data has a row of headings, you can indicate such and GMS will use the headings in the next step to determine what kind of data each column represents.

GMS:Importing Non-native GMS Files

2012-05-18T16:54:16Z

← Older revision		Revision as of 16:54, 18 May 2012
(2 intermediate revisions not shown)
Line 1:		Line 1:
-	GMS can import many files generated by other software in their native format. The files that can be imported to GMS are shown in the tables below. Each file type is identified by the file extension. The file filter corresponding to the desired extension should be selected in the Open File dialog.	+	GMS can import many files generated by other software in their native format. The files that can be imported to GMS are shown in the tables below. Each file type is identified by the file extension. The file filter corresponding to the desired extension should be selected in the ''Open File'' dialog.

	==Text Import Wizard==		==Text Import Wizard==
-	In addition to the file types listed below, several other types of data can be imported via the Text Import Wizard. Refer to the section on the Text Import Wizard for more information.	+	In addition to the file types listed below, several other types of data can be imported via the ''Text Import Wizard''. Refer to the section on the ''Text Import Wizard'' for more information.

	{\| border="1" cellpadding="2"		{\| border="1" cellpadding="2"
Line 9:		Line 9:
	!width="650"\|Description		!width="650"\|Description
	\|-		\|-
-	\|<center>Model Super Files</center>\|\|.mfs, .rsp, .mts, .rts, .sms, .uts, .fws, .ats, .sps\|\|GMS uses super files to help organize model files, which can be numerous. Opening the super file will import the entire model and all associated model files. This will NOT open any GMS specific data, such as Map data or TIN data etc. The file models associated with each super file extension are as follows: .mfs = MODFLOW, .rsp = MODPATH, .mts = MT3DMS, .rts = RT3D, .sms = SEAM3D, .uts = UTCHEM, .fws = FEMWATER, .ats = ART3D, .sps = SEEP2D	+	\|<center>Model Super Files</center>\|\|.mfs, .rsp, .mts, .rts, .sms, .uts, .fws, .ats, .sps\|\|GMS uses super files to help organize model files, which can be numerous. Opening the super file will import the entire model and all associated model files. This will NOT open any GMS specific data, such as Map data or TIN data etc. The file models associated with each super file extension are as follows: .mfs = MODFLOW, .rsp = MODPATH, .mts = MT3DMS, .rts = RT3D, .sms = SEAM3D, .uts = UTCHEM, .fws = FEMWATER, .ats = ART3D, .sps = SEEP2D
	\|-		\|-
-	\|<center>Text files</center>\|\|<center>.txt</center>\|\|Text files where the data is in columns, as you might export from a spreadsheet. This brings up the GMS [[GMS:Text Import Wizard\|Text Import Wizard]]. Many different types of data can be brought in to GMS by using the Text Import Wizard.	+	\|<center>Text files</center>\|\|<center>*.txt</center>\|\|Text files where the data is in columns, as you might export from a spreadsheet. This brings up the GMS [[GMS:Text Import Wizard\|Text Import Wizard]]. Many different types of data can be brought in to GMS by using the Text Import Wizard.
	\|-		\|-
-	\|<center>DXF/DWG</center>\|\|<center>.dxf, .dwg</center>\|\|Vector drawing data used for background display or for conversion to feature objects.	+	\|<center>DXF/DWG</center>\|\|<center>.dxf, .dwg</center>\|\|Vector drawing data used for background display or for conversion to feature objects.
	\|-		\|-
-	\|<center>JPEG - TIFF</center>\|\|<center>.jpg, .tif</center>\|\|Raster image files used for background display or for texture mapping to a surface.	+	\|<center>JPEG - TIFF</center>\|\|<center>.jpg, .tif</center>\|\|Raster image files used for background display or for texture mapping to a surface.
	\|-		\|-
-	\|<center>Shapefiles</center>\|\|<center>.shp</center>\|\|ArcView shapefiles.	+	\|<center>Shapefiles</center>\|\|<center>*.shp</center>\|\|ArcView shapefiles.
	\|-		\|-
-	\|<center>DEM / Grid</center>\|\|<center>.asc, .ddf, .ggd, .dem</center>\|\|ASCII 2D grid exported from Arc/Info or ArcView, , ASCII 2D grid exported from GRASS	+	\|<center>DEM / Grid</center>\|\|<center>.asc, .ddf, .ggd, .dem</center>\|\|ASCII 2D grid exported from Arc/Info or ArcView, ASCII 2D grid exported from GRASS
	\|-		\|-
-	\|<center>Surfer Grid</center>\|\|<center>.grd</center>\|\|ASCII 2D grid exported from Surfer.	+	\|<center>Surfer Grid</center>\|\|<center>*.grd</center>\|\|ASCII 2D grid exported from Surfer.
	\|}		\|}

GMS:Risk Analysis Wizard

2012-05-18T16:51:36Z

Capture Zone Analysis Dialog:

← Older revision		Revision as of 16:51, 18 May 2012
(One intermediate revision not shown)
Line 10:		Line 10:

	==Risk Analysis Wizard Dialogs==		==Risk Analysis Wizard Dialogs==
-	The risk analysis wizard is entered through the right-click menu for a folder in the [[GMS:Project Explorer\|Project Explorer]] and choose ''~~Risk Analysis~~''... .	+	The risk analysis wizard is entered through the right-click menu for a folder in the [[GMS:Project Explorer\|Project Explorer]] and choose '''''Risk Analysis...''''' .

	[[Image:Tree_Risk_Anaylsis.gif]]		[[Image:Tree_Risk_Anaylsis.gif]]
Line 38:		Line 38:
	'''Particle Starting Locations - Distribute particles on water table surface'''		'''Particle Starting Locations - Distribute particles on water table surface'''

-	Choose this option to distribute particles only on the water table surface. By default, one particle is placed at the ''xy'' center of the cell at the water table, but you can use the ''Particle placement within cells'' option to change the number of particles placed on the water table in each cell. This option will create a 2D probabilistic capture zone representing the intersection of the entire 3d probabilistic capture zone with the water table.	+	Choose this option to distribute particles only on the water table surface. By default, one particle is placed at the ''xy'' center of the cell at the water table, but you can use the '''Particle placement within cells''' option to change the number of particles placed on the water table in each cell. This option will create a 2D probabilistic capture zone representing the intersection of the entire 3D probabilistic capture zone with the water table.

	'''Particle Starting Locations - Distribute particles within cells'''		'''Particle Starting Locations - Distribute particles within cells'''

-	Choose this option to distribute particles within each cell. By default, one particle is placed at the center of each cell, but you can use the ''Particle placement within cells'' option to change the number of particles placed on within each cell. This option creates three different probabilistic capture zones. The first represents the 3D capture zone, the other two represent different 2D projections of the 3D capture zone.	+	Choose this option to distribute particles within each cell. By default, one particle is placed at the center of each cell, but you can use the '''Particle placement within cells''' option to change the number of particles placed on within each cell. This option creates three different probabilistic capture zones. The first represents the 3D capture zone, the other two represent different 2D projections of the 3D capture zone.

	'''Tracking Duration - To end'''		'''Tracking Duration - To end'''

GMS:Gaussian Field Generator

2012-05-18T16:43:20Z

Running the Simulation:

← Older revision		Revision as of 16:43, 18 May 2012
(2 intermediate revisions not shown)
Line 19:		Line 19:
	== Gaussian Simulation Options ==		== Gaussian Simulation Options ==

-	The first step in setting up a GSS is to import a set of scatter points with the values to which you intend to condition your simulation. This step can be skipped if you have no conditioning data. The next step is to select the '''''Gaussian Simulation Options''''' command in the ''Interpolation'' menu in the ''2D Scatter Point'' module. This brings up the following dialog:	+	The first step in setting up a GSS is to import a set of scatter points with the values to which you intend to condition your simulation. This step can be skipped if you have no conditioning data. The next step is to select the '''''Gaussian Simulation Options''''' command in the ''Interpolation'' menu in the 2D Scatter Point module. This brings up the following dialog:

	[[Image:gaussian_sim_options.gif\|frame\|center\|320px]]		[[Image:gaussian_sim_options.gif\|frame\|center\|320px]]


-	The '''Solution name''' at the top is the name that will be applied to the set of Gaussian fields. The '''Number of realizations''' item is the desired number of Gaussian fields. The original GSLIB code was designed to work with uniform grids (constant cell sizes). The '''Non-uniform grid''' option controls how the data are converted to a non-uniform grid (if necessary). The '''''Edit Variogram''''' button should be selected to set up a model variogram using the GMS [[GMS:Variogram Editor\|variogram editor]]. A model variogram must be defined whether or not you have scatter points for conditioning.	+	The '''Solution name''' at the top is the name that will be applied to the set of Gaussian fields. The '''Number of realizations''' item is the desired number of Gaussian fields. The original GSLIB code was designed to work with uniform grids (constant cell sizes). The '''Non-uniform grid''' option controls how the data are converted to a non-uniform grid (if necessary). The '''Edit Variogram''' button should be selected to set up a model variogram using the GMS [[GMS:Variogram Editor\|variogram editor]]. A model variogram must be defined whether or not you have scatter points for conditioning.

	== Running the Simulation ==		== Running the Simulation ==

-	Once the GSS options are selected, the next step is to run the simulation. This is accomplished by selecting the Run Gaussian Simulation command in the Interpolation menu. During the simulation, you should see a window displaying the progress of the simulation:	+	Once the GSS options are selected, the next step is to run the simulation. This is accomplished by selecting the '''''Run Gaussian Simulation''''' command in the ''Interpolation'' menu. During the simulation, you should see a window displaying the progress of the simulation:

	[[Image:gaussian_fieldgen_wrapper.gif\|frame\|center\|250px]]		[[Image:gaussian_fieldgen_wrapper.gif\|frame\|center\|250px]]

GMS:Stochastic Modeling

2012-05-18T16:41:34Z

Using Indicator Simulations With Stochastic Modeling:

← Older revision		Revision as of 16:41, 18 May 2012
(2 intermediate revisions not shown)
Line 7:		Line 7:
	One approach for dealing with model heterogeneity is stochastic simulations based on multiple equally plausible candidate realizations of the site heterogeneity. Ideally, such an approach would enable the generation of variability in subsurface soil stratigraphy based on interpretable geologic parameters such as lens width, material proportions, juxta-positioning tendencies and anisotropy. Multiple realizations that are conditioned to borehole data provide modelers with a rational approach for dealing with uncertainty associated with site characterization. Stochastic simulations can be applied to regional representations of the aquifer behavior in addition to local scale simulations. Stochastic simulations are particularly well-suited to local scale models since the resulting complex heterogeneity is more representative of actual stratigraphic deposition. This heterogeneity makes realistic and potentially more accurate contaminant transport simulation possible by simulating the preferential flow channels resulting from thin lenses of clays, sands, or other materials. The ultimate result of a stochastic approach is multiple simulations of hydraulic parameters that create a probabilistic solution. Such a solution has more credence and provides a better understanding of actual site conditions.		One approach for dealing with model heterogeneity is stochastic simulations based on multiple equally plausible candidate realizations of the site heterogeneity. Ideally, such an approach would enable the generation of variability in subsurface soil stratigraphy based on interpretable geologic parameters such as lens width, material proportions, juxta-positioning tendencies and anisotropy. Multiple realizations that are conditioned to borehole data provide modelers with a rational approach for dealing with uncertainty associated with site characterization. Stochastic simulations can be applied to regional representations of the aquifer behavior in addition to local scale simulations. Stochastic simulations are particularly well-suited to local scale models since the resulting complex heterogeneity is more representative of actual stratigraphic deposition. This heterogeneity makes realistic and potentially more accurate contaminant transport simulation possible by simulating the preferential flow channels resulting from thin lenses of clays, sands, or other materials. The ultimate result of a stochastic approach is multiple simulations of hydraulic parameters that create a probabilistic solution. Such a solution has more credence and provides a better understanding of actual site conditions.

-	The ultimate application of T-PROGS is to generate stochastic simulations of soil heterogeneity. These realizations can then be incorporated into MODFLOW simulations as ''material sets'' in the [[GMS:LPF Package\|LPF package]] or as ''HUF data'' in the [[GMS:HUF Package\|HUF package]]. (See [[GMS:T-PROGS\|T-PROGS]])	+	The ultimate application of T-PROGS is to generate stochastic simulations of soil heterogeneity. These realizations can then be incorporated into MODFLOW simulations as "material sets" in the [[GMS:LPF Package\|LPF package]] or as "HUF data" in the [[GMS:HUF Package\|HUF package]]. (See [[GMS:T-PROGS\|T-PROGS]])

	==Stochastic Inverse Modeling==		==Stochastic Inverse Modeling==
	Stochastic inverse modeling is a [[GMS:Global Options/Basic Package\|MODFLOW run option]] that takes each run in a stochastic simulation and performs [[GMS:Automated Parameter Estimation\|parameter estimation]] on the run to find the optimal values based on observation data. This option is very time consuming compared with a regular stochastic simulation and a parameter estimation run because you are doing parameter estimation for each stochastic run times.		Stochastic inverse modeling is a [[GMS:Global Options/Basic Package\|MODFLOW run option]] that takes each run in a stochastic simulation and performs [[GMS:Automated Parameter Estimation\|parameter estimation]] on the run to find the optimal values based on observation data. This option is very time consuming compared with a regular stochastic simulation and a parameter estimation run because you are doing parameter estimation for each stochastic run times.

-	Stochastic inverse modeling can be performed only when using [[#Using Indicator Simulations With Stochastic Modeling\|material sets or HUF arrays]] as chosen in the Stochastic Options dialog. [[GMS:Automated Parameter Estimation\|PEST]] is the parameter estimation code supported by GMS.	+	Stochastic inverse modeling can be performed only when using [[#Using Indicator Simulations With Stochastic Modeling\|material sets or HUF arrays]] as chosen in the ''Stochastic Options'' dialog. [[GMS:Automated Parameter Estimation\|PEST]] is the parameter estimation code supported by GMS.

	The following occurs during the stochastic inverse process:		The following occurs during the stochastic inverse process:
Line 28:		Line 28:

	===Parameter Randomization===		===Parameter Randomization===
-	This option uses parameters defined in Parameters Dialog.	+	This option uses parameters defined in ''Parameters'' Dialog.

	===Material Sets===		===Material Sets===
Line 48:		Line 48:
	*[[GMS:Automated Parameter Estimation#4. Define Parameter Zones\|Define parameters]] that link with your zones.		*[[GMS:Automated Parameter Estimation#4. Define Parameter Zones\|Define parameters]] that link with your zones.

-	*Select the Stochastic Simulation option from the [[GMS:Global Options/Basic Package\|Global Options]] dialog.	+	*Select the '''Stochastic Simulation''' option from the [[GMS:Global Options/Basic Package\|''Global Options'']] dialog.

-	*Select the Parameter Randomization option from the Stochastic Options dialog.	+	*Select the Parameter Randomization option from the ''Stochastic Options'' dialog.

-	*Choose whether you want to use the Random Sampling or Latin Hypercube randomization approaches in the ~~parameters~~ dialog.	+	*Choose whether you want to use the Random Sampling or Latin Hypercube randomization approaches in the ''Parameters'' dialog.

	*Save and Run your model.		*Save and Run your model.
Line 91:		Line 91:
	<math>\prod_{i=1}^n P_i</math>		<math>\prod_{i=1}^n P_i</math>

-	number of simulations, where n is the number of parameters and P is the number of segments for the ith parameter. For example, if there were three ~~parameter~~ with four, four and five segments, the number of model runs would be as follows:	+	number of simulations, where n is the number of parameters and P is the number of segments for the ith parameter. For example, if there were three parameters with four, four, and five segments, the number of model runs would be as follows:

	<!--[[Image:comb_example.gif]]-->		<!--[[Image:comb_example.gif]]-->
Line 103:		Line 103:
	*Generate Material Sets or HUF data using [[GMS:T-PROGS\|T-PROGS]].		*Generate Material Sets or HUF data using [[GMS:T-PROGS\|T-PROGS]].

-	*Select the Stochastic Simulation from the [[GMS:Global Options/Basic Package\|Global Options Dialog]].	+	*Select the '''Stochastic Simulation''' from the [[GMS:Global Options/Basic Package\|''Global Options'' Dialog]].

-	*Enter the Stochastic... dialog from the MODFLOW menu.	+	*Enter the ''Stochastic...'' dialog from the ''MODFLOW'' menu.

	*Select the Material Sets option and choose the appropriate material set or HUF data simulation.		*Select the Material Sets option and choose the appropriate material set or HUF data simulation.

GMS:Standard MODFLOW Parameters

2012-05-18T16:32:47Z

MODFLOW Parameter Clusters Dialog:

GMS:Pilot Points

2012-05-18T16:29:55Z

← Older revision		Revision as of 16:29, 18 May 2012
Line 13:		Line 13:

	===Pilot Point Conditioning===		===Pilot Point Conditioning===
-	For pilot point interpolation of hydraulic conductivity, it is sometimes useful to include one or more measured K values with the pilot point set. These measured values could represent K values extracted from a field pump test. The Pilot Point Conditioning option is available to represent this scenario. One of the properties associated with scatter points is a Fixed pilot point toggle. If this toggle is on and the corresponding scatter point set is used for pilot point interpolation, the K value assigned to the point is not allowed to vary during the parameter estimation process.	+	For pilot point interpolation of hydraulic conductivity, it is sometimes useful to include one or more measured K values with the pilot point set. These measured values could represent K values extracted from a field pump test. The Pilot Point Conditioning option is available to represent this scenario. One of the properties associated with scatter points is a '''Fixed pilot point''' toggle. If this toggle is on and the corresponding scatter point set is used for pilot point interpolation, the K value assigned to the point is not allowed to vary during the parameter estimation process.

	[[Image:Pilot_Point_Cond.gif\|frame\|center\|180px]]		[[Image:Pilot_Point_Cond.gif\|frame\|center\|180px]]

GMS:Parameter Dialog

2012-05-18T16:28:53Z

BSCAL:

← Older revision		Revision as of 16:28, 18 May 2012
Line 57:		Line 57:
	MODFLOW documentation includes:		MODFLOW documentation includes:

-	This value is an alternate scaling factor for the parameter, and always needs to be a positive number. If the parameter value becomes 0.0, which can occur for parameters that are not log transformed, BSCAL is used in the scaling. If the absolute value of the parameter is less than BSCAL, BSCAL is used in the scaling. The best value to use is problem dependant. Good choices are the smallest reasonable value of the parameter or a value two to ~~threee~~ orders of magnitude smaller than the value specified by the starting value. If the smallest reasonable value is 0.0, a reasomable non-zero value needs to be used. BSCAL has no effect on the scaled sensitivities for log-transformed parameters.	+	This value is an alternate scaling factor for the parameter, and always needs to be a positive number. If the parameter value becomes 0.0, which can occur for parameters that are not log transformed, BSCAL is used in the scaling. If the absolute value of the parameter is less than BSCAL, BSCAL is used in the scaling. The best value to use is problem dependant. Good choices are the smallest reasonable value of the parameter or a value two to three orders of magnitude smaller than the value specified by the starting value. If the smallest reasonable value is 0.0, a reasomable non-zero value needs to be used. BSCAL has no effect on the scaled sensitivities for log-transformed parameters.

	===Multiplier===		===Multiplier===

← Older revision		Revision as of 17:27, 18 May 2012
Line 83:		Line 83:
	*crashes at end of MODFLOW Translator run - User: David Li		*crashes at end of MODFLOW Translator run - User: David Li
	*crash when selecting multiple 3d mesh nodes - User: Lance Jones		*crash when selecting multiple 3d mesh nodes - User: Lance Jones
-	*Problem opening “.bas” file in GMS 8.1.6 32-Bit which opens in 8.1.6 64-bit - User: Mary Halstead	+	Problem opening “.bas” file in GMS 8.1.6 32-Bit which opens in 8.1.6 64-bit - User: Mary Halstead
	*select cross section and then delete from project explorer		*select cross section and then delete from project explorer
	*Starting head values aren't saved after running the model.		*Starting head values aren't saved after running the model.
Line 207:		Line 207:
	*GMS hangs after running SEEP2D.		*GMS hangs after running SEEP2D.
	== Intermediate Release GMS 8.0.9 - Aug 9, 2011 ==		== Intermediate Release GMS 8.0.9 - Aug 9, 2011 ==
-	*Crash when loading .gpr file - User: Emanual Amen Storey	+	Crash when loading .gpr file - User: Emanual Amen Storey
	*Generating MODPATH pathlines takes up more than 2-3 GB of RAM - Jack Dahl		*Generating MODPATH pathlines takes up more than 2-3 GB of RAM - Jack Dahl
	*Interpolate To \| MODFLOW Layers command does not run successfully - User: Jack Dahl		*Interpolate To \| MODFLOW Layers command does not run successfully - User: Jack Dahl
Line 489:		Line 489:
	== Intermediate Release GMS 7.1.1 - March 15, 2010 ==		== Intermediate Release GMS 7.1.1 - March 15, 2010 ==
	* Unable to extract 2D water table from FEMWATER. - James Bellin		* Unable to extract 2D water table from FEMWATER. - James Bellin
-	* Double-click on project (.gpr) file doesn't load it in GMS.	+	* Double-click on project (*.gpr) file doesn't load it in GMS.
	* Unable to convert CCF file to data sets. - Griet Heuvelman		* Unable to convert CCF file to data sets. - Griet Heuvelman
	* Color fill won't display correctly for pore pressure in SEEP2D.		* Color fill won't display correctly for pore pressure in SEEP2D.

← Older revision		Revision as of 17:00, 18 May 2012
(One intermediate revision not shown)
Line 1:		Line 1:
	[[Image:image166.jpg\|right\|300px]]		[[Image:image166.jpg\|right\|300px]]
-	The '''Import USGS DEMs''' dialog is used to examine the limits of DEM files as well as defining a clipping boundary to eliminate regions outside the area of interest prior to actually reading the elevations in. The '''Add''' button is used to add a new file to the list of files (you can now select multiple DEM files at the same time rather than adding them one at a time, but they must all be of the same format) that will be read. The standard file opening dialog appears from which you may select DEM files. Once the file(s) are added to the list a bounding rectangle is displayed in the small graphics window in the center of the dialog. As additional files are added the graphics region is updated with new rectangles in order to provide an understanding of where DEMs are located in relation to one another.	+	The ''Import USGS DEMs'' dialog is used to examine the limits of DEM files as well as defining a clipping boundary to eliminate regions outside the area of interest prior to actually reading the elevations in. The '''Add''' button is used to add a new file to the list of files (you can now select multiple DEM files at the same time rather than adding them one at a time, but they must all be of the same format) that will be read. The standard file opening dialog appears from which you may select DEM files. Once the file(s) are added to the list a bounding rectangle is displayed in the small graphics window in the center of the dialog. As additional files are added the graphics region is updated with new rectangles in order to provide an understanding of where DEMs are located in relation to one another.

	A small black rectangle is displayed in the central graphics window. Only elevation points inside this rectangular region will be read in when hitting OK from this dialog. This boundary rectangle can be modified in three different ways.		A small black rectangle is displayed in the central graphics window. Only elevation points inside this rectangular region will be read in when hitting OK from this dialog. This boundary rectangle can be modified in three different ways.
Line 16:		Line 16:
	'''NOTE:''' This option does not change the base planimetric units of the DEM and you should make the elevation units consistent with the planimetric units in order to ensure that slopes are computed properly when computing basin geometric parameters.		'''NOTE:''' This option does not change the base planimetric units of the DEM and you should make the elevation units consistent with the planimetric units in order to ensure that slopes are computed properly when computing basin geometric parameters.

-	At the bottom of this dialog the total number of DEM points from all DEM files which have been added and the approximate number of points inside the bounding rectangle are displayed. These numbers can be used to determine how many points your system is capable of reading. For example, each DEM point requires 5 bytes of memory, so that if you read an entire 1:250,000 DEM with about 1.4 million points, 1.4 meg * 5 bytes = 7 meg of memory would be required (in addition to whatever other memory being used by ~~WMS~~). This means that you would need at least 8 meg of RAM, or some type of virtual memory capabilities would be required to read in the entire DEM file.	+	At the bottom of this dialog the total number of DEM points from all DEM files which have been added and the approximate number of points inside the bounding rectangle are displayed. These numbers can be used to determine how many points your system is capable of reading. For example, each DEM point requires 5 bytes of memory, so that if you read an entire 1:250,000 DEM with about 1.4 million points, 1.4 meg * 5 bytes = 7 meg of memory would be required (in addition to whatever other memory being used by GMS). This means that you would need at least 8 meg of RAM, or some type of virtual memory capabilities would be required to read in the entire DEM file.

-	This same dialog is used for all five types of DEMs supported in the ~~WMS~~ import options: USGS, ARC/INFO®, GRASS, DTED, and SDTS.	+	This same dialog is used for all five types of DEMs supported in the GMS import options: USGS, ARC/INFO®, GRASS, DTED, and SDTS.

	===DEMs in Different UTM Zones===		===DEMs in Different UTM Zones===
-	Occasionally two adjacent USGS DEM files will be read in but do not appear adjacent in the import dialog. This occurs because while the two DEMs are adjacent, they lie in different UTM zones. X coordinates within UTM zones repeat and therefore the DEMs do not lie adjacent to one another as they should. WMS does not contain the utility functions necessary to transform a DEM from one UTM coordinate zone to another. However, ~~WMS~~, ARC/INFO® and possibly other GIS software can be used to convert from one zone to another.	+	Occasionally two adjacent USGS DEM files will be read in but do not appear adjacent in the import dialog. This occurs because while the two DEMs are adjacent, they lie in different UTM zones. X coordinates within UTM zones repeat and therefore the DEMs do not lie adjacent to one another as they should. WMS does not contain the utility functions necessary to transform a DEM from one UTM coordinate zone to another. However, GMS, ARC/INFO® and possibly other GIS software can be used to convert from one zone to another.

	{{Navbox GMS}}		{{Navbox GMS}}
	[[Category:GMS General Information]]		[[Category:GMS General Information]]
	[[Category:Importing Data]]		[[Category:Importing Data]]

← Older revision		Revision as of 16:32, 18 May 2012
(2 intermediate revisions not shown)
Line 15:		Line 15:

	===Editing===		===Editing===
-	When GMS reads a model that uses standard MODFLOW parameters it converts them to regular GMS key value approach parameters. The parameters can then be edited using the Parameters Dialog. Recharge, evapotranspiration, LPF, and HUF parameters are special in that you can edit the instance and cluster information associated with these types of parameters.	+	When GMS reads a model that uses standard MODFLOW parameters it converts them to regular GMS key value approach parameters. The parameters can then be edited using the ''Parameters'' Dialog. Recharge, evapotranspiration, LPF, and HUF parameters are special in that you can edit the instance and cluster information associated with these types of parameters.

	==MODFLOW Parameter Clusters Dialog==		==MODFLOW Parameter Clusters Dialog==

-	The MODFLOW Parameter Clusters Dialog allows users to define instances for RCH, EVT, LPF, and HUF parameters that use clusters. The inputs in this dialog basically follow the necessary inputs for defining a parameter instance in a package file. You may wish to review the [[#MODFLOW Parameter Clusters and Instances\|MODFLOW Parameter Clusters and Instances]] section below.	+	The ''MODFLOW Parameter Clusters'' Dialog allows users to define instances for RCH, EVT, LPF, and HUF parameters that use clusters. The inputs in this dialog basically follow the necessary inputs for defining a parameter instance in a package file. You may wish to review the [[#MODFLOW Parameter Clusters and Instances\|MODFLOW Parameter Clusters and Instances]] section below.

	Array based parameters are defined using clusters. A cluster is a multiplier array, a zone array, and specified zone values where the parameter is applied. Multiplier arrays and zone arrays have associated data sets underneath the three dimensional grid in the Project Explorer.		Array based parameters are defined using clusters. A cluster is a multiplier array, a zone array, and specified zone values where the parameter is applied. Multiplier arrays and zone arrays have associated data sets underneath the three dimensional grid in the Project Explorer.
Line 25:		Line 25:
	Instances are enabled for RCH and EVT parameters. Instances allow the user to define multiple sets of clusters that are all tied to one parameter. Then the user may use different instances in different stress periods in their MODFLOW model. For more information on parameter instances consult the MODFLOW documentation.		Instances are enabled for RCH and EVT parameters. Instances allow the user to define multiple sets of clusters that are all tied to one parameter. Then the user may use different instances in different stress periods in their MODFLOW model. For more information on parameter instances consult the MODFLOW documentation.

-	In the MODFLOW Parameters dialog the user selects the "Define clusters" option for a parameter. This will allow the user to specify the number of instances and clusters that are used to define the parameter.	+	In the MODFLOW Parameters dialog the user selects the '''Define clusters''' option for a parameter. This will allow the user to specify the number of instances and clusters that are used to define the parameter.

	{{hide in print\|[[Image:ParametersDialog.png\|640px]]}}		{{hide in print\|[[Image:ParametersDialog.png\|640px]]}}
Line 31:		Line 31:


-	In the Parameter Instances dialog the user defines a name for each parameter instance for RCH and EVT parameters. For LPF parameters a level is defined and for HUF parameters a hyrdogeologic unit is defined. Then for each cluster the user selects a multiplier array and a zone array. These are [[GMS:Data Sets\|data sets]] on the 3D Grid. The user must also specify the zone values (IZ) where the parameter is to be applied in the model. If there is more than one IZ value for the cluster then the user enters the numbers with spaces between the entries. So if the parameter is to be applied where the zone array values are 1 and 3 then the user would enter "1 3". The user must also specify the stress periods where an instance is to be used. The numbers entered in the Stress Periods field should also be space delimited. This means if you want an instance to be used in stress periods 1, 2, and 5 then your entry in the Stress Periods field should be "1 2 5".	+	In the ''Parameter Instances'' dialog the user defines a name for each parameter instance for RCH and EVT parameters. For LPF parameters a level is defined and for HUF parameters a hyrdogeologic unit is defined. Then for each cluster the user selects a multiplier array and a zone array. These are [[GMS:Data Sets\|data sets]] on the 3D Grid. The user must also specify the zone values (IZ) where the parameter is to be applied in the model. If there is more than one IZ value for the cluster then the user enters the numbers with spaces between the entries. So if the parameter is to be applied where the zone array values are 1 and 3 then the user would enter "1 3". The user must also specify the stress periods where an instance is to be used. The numbers entered in the Stress Periods field should also be space delimited. This means if you want an instance to be used in stress periods 1, 2, and 5 then your entry in the Stress Periods field should be "1 2 5".

	When the package is written out for MODFLOW the instances will be included in the parameter definition and used for forward runs or for parameter estimation runs.		When the package is written out for MODFLOW the instances will be included in the parameter definition and used for forward runs or for parameter estimation runs.