Jump to content
GMS, SMS, and WMS User Forum


  • Content count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About Joel

  • Rank

Contact Methods

  • ICQ
  1. Thanks Rusty Joel Bailey JFA Consultants
  2. heimo, Thanks for your help, this does fix the problem (although, I'm not sure why!). I have also discovered that if the log is created prior to running the model (e.g. if you re-run the model after running it previously, or if you create a blank .log file), then the problem doesn't occur. Thanks again, Joel
  3. Hi all, We are having a problem with BOUSS2D. For a number of projects, we need to run many BOUSS2D simulations to test a range of different wave conditions. For example, a recent piece of work we did involved more than 450 model runs. In order to do this, we use the SMS interface to set up the model runs, and then run all of the models through the command prompt (as per page 39 of the BOUSS-2D manual) using a batch file. We have found an issue, which we believe has only started occurring since we updated from SMS 10.0 to SMS 10.1 (I understand that associated with this was an updated from bouss2d V2 to V3), the problem is as follows: After completing each model run and writing the solution files/outputs, the model encounters an error during writing of the log file. A windows error box pos up saying that bouss2d has encountered an error, and upon viewing the log file, it is always missing the last few timesteps (generally 10 to 30 timesteps missing). This is a problem, because when the error pops up, the command prompt hangs, and doesn’t move onto the next model run, until we click OK on the error window. In this regard, we are currently unable to automatically batch our model runs. If we run the exact same model run through the SMS interface, the log file writes fine, and there is no error, but we can’t “batch” model runs in this way (at least not to my knowledge). Has anyone else come across this problem? Regards Joel Bailey JFA Consultants
  4. Loading ts1

    Hi there We have experienced the same problem. When loading the .ts1 file, the following error message is generated (see attached image also): "Error reading BOUSS2d (.ts1) file: values" It appears to occur when there are more than 3 probes (more than 4 columns of data) in the .ts1 file. We are working around this by running the model multiple times with 3 probes at a time (obviously a less than ideal situation). We have emailed support about this previously - looking forward to seeing this issue rectified. Regards Joel Bailey JFA Consultants
  5. Modelling a breakwater on bouss2d

    Hi John, We work extensively with Breakwaters in Bouss2D. I'm not clear where your problem lies, so I will respond to the original queries from Benjamin: 1) The BOUSS2D manual and associated technical notes indicate that porosity layers can be used to simulate breakwater effects, however we have had limited success with this - note our work is predominantly with rubble mound breakwaters. We generally simulate breakwater effects using damping strings - the manual and Bouss2D page on the SMS Wiki (http://www.xmswiki.com/xms/SMS:BOUSS-2D) provide a chart which can be used to estimate the required damping parameters based on a desired reflection co-efficient for the breawater. Be careful using damping strings in smale scale applications (e.g. entrances to small harbours/inlets where damping strings have the potential to reduce the effective entrance width). 2) These standing wave effects occur when waves reflected form the structure interact with the incoming wave train. It is important to note that these standing wave effects do occur in reality (this effect is known as clapotis http://en.wikipedia.org/wiki/Clapotis). If your wave maker is too close to the breakwater, or if your reflection coefficient for the breakwater is too high (see number 1 above), these effects may become amplified in a non-realistic manner (this may also cause the model to crash). Some methods to avoid this include: - use realistic reflection co-efficients - keep your wavemaker at least 4 wavelengths (rule of thumb) from any structures in your domain - consider using an internal wavemaker with damping on the seaward boundary - if you are not concerned with the region in between the wave maker and the seaward side of the breakwater, consider applying some strong damping to stop the formation of standing waves. As noted above, there is some good info on the Wiki regarding these issues (http://www.xmswiki.com/xms/SMS:BOUSS-2D). As a word of caution, remember that these standing wave effects are real before trying to eliminate them. In our work, we sometimes have to carry out additional post processing and analysis to separate the incoming and reflected wave trains. Regards Joel JFA Consultants
  6. To any other users experiencing this problem, I have received a reply from Aquaveo support confirming the bug, and indicating it should be fixed in the next update. Thanks to Aquaveo support for getting back to me, I look forward to the update. Cheers Joel
  7. Hi SMS Team/Users We are experiencing a problem with SMS 10.1 (using SMS10.1.1), whereby we are not able to manually split a bouss2d cell string. This problem is occurring on two separate machines that we have SMS 10.1 installed on. When we select a grid node and try to split the string, SMS locks up for a period of time, before an error box pops up, with no information (just an OK button) – see screen grab attached. After this happens, SMS will not allow us to do anything (not even save). I have attached a zip file with a project where this error occurs. It happens on small and large grids. For anyone else experiencing this problem, we are working around this by splitting cell strings in SMS 9.2, and then transferring back to SMS 10.1, but this is abviously not ideal. Cheers Joel Bouss2D Cellstring Test.zip
  8. Hi SMS Team, I have a feature request: In the Spectral Energy toolbox (found for example in the BOUSS2D menu), it is possible to generate or import wave spectra, create polar plots of the directional spectra, and then create integration plots of Energy vs Direction or Energy vs Frequency. Unless I have missed something, it is not possible to export these plots (say to the clipboard) for pasting into reports etc. This functionality would be very useful. The integration plots from the Spectral Energy toolbox are very similar in style to the typical plots that are created from SMS through the Plot Wizard. It would also be very handy if the data from the integration plots could be exported (in the same way that data from other plots in SMS can be exported). Regards, Joel
  9. Problem with Bouss2D in SMS 10.1

    After looking into this problem in more detail, I discovered that the problem only arises if you use SMS 10.1 to run a BOUSS2D project that was created/saved in SMS 10.0. If you do this, without first saving the project from SMS 10.1, the direction grids will not be output. Cheers Joel
  10. Dear SMS team, I have encountered a problems with BOUSS2D V3, which is included as part of SMS 10.1. Wave direction grids are not being output, even through this output is specified in the .par file. Could you please confirm whether this is a problem with the code, or if we are the only ones experiencing this problem. Regards Joel
  11. Hi there, Can someone advise whether it is possible to have a manually varied (time series) of wave parameters input on the wavemaker in BOUSS2D? For example, I have set up a model and wish to test incident wave heights of 1, 1.5, 2m etc. If this is possible, how would it be done? Regards Joel
  12. Problems with PTM

    Thanks for your response John, In answer to your queries: - .err is not being generated - I clicked OK after setting the XMDF paths, with no change to the result Joel
  13. Problems with PTM

    Hi all I have been trying to run a simple PTM run to test it's capabilities. First I tried forcing the particles with outputs from a CMS-FLOW simulation I completed recently. While I followed the documentation as closely as I could, and was confident that I had set everything up correctly, the model would not run, and kept giving the following error message: forrtl: severe (157): Program Exception - access violation I thought that perhaps the problem was with using the CMS-FLOW outputs, so I tried to force the particles with outputs from the ADCIRC tutorial simulation. Again, after setting up the model I received the same error. I have tried a number of variations on the model setup: different time steps, with and without particle sources/traps, etc. I also downloaded and installed the latest model exe updates, without success. If someone could provide any insight on whether I'm doing something wrong, or whether there is a bug in the model it would be much appreciated. Regards Joel