Jump to content
GMS, SMS, and WMS User Forum

Todd Wood

  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by Todd Wood

  1. HorizonID

    The "Auto-Assign Horizon" tool referenced on the wiki is currently only available in GMS (the Groundwater Modeling System). When using this tool, it is important to review the results since they can often have problems with complex borehole data. Another method such as classifying the data based on material or unit descriptions will need to be used to populate HorizonIDs in a BorePoint feature class.
  2. Many of our users live in areas that display times and dates in different formats than what GMS uses. It would be helpful to allow the user to specify the time/date settings to control how GMS displays times and dates, similar to the "Time Settings" window in SMS.
  3. It would be nice if it was possible to copy the state of the Log Xform checkboxes in the MODFLOW parameters list. One GMS customer had several hundred parameters that were negative (CHDs) so he had to toggle off each Log Xform checkbox manually and this capability would have been very helpful in doing this task.
  4. The user is interested in this because they would like to plot groundwater gains and losses for arc groups in the map module while using the SFR package. This is currently possible with the STR package, but not the SFR package.
  5. Observation Points

  6. Run Code Convergence Issues

    Hi Ryley, I'd suggest that you start troubleshooting by reviewing the mesh geometry. You can use the mesh quality display options and/or the mesh quality scatter set to check mesh elements and find poorly formed elements or other similar issues. I'd also recommend reviewing mesh element elevations by turning on and inspecting elevation contours. The other thing I would look at are your boundary conditions to check for reasonableness and/or errors. If there are issues related to any of these items you may be able to set the time step to a slightly larger value.
  7. Add ability to use PHAST

    Ability to use PHAST (MODFLOW plus MT3DMS plus PHREEQC) (requested by a user)
  8. Mesh resolution based on Topography

    M, I would recommend looking into the scalar paving density mesh generation method in SMS. This method uses the values specified at each point in a particular scatter set (referred to as a "size function") to determine mesh element sizes. The "Size Function" SMS 12.1 tutorial demonstrates how scalar paving density can be used in SMS.
  9. After hiding cells (select a cell, then select the Hide macro), saving a project, and then reopening the project, the hidden cells are now unhidden. It would be helpful in some cases to preserve the "hidden" status of cells when saving and then reopening projects.
  10. Include a feature that would allow the user to output a summary of the number of the number of active, flooded and dry cells for a particular stress period. (requested by a user) The user also suggested that if the head output values were displayed in a similar fashion as the input parameters such as top layer elevation, then they could copy the head values to Excel and do the flooded cell statistics on their own.
  11. A GMS user suggested that pressing the up arrow should go to a higher layer (lower k value) to be consistent with the display and more intuitive to the user. From the user: "In the min-grid plot you press the up arrow to go from layer 1 to layer 2 to layer 3 (etc) but layer 1 is the top layer and layer 3 the bottom layer and it is more natural to press the down arrow to down the layers. Indeed, the tutorial (MODFLOW grid approach) says to press the decrement button to go down from layer 1 to layer 3 (which would be sensible) but you have to press the increment button to do that - which is confusing and should perhaps be changed in future versions." Would it be possible to add a preference to change the order in which the spin control for the mini grid so it is more intuitive?
  12. It would be nice to give the user the option of inverting the mouse wheel zoom direction in the "Edit | Preferences" window.
  13. When modifying a borehole, it automatically deletes all cross sections attached to that borehole. Then the user has to auto-create blank cross sections, delete the ones he doesn't want, then auto-fill blank cross sections. Instead of automatically deleting, you could have a list of options come up: 1. Replace existing cross sections with blank cross sections. 2. Update cross sections by matching horizon IDs. 3. Update cross sections by matching materials. 4. Delete cross sections. (requested by a user)
  14. A user would like to be able to see which materials correspond to the different layers in a cross section while in the cross section editor. They suggested a legend be included in the cross section editor to accomplish this. I suggested they try turning on the materials legend and view it in the main window behind the cross section editor, but they said that they prefer to use the cross section editor full screen.
  15. One of the GMS training course participants in the August 2014 Provo course suggested that we give the user the option to adjust the size of macros/buttons/tools in the GMS interface. He mentioned that he would be interested in having this option when working on larger screens with high resolutions.
  16. Include a feature to convert a 3D Mesh to 3D solids based on the material properties. (Requested by a user)
  17. Implement a FEFLOW interface in GMS. (requested by a user who was very excited about using FEFLOW)
  18. Implement the LGR (Local Grid refinement) option of MF2K5 in GMS. (click here for more information) (requested by user, who noted that there is a big demand for this feature at their company)
  19. A user would like to be able to snap boreholes to TINs representing the top and bottom elevations, similar to how you can snap cross sections to TINs using the "Boreholes | Advanced | Snap Cross Sections to TIN".
  20. A user would like to be able to export all of their wells with transient pumping data that are defined in the map module at the same time. They are able to export the pumping data for each well one at a time, but they have over 100 wells so they have to open the XY Series Editor for each well and select "Export..." over 100 times. It would be nice if you could export them all at once in this same format.
  21. Include a "copy to coverage" command for feature objects (similar to what SMS has when you right click on a node) that allows feature objects in one coverage to be copied to another. (suggested by a user)
  22. Include an option to export/save materials from the "Edit | Materials" window. The user who suggested this to us asked: "Is there a way to save the materials designations (by this I mean the name, color, pattern, and so forth of the soil units or horizons) so that these can easily be imported into a new project. I realize they are saved if I save the project I created them in, but I’d like to be able to just import this information if I create a new project rather than having to rebuild the designations."
  23. In GMS, you can specify a time series or a TIN in the map module for a drain polygon. One GMS user would like to specify different TINs for different stress periods for drain elevations.
  24. It would be nice to add some text to the legend that reported that the "Fill below" and/or "Fill above" contour options were selected. A user suggested that "and below"/"and above" be appended to the min/max values in the legend to tell the user that all values below/above the min/max value were the same color. From the GMS user: "When I have the ‘fill above’ option on, is there a way of editing the legend so that it says this? At the moment it stops at the 2 m maximum I have told I to plot, but would like the legend to say something like ‘2 m and above’. I can do this in ArcGIS, not I can’t see if this can be done in GMS."
  25. A GMS user has a model that is configured to work in time (i.e., days from some reference point). For instance, they would like to be able to import the following two lines into a transient observation coverage: Point-Name Time Obs-CFC-11 AS-MW-03 30000 1 AS-MW-04 20000 66 They would like the first point to havea data point at 30,000 days, and the other to have the point associated with 20,000 days. This page of the wiki explains that both a time and date field are required to import transient observation data. They would like to be able to import transient observation data with only one time parameter (days in this case).