Jump to content
GMS, SMS, and WMS User Forum

Alan K. Zundel

SMS Development Team
  • Content Count

    105
  • Joined

  • Last visited

Community Reputation

-1 Poor

1 Follower

About Alan K. Zundel

  • Rank
    President of Aquaveo

Profile Information

  • Gender
    Male
  • Location
    Provo, UT

Recent Profile Visitors

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

  1. Jeremy, The recommended method for do that is to use a rating curve. You can use the populate tool to compute a level for any flow in the expected range of flows that will occur during a hydrograph. This avoids needed to worry about latency and attenuation of the flow from the inflow to the outflow. Alan
  2. Don has reminded me that the default "Wall" boundary does have velocities of zero. I will be revising SRH-Post to treat walls as zero-velocity while wet/dry boundaries will still be scaled. In the future I hope to use both cell centered and edge values to give a more accurate representation of what SRH-2D is doing internally.
  3. Don, This changed as a result of update to SRH-2D 3.2. However, as I recall, the edge of the pier did not get assigned a zero velocity even in the old version. SRH-2D would assign values to the nodes from the cell centered values that it computes. The process used a simple averaging of the wet/active cells attached to each node. So for a pier wall, the velocity from the cell centers was mapped to the edge of the mesh. When 3.2 was released we detected that the node interpolation changed from the 3.1 and the activity mapping appeared to have an error. We asked the SR
  4. SRH-2D only plots the first two points in the graph while it runs and the model developer would like to remove that option to streamline computations. However, the model creates an output file for each monitor point in the folder where the model runs. You can open those at any time and see the values. To get a plot you have to use something like EXCEL. In future versions of SMS there will be an option to view any of the monitor point plots while the monitor runs.
  5. Where did your SOF file come from? Was it created when you launched SRH from inside of SMS? Which version of SMS are you using? SMS 11 used what SRH referred to as the "Full" interface. SMS 12 uses what SRH refers to as the "Custom" interface. If SMS 12.1 or SMS 12.2 are creating an incomplete SOF file, I would be very interested in getting the data files and resolving this issue as a bug.
  6. Hello. The SRH-2D simulation should be able to run from a previous project. The "sof.dat" file created by SRH-Pre will contain all the input that was processed by SRH-Pre. Looking at it or stepping through the SRH-Pre run in partial mode can give greater insight about what is not working. Another option would be to make sure you have exported the SRH input files again. That would replace all the input you have so you may want to save them for forensic reasons. Finally, if you submit your data files to the Aquaveo tech support group, we can evaluate the project to see what is
  7. What numerical model are you using that supports this function? The TUFLOW model allows for alterations of the elevation at a specific time in the simulation or based on a trigger. The AdH model automatically refines elements when the gradient across the element is larger than a specified amount. Other adaptation would need to be model specific. If you want to try your second approach, you have to specify the time to stop the initial run explicitly, then interpolate the solution to the refined/modiied grid, then restart the second run with a hotstart file.
  8. Amy, I just reviewed this with the tech support and here is what I understand: 1- The date in the "Time" tab is recorded with the SMS project. It is the intent of SMS that this date should be specified before extracting tidal constituents and be kept current with the boundary conditions being applied in the simulation. 2- The date in the "Tidal Constituent" tab comes from the ADCIRC control file. This means that the date is unknown. The tidal constituent tab allows the user to apply amplitudes and phases for the boundary nodes based on any tidal database, including those not supported fro
  9. Amy, Did you load an SMS project, or just the ADCIRC control and grid files? Alan
  10. Karl, My guess is that this is a licensing bug on our end. Did you submit your map file that is causing the crash to our tech support? If we have the file I am sure we can get the issue resolved. Alan
  11. Amy, ADCIRC has not traditionally saved this date. It is used when you extract the tidal potential and tidal amplitude values from the database, but it is not saved in the fort.14 or fort.15. SMS saves it as part of the project that builds the ADCIRC files. If you have the ".sms" project file, it is there. You can view the value by loading the project into SMS and looking at the time control tab of the model control. You can also load the sms project file into HDFview which is a free viewer/editor for HDF5 files. There are some new features in ADCIRC that use the date, so this inform
  12. Alfredo, You can email your files to support@aquaveo.com. If they are too large to attach, we have an anonymous ftp site. I would start with an email. If I (or tech support) could see your files I am sure we could get your problem resolved very quickly. If we can understand what has caused your confusion, we can post a notice to help others avoid it. Alan
  13. It sounds like the simulation is not getting the wave conditions saved correctly. The details of managing those files has changed between 11.0, 11.1 and 11.2, so depending on which version you are using it may require different checks from your part. If you go into the model control dialog, then into the boundary condition cases, and verify that the spectra are assigned there, that is the first step. If that looks right, you need to make sure SMS knows where the simulation is saving out. Doing a "Save As...|STWAVE" usually clarifies this. If all of that is already set, I would suggest you s
  14. Emma, I am not sure exactly what issue you are talking about. The nodestrings do not require sequential node numbers, you just need to know which nodes make up each nodestring, and SMS saves all this information automatically in the fort.15. If you renumber nodes from a nodestring, SMS does assign the nodes in that nodestring the intial node IDs, but neither ADCIRC, nor SWAN care about that. We recommend that you use the global node numbering (added in SMS 11.1). Then none of the nodestrings will be numbered with sequential node IDs, but as I said, this is not an issue. There can be
  15. Heeyoon, The dx value for LTEA does not control the mesh size. The mesh size comes from a distribution of nodes based on the LTEA ananlysis and result in a specified target number of nodes. The dx value is a base grid size utilized by the LTEA calculations. Basically, it is the limits the how quickly the distribution can change in more than a linear fashion. Alan
×
×
  • Create New...