Jump to content
GMS, SMS, and WMS User Forum

John Howlett

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by John Howlett

  1. Lauren, What version of SMS and PTM are you using? An updated version of SMS 10.1 and the PTM model will be posted soon. I believe a problem was fixed recently where the first (x,y) point would be repeated in the trap file so there was one extra point per trap. Until the new version is posted, you may want to check if this is what is causing the problem. - John
  2. Let me see if I understand You have a .geo file with linear or quadratic elements You have a .sol file with a value for each node in the .geo file When you read in the .sol file after reading in the .geo file you get an error message saying, "THE SOLUTION FILE DOES NOT MATCH THE MESH" I believe we will need to take a look at your files. Please send them to technical support.
  3. Jose, What is the build date of the version of SMS you are using (See Help | About)? Thank you, John
  4. Have you tried to represent the structure as part of the mesh? SRH-2D is very stable and I believe you should be able to add the spillway to the mesh. Once the spillway is part of the mesh (and has the proper elevation assigned), the water will only flow over the crest when the water surface elevation exceeds the crest. The boundary conditions you inquired about are described in the manual as follows, but I would try adding the spillway to the mesh. EXIT-H: It is a downstream exit boundary with a subcritical flow. Water surface elevation should be specified at this boundary along with the unit. For a steady state simulation, a real positive value is the input as a constant water surface elevation (therefore, elevation below zero is not allowed in SRH-2D). For an unsteady flow, a negative integer, -n, is the input. The integer, n, refers to the data function specified in the “DATA_FILE_0n” in the Global Parameter setup. If it is a time series function, time(hour) versus elevation(ft or meter) is the input data; if it is a general function, discharge(cfs or cms) versus elevation(ft or meter), the rating curve, is the data. The unit of the data is also specified: 1 for feet and cfs and 2 for meters and cms. EXIT-Q: It is a downstream exit boundary with a known discharge where the water flows out of the domain. The input is the same as INLET-Q: discharge and unit. Caution: at least one EXIT-H is needed for modeling and EXIT-Q is intended only for cases with multiple exits. It is preferable that EXIT-H is the main exit and EXIT-Q is only a secondary exit with a small flow discharge. EXIT-EX: It is a downstream exit boundary where the flow is supercritical. No boundary conditions are needed at such exits, neither discharge nor water surface elevation.
  5. Simo, In addition to the tutorial Rusty mentions, there is a brief description of feature stamping on the documentation wiki: http://xmswiki.com/xms/SMS:Feature_Stamping - John
  6. 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
  7. MO, The interpolation issue has been resolved. Any versions of SMS created after 2009-10-30 will no longer have this issue.
  8. Joel et al, This problem has been resolved in the latest version of SMS 10.1.
  9. You may want to send this question to the ADCIRC Listserv, which is monitored by the developers of ADCIRC and other ADCIRC users. Instructions on how to join are posted at the ADCIRC website (http://www.adcirc.org).
  10. Lauren, Unfortunately the model PTM does not have an option to loop or extrapolate hydrodynamic data. Depending on what model your hydrodynamic output is from, it may be possible to manually alter the file to add additional timesteps. - John
  11. You may find the following post helpful: http://aquaveo.invisionzone.com/index.php?showtopic=379 See the PDF posted towards the bottom.
  12. Thread continues at http://aquaveo.invisionzone.com/index.php?showtopic=810
  13. 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.
  14. SMS does not currently have a model for modeling oil spills. Although the RMA4 manual suggests that it can be used for this, RMA4 should not be used to evaluate highly volatile materials such as gasoline, nor materials that do not mix with water, such as oil. See http://www.xmswiki.com/xms/SMS:RMA4 The model PTM can be used for particle tracking, but again, it would provide a crude estimate at best in my opinion. You may want to investigate the NOAA oil response software program GNOME. From the NOAA website: GNOME (General NOAA Operational Modeling Environment) is the oil spill trajectory model used by OR&R Emergency Response Division (ERD) responders during an oil spill. ERD trajectory modelers use GNOME in Diagnostic Mode to set up custom scenarios quickly. In Standard Mode, anyone can use GNOME (with a Location File) to: predict how wind, currents, and other processes might move and spread oil spilled on the water. learn how predicted oil trajectories are affected by inexactness ("uncertainty") in current and wind observations and forecasts. see how spilled oil is predicted to change chemically and physically ("weather") during the time that it remains on the water surface. To use GNOME, you describe a spill scenario by entering information into the program; GNOME then creates and displays an oil spill "movie" showing the predicted trajectory of the oil spilled in your scenario.
  15. Lauren, The ability to create a transient dataset from a steady state dataset is a new feature in SMS 10.1. Unfortunately, SMS 10.0 does not have this functionality.
  16. Mark, I'm glad you were able to resolve the .cst issue. If the need does arise to revisit an earlier version of SMS, sales / tech support is aware of the issue and should be able to work with you to find a solution.
  17. A couple of questions: Are you using SMS 10.1? Which module is the data in?
  18. Hardware locks are currently tied to a specific version of SMS. That is - a SMS 10.0 hardware lock will not work with SMS 10.1 and vice versa. We are considering alternatives (for the future) that would allow hardware locks to span multiple versions. Please do describe the *.cst file problem in a separate post. - John
  19. If you are having problems getting your FESWMS model to run, you may want to consider trying the following: Transform your mesh so it is close to the origin (0,0). For some reason if the x and y coordinates are large and mesh element sizes are small, FESWMS can have problems. Try using the Steering Tool Make sure your mesh does not have incorrect elevation values (often due to extrapolation). Try looking at the mesh in a rotated view. Verify that wetting / drying is turned on in the FESWMS model control Is the problem a known issue with the version of FESWMS you are using? Keywords: ds=0, ds = 0, convergence, error
  20. System requirements are posted at http://xmswiki.com/xms/SMS:System_Requirements. We are currently working to support the newly released Windows 7 operating system in new versions of our software.
  21. To interpolate vectors: In the Dataset toolbox, split the vector into two scalar quantities (Vx and Vy or Magnitude and Direction) Interpolate the two scalar datasets to the mesh In the Dataset toolbox, recombine the two scalar quantities into a vector
  22. Abhi, With the release of SMS v10.0, Aquaveo switched to a maintenance model for this and future versions of SMS. You will no longer have to pay upgrade fees for each new version; rather, you will automatically receive future versions through your annual maintenance fee of 15% for each SMS license. Your annual maintenace will also include intermediate updates and technical support. If you currently have SMS v9.0 or higher licenses, you only need to keep your maintenance current in order to upgrade to version v10.1. If you currently have older versions of SMS, you will first have to upgrade your license to SMS v9.2 at current upgrade fees, then pay the 15% annual maintenance fee. If you are not current on maintenance for v10.0, you will need to bring your maintenance up to date for v10.1. Annual Maintenance - 15% of version 10.1 pricing for your license - Call for quote. 801-302-1400 See http://www.aquaveo.com/sms-pricing
  23. Matt, I have posted the PTM tutorials on our FTP site: ftp://pubftp.aquaveo.com/download/PTMTutorials/ Please note that the reason they aren't being "officially" distributed yet is there are still some changes we need to make. Hope this helps. - John
  24. PTM does allow neutrally buoyant particles to be tracked. See http://xmswiki.com/xms/SMS:PTM for more details about PTM. The external links section may be of interest to you. http://el.erdc.usace.army.mil/dots/doer/pdf/TR-06-20.pdf Advection velocity - page 22 Diffusion velocity - page 31 - John
  25. Heimo, I'm not sure why ERDC has chosen to add an expiration to their models. I suppose it is to "force" users to use the most updated version of the model. - John
  • Create New...