Alan Lemon

GMS Development Team
  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by Alan Lemon

  1. This functionality of this package will be available in MODFLOW 6. A new version of MODFLOW that will become the "new" main version of MODFLOW (like MODFLOW 2005). It has not been formally released yet but should be available in the fall of 2017.
  2. Once you have imported the MODFLOW solution you should see a CCF item in the project explorer. Right click on the CCF item and choose the CCF->Datasets command. You should see a RIVER LEAKAGE dataset. Select the cell with the data set and then choose the Display | Plot Wizard command. Select the Active Dataset Timeseries plot and then click on Finish. You should now see a plot of river leakage for the selected cell. Right click on the plot and select View Values if you want to copy the data elsewhere.
  3. The plot tells you information about the dataset. The histogram tells you the number of values in the data set within different ranges. I personally don't fine the histograms terribly helpful when doing a seepage problem. I look at contours and values on the mesh itself.
  4. Can you tell us how you created these plots? What commands did you make in GMS to create them. It is not clear to me what you are looking at or trying to do.
  5. I don't think there is a problem contouring datasets in GMS. My guess is that the values in the datasets that you are trying to contour do not vary much. For example, maybe there is a value of 1 at the cell where the well is and all of the other cells have a value of 0. I would create a MODPATH model for one of the wells and see how it changes when you change to the various MODFLOW outputs.
  6. If you have not done so already please contact to look at your project.
  7. You can create parameters from the values of HK assigned to the materials. Then use the parameters dialog for these HK parameters just as you did the RCH parameters.
  8. Those are dataset that you should be able to contour. If something is still not working you should contact
  9. From looking at the code it looks like the warning means that there is something wrong with the input lag parameters and that the kriging code could not find points to create the variogram. As to your second question... The experimental variograms are used as a guide to create a model variogram. This is the variogram used to do the interpolation. I am guessing that your model variograms would be quite different if compared logarithmic to non-logarithmic.
  10. The solids to MODFLOW command will create the HK data for the LPF package. The HK array can then be contoured. Currently, there are no tools in GMS for creating a dataset of HK values from the HUF package. If your HUF data was created from solids, you could use the Solids->MODFLOW command to generate an HK array with the LPF package so that you could visuallize the HK data.
  11. If you have not done so already, you should contact to check your model.
  12. The documentation for GMS is available at this website: or as a help file in the installation directory. The file is called GMS_Help.chm.
  13. A first pass of this is available in GMS 10.3.
  14. This has been implemented in the development version of GMS and will be included in GMS 10.3.
  15. This has been implemented in the development version of GMS and will be released in GMS 10.3.
  16. This has been implemented in the development version and will be included in the next release of GMS (10.3).
  17. The iConcINTP variable has been implemented. The name of the point has also been added to the comment section of the TOB file. Both of these have been implemented in the development version and will be in the next version of GMS.
  18. The recharge mapping has also been implemented in the development version of GMS. We will also have a tutorial that explains how it works with USG.
  19. pht3d

    GMS doesn't interact with this file. So if you have a simulation that uses this file you can copy it to the appropriate directories before PHT3D runs.
  20. You are correct. Currently there is just one display property for all shape files. We do plan to change this is future versions of GMS.
  21. A first pass integration with MT3D-USGS has been implemented in our development version and will be released in the next version of GMS (10.3). Additional packages for MT3D-USGS will be added to future versions of GMS.
  22. This has been implemented in our development version and will be in the next release of GMS. (Most likely 10.3)
  23. Currently there is no transport available for MODFLOW-USG except for mod-PATH3DU. Hopefully, the USGS will release a version of MODFLOW-USG with the transport package.
  24. If you open the *.out file for the MODFLOW simulation can you tell if MODFLOW terminated successfully?
  25. After doing a "deep dive" into the Map->MODFLOW code we have decided that adding the <Cell top>, <Cell bottom> is not the best way to address this issue. Part of the problem is that we like to keep the data completely independent of the grid in the conceptual model. Also, we have an option to auto assign the layer based on elevation. I not sure how that could work with the <Cell top>, <Cell bottom> option. If you really want to make sure that your boundary conditions get the same value that is assigned to the grid top or bottom you can convert the MODFLOW grid to scatter points using the Grid | MODFLOW Layers -> Scatter Points command. Then you can convert the scatter to a TIN and that TIN can be associated with your boundary condition. This should make it so you boundary conditions get the same value assigned to the grid cell and you won't have to do any extra processing outside of GMS.