Jump to content
GMS, SMS, and WMS User Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by calberts

  1. Jim, As a follow-up, is it that the triangles that are automatically generated are undesirable and you have to delete them and create the triangles by hand? You may consider using breaklines, which can allow you to easily control the triangulation to force the triangles to behave how you want them to. Here are a few links on breaklines that may be helpful: https://www.xmswiki.com/wiki/SMS:Breaklines_Workflow https://www.xmswiki.com/wiki/SMS:Breaklines -Cody
  2. Jim, I see that we have an option for the opposite of what you want (when a vertex is deleted we can specify whether SMS retriangulates the void or not) in the Scatter Options of the Scatter menu. However, I am unaware of an option to specify whether SMS retriangulates when adding a vertex. I have submitted a feature request to our development team for them to consider adding this as an option to future releases. -Cody
  3. Hi Jim, The .map file contains the materials coverage. If you load that into the new project it will load in all the map coverages that were included in the original project and you can delete the ones you don't want. In SMS 12.2, the limitation to this method is if the materials coverage is one of the coverages that use the new dynamic model interface (DMI) such as an SRH-2D materials coverage, the attributes and coverage type will be lost and only the polygon geometry will be loaded in. You can easily get around that DMI limitation and ensure that the attributes are preserved in one of two ways: The first way is nice if you are starting a new project from scratch. You would make a duplicate of the project you are working on, open the duplicate and delete out all the stuff you don't want in the new project you are building, except for the materials coverage. This will ensure that none of the materials attributes The second way is nice if you already have a project and you just want to add a new materials coverage. You would select the materials coverage to make it the active (bolded) coverage, select File | Save as... and then change the Save as type to "Shapefile". In the export options you will select Feature Polygons -> Polygon Shapefile. This will create a polygon shapefile that can be opened in the new project and converted back to a map coverage by right clicking on it and selecting Convert | Shapes -> Feature Objects. This will start open the a wizard to walk you through the conversion process. If you specify the material attribute in the shapefile as "Material" in the GIS to Feature Objects Wizard ---- Step 1 of 1window, the material type will be preserved and transferred to the coverage. -Cody
  4. Hi Dale, I can see the concern. The old way of viewing materials assigned to the elements was definitely an easy way to see the element material assignments. We are always looking at improving our users experience with the software so I have made some notes that I will send them to our development team. For the time being, you can adjust the elevations of the polygon nodes and vertices in the material coverage by interpolating your scatter set (if you have one loaded into the project) to the map data. To do this make the materials coverage the active coverage by clicking on it, switch to the scatter module, and then select Interpolate to map... from the Scatter menu. This will interpolate the scatter elevations to the map coverage and bring it from zero up to the level of the mesh. Now, this may still not be optimal for viewing as some of the polygons may protrude through the mesh surface, partially obscuring the elements, but that will depend on the data configuration. It may be just as helpful to just leave the polygon vertices and nodes at zero and turn off the mesh contours to view the mesh in plan view. -Cody
  5. Hi Dale, With the new simulation based approach to modeling in SMS the material properties are no longer stored in the mesh for SRH-2D meshes. They are rather stored in the materials coverage and polygon material properties are then assigned to the underlying elements. An alternate way of seeing how the materials are getting assigned to the mesh would be to go to the "Map" section of the display options and turn on "Snap Preview". If the mesh and materials coverage are both linked to a simulation, then dotted lines will appear which show how the materials are being "draped" or assigned to the mesh elements. -Cody
  6. Dale, my mistake, I mentioned that you could run SRHPre with the "Partial Interface", which is Option 2. You are actually correct, if you use the .srhhydro you want to use option 3 which is the "Custom Interface". I am not sure what happened when you ran the custom interface as this should generate the three files you showed and the .DAT file should be complete and not 0kb in file size. I'd be curious to try and run it to see what happened. The renaming of the casename_SOF.dat file to casename_SIF.dat works with the SRHPre partial mode (Option 2) as you have noticed, but that requires that you have already ran SRHPre previously, since SRHPre is what spits out the casename_SOF.dat file. In the end, it looks like that workflow worked for you...although I'm still wondering why the custom interface did not work using the SRHHYDRO file... -Cody Yes, catbert is fine haha, that's a first
  7. Dale, In SMS 12.2, you can export the simulation files without launching by right clicking on the simulation and choosing "Export". This will export all the simulation files to a sub directory where your SMS project files are stored. Dig down to the folder which has the name of the simulation you created in SMS and the exported files are there. You can use the .srhhydro file (alongside the other exported files) to run SRHPre in the partial interface mode from a command line. Let me know if you run into any dead ends and I can shed some light on the process. I believe there are plans for future releases of SMS to allow you to run a simulation without locking you out of the SMS project. -Cody
  8. Looks like we posted at the same time. Glad you figured it out. -Cody
  9. Hi Dale, It sounds like you are creating multiple coverages for the different obstructions? Try creating all of the obstructions in the same coverage. You can merge coverages by selecting both in the project explorer while holding down the shift key and then right clicking on the two selected coverages and selecting "Merge coverages". Let me know if this is not helpful and I may have a few more ideas. -Cody
  10. WIALLEN, I have not had any issues with it stalling to date. If you click on the PreSRH-2D line of the SMS model wrapper (shown below) is there any error message displayed? If not, what are the last f ew lines of the model wrapper saying while it is stalled out? -Cody
  11. mikeg20, it is difficult to say what the issue could be just from what the translator gives us in this screenshot. I would recommend contacting Aquaveo Technical Support at support@aquaveo.com. They can set up a file share link where you can upload your project and have them take a closer look as to what may be causing this issue. -Cody
  12. Currently GMS reports an Error if negative values are input for the FEMWATER hydraulic conductivity tensor values. We have recently learned that in some cases these values can be negative. This feature request is to change GMS so that instead of reporting an error, a warning message will be displayed. A warning message would still be nice, since from our understanding most cases will only have positive values in the tensor. -Cody
  13. Hisham, we have had others report the same behavior to Aquaveo technical support in the past. We submitted the issue for feedback from our AHGW development team. They discovered that it was not a bug in the AHGW processes but rather in the ESRI plotting tools since AHGW uses the ESRI plotting tools in this process. The customers that have reported this in the past were all using ArcGIS 10.3. Are you by chance using ArcGIS 10.3 or earlier? Up until now we have not had any reports of this occurring with later versions of ArcGIS, so it is possible they have fixed the plotting issues. -Cody
  14. mikeg20, the Z location of the features in the SRH-2D Boundary conditions type coverage displayed in your two images is not important. That is the case for most map coverages with a few exceptions. Since it appears you are using SRH-2D the one SRH coverage type which does make an exception is the SRH-2D Obstructions coverage which uses the z location of arcs and points to define it's position in the z direction. -Cody
  15. WIALLEN I have not yet encountered this error. Would you be able to contact Aquaveo Technical support (support@aquaveo.com) and send a copy of your files? If the files are too large for email, they can provide you with a link to upload your files to the Aquaveo filecloud. We normally document all errors on our wiki at: http://www.xmswiki.com/wiki/SMS:SRH-2D_Errors. If they can replicate the error, then we will be able to provide a solution to you and also update our wiki page to include this issue. -Cody
  16. Mark, As Pablo mentions, it does depend on various factors. You should consider the terrain at the boundary as well as other hydraulic factors (i.e. roughness, anticipated velocities, magnitude of inflows). Although these factors will assist in determining the width of the inflow/outflow boundary, it still ends up being an educated guess which could be near or far from what the flow width really is. The suggestion I have is that you simply ensure that the Inflow/outflow boundaries are far enough away from the area you are interested in for your analysis. If you move these boundaries far enough upstream/downstream away from the area of interest, then within the model, any poor guess that was made for the width of flow will not affect the results since the width of flow will have ample space to either contract or expand into a more natural flow width before it arrives in the area of interest. This process of extending the model upstream/downstream may be an iterative process as you do some initial runs and look at the results to see what is occurring. I do recommend reading Hope this helps. -Cody
  17. Pablo, I have included your questions below with a few responses: "How can I get [the residual plot] back?" What you are seeing was intentional. With the most recent SRH-2D the plot was removed. There is currently not an accessible way to turn on the display of this plot. "Is there any way to display the Courant Number in real-time?" You can't display this information in real time, however you can monitor the average CFL and Max CFL numbers as well as the residuals in the casename_INF.dat file that is output during a run. It is my understanding that the residuals are not a direct indication of stability and convergence during an SRH-2D run, someone can correct me if I am wrong. "is there any way to display the inflow/outflow in real-time?" As with the previous question, no. But you can monitor the inflow and outflow if you place monitor lines near the inflow and outflow boundaries by checking the monitor line report files (casename_LNn.dat) that are written during the run. Different ideas are currently being discussed about possibly including something like this, but it is still in the idea/discussion phase of development. If you have ideas you'd like to share about this topic and what you feel could be useful, please let us know, we love feedback. "I would be interested to know how the community follow the progress of their simulations." If by progress, you are talking about run stability, I do not have many suggestions, anyone else? If you are simply wanting to know how much progress of the total simulation time has been made, usually this can be done by looking at one of the report files such as a monitor point or monitor line report file (casename_PTn.dat or casename_LNn.dat). SRH-2D writes to these files every 100 timesteps throughout the simulation run so they do a good job of displaying where the simulation is with respect to the time of the run. -Cody
  18. I wouldn't say that ~41,000 elements is excessive by any means, there is likely something else that is going wrong. It sounds like you aren't seeing any error messages or status updates during the process? How long have you tried letting it run so far? I would recommend submitting these files to tech support at support@aquaveo.com so they can investigate and report any issues that could be occurring with the translator. -Cody
  19. Try going to the "Data" menu and choose "Switch Current Model...". From the options in the "Select Current model" you should choose "Generic Mesh" for HEC-RAS meshes. After selecting this you should be able to link the mesh to the simulation. Let us know if that does not help. -Cody
  20. This error usually indicates that something went wrong when SRH-Pre ran. If SRH-Pre runs into an error, the simulation *.dat file is not created and when SRH-2D tries to run, it will report that it cannot find the file (the error shown in your screenshot). There is usually a more descriptive error in the SRH-Pre model wrapper window. Have a look at the SRH-Pre error and refer to the SRH-2D error wiki page for a description and resolution. If that page is not much help for the error you see, please post the error you are seeing along with any information about your model that may help to identify the issue. -Cody
  21. There is an input in the GSSHA long term simulation options called "Minimum event discharge". I believe this message shows up when you have specified something other than the default of "0". It is a way to tell GSSHA to end the event and move on if the discharge falls below the flow specifed. You can read more about this in the following wiki page: http://www.gsshawiki.com/Long-term_Simulations:Global_parameters -Calberts
  22. Given the broad range of changes that were made and the fact that the error message shown is not indicative of anything specific, I would recommend contacting the Aquaveo Technical Support Team and providing them with your files. They will be able to troubleshoot the issue and give some steps to resolve the error. You can contact them by emailing support@aquaveo.com. -Cody
  23. DHendon is right. You can delete the triangles, but the scatter points at the triangle edges will remain in the scatter set and be triangulated again. You can turn on scatter points in the display options and see where the points are that are representing the embankment. If you select and delete those points and then triangulate, your embankment should be removed. Making a copy of the original is always a good idea. -Cody
  24. With the TIN turned on, is difficult to tell from just the image if your segment coverage has a lake boundary defined by feature arcs (Tutorial sections 4.1 or 4.2 show two ways to create the boundary). If it does have the boundary, WMS has a built in snapping feature so that if you click close (within a couple computer monitor pixels) to the boundary, it will snap to the arc. If it doesn't have the boundary already, you can create it by one of the methods in the tutorial referenced above and then recreate your segment dividing arcs keeping in mind that you must click close to the boundary arc to get it to snap. Regarding your other question, I believe that you still need to specify the single branch as the main branch and go through all the steps to create segments, even if no other stems exist. -Cody
  25. SRH-2D pressure flow structures are different than the other SRH-2D structures. For weirs, culverts, and gates it used to be recommended that you leave the materials for area between the structure arcs "unassigned", that is something that has recently changed. SRH-2D now will inactivate these areas when it runs the model, which is one less thing we have to try and remember to do now. Pressure flow structures actually need a material assigned to them because the area between the structure arcs (bridge deck) never gets unassigned. The 2D simulation results are computed in that area and represent the flow beneath the bridge deck. Try assigning a channel roughness to the polygon beneath the bridge and everything should run correctly. -Cody
  • Create New...