Jump to content
GMS, SMS, and WMS User Forum

Alan K. Zundel

SMS Development Team
  • Content count

  • Joined

  • Last visited

Everything posted by Alan K. Zundel

  1. Water Elevation at Monitor Points

    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.
  2. SRH2D Pre Error

    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.
  3. SRH2D Pre Error

    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 wrong.
  4. Mesh Alteration During Simulation

    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.
  5. 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 from inside of SMS. This means that once the user specifies the tidal constituents, there is know way to verify the values short of performing the extraction again. 3- When SMS extracts tidal constituents from either the LeProvost or ADCIRC databases, the default date if populated with the reference date from the time tab. That does not mean that the user is forced to use that date. Since the user can provide any data he/she feels is appropriate, ADCIRC (and SMS) leave that responsibility with the user. The user could document the process he/she followed in the meta-data of the project. Therefore, my understanding is this: a- If the process is followed correctly, the user will specify a simulation reference date in the time tab and all data will be consistent with that date. b- The simulation reference date is preserved in the SMS project file. c- The user can further document the work that has been done in metadata for the project. d- Nothing is forcing the user to follow these practices, so a reviewer or engineer that is trying to apply the model must be careful not to assume too much, and may want to perform verifications. Do you have any suggestions that we could implement from an interface point of view to facilitate the process? Alan
  6. Amy, Did you load an SMS project, or just the ADCIRC control and grid files? Alan
  7. Map file causes SMS to crash

    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
  8. 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 information may become part of the standard ADCIRC simulation. Alan
  9. some problem using STWAVE v. 6.0.17

    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
  10. some problem using STWAVE v. 6.0.17

    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 submit your files to Aquaveo tech support and we can get your problem resolved. Alan
  11. Renumbering multiple ocean boundaries

    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 issues with multiple nodestrings connecting end to end. For that situation, you are best off merging the nodestrings into a single nodestring. This requires that the two nodestrings actually share one end point. Select both nodestrings, right click and select merge, and they become one nodestring. If the two nodestrings begin and end at separate nodes, they cannot be merged, but I think ADCIRC will still work for that case because the boundary conditions are actually assigned at the nodes. If this is not the problem you are encountering, please clarify and we can try again. Alan
  12. dx for LTEA, SMS

    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
  13. Mesh generation from scatter

    Mithun, If I want to increase the resolution (or decrease it for that matter) of an existing mesh, the easiest way is to scale the size function I use in my conceptual model. However, that requires that I have a conceptual model that I used to generate the mesh and I used a size function. If I don't have a size function, you can create one using the dataset toolbox. The steps are as follows: 1- create a "spacing" dataset (This computes the average edge length for each node in the mesh) 2- use the dataset calculator to scale the spacing dataset. (finer mesh, scale by less than one - coarser mesh, scale by greater than one) 3- convert the mesh to a scatterset If you don't have a conceptual model at all: 1- convert the mesh to map (right click on the mesh). Converting mesh boundary to arcs. 2- Split/merge the arcs as needed to represent your boundary conditions and assign the boundary conditions to the arcs. 3- Build polygons (feature object menu). 4- Assign the polygons to use the size function (scalar density paving). If you are using patches, let me know and I can help you work through that. Regenerate the mesh using the Map -> 2D Mesh command. Alan
  14. Email Notification

    We have experimented with using email notifications in the past. This seems like a useful possibility. We will investigate.
  15. Convert Mesh to Scatter Set v11.1.6 64bit

    Ian, I have not yet been able to reproduce your error. When you import the fort.53, are you importing any other ADCIRC solution files at the same time? How many constituents have you included in the harmonic run? Alan
  16. Convert Mesh to Scatter Set v11.1.6 64bit

    Ian, I have not heard of this issue before. I will investigate and get back to you. Alan
  17. Warning elevation near open bounday

    Jismy, I assume this is an ADCIRC simulation. Are you using NWS = 8 or NWS = 19? Where is the cyclone track? Alan
  18. Several pressure files in scatter data

    Amy, Is there any chance you can post a couple of .nc files for subsequent timesteps on the aquaveo ftp site (pubftp.aquaveo.com)? Alan
  19. how to change map vertex duplicate tolerance

    Send the files to support@aquaveo.com.
  20. paving density mode loses resolution

    Sorry for the delay in getting you a response. The contours you are displaying are from the scatter set based on the legend. The range of sizes is 10-3 to 10-5 and your coordinates show geographic. I recently found a tolerance issue bug in the mesh generator that has caused some issues when paving in geographic coordinates. I am adjusting those tolerances and I think it should be fixed (at least significantly improved) in the next update of SMS. I personally try to avoid using fractional degrees as the size because the values don't mean anything to me intuitively. You could reproject to a UTM zone and pave there, but you would need to scale the size values (data values for the scatter set) up to make them meters rather than degrees. The other thing you could do is get the build next month (or off of the nightly builds) to see if it addresses your problem. If not, then you could report it to SMS tech support to get the specific issue addressed.
  21. Several pressure files in scatter data

    Amy, The support in SMS for several of the wind formats that ADCIRC allows is not fully there. This is an area we are trying to enhance. The approach we have taken to date is to allow the user to specify through the SMS interface the type of wind file that exists and then the user provides the fort.22 to conform to the option. We have been adding support for more of the options inside of the interface. In these situations, SMS will create the appropriate fort.22 file. The NWS=5 option uses velocity and pressure at each node in the ADCIRC mesh. So your pressure files need to have pressures at the locations of the nodes in the fort.14 or grid file. Is that what you have? Secondly, you must have a single dataset with multiple timesteps (one per day if that is your increment). We have had requests to allow you to concatenate multiple datasets to create a series of timesteps. That seems like a logical tool and I would like to get it added to the data set toolbox, but it isn't there right now. That means you will need to get the datasets combined outside of SMS. What format are your pressure files in? I may be able to give you steps to get them combined if I know the format you are starting with. Alan
  22. ADCIRC fort.22 NWS=8

    The format for NWS=8 is described as a BEST track file, but it really isn't. We have a tutorial demonstrating the use of NWS=8 in ADCIRC under development. I will check on the availability of the files.
  23. paving density mode loses resolution

    There are two ways to increase resolution when using paving. The first applies to regular paving (no scalar size function). To use this add a feature point or arc in the area you want the increased resolution and specify the desired resolution by assigning the refine attribute to the feature point or redistribute the feature arc. The second applies to scalar paving. In this method you specify a size function in the form of a scattered data set. When using this method, you can just create a new scatter vertex in the area where resolution is being lost and specify the size in that area to be smaller.
  24. CMS-Flow will output a final bathymetry (z) value for each cell in the grid. If you read in the full survey of final measured bathymetry as a scatter point set (TIN) in the scatter module, you can interpolate that to the grid. Then you use the data calculator or the compare function in the dataset tool box (Data menu) to create a difference dataset.
  25. What engine (numeric model) are you using? What is the format of the "measured" change in bathymetry? Do you have it at multiple locations, a full survey, or just a few points?