Jump to content
GMS, SMS, and WMS User Forum

Jack Grayson

Administrators
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jack Grayson

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Provo, Utah
  1. A bug in GMS version 10.3.3

    Speedy, Thank you for letting us know about a potential bug with our software. We're having trouble attempting to replicate the crash that you describe with GMS. If you would contact Technical Support at "support@aquaveo.com" with perhaps a copy of your model files and the specific steps you take to replicate the problem they will work on replicating the crash and submitting a bug report to our development team.
  2. Index is out of range

    Khaled, We noticed that you did not contact Technical Support with respect to this issue you were having. Were you able to resolve the problem? If not we invite you to contact Technical Support at support@aquaveo.com to try and resolve the problem. We would be interested in getting a copy of your files which you are able to replicate the error message with so that we can investigate the cause.
  3. SMS 12.1 SRH-2D sediment transport simulation

    LuboBa, Are you referring to the documentation on our wiki site? The information on our wiki site about simulating sediment transport with SRH-2D was recently added in preparation for SMS 12.2 which is currently in beta and has the sediment transport interface added. Due to this interface still being new and in beta, it is not available in the current official release of SMS (Which is SMS 12.1).
  4. Problems with GFGEN when running RMA2

    This problem appears to be similar to a known problem with GFGEN, and it has to due with having X and Y coordinates which are too large in value. See this page of the xmswiki for more information on that error.
  5. It sounds like something went wrong in the ADCIRC simulation run, perhaps a problem with converging or something like that, and as a result the solution dataset was messed up. It's difficult to say what is causing the problem without taking a closer look at your model. If you want you can send an email to our technical support team and they will see if it is a problem with your model or a bug in SMS. Their email is "support@aquaveo.com".
  6. Cutting holes into existing mesh

    The problem is that the polygons defining the buildings have their bathymetry type as "Constant". To fix this you can use whatever topographic data you had used to make the mesh before and interpolate it once more to the mesh. Then assign the interpolated dataset as the "Map Elevation" from the "Data" toolbar. Another way of doing this is to assign the bathymetry type to use your topographic data instead of being constant for those polygons defining your buildings. I would also suggest that you increase the number of vertices on the arcs defining those polygons, so that the elements around these holes in your mesh are less erratic.
  7. How to implemented drainage from tif files

    It looks like GMS takes a long time because it has to create all 45000 points at once, but if they are already made then copying and pasting in the 45000 rows of data only takes a couple of minutes. I've created a *.map file which contains a coverage with 45000 points in it for you. You can just click and drag this file into GMS and you can then drag that coverage under a MODFLOW Conceptual Model item in the Project Explorer to give it MODFLOW-type properties. After giving the coverage a Drain property, you can then copy and paste those conductance, elevelation, etc. values from Excel into the Attribute table as Bill was saying. I'll attach the file to this message, let me know if you have any trouble using it as I've explained. I'm afraid I don't understand very well your second question. Are you saying that the raster pixels do not match the cells in the middle of the MODFLOW grid? 45000pointscoverage.map.txt
  8. Ted, I'm no expert on this, but if your heterogeneous layer has more than just a couple of different Kh and Kv values then you would probably be better off using the data array method instead. You could possibly define unique material definitions for different sets of Kv and Kh values in the layer, but again depending on how varied those values are this may be very time-intensive. Instead It should be simpler for you to transition the material-based model into one that uses data arrays. You could convert the FEM model's Kh and Kv values into a set of 2D scatter points with a unique data set for each layer, and then have their datasets directly interpolated into the Kh and Kv arrays for each layer of the MODFLOW 3D grid. The "Interpolating Layer Data" tutorial on the learning center for GMS on the Aquaveo website has some good guidelines for doing this. Hope this helps.
  9. We've had several users ask Technical Support about having solute routing included in GMS, specifically by having it included in our stream/river packages for MODFLOW. The online guide to MODFLOW shows that the SFR package has the capability for including solute data in the MODFLOW simulation run, but requires the use of MODFLOW-GWT. The request then is to add a solute routing interface to the existing SFR2 package interface and include MODFLOW-GWT with GMS for just this circumstance. The users requesting this feature have mentioned that this is essential to their work.
  10. Transport Obs Package Flag iConcINTP

    This bug has been resolved, and I have verified the fix in the 19 Nov 2015 build of GMS 10.0.12. We are working on getting the nightly build and GMS version download links updated on our website, but if you would like a link to download the "19 Nov 2015 build of GMS 10.0.12" installer then please email support at support@aquaveo.com and we will get you the installer.
  11. Singling out sets of Data points

    I think that what Alan is referencing here is a 3D Scatter Set. These have x,y,z coordinates as well as a data value (typically given as "f" if you were to View Values within GMS). The idea then is that you would select all the points of a given cross section and give it an F-value of 1. The next cross section would have an F-value of 2 and so on. You can assign these data set values by selecting all the points and then entering in a number in the "F: " field, located beside the xyz coordinates in one of the toolbars at the top of the GMS project explorer screen. Then when you export the scatter set as a tabular .txt file each set of points in a cross section can be classified or sorted according to the F-value. I'll include an attached example of a dummy 3D scatter data set that I've exported from GMS. Would this be something useful to you? You would be sorting the dataset column in Excel in ascending or descending order. Cross_Section_ex.txt
×