Jump to content
GMS, SMS, and WMS User Forum

calberts

Members
  • Content count

    42
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About calberts

  • Rank
    Senior Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

2,272 profile views
  1. Coverages on the same plane

    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
  2. Error: Case_INTERNAL*.dat

    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
  3. Length of BC

    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
  4. SRH-2D Progress Status window

    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
  5. Importing Mesh into HEC-RAS

    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
  6. Importing Mesh into HEC-RAS

    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
  7. Missing Case.dat Error

    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
  8. Event is over due to flow below cutoff value

    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
  9. Pre Run Error Code

    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
  10. Retriangulating to remove embankment

    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
  11. CE-QUAL-W2 - what am I missing?

    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
  12. Problems With Pressure BC

    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
  13. Diverting a Drainage Path

    Mike, This is exactly what I ran into the other day for a project I was working on. One possible workflow would be to edit the DEM using a feature arc. This is done by creating a new coverage, digitizing an arc through the center of the culvert (terminating it at the toes of the roadway embankment, or just beyond), editing the underlying DEM cells along the arc, and then rerunning TOPAZ. You can read more about this process in the online documentation: http://www.xmswiki.com/wiki/WMS:Editing_DEM_Elevations. An easy way to get the "Edit DEM Elevations" to pop up is to select the arc running through the culvert and then right click on it and select "Edit DEM Elevations". In the "Edit DEM Elevations" window, you can multi-select the first and last points in the plot by holding down shift and then you can press the "interpolate" button to linearly interpolate the elevations between the two selected points. When you select OK, it will edit the DEM elevations accordingly. Don't forget to rerun TOPAZ to pick up the new drainage path and then re-delineate your basins. If after doing the above, TOPAZ still does not pick up on the new drainage path further editing could be required such as widening the gap by repeating the process with a parallel arc or extending your culvert centerline further upstream/downstream. Let us know how it goes. -Cody
  14. Boundary Condition Issues

    Hi WIALLEN, Did you also extend your materials upstream? I have seen this message when my materials do not cover the inflow boundary. -Cody
  15. Scatter Data question

    John, As far as some of the more routine or general processes go in SMS like filtering, retriangulating, and merging go, my understanding is that most only utilize a single core. And as far as running models goes in SMS, there are some numerical models which allow parallel processing such as ADCIRC, ADH, and even TUFLOW has a form of parallel processing with their GPU solver, but there are also many which do not have that capability. Are you planning on using any of those models? The general set of hardware requirements are listed at the bottom of the following page: https://www.aquaveo.com/software/sms-surface-water-modeling-system-introduction You could stick with the 32G of RAM that you have, and match that with a processor with the fastest clock speed that your budget will allow, as mentioned in those general set of requirements. -Cody
×