Jump to content
GMS, SMS, and WMS User Forum

Leaderboard


Popular Content

Showing content with the highest reputation since 07/28/2009 in Posts

  1. 2 points
    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."
  2. 2 points
    Unfortunately, there is not an automated method to export well transient pumping data for all wells in the format you'd like it to be in. However you can export out the pumping data for each well (if you have them assigned as feature points in the map module) by following the steps below. 1. Double click on a feature point representing a well with transient pumping data 2. Select the button in the "Flow rate" column with the three dots to bring up the XY Series Editor 3. Select the "Export..." button 4. Specify the file name and location and then select "Save" I realize that with many wells this will be a tedious process. I am therefore submitting this as a feature request to the GMS developers. I apologize for the inconvenience.
  3. 1 point
    Hi, My University has a parallel computing system and I would like to know if there is a parallel version of ADCIRC model to run the SMS in that cluster, using e.g. 20 processors. If yes, can you give me information about how it works? Thanks, Amy
  4. 1 point
    Customer: Ma'mmon Ismail He cannot find the projection in GMS for his data. Here is the coordinate system information: Projected Coordinate System: Palestine_1923_Palestine_Belt Projection: Transverse_Mercator False_Easting: 170251.55500000 False_Northing: 1126867.90900000 Central_Meridian: 35.21208056 Scale_Factor: 1.00000000 Latitude_Of_Origin: 31.73409694 Linear Unit: Meter Geographic Coordinate System: GCS_Palestine_1923 Datum: D_Palestine_1923 Prime Meridian: Greenwich Angular Unit: Degree More info can be found here: http://spatialreference.org/ref/epsg/28192/
  5. 1 point
    Dear Colleagues: This is only a help for the case you get problems when installaing SMS. I have just moved to Windows 7 ultimate, and SMS could not be installed. I got a message "Error 1935.An error occurred during the installation of assembly - HRESULT: 0x80070020". I haved spent some 5 or 6 hours looking for a solution, since I am in a hurry, trying to finish a modelling. Well, after finding several possible solutions and buying a couple of cleaners, the way to fix the problem was very, very simple: - The main problem is the size limit of the registry - The solution: -- Open the registry (regedit) -- Go to HKEY_LOCAL_MACHINE ---------System ---------CurrentControlSet ---------Control ------------ Key: RegistrySizeLimit, type REG_DWORD ------------ Change the size to FFFFFFFF -- Close and reinitiate Cheers, Jose
  6. 1 point
    A new SMS 10.1 update executable has been posted on the Aquaveo site. This version contains several bugfixes. Complete bugfix details can be found at: SMS 10.1 Bugfixes wiki page You can get the new version from the Aquaveo downloads page. Please let us know of any problems you encounter by contacting support@aquaveo.com.
  7. 1 point
    The tin idea gave me a direction to go. After a bit of fiddling. I got the solution I was looking for. I created a tin for the river that only included that area. I created another tin for the rest of the area that used the exact verticies of the river boundary. Then I used a 2d scatter file to create a tin for each layer using the appropriate base tin (river or surrounding) putting them into an appropriately named folder. Using horizons to solids, I used the tin folders and put them to the river or surrounding tin. I then combined the solids that were created into a single folder. That created a perfectly vertical contact.
  8. 1 point
    Can you Please Email me at Support@aquaveo.com and I send some Trouble shooting steps. We would love to get this working for you.
  9. 1 point
    Rob, I'm not sure what could be going on here. Right away, I would suggest lowering the timestep and see if that makes a difference. I would try hourly timesteps and then even a 1 minute timestep if you're still getting errors. If this doesn't solve the problem, I would suggest looking through the unsteady flow troubleshooting chapter in the HEC-RAS user's manual (p. 8-57 "Model Stability"). This has a number of suggestions for things to check to fix the problem (cross-section spacing, computation time step, etc). Sorry I can't be of more help. If these suggestions don't help, you could also send the model to us and have us look at it for you, but that doesn't fall under normal tech support. If it comes to that, let me know and we'll work something out with you. Thanks, Clark
  10. 1 point
    I was able to run the MODFLOW SFR2 tutorial model. I would recommend going through the MODFLOW-SFR2Package.pdf tutorial located in C:\Program Files\GMS 7.0\tutfiles\MODFLOW. There it explains how to set up a model using the SFR2 package. You can also see a finished model that uses the SFR2 package in C:\Program Files\GMS 7.0\tutfiles\MODFLOW\trans\sample. If you need to download the tutorials, you can find them here.
  11. 1 point
    SMS reads values larger than 360 degrees however these values correspond to a value between 0 and 360 degrees (ie. 540 degrees = 180 degrees) so there is no need to enter in any values greater than 360. The degree is measured from the positive x-axis counterclockwise. This makes straight up 90 degrees (or 450 or 810, etc) You may check what units RMA2 is looking for by opening the .bc file and checking the BWC Card. The second value is the IWMX flag and as stated in the manual this value corresponds to the units: 0 = miles/hour 1 = meters/second I believe by default this value is set to 1 meaning the winds would be entered in m/s but can be changed to 0 for mph if desired. The .bc file generated by SMS can be opened in a text editor like notepad.
  12. 1 point
    There are several computer codes that will simulate flow of water in an aquifer (such as MODFLOW). There is an extension to AHGW called MODFLOW analyst that allows you to create, edit, visualize MODFLOW simulations in ArcGIS. Are you looking for something different than MODFLOW?
  13. 1 point
    Please send your files to Technical Support and I will take a look at them. The previous posts pretty much cover any suggestion I could offer without looking at your files. When you send the files, tell them John Howlett wanted to look at them. Also, for the SRH-2D users out there - We have been working with Yong Lai, the developer of SRH-2D, on changes to SRH-2D that will allow the model to write the model output as XMDF files. This should make post-processing in SMS easier in the future. - John
  14. 1 point
    Further to my previous post, here is a workaround... 1. Create a GMS project (Projecta) with the mesh with regular layer thickness (created using the TINs|Horizons -> 3D Mesh command). Set up all the project options and boundary conditions. It gives you a "normal" GMS project with which to compare the results of editing the mesh. Run FEMWATER on this project and view the results. 2. Copy the project to a new name (Projectb). Then use a script (e.g. MATLAB) to edit the 3dm file (by adjusting the z coordinates of the nodes) to give non-uniform layer thickness as desired. Run FEMWATER on this to get the output on the non-uniform mesh. 3. Copy this project to yet another new name (Projectc). In this project, delete the 3D mesh. Then Open the edited 3dm file from Projectb. This loads the non-uniform mesh. Then use FEMWATER|Read solution to read the solution from Projectb.fws. This loads the solution into the new mesh. Now you can view the solution in Projectc. (You can't view it in Projectb because Projectb.gpr contains the original mesh but the Projectb solution is based on the modified mesh).
  15. 1 point
    Hi Clint, After getting some data that works for you, the filter command in the TIN menu is probably what you need. This command lets you filter the points on your TIN to a certain angle. We usually recommend using 4 or 8 degrees for the angle. You can also trim only the vertices you want on your TIN using the "Trim" command in the TIN menu. There is also a merge command that helps you to merge TINs together. Also remember that you can always convert between DEMs and TINs so you can merge DEM and TIN data together. Chris
  16. 1 point
    Hi, I am using TUFLOW in SMS 10.1 and I would like to link a fine Grid in some areas to a coarser Grid. We already ordered the multiple domains license. When I try to link the two 2D domains according to the help file on http://www.xmswiki.com/xms/SMS:TUFLOW_Linking_2D_Domains as below To setup multiple 2D domains in SMS: 1. Create multiple TUFLOW grids and associated grid components. 2. Define a 2D/2D Linkage coverage and attributes (see below). 3. Add all the 2D domains being used and the 2D/2D Links Coverage to the simulation. the program always tells me, that "this component already has a grid linked to it!". So what can I do to get this thing done? I already posted my question in the TUFLOW forum and they gave me a Tutorial. Unfortunately the multiple domains tutorial is not yet documented and so it is not easy to understand, how to use this tool. Kind regards
  17. 1 point
    Hi malibec Open your mesh, go to "nodes" and then to "transform". Then you will be asked "No nodes are selected. Do you want to edit the entire mesh" where you have to say yes if you want to transform the whole mesh. Then you can enter the transform, scale or rotation parameters and your done greetz Chris
  18. 1 point
    1. Variable flux bcs in steady state model: I think what FEMWATER is doing is figuring out whether flux is inward or outward at each node. It could be outward if the water table comes near the surface so that net flux is outward. For some reason it (perversely) initially assumes it is outward everywhere. 2. Slow convergence: I found the cause behind my slow convergence was poor resolution in the van Genuchten curves. GMS produces curves that have poor resolution at the dry end of the curve. If you have the FEMWATER spline interpolation switched on, this can then produce curves that are non-monotonic I think, which screws up convergence. It worked better for me when I dramatically increased the number of points in the VG curves to 500 (I had increase MXSPMK and recompile FW to do this). Also note that the GMS preset VG curves are incorrect if your length scale is not centimetres. 3. Minimum pressure head: I think the only purpose of this parameter is to truncate the pressure head at the surface to limit how dry it can get, to avoid running off the end of the VG curves for instance. I am assuming this is only applied at the variable flux bc nodes but I am not sure.
  19. 1 point
    Hi Sreekanth I am not an expert on GMS observation wells, so I don't know whether you are describing a bug, but I can offer several comments: 1. FEMWATER does not have observation wells as such, so you have to output the solution for the whole mesh at every time step you are interested in. So it not very efficient at producing time series at a particular node. 2. It is fairly easy to run FEMWATER from another application. You can use GMS to set up the input (text) files initially, then FEMWATER can be run from the command line. Then you would need to extract the outputs you want from the FEMWATER output (text) files. 3. Another option is to modify the FEMWATER code to do the things you want. I have not done this, but I would say it would be straightforward for someone with FORTRAN programming experience. Simon
  20. 1 point
    Simon, Thank you for the useful information. I neglected to mention that I also have a large number of wells in my simulation. These also contribute to the number of XY series cards in the .BC file. The wells are representative of an even larger number of domestic wells in the area being modeled.
  21. 1 point
    PS. I set up the files with GMS, tidy them up with a Matlab script, then run femwater from the command line (> femwater3 projectname.fws), then use Read Solution to view the results in GMS.
  22. 1 point
  23. 1 point
    I found if you work on a GMS:FEMWATER project for some time, changing bcs and materials, GMS does not throw out the old XY1 series (mostly boundary condition values and unsaturated material properties). So you get a 3bc file with many XY1 series, many of them redundant, and particularly the ids of those series start to get large. When the XY1 id values exceed 250 FEMWATER reports an array bound error. It would be good if there was some way in GMS to renumber the XY1 series and throw out the old ones. PS: I managed to do a workaround by deleting the 3bc file then restarting GMS. I may have deleted the materials and Simulation too (I don't remember). So I had to reenter the material properties and simulation options, but GMS did regenerate the 3bc file without all the old XY1 series/series numbers.
  24. 1 point
    Just as an update - we rewrote some of the code in SMS to reduce the amount of memory used while reading in large scatter sets. You should now be able to read in large scatter sets and still check the triangulate button.
  25. 1 point
    John, If you can contact technical support and send them your files, I can take a look and see what is causing the problem. Without the files, it is hard to narrow down the cause. Regards, John
  26. 1 point
    John, In the scatter module there is no way to assign an "elevation" data set to the scatter. All data sets are treated as "scalar" or "vector" data sets. When you switch the active data set, you will notice that not only the Z (elevation), but also the S (scalar) value of the scatter vertex updates and is always the same. The reprojection command only works on Z (elevation) data sets, so it does nothing for the scatter module. There are two ways to get around this: Convert the scatter set to a mesh, perform the elevation data set conversion, convert back to a scatter set Use the data calculator to convert the elevations from meters to feet by multiplying by 3.28... I apologize that this is confusing - we are hoping to improve this in future versions of SMS.
  27. 1 point
    The 2D Surface Water Modeling with SMS training course is designed for hydraulic engineers who wish to learn how to use automatic mesh generation tools in combination with proven analytical software to perform their two-dimensional hydrodynamic modeling projects. In this hands-on, application oriented training course will provide you with the knowledge and tools necessary to solve 2D hydrodynamic modeling problems quickly and efficiently with the latest version of SMS. The course will teach users how to use SMS visualization tools to illustrate flow fields in 2D also. A series of lessons and tutorials are provided on RMA2 and FESWMS for flow modeling and RMA4 for transport modeling, including how to use the SMS Map module to create numercal models from high-level conceptual model data (GIS objects). For more information and to register, visit http://www.aquaveo.com/training-courses
  28. 1 point
    The groundwater modeling training course by Aquaveo is designed as a hands-on, application oriented training course. The course will provide the attendees with the knowledge and tools necessary to solve groundwater modeling problems quickly and efficiently. The course will begin with a discussion on how to use the geostatistical tools in GMS to characterize existing contaminant plumes in both two- and three-dimensions. A series of tutorials and lessons on the GMS interface to MODFLOW/MODPATH/ MT3DMS/RT3D will then be given including an explanation of how to use the Map Module to create numerical models directly from a high-level conceptual model constructed with GIS tools. Analytic element modeling with MODAEM will also be covered. For more information and to register, visit http://www.aquaveo.com/training-courses
  29. 1 point
    Our latest newsletter is available for viewing on our <a href="http://www.aquaveo.com/announcements" target="_blank">News Page</a>: April 2009 Newsletter (PDF, 1.48 MB) Previous newsletters: January 2009 Newsletter (PDF, 846 KB) October 2008 Newsletter (PDF, 2.12MB) July 2008 Newsletter (PDF, 628 KB) April 2008 Newsletter (PDF, 395 KB) January 2008 Newsletter (PDF, 200 KB) October 2007 Newsletter (PDF, 826 KB)
  30. 1 point
    I don't think that is quite right. There are two compressibilities: The value supplied to the MP3 card (beta) is the compressibility of water in units of L T^2/M. According to the manual (page 41) Femwater converts this to modified compressibility (betap, Equation A23, manual page 93). This occurs at line 5137 of the source code. So GMS should not (and I think does not) modify this. Freeze & Cherry (1979, page 529) suggest a value of 4.4E-10 m^2/N = 5.9E-20 m d^2/kg, similar to what Rob quoted. The value supplied to the MP2 card (alp) is the compressibility of the medium, also in units of L T^2/M. According to the manual (page 47) Femwater converts this to modified compressibility (alp, Equation A22, manual page 93). This occurs at line 5109 of the source code. GMS should not (and I think does not) modify this. Freeze and Cherry (1979, page 55) suggest values of 1E-6 to 1E-11 m^2/N across a range of materials. By the way, I am using GMS 6.5.6.
  31. 1 point
    You can use GMS to set up your femwater model files (fws, 3dm, 3bc), then go into the files, especially the 3bc file, and make any changes/corrections you want. Then you can go back to GMS and RUN the model and view the outputs (don't save though or you will overwrite your changes). Another approach is to run FEMWATER from the command line: copy the femwater3.exe into the same folder as the fws file, go to dos and type > femwater3 whatever.fws. I prefer this way. Once you have got your mesh and bcs set up you can make other changes directly in the 3bc file without using GMS. Then you can use the FEMWATER|Read Solution to load in the results and view them in GMS.
  32. 1 point
    Jose, You will probably also want to stick with SMS 10.0 for your projects until SMS 10.1 comes out of BETA and is more stable. This should be happening in the next couple of months. - John
  33. 1 point
    Jose, SMS 10.0 runs on Windows Vista as a 32 bit application. SMS 10.1 is available as bot a 32 bit and 64 bit application. Since you have a 64 bit operating system, you will probably want to run the 64 bit version of SMS 10.1 which will allow you to work with larger meshes, scatter sets, etc. - John
  34. 1 point
  35. 1 point
    I am running a contaminant transport model in FEMWATER. I am wondering if I have set up the dispersion coefficient parameters correctly. In the FEMWATER manual it gives the equation for the D tensor as theta D = aT |V| delta + (aL-aT) V^2 / |V| + am theta tau delta where theta is the moisture content (not the porosity) delta is the Kronecker delta function (basically an identity matrix) am * tau is the molecular diffusivity D* V is the fluid velocity aL is the longitudianl dispersivity aT is the transverse dispersivity My problem is the first theta. In all the other references I have seen it is not there, for example Zheng & Bennett 2002. I am wondering if it is a typo. If it is not a typo then the parameters in this equation are different the usual form such as given in Zheng & Bennett and it would make a big difference. Would appreciate your help. Thanks. Edit: Update: Actually V in the above equation is the Darcy velocity = theta * Fluid (seepage) velocity. So theta appears in every term. It seems this equation is the correct form for unsaturated conditions. My mistake.
  36. 1 point
    I also forgot to mention that you can use the menu command "Elements | Select thin triangles" to find the elements with a bad aspect ratio.
  37. 1 point
    The aspect ratio for the 2D mesh module defaults to 0.04 in SMS regardless of the model. I don't know of any published recommendations for CGWAVE on aspect ratio. In general, you want to avoid "skinny" triangles. You can use the menu command "Elements | Options" to view and change the current aspect ratio. You can try changing it, redo the model check, until the model check doesn't give the error to find out what your worst aspect ratio is. Remember that the model check points out items that may cause problems, but are not guaranteed to. You may want to turn on mesh quality in the 2D Mesh display options and see if you can identify any problem areas of the mesh that may need tweaking. Since you are using CGWAVE are you using a size data set to create the mesh? If you are, you may want to use the data set smoothing tool to smooth the size data set you are using. This can help with mesh quality problems. More information can be found here: http://www.xmswiki.com/xms/SMS:Smooth_Data_Set_(Data_Menu)
  38. 1 point
    Onur, Thank you - it is much easier to fix problems with a smaller case. I will keep you updated of any progress we make. Regards, John
  39. 1 point
    Onur, Is it possible for you to contact Technical Support and send them your files so we can try to pinpoint the problem? Thank you, John
  40. 1 point
    I believe ADCIRC may be more stable when wetting and drying is occurring. However, if you want to use your hydrodynamic solution to run RMA4, you will need an RMA2 solution. It sounds like you have most of the data you would need to use the reflection / absorption BC - can you also get TAREA? You may also want to consider extending the mesh if possible so you don't need to use a reflection / absorption BC. It is more difficult to get a solution from models with wetting / drying - I also believe the reflection / absorption BC can be difficult, and it is hard to know what value to use for BETA.
  41. 1 point
    Are you able to extend the domain further upstream? If you are, I believe this would be preferable to using the reflection/absorption BC. The user manual also offers the warning, "This boundary condition has been found to work far better when applied to a one-dimensional element rather than to a two-dimensional element." Although the reflection / absorption boundary condition does not require transient water surface elevation data (how the water surface elevation changes with time), it DOES require other information, such as the steady state water surface (SSWSE) and flowrate (AC1X) to be known / specified. As stated in the manual, SSWSE is the mean value about which the progressive or reflective wave crossing the boundary oscillates. You said no precise flowrate data is available for the upstream boundary. In this case, I don't think you will be able to use the Reflective / Absorption boundary condition since flowrate information is required as part of the specification of a reflection / absorption boundary condition. From page 145 of RMA2 user manual VARIABLE, VALUE, DESCRIPTION AC1X -, 0, + Average (net) river discharge ft3/sec or m3/sec, (Variable Qo in the equation below). BETA 0 to 1 Reflection/Absorption coefficient used to calculate A2 in the rating curve equation below. BETA = 1 specifies total reflection at the boundary. BETA = 0 specifies total absorption at boundary. SSWSE -, 0, + The steady state solution for the water surface elevation at the first node on the specified continuity line number. If SSWSE is less than or equal to zero, RMA2 will incorporate the steady state solution (Eo) before advancing to dynamic. Note: If Hotstarting a steady state run, use a value of –1. If Hotstarting a non-steady state (dynamic) run, you must supply SSWSE with at least 4 significant figures past the decimal. THETA -, 0, + Direction of flow into the mesh in radians measured counterclockwise from the x axis. Note: The program adjusts the boundary directions to maintain flow parallel to the edges for nodes at the ends of the continuity line. TAREA 0, + Surface area of tidal storage beyond the boundary. Used in defining standing wave flows. TAREA is the maximum tidal discharge divided by the maximum fall rate of water surface for a given time step. TAREA = Velocitymax * Width * Depth / Rmax Rmax = Δ WSELV / (ΔT * 3600)
  42. 1 point
    Ok you're talking about Soil properties for unsaturated zone in FEMWATER (SP1 card) (next time be more specific) Yes I agree the preset Silt in GMS:FEMWATER is different from the parameters in Table 5 in the FEMWATER manual. The parameters in the manual are just examples, maybe they changed the defaults for GMS. Or there may be an error in the manual or in GMS. I notice that the alpha parameter is inverse-length-dependent, maybe they don't adjust the default value properly for units in GMS.
  43. 1 point
    I think combining would be better (at the moment, with small member numbers) because 1) some of the MODFLOW forum issues are probably actually GMS issues, so I want to know about them. 2) more people means more help with my problems. 3) more activity would make the forum better, it might get to critical mass.
  44. 1 point
    I'm glad you were able to resolve the problem. I'm guessing you found the line in the .2dm file Yong Lai has put together for SRH-2D that limits the Manning's Coefficient to the range of 0.0 to 0.2, to help prevent users from using unreasonable values for typical situations. MD 1 "Manning's Coefficient" MV "Manning's Coefficient" 0 0 0.2 The .2dm file is described here. I have attached the SRH-2D template file that we have been using to test SRH-2D and will be distributed with SMS 10.1. Yong Lai has a different version also for SMS 8.1. Both are available from the SRH-2D website. We are very excited about the SRH-2D model. How long have you been using SRH-2D? What types of applications have you used it on? - John srh_2d_model_definition.zip
  45. 1 point
    Matevz, You may want to check your units. They should be consistent each time your are entering parameters for the model. The "Edit | Units" dialog should be set up correctly, and these units should be used in each subsequent step. In the "Seep2D | Analysis Options" dialog, is the "Compute flow lines" check box activated? If not, it should be in order for them to appear. Regards, Todd XMS Technical Support
  46. 1 point
    I've been transferring a model back and forth from a computer with XP to one with Vista and am finding that when I'm in Vista, the labels for the materials legend, borehole names, and horizon IDs all show up as symbols rather than text. Any thoughts on this? This occurs in both v6.0 and v6.5.
  47. 1 point
    Hi all I have been trying to run a simple PTM run to test it's capabilities. First I tried forcing the particles with outputs from a CMS-FLOW simulation I completed recently. While I followed the documentation as closely as I could, and was confident that I had set everything up correctly, the model would not run, and kept giving the following error message: forrtl: severe (157): Program Exception - access violation I thought that perhaps the problem was with using the CMS-FLOW outputs, so I tried to force the particles with outputs from the ADCIRC tutorial simulation. Again, after setting up the model I received the same error. I have tried a number of variations on the model setup: different time steps, with and without particle sources/traps, etc. I also downloaded and installed the latest model exe updates, without success. If someone could provide any insight on whether I'm doing something wrong, or whether there is a bug in the model it would be much appreciated. Regards Joel
  48. 1 point
    Thanks for your response John, In answer to your queries: - .err is not being generated - I clicked OK after setting the XMDF paths, with no change to the result Joel
  49. 1 point
    It looks like your computer is good enough to handle it, so it must be something else. If you would like, you can contact support@aquaveo.com and we will look at your files.
  50. 1 point
    GMS 6.0 and 6.5 do not support Windows Vista. The next version of GMS will support Vista. You can run GMS on Vista but you will get these display oddities, typically dealing with fonts.
×
×
  • Create New...