Jump to content
GMS, SMS, and WMS User Forum


  • Posts

  • Joined

  • Last visited

  • Days Won


heimo last won the day on March 17 2011

heimo had the most liked content!

heimo's Achievements


Newbie (1/14)



  1. Hi! I tested you file and it opened in SMS 9.0. I also created following test file. Both nodes and elements are loaded and shown correctly. May be a SMS version problem. Testgrid.2dm
  2. I had a similar problem with an other program. Our IT managed to avoid it be generating a rule to allow the execution of bat files generated by specified program xxx. For this they needed a unique file hash of a bat file generated by the program. I just checked the net and the file hash can be obtained either with Windows Powerhell ('Search programs and files/powershell') or with 7-zip by right clickin on file name, CRC, and select encrypition (see image attached). Maybe your IT can go from here and find out how to determine the program that generated the file and then generate the rule. Or then our IT used some other method than file hash for that. Wishes, Heimo
  3. Well, I was talking about RMA2 when I said BC - not RMA4. Did you check the users manual? I would advice you to read about the use of cards BC and BQ from 'RMA2 Users Guide'
  4. Not sure about definition by node (point) but you could read from RMA2 users guide about BQ and BC (especially BQN and BCN). I normally use discharge and load by elements (BQE in RMA2 and BLE in RMA4). According to the guide: BCN node_num 11000 1.1 1.2 should define x-vel=1,1 and y-vel=1.2 to node_num, but like I said, I haven't tested. Anyway, for loads, the element approach is more understandable. You will propably need to add these BCN etc lines to your .bc (and .trn) files with notepad or similar editor. At least this is the case for older SMS versions, which do not allow defining all of these boundary conditions from within SMS. best regards, heimo
  5. Hi Cameron, I managed to try out the new version, but alas - I use SMS9 and XMDF (at least in the form produced by SRH) doesn't seem to be supported by it. So, unfortunately I'm stuck with these make shift tryouts at least for now. Heimo
  6. I tried to write a simple program that would generate a 'generic ascii data file' from SRH output files, but had problems. I then realized that SRH output in SMS format writes data to cell centers instead of nodes. When you select 'SRH' as output format, this program (hopefully) works. Edit the file 'MeshInfo.dat' to suite your model and run 'CreaGene.exe' in dos. So, this program will write a file with data on all nodes and all timesteps (if wished) so that time series and animations of SRH results can be made (one file per variable). No guarantees given, though Heimo CreaGene.zip
  7. Hi Cameron. The program simply reads the lines with given x,y nodal coordiantes and appends (with dos for loop) it to tserie.txt. This file you can then open in excel, sort the rows according to time step and draw your time series. Here's a clip of the mail to Vera: --- clip begins --- Steps here: 1) generate an empty file "tserie.txt" (with notepad). This file can atually have a header line if you wish. All data from dat files is then simply appened to the end of this file 2) generate a file called "TsPoint.txt" that contains the X and Y coordinates of the selected node 3) run the program timser.exe in dos for %a in (c_sms*.dat) do timser %a NOTE that dos has a restriction of 8+3 charaters for file names, so you'll have to run SRH so that the name of the case is restrited to 1 char (as you have more that 100 steps so that the maximum is 'c_sms999.dat' which is 8 chars long). On the other hand, you coud try to rename/copy the files, although I can't think of a fast (automatic) way to do that. Heimo
  8. Vera, here is the simple program (with some files) I mailed you about to extract nodal info from the SRH dat files. TsPoint.zip
  9. Hi Vera, Just got back from holidays. You may have already solved this, but if not - here's how to open those dat files. You should open it as a scatter set. In SMS9 you just open the the dat-file and as SMS does not automatically recognize it, there should appear a window where the topmost selection is 'use import wizard'. Select that option (default options should be OK. If not, add 'comma' to column delimiters). Then select 'Next'. Now you can choose what data you want to import. The file with headers is Type X Y Z Not Mapped Not Mapped etc... Header Point_ID X(m) Y(m) Bed_Elev(m) etc.... 1 123.4 567.8 -10.00 ... Select the types as: X --> not mapped Y --> X Z --> Y Not Mapped (=Bed_elev) --> scalar data etc (all the rest to --> scalar data except for Vel_X(m/s) -->Vector X Vel_Y(m/s) -->Vector Y also change the header line of both Vexor X and Vector Y to same name, e.g. 'velocity'. [ Btw, If you have lots of time steps to import, it is adviseable to remove the 'point number' header and the numers from the dat files and renaming the vector header line names with a simpe program, via excel or someting else you can think of. This should make it easier to open the files.] Now you can use the scatter set as such (by selecting display options/Scatter set and checking some of the following three options 1) points/use contour color scheme, 2) contours and 3) velocity vectors) Also, you can interpolate the scatter data to the 2dm mesh by clicking on each data set and selecting from menu Scatter/Interpolate to mesh. (No actual interpolation is done as the scatter points and mesh nodes coincide) Heimo
  10. Hi again Vera! I think I uploaded this option for you way back in april(?). If not - I'm sorry. Anyway, here's a short demo run (although with very small elevation forcing. In the doc there is the start of the bc-file and some images. As the most important think, I believe you need to make sure the inital surface elevation is the same as the boundary elevations for first time step. So check that all three elevations in your model are the same (both boundaries and initial wse). Heimo Elevation_boundaries.doc
  11. Hi! I tried to send the 8Mb and the 950 kB from my work pc, but that didn't succeed. I also tried to send the smaller package (a zip file) from my person e-mail account but failed. I got the following error message: (at the end f it, there's "Our system detected an illegal attachment on your message." so it seems attachements are not allowed in the mail?) "
  12. I believe you can install the new SMS (preferably to different pc than what you are using), then copy the rma2/rma4 executables and the dat-files to your pc. After that you can uninstall the new SMS (as you will not have the password for that). Now you have the new models. On the other hand - I have an installation package of the models (without SMS) that was downloaded from aquaveo some years ago (in 2008). There is, among others, v454 of rma2. I can mail it to you if you give your e-mail address. The file size is 8.4 Mb. Or I could zip just rma2/4, gfgenv45 and dat files (size 950 kB) and mail you that. Yes, I think you can't modify the max node number in your version of the programs. Of data size, Is there need for high resolution at boundaries? You could make the elements there larger by redistributing the vertices on the boundary (-ies). Just select the bounday arc and select 'Feature Objects/Redistribute vertices' and give a reasonably large value (mesh size) for the vertex spacing. That also reduces the number of points in the arc, so that (with luck) you would not have to split the arc as given in my previous posting. This redistribution can be done of course also for shoreline arcs. Please, save your original map data however, first. Redistributing a complex shoreline with too large vertex spacing can lead to an unwanted shoreline apperance (details smaller than the spacing will be removed). The other way to decrease the number of elements is to use so called refine points. In the doc below is a short example. In short, add (in map coverage) some points inside your mesh to areas of lesser importance, assign the points as refine points (well, we should in this case name them the opposite) and regenerate the mesh with an outcome of larger element sizes near the points). You can give each point a different size value or same value for all points. Refine.doc Regards, Heimo
  13. Hi again Vera, If you can't upgrade your rma2 executable, a not so elegant way could be to split your check line (providing you are using them as boundary conditions). Here are two pictures, where the left side of the grid is divided to three bounday lines. Note that there needs to be a disabled element (show as black triangle in the image) between two boundary lines (i.e. they cannot be connected). In this example, the boundary lines have incoming discharges of 500, 100 and 500 m3/s and the right side is surface elevation boundary.
  14. Vera, I'm using a newer version of RMA2 (v4.54) with SMS9.0. It seems that the older version you are using does not support dynamic allocation of memory as it was just added to v4.54. Here is the version history from http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=ARTICLES;394 Version 4.54 (May 2002) RMA2 static memory was converted to dynamic memory allocation. Minor bug fixes and enhancements. The files r2memsize.dat and r4memsize.dat are situated at the 'models'-directory (where rma2v45.exe etc are located).of SMS installations since SMS9.0 I am not sure, if your licence agreement allows this, but you could download a newer version of SMS full installation and get the new rma2 (and rma4 if necessary) from that package. Then, you need to point your SMS to these executables (in SMS9 it is done in Edit/Preferences/File Locations) Regards, Heimo
  • Create New...