Jump to content
GMS, SMS, and WMS User Forum

Bill Dolinar

GMS Development Team
  • Posts

  • Joined

  • Last visited

Everything posted by Bill Dolinar

  1. From the error numbers it looks like the model is failing to converge and crashing. If you could pass the model on to tech support we could take a look at the model files saved in 10.3.5 and 10.3.7 to make sure there aren't any differences. We could also pass the model on to the model developers to see if they have ideas.
  2. In MODFLOW-2005 and related flavors of MODFLOW there is a BAS package "CONVERGE" option that forces converges so the model will keep running if any time step fails to converge which can be useful to prevent termination of parameter estimation runs. Add support for this option to GMS.
  3. Michal, It would be possible to change mapping with a layer range to work when the covered column of cells all have the same plan view discretization like you mention. I've added a feature request. There would have to be the same discretization for the covered cells for the entire layer range. If mapping found mapped segments or areas that aren't identically discretized as a cell column, mapping would stop and give an error. It would also need to require that in a layer range, the top layer's cells completely cover all of the cells of the layers below. It would be complicated to intersect an arc or polygon with the cells in multiple layers and then make sure a portion didn't get mapped more than once. Thanks, Bill
  4. Allow specified flow in a conceptual model with a layer range to be mapped to MODFLOW-USG with a unstacked UGrid. See following post:
  5. Thanks for reporting this. We've fixed the issue and added a test. The fix should be in the next release of GMS.
  6. Splitting the one row or one column should work.
  7. This is a bug where if the model has only one row or one column of cells then the error incorrectly showed. This should be fixed in the next release of GMS 10.3.
  8. For interpolate to MODFLOW Layers, add the ability to interpolate to EVT arrays.
  9. Sounds like a bug. When I try the same thing with the latest release of GMS 10.2 it works for me. Looks like there's something specific to your setup or project. If you could contact tech support (support@aquaveo.com) they could help with tracking down the issue.
  10. It sounds like the values haven't been entered as a step function. It's taking the values at the beginning of the stress period and the end of the stress period and averaging them. When you enter the values as step functions like shown in the attached image, then no averaging is done. The "Managing Transient Data" tutorial (http://aquaveo.com/software/gms-learning-tutorials) has more info.
  11. The way it currently works is as intended. For shapefiles, exported points are those that aren't associated with an arc. Nodes are exported with the arcs. It is possible to get at the X, Y, and Z values along with stage and elevation by right clicking on the coverage, selecting Attribute Table, changing the Feature type to Nodes and then turning on Show coordinates. Then the X, Y, and Z values could be copied along with stage and elevation by clicking in a cell and typing control-A to select all, and control-C to copy.
  12. Matt, When I try interpolate to layers in the latest version of GMS (10.2.3) with an adf file it works for me. It may be a problem that is specific to your project. Can you contact support@aquaveo.com? We will take a look at your files and see if we can figure out what's going on.
  13. The bug fix in 10.0.6 had to do with an error converting the raster values from meters to feet. Are the values you see different by a multiple of 3.28? If you select the Display | Display Projection... menu item in your project, are the vertical units feet while the raster is in meters? It may be that the grid and coverages in your model are in the incorrect units and need to be adjusted. The display units should be the same as your planning on using for your model. After making sure the units for the display are correct the projection and units for the grid and coverages could be changed by right clicking on them in the Project Explorer, selecting the Projection | Projection... menu item, and adjusting the values. It also may be a bug that is specific to your project. If so, could you contact support@aquaveo.com? We will take a look at your files and see if we can figure out what's going on.
  14. The legend scales the portion between the numbers by the difference or interval size. For intervals shown, the intervals between the numbers would be 1.0e5, 9.0e5, and 1.0e5, making the interval between 1.0e5 and 1.0e6 much larger.
  15. When you go to the MODFLOW | Flow Budget dialog does it show line items for flow it's complaining about? Also, what version of MODFLOW are you using? The only way I can think of this happening is if the model was somehow run to generate a CCF file, but not generate the flow across faces. When running MODFLOW from GMS and generating a CCF file, the flow package is automatically set to output flow across cell faces. If the model was ran outside of GMS and the solution manually read in, it could be that the flow package wasn't set to output CCF data but other packages were. If so, the flow package needs to have CCF output turned on. If the model was generated and ran from within GMS, you could contact Aquaveo Tech Support (http://www.aquaveo.com/technical-support) for help.
  16. You could try adjusting the PCG solver values (MODFLOW | PCG - Pre. Conj. Gradient Solver menu item) to get it to converge (see http://water.usgs.gov/nrp/gwsoftware/modflow2000/MFDOC/index.html?pcg.htm). Some changes that might help include: increasing the number of outer iterations, setting the damping lower (1.0 is the default and it should be between 0.0 and 1.0), adjusting the relaxation, and making sure HCLOSE and RCLOSE values make sense for your model.
  17. It sounds like you want to use ft for your model. You should change the units in Edit | Units to ft to get the model and coverage inputs to be correct. To get the values from the rasters in feet you should set the display projection to the projection and units you want use for the coverages and grid (using the Display | Display Projection... menu item). GMS will automatically convert the raster data to the display projection when interpolating from the raster. More info on this can be found in the Projections/Coordinate Systems tutorial (http://www.aquaveo.com/software/gms-learning-tutorials).
  18. Normally the translator output should look something shown in the attached image saying that SEAWAT terminated successfully. When there is an error during translation the output in the window can give clues to what caused the error. What does the output look like when you run the translator?
  19. It sounds like it may potentially be a bug in SEAWAT. If you could contact Aquaveo tech support (support@aquaveo.com) we can take a look. If it's a bug in SEAWAT we can let the author know about it. There may also be some way to workaround the bug.
  20. From the screenshot of the SEAWAT dialog it appears SEAWAT finished successfully. Does the "Premature end of file..." message appear after closing the SEAWAT dialog? Does it say anything else in the message? You could find out more info about how SEAWAT ran by opening and inspecting the model3_sw.out file in a text editor. The model3_sw.out file would be in the model3_sw_MODFLOW folder. You could view it by opening NotePad and then dragging the file onto NotePad.
  21. To renumber the 2D mesh, select the 2D mesh in the Project Explorer (under 2D Mesh Data), and select the Mesh | Renumber menu item. An alert will pop up saying: "No nodestrings selected. Renumber anyway?" Hit OK to renumber the entire mesh. Then you should be able to build the 3D mesh.
  22. Trying the option to save a native text copy (select MODFLOW | Global Options... menu then toggle on Save native text copy) should work. Then when you save the project it should give you a text export in a new folder along side the GMS MODFLOW folder. This could be caused by changes in the STR file format with the 1.11.00 release of MODFLOW-2005. With MODFLOW-2005 v1.11.00 the format used for the STR package changed from always fixed format (where numbers running together could be read by MODFLOW) to either fixed or free format depending on the Basic package setting. GMS saves MODFLOW files using free format. The native text export should work with either fixed or free format so it could also be read by older versions of MODFLOW-2005.
  23. You could maybe read the tif file in GMS, convert the raster data to scatter data, export the data, use Excel to combine the data to points with elevation and conductance, and then copy and paste the values into a coverage. More detailed steps: Read tif into GMS by dragging and dropping the file onto GMS. Convert the raster to a 2D scatter set by right clicking on the raster and selecting the Convert To | 2D Scatter menu item. Export the values by right clicking on the 2D Scatter dataset, selecting the View Values menu item, and then clicking on the Export button at the bottom of the dialog. Open the exported data file in Excel. In GMS create a MODFLOW conceptual model with Drains turned on by right clicking in the Project Explorer and selecting the New | Conceptual Model menu item, and toggling on Drains. Create a new coverage by right clicking on the conceptual model in the Project Explorer and selecting the New Coverage menu item. Open the coverage attribute table by right clicking on it and selecting the Attribute Table menu item. Turn on the X, Y, Z columns in the attribute table by toggling on Show coordinates. Copy the X, Y columns from Excel. Paste the X, Y columns into the attribute table. In the All row in the attribute table change the type to Drain. Copy the conductance and elevation columns from Excel. Paste the the values into the attribute table. Now the coverage can be used to map the values to MODFLOW. The same steps could be used for the river package data into a new coverage. This assumes that the raster pixels match the MODFLOW grid and that the cells without boundary conditions are masked out of the raster.
  24. If you're using GMS 10.0 or later, one thing you could try is turning on "save native text copy" found in the MODFLOW Global/Basic Package dialog (MODFLOW | Global Options... menu item), and then saving the project. A new folder will be created along side the GMS MODFLOW folder with a native text export. It may also be that the error is specific to your particular model. You could contact tech support at support@aquaveo.com for additional help.
  25. The layer range can be used to assign one to many layers over which a boundary condition is applied. When turned on, three fields are added to the attribute table including Auto assign layer, From layer, and To layer. If you would like to use your shape file to determine the well layer you could turn this on, set Auto assign layer to Use layer range, and then map the layer field from the shape file to the from and to layer fields. When "Use to define model boundary" is checked, any polygons defined in the coverage get added to the model area that is used when running the "Activate Cells in Coverage(s)" command. For no flow boundary cells a majority of the cell has to be with a polygon for it to be active. For specified head cells if any portion of the cell is inside a boundary polygon then it is activated. The "Activate Cells in Coverage(s) command is described in more detail here: http://www.xmswiki.com/wiki/GMS:Activate_Cells_in_Coverage.
  • Create New...