Jump to content
GMS, SMS, and WMS User Forum

Leaderboard

Popular Content

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

  1. 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 points
  2. 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.
    2 points
  3. Hi, I'm now using RMA2, I am working on a lake with one incoming flow and two outgoing flows. I would like to manage so that one of the ougoing flows opens only some hours every day in the simulation. How can I do this? Thank you for your help. Anna
    1 point
  4. 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
    1 point
  5. Hi Matt, I am not aware of SMS ever being able to export out 3D polyline shapefiles. However, you could export the map data as a dxf/dwg file by right clicking in the "Project Explorer" and selecting "Convert to CAD", then selecting "File | Save As" and changing the "Save as type:" to "AutoCAD Files (*.dwg;*.dxf)". You can then add this AutoCAD file into ArcMap using the "Add Data" tool and the lines will be loaded as Polyline Z features with the elevations specified in SMS.
    1 point
  6. Good feature request - I have often longed for this option also
    1 point
  7. 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.
    1 point
  8. 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.
    1 point
  9. Hi, Have you checked to see whether the inflow through the boundary is what you are specifying? I found that adcirc didn't get fluxes right for the pipeflow wier boundary condition and so it may have a problem here as well. Specify a flux that runs without the errors and then check in the results that the actual flux is what you put in. If the flux turns out to be much greater than expected then you will have to edit the code to correct this error. Hope this helps a little Ian
    1 point
  10. Anyone know of any recent issues with WMS becoming unresponsive? I have a model built that was doing just fine last night, but WMS now freezes when opening. I have installed the latest update, rebooted, restarted several times, and tried copying the files to different sources, all to no avail. It reads through all of the components, and then goes blank with a rotating hourglass. I have also tried to let it take its time opening, and after 45 minutes, still no go. Any thoughts on what could have changed within the last 12 hours? Thanks, Rob
    1 point
  11. Don, You can export the vectors as a shape file and then load that into ArcMap. To do this: 1) Turn off everything in the project explorer except for the vectors. 2) Select File | Save As 3) In the "Save as type" combo box select Shape Files. 4) Click Save 5) In the Export Shapefile dialog that appears select Feature Arcs -> Arc Shapefile and Feature Polygons -> Polygon Shapefile. 6) Select the files that were just saved and drag them into ArcMap.
    1 point
  12. In testing the new capability to export film loop to kmz, I have found a slight positioning error when viewing the animation in Google Earth. The horizontal shift looks to be about 15 m. For background, I am importing TUFLOW results into SMS 10.1 and then setting the projection to the appropriate global projection (Map Grid of Australia Zone 56) and datum (GDA94). Although the error is small, its enough to make the results look incorrect when viewed closely (eg. roads/houses are inundated when they are actually dry). When the raw TUFLOW results are mapped in our GIS (ie. independent of SMS) there is no spatial error. Similarly, when I import the background aerial (ecw file) into SMS the results overlay correctly. Has anyone else found similar issues exporting to GE? And hopefully resolved them! My guess is that the problem is going back to lats/longs in GE, and therefore not something that can be worked around. Cheers, Nick
    1 point
  13. 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
    1 point
  14. 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).
    1 point
  15. Ok, I have made some progress. I created a regular mesh in GMS. Then I wrote a MATLAB script to read in the 3dm file and smooth the z positions of the nodes in each vertical profile (by cubic interpolation, holding the material layer boundaries fixed). You can then open the GMS project, delete the existing 3D Mesh, and import the new mesh by opening the modified 3dm file. (GMS crashes if you don't delete the old mesh first).
    1 point
  16. Thread continues at http://aquaveo.invisionzone.com/index.php?showtopic=810
    1 point
  17. Thank you for the information. We are working to support Windows 7. I will pass along the information you found to those in charge of building the installation packages.
    1 point
  18. 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
    1 point
  19. 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
    1 point
  20. Must be a pain entering all those time series into GMS.
    1 point
  21. I'm adding this note for anyone following this thread, because of a similar problem. I've found that the FORTRAN compiler G95 seems to do a fine job of compiling the FEMWATER source code. Its free and available here: http://www.g95.org/index.shtml
    1 point
  22. 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.
    1 point
  23. Simon, Thanks for the reply. Can you tell me which compiler you've used? What I am not sure of is whether the FEMWATER executable exchanges any information with GMS via binary files. I know from limited past experience that binary formats can be compiler specific. As for the number of XY series, it appears from my .BC file that they do indeed number over 250. Ironically for me, many are the consequence of FEMWATER's requirement that unsaturated zone parameters be defined for all materials. Most of these definitions are pointless in my model, because most of the materials should never become unsaturated. In fact, I would love to be able to bypass FEMWATER's unsaturated flow routines entirely. I have no interest in the unsaturated zone calculations and would be happier to be handling saturated zone recharge as an input (ala MODFLOW). However, as these can not be bypassed (as far as I know), I am obliged to define the materials with realistic unsaturated material properties.
    1 point
  24. 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.
    1 point
  25. The combination of multiple materials in a newly created cell will result in a representative conductivity value. That is, I think you're seeing a combination of materials instead of a cell containing only a single material.
    1 point
  26. 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
    1 point
  27. 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.
    1 point
  28. See http://www.aquaveo.com/sms_training_orem for complete details Coastal Circulation and Wave Modeling with SMS December 8-11, 2009 | Orem, Utah A hands-on course featuring coastal storm surge modeling, coastal morphology modeling, wave modeling, and ocean circulation modeling. Aquaveo will award 2.8 CEUs to each participant who successfully completes this course. Course Description This course will provide you with the knowledge and tools necessary to apply numerical models for coastal circulation, tides, waves, wave-current interaction, sediment transport, and morphology change. A step-by-step approach will be used providing instruction and examples covering the modeling process from regional to project scale. Models covered include ADCIRC, STWAVE, CMS-FLOW, CMS-WAVE, CGWAVE, and BOUSS-2D. An introduction to the newly released Particle Tracking Model (PTM) will also be included. You will learn to use the latest tools available in SMS v10.1 for network generation, data filtering, and advanced conceptual modeling. Come and learn how to be more effective in your coastal modeling projects! Course Outline - 4 Days Review coastal processes involved in hydrodynamic simulation. Learn advanced techniques for network generation. Model wind and storm surge to predict coastal flooding. Simulate circulation in large scale coastal systems with ADCIRC. Model circulation and sediment transport with CMS-FLOW. Learn to use the STWAVE and CMS-WAVE spectral wave models. Perform phase-resolving wave modeling with CGWAVE and BOUSS-2D. Practice circulation/wave model coupling to evaluate the interaction of currents and waves. Simulate particle transport processes with PTM.
    1 point
  29. 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)
    1 point
  30. After the forum was upgraded, I noticed when I clicked on "View New Content" all of the forum posts appeared. Somehow my viewing history had been lost. You can click on the "Mark Board As Read" link at the bottom of each page to remark all existing posts as read.
    1 point
  31. 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.
    1 point
  32. I will make sure that I have the permission to send the files out first. If I do, I will definitely contact the technical support. Thank you Onur Edit: Ok, I contacted the technical support. I recreated the problem with a much smaller mesh grid.
    1 point
  33. Announcing Final Release Candidate One of Groundwater Modeling System 7.0 The final release of version 7.0 will be freely available to all GMS 6.5 users who have current paid maintenance! Changes Since the Last Beta Release Added DRT1 package.Added STR parameters.Several bugs have been fixed. Previous versions of GMS 7.0 beta must be uninstalled before installing this new beta release. Download the beta release of GMS 7.0: Click Here Learn more about what's new in GMS 7.0: Click Here A Word About Beta Software This beta release is meant for experimentation and testing purposes only and not for production work. We will continue to develop this release until we feel it is suitable for final release. Please keep a backup of your files in the event something does go wrong during your testing. We welcome any feedback you may have. Learn more at: http://www.aquaveo.com
    1 point
  34. 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.
    1 point
  35. 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)
    1 point
  36. O.K. Thank you very much
    1 point
  37. ADCIRC requires that all input files reside in a single directory and that they be named with the fort.xx convention. When a project is saved from SMS, all of the necessary simulation data are saved in .sms, .ctl, .grd, etc. When the model is launch from SMS, all of the necessary ADCIRC input files are written to the working directory. For example, the .ctl data are saved in a fort.15, .grd in the fort.14, and so on. Because of this convention, it is impossible to have a single ADCIRC run reference files scattered across multiple directories.
    1 point
  38. Hi, John: ADCIRC Best regards, Jose
    1 point
  39. 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.
    1 point
  40. Jose, What model are you having these problems with? Thank you, John
    1 point
  41. Mark, Tom just tried doing the conversion in SMS 10.1 and the results look correct. We did a major overhaul on our coordinate system support in SMS 10.1. You may want to try downloading SMS 10.1 Beta from the Aquaveo Downloads page and using it for this project. - John
    1 point
  42. This somewhat relates to my previous post. We are using a Generic model with the SRN2D progrom. We were provided a templete file which a text file with a .2dm extension. The file is passing instructions to SMS. Is it possible to obtain any general information related to the proper formating to do this. We can edit the text file but we have to be carefull because it is not obvious what effects the lines in the file might have. It appears to be appending some unnecessary lines to the working .2dm file each time it is saved. I hesitate to go back to the developer because the program was provided free without support.
    1 point
  43. 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
    1 point
  44. 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
    1 point
  45. Chris, We have determined that merging the two meshes requires more memory than a 32 bit operating system can allocate to SMS. You may want to try splitting the mesh into smaller sections and merging them incrementally. John
    1 point
  46. 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.
    1 point
  47. 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
    1 point
  48. 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
    1 point
  49. 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.
    1 point
  50. 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.
    1 point
×
×
  • Create New...