Jump to content
GMS, SMS, and WMS User Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by daellishou

  1. I am about out of ideas. Does SRH-2D show up at the top of the window? That is another way to assign boundary conditions and monitoring lines; after the nodestring is selected go to 'SRH-2D' 'Assign Boundary Conditions'. If SRH-2D does not show up then the templete must not be loading correctly or somehow SMS has defaulted to another model rather than 'Generic'. Good Luck. As a last resort you might send and email to the USBE contact person. They don't provided support but I have been able to get them to respond to questions in the past.
  2. Are you sure you are working in the Mesh module? You have to create a nodestring in that module not an arc in the map module. If you are in the mesh module 'with the SRH-2D templet installed' then I have no idea what the problem is.
  3. We have been running SMS and SRH-2D in the Full Interface mode with the templete provided by the USBR for the last year or so. In that mode you just right click after you select the nodestring and set the boundary conditions to Monitor line. I am sure this could be done in the SIF file because we did it before they released SRH-2D version 2. However, I can't think of any reason why you would want to unless you are using a version of SMS prior to 10.0.
  4. The monitoring lines are relatively easy to set up and use in the Full Interface Mode. Create a interior nodestring in SMS (I don't think it works on the boundary). Select the nodestring and assign it as a monitoring line. The calculated flow is added to a text file during execution of SRH-2D. Remember that you can only have 9 lines. See user SRH-2D user manual section 3.1.2, page 20.
  5. Your guess was totally correct. The Out of Memory message just caused me to look in the wrong direction. I found several problems in the 2dm file that I had created. After correcting those everything worked great. For genereal information, having SMS allows us to NOT purchase another DHI Mike module. Thanks for the reply.
  6. Is there any way I can open a Mike21 FM mesh in SMS in order to create a dxf file? I have converted the text version to a 2dm format. When I try to open it I get a message that I don't have enough memory even though Task Manager indicates that there is memory remaining. Is this message generated in SMS or Windows? We are using a Windows XP 32bit system with 3G memory. We will eventually upgrade to a 64bit system and that will probably solve this problem but in the meantime??
  7. This somewhat relates to my previous post. We are using a Generic model with the SRN2D progrom. We were provided a templete file which a text file with a .2dm extension. The file is passing instructions to SMS. Is it possible to obtain any general information related to the proper formating to do this. We can edit the text file but we have to be carefull because it is not obvious what effects the lines in the file might have. It appears to be appending some unnecessary lines to the working .2dm file each time it is saved. I hesitate to go back to the developer because the program was pr
  8. We are using the generic model for SRH2D. We are trying to represent an opening in an embankment without changing the mesh layout. The mesh elements are larger than the opening. We are trying to compensate by increasing the N value. When we try to increase to a value larger than 0.2 the program appears to default back to a maximum value of o.2. We want to use values greater than 0.2. We can edit the ".2DM" file but we think it will change back to 0.2 when we save. Any comments or suggestion would be appreciated. Sorry, please ignore this post. The problem is in a templete file (.2dm f
  9. I checked these sites. Would it be usefull to us to have the HDFView installed? Would this assist in checking or finding problems in any of the SMS files?
  10. Thanks for the quick replies. It is not really a serious problem to run the program on a local drive. We considered that approach at one time because it can be faster if the server has a lot of activity. I think we can consider this problem solved.
  11. This issue is somewhat related to my previous post (Problem saving 2dm file). I thought the problem with saving the 2dm file might be related to the file path. The SMS 10.0 tutorial indicates that the project file is a text file (Overview Section 17). So I thought I would check the project file (.sms). It is not a text file. Am I missing something?
  12. Previously all of my work with SMS 9.2 and 10.0 has been with all the files located on a local driver (D:). Recently I moved the files to the server to allow others to assist with some of the tasks. Since doing this when we save the project we are getting a system message that the 2dm file cannot be opened and to check permission. The file was not write protected. I think we have found a work around but I would like to know how I created the problem. We think we solved the solved the problem by doing a 'save as' to a temporary project and then a 'save as' back to the original project. Up
  13. Creating the DXF file did the trick. I now have a mesh layout that I can use as the background for a CAD or GIS drawing. It did take a few minutes to creae the DXF file but that is OK. Thanks. Another problem solved.
  14. I am receiving requests to see the mesh elements that I have created. The best way for us to use the data would be with a shape file. I have tried several times in the past to export the mesh to a shape file. The program does not export all elements but only the original polygon boundaries. Is this all I can get? I can capture a screen shot but this is not very helpfull. Any suggestions?
  15. I think I found a solution. I just had to quit trying to work with the large scatter files. I created a mesh with a constant elevation. Using the nodes locations from the 2DM file I was able to develop a point file with a point for each mesh node (about 36,000 nodels). Using ArcGIS I was able to interpolate or add an elevation value for each point. I used this point file to create a scatter set and interpolated to the mesh. The results look OK but if I make significant changes to the mesh file I may need to go through that process again. SMS 10.0 handles the mesh and scatter set with no
  16. Thanks for the quick response. Some clearification: I assume the scatter sets are the problem. The original dat is an ESRI 15-ft grid. I converted these to xyz point files. The point files (5) range in size from 77MB to 133MB (I have no idea about the number of points). Thats why I subdivided and maybe I need to further subdivide. The h5 files ranged from 95-165MB. In 9.0 I was able to get by with subdividing the scatter data into 2 areas. I think I resampled the grid to a 45' grid for the previous work. I am trying to convert the grid to a TIN and then go to a point file. This wou
  17. We have been using SMS 9.0 for a couple of years with SRH2D. We recently upgraded to 10.0. I am having a couple of major problems. 1. Program crashes when zoomed in in the map module and trying to move nodes (several times). I have been able to work around this. 2. Program crashes when converting a second group of polygons to mesh without deleting the mesh that was previously created. We are working with a large model (over 40000 elements). We are now trying to expand the model slightly. In version 9.0 I was able to subdivide the scatter set to create the model. The full scatter set w
  18. We are using SMS 10.0 with the SRH2D program (i.e. a generic mesh). We would like to get a table of surface area for all mesh elements with the same element number as given in the 2DM file. We need to get an estimate of the total volume under the water surface. Can this be done? I know that I can get this information on an element by element basis but we are working with over 40,000 elements so that doesn't work. Any ideas?
  • Create New...