calberts

Members
  • Content count

    22
  • Joined

  • Last visited

Everything posted by calberts

  1. NicT, SMS will allow you to create a text file including node point locations and computed datasets in the "Save as" menu. 1. Select the Mesh to make the mesh module active 2. Select "File | Save As..." 3. Change the "Save as type:" to "Tabular Data Files (.txt)" 4. Give it a name and click Save. 5. Specify the number of columns, Precision, and Delimeter type 6. In the "Data" row at the bottom select the "Data" button for each column to choose a mesh dataset that will be written to the text file. You can choose "X" and "Y" which are the coordinates of each node, and then choose other datasets to add the the other column(s) (which will be however many columns you chose to include) 7. Select OK when finished setting up the columns and it will create the text file with the columns configured how you set them up reporting data at the node locations. I have used this quite a bit to transfer mesh data to other programs and excel. -Calberts
  2. Hi, For the FST culvert, which is called "Culvert" in the SMS SRH-2D Linear BC assignment window, your best reference will be the Bureau of Reclamation's Technical report SRH-2016-09 which can be accessed at the following link: https://www.usbr.gov/tsc/techreferences/mands/mands-pdfs/ModelingIn-StreamStructuresInternalFeaturesWith SRH-2D_02-2016_508.pdf That paper also provides detailed description of all other structures in SRH-2D. For the HY-8 culvert, which is called "Culvert HY-8" in the SMS SRH-2D Linear BC assignment window, you will most likely find the HY-8 user manual to be most helpful. http://wmsdocs.aquaveo.com/HY-8_UserManual_v7.5.pdf -Calberts
  3. Thank you for posting this. We are unaware of any problem such as the one described at this time. However, we would like to run some tests to try and replicate it. Could you send an email to our support team at support@aquaveo.com with a description of this problem and details of your SMS setup? This will help us narrow down our testing. Please be sure to mention which SMS build you are using and any pertinent information such as the steps you take to assign the bathymetry and scalar paving data.
  4. Fahad, Thank you for posting this. Could you provide more information on this so we can adequately answer your question? What type of boundary conditions are you currently using? What is it that you are wanting to see the model simulate? Kind regards, calberts
  5. Here is an example of a landXML file format that SMS can read, you can use it as a guide for formatting yours. It looks like for the most part you have all the necessary components, you may just need to add a line or two and make sure the formats match. To answer your questions: Q1: If the XML file is not able to be read by SMS, please use the attached file as a guide as there could be some incorrect formatting. Q2: The open file dialog, is how you would read in a landXML file. Correction: SMS may be different than other programs you have worked with. It views TINs and Finite Element Meshes as different data types. TINs in SMS could have several uses, however one of the more common uses of a TIN surface in SMS is to provide an elevation surface from which a finite element mesh acquires it's elevations. The two data types are usually overlaid and elevations from the TIN surface are assigned to each node in the finite element mesh using an interpolation process. simple road3.xml
  6. Is the inner ring its own polygon? If you make it a polygon, the decreased density resolution should go throughout the entire inside of the ring. The bias setting in the polygon properties of your "outside" polygon can influence this as well.
  7. Ryley, Thank you for the screenshots. The error you mentioned is more of a secondary error, the message of not finding the simulation data file "mycasename.dat" typically indicates that SRH-PRE did not run correctly, therefore the data file was not created. The real error is what is shown in the second image in your Word Doc. where the SRH-Pre messages are listed. This error could mean there is a problem with the SRH2D boundary condition coverage, specifically the culvert arcs, as you have mentioned. Rebuild a new BC coverage identical to the first and use it in your simulation. If this is related to the issue I am thinking of, it will be fixed with the release of SMS 12.1.8. If rebuilding the coverage does not work, please contact technical support at support@aquaveo.com where they can troubleshoot your model files further. Best regards, -Calberts
  8. Fahad, 1. You don't have to convert. The units for flow vs time or Head vs Time are consistent with whatever units the display projection is using. You can check the units of the display projection by selecting "Display | Projection..." 2. Sounds like a projection units issue. In SMS you can specify the "Display Projection" and each individual object also has an "Object Projection". Right click on the scatter set in the Project Explorer and choose "Projection..." to see what it is set at. Make sure the units for it are "Feet" as you have them specified in ArcGIS. 3. Unless you need your DEM to be a scatter set, to perform edits, you can leave it as a Raster and use that for the Grid Elevations. The raster can be specified for use in the "Grid Frame Properties" under elevation options as shown in the attached image. If you do need it in scatter format, here are some options: 1) use SMS to create a resampled raster at a newly specified larger resolution than 10 ft and then convert to scatter (note: this will degrade the elevation data making it more coarse, yet it will allow you to thin the number of points that will be created) and 2) Turn off the display of "Points" and "Triangles" in the scatter set options of the Display Options before converting the DEM to a scatter set. This will ease the burden on your computer graphics. Unfortunately it will probably not do much with the RAM issue as the conversion does require a good amount of RAM for larger scatter sets. Let us know what works. -Calberts
  9. 2d-srh

    This may not be caused by having a third simulation with a different mesh, but rather it is more likely something to do with the setup of a culvert structure in your simulation. The first thing I would check is to make sure that the BC arc and Material polygon snapping is the same. The images below show how the BC arcs for a culvert and the "unassigned" material zone are snapped to the mesh. The dotted lines can be turned on in the display options and are called "Snap Preview". They are helpful to see how the materials and BC arcs are spatially assigned to the mesh. The image below shows a valid snapping configuration. Notice how the dotted snapping lines from the culvert BC matches the dotted snapping lines from the material polygon. The image below shows an invalid snapping configuration since the snapping edges are not the same. Likewise, the image below shows inconsistent snapping between the BC arcs and material polygons and is therefore an invalid configuration. Hopefully this is helpful. -Calberts
  10. smstuflow

    Fahad, That is good that you have access to both bathymetry and land elevation data. To know if you should mosaic the two data sets really depends on what you are trying to simulate or analyze. In some coastal models bathymetry data is not included because boundary conditions can be used to represent the interface of land and sea. The TUFLOW manual talks more of what BC types are used to simulate tides and storm surges. If you think you will be needing to combine the data, the easiest way in SMS would be to merge them as either rasters or 2D scatter sets. -calberts
  11. smstuflow

    Hi Fahad, Thank you for your interest in SMS. There are links to TUFLOW tutorials and tutorial data files at: http://www.aquaveo.com/software/sms-learning-tutorials I would recommend starting with the "TUFLOW 2D" tutorial which will walk you through the steps to create a TUFLOW grid using elevation data. SMS supports many raster formats, so depending on the format of your DEM and whether it is one of the compatible formats, you may be able to use it directly to assign elevations to the TUFLOW grid. Best of luck, calberts
  12. This problem may not be specific to one single specific type of issue with the model. I would suggest following the suggestions in the following thread as an overall troubleshooting process.
  13. Is this an SRH2D question? If so, it sounds like SRH Pre is failing. There is a "SimulationCaseName"_OUT.dat file in the output directory that should have been created. Opening that file in a text editor may show you an error that SRH Pre ran into.
  14. Are you creating the output feature class inside a GeoDatabase? I have seen the same error when trying to create a feature class in a non-geodatabase location.
  15. I have seen this error before when I have stream arcs defined as "General Stream" as the stream arc type and diffusive wave turned on for the stream routing in the job control. If you would like to use stream routing, it requires you to define the stream arcs as "Trapezoidal Channel" and define the geometry (base width, side slopes, etc.). The other option would be to leave them as "General Streams" and turn off 1D channel routing. -Calberts
  16. Hi Joel, It is convenient you have access to all of the software you have listed. Here is one method you could use, you could take your .2dm file from SMS and use the file import wizard within WMS to load in the X,Y,and Z values of the mesh nodes as TIN vertices. You would then triangulate the tin in WMS and convert the TIN to a DEM which will allow you to specify the resolution as fine or course as you desire. Once it is a DEM, use File | Save as... to save it as an arc/info grid format (which should be compatible with mostly any program you are going to use it in). One thing I would say about this process, or any process where you are drastically changing the structure of the original data, is that you will likely be degrading your data by forcing a set of unstructured mesh nodes to fit a structured raster grid. The extent of the degradation will depend largely upon the resolution you specify for the DEM. Best of luck, calberts
  17. The feature objects are displayed at the elevations of the points, nodes, and vertices of the feature objects. You could set the elevations of all points, nodes, and vertices to something greater than the mesh elevations. Careful when doing this, some of the models use the elevation of these features for model inputs (such as obstructions in SRH-2D). If this is the case with your feature objects, a safer route could be to duplicate the coverages and change the elevations on the duplicated coverage points, nodes, and vertices on the duplicated (unused) coverages.
  18. Thanks for the clarification, several models compute a total flow and write it to the output, something I wouldn't know about Hydro_AS. I am not aware of any other tools in SMS to calculate that type of output. Using my previous suggestion and placing the arc(s) near the exit boundary you could sum the flows for the timesteps and get an idea of how much has passed through the model during the entire simulation time, but that is all I can think of. -Cody
  19. dlpsbg, Flows can be calculated using an observation arc along with the depth and velocity datasets. Here is a link from the Tuflow wiki showing the process: http://wiki.tuflow.com/index.php?title=SMS_Tips#Flow_Timeseries Although the steps in that link are using a Tuflow mesh, the process is universal and can be applied to your Hydro_AS model. -Cody
  20. WMS has the ability to export images used in the WMS project to HMS. It would be nice to have the same ability for RAS projects that are exported from WMS.
  21. By default, RMA2 looks for a hotstart file in the same file directory as the project. You must browse to the location of the hotstart file by selecting the file directory button. Once you have located it, select open and the location will be saved. Then you must save the file before running. When I did this, RMA2 seemed to run successfully. However, it did re-run GFGEN before running RMA2. Perhaps there is still some issue here?