Jump to content
GMS, SMS, and WMS User Forum

Bill Dolinar

GMS Development Team
  • Posts

  • Joined

  • Last visited

About Bill Dolinar

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Bill Dolinar's Achievements


Newbie (1/14)



  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.
  • Create New...