Jump to content
GMS, SMS, and WMS User Forum


Aquaveo Tech Support Team
  • Posts

  • Joined

  • Last visited

About kcornwell

  • Birthday June 30

Profile Information

  • Gender
  • Location
    Provo, UT

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

kcornwell's Achievements


Newbie (1/14)



  1. Ayman98, For WARNING 41784, you can try decreasing the time step. Usually a 30 minute time-step does not return that warning. As for the other errors, if you would be able to email Tech Support at support@aquaveo.com and include your project file, it will be much easier for us to find a solution for you. Regards, Kyle
  2. kcornwell


    Brianne, The variation in IBOUND Array values doesn't change any process in the model. From what I am able to find, the different numbers are only to differentiate between arrays for each layer. The Online Guide to MODFLOW outlines that the only the sign of values are important to how the model is handled. Regards, Kyle
  3. Ben, If you wouldn't mind sending an email to support@aquaveo.com along with your project files, we would be glad to help you. This sounds like it is a bug, and we would like to replicate it so that we can find a solution. Regards, Kyle
  4. Maneesha, From the ADCIRC Model Documentation (see Notes for NWS = 8), it shows that NWS should be either 8 or 19, which is odd that it would set NWS=-8 or -19. Doing a runthrough of a Symmetric Storm simulation using Holland's Model, the .ctl assigned the correct 'NWS=8', which is on line 16 of the .ctl file. The YYYY,MM,DD,HH24,StormNumber,BLAdj does not appear in the file until line 23. If you could send your files to support@aquaveo.com , we would like to try to recreate your error and troubleshoot it. The storm number (from the same ADCIRC Model Documentation) is the number of the storm in the forecast for that year. At the start of each new year, the integer must be set to 1. Regards, Kyle NWS8.ctl
  5. Speedy, An old Technical Support case of the same error with SEAWAT was solved by changing the density/concentration slope value, as it was too high. Take a look at the definition for this parameter and then come up with a more accurate value and you should see the problem resolved. Regards, Kyle
  6. Raquel, What model are you creating the mesh for? Viscosity is used differently in multiple models used by SMS, and knowing which you are using would be a great help in finding a solution for you. Regards, Kyle
  7. agarza4c, I could not see any detail, since your picture is very small for some reason. However, the information on our wiki page may be able to assist you. Regards, Kyle
  8. Hi all, The main issue with the "Elevation.gt.ErrorElev.ADCIRC stopping" message is that the model is becoming unstable. Instability in a model can be caused by many different factors. It could be due to poor elevation interpolation but there can also be many other factors, like the bathymetry data. In the past, we have had success using LTEA to generate the mesh, running shorter simulations and experimenting with the values of the Tidal constituents and what your convergence criteria is. For more information on LTEA, you can go to our wiki and our tutorial for ADCIRC LTEA Meshing. I would also recommend activating the 'Mesh Quality' option, so you can more easily visualize elements that may be creating problems for your model. Information on that can be found here. Regards, Kyle
  9. mrabo, The Sediment Transport module within SRH-2D is not yet publicly available, so SMS will not be able to process the SRH-2D Sediment module at this time. Be sure to check back for SMS Updates here on the Forum, and you will know when it will be available. Regards, Kyle
  • Create New...