Updates & Feature Requests

As more people are using the model, a common desired workflow looks like: 1) Create and fine-tune the model setup using the Web interface

2) Run various different cases, including modifications to water levels, waves, bathy/topo etc Right now step 2) is laborious, requiring alot of manual interaction, including loading the files for each case, clicking Run, setting up the desired output, and then curating (copying, processing) the output. With Chrome, it is possible to automate / script all of step 2). Chrome distributes a "chromedriver" browser application, which can be controlled externally via a library in Python (e.g. Selenium). An example script on how to do this is given below. Right now, the automation abilities allow the user to:

• Create an animated gif, starting at some specified time with a specified frame interval

• Output 2D surfaces of model data (e.g. free surface elevation, velocity) between some start and end times, at a…

Code updates: > Periodic boundary conditions are now functional for the Boussinesq model. Use with care however. Strictly speaking, the wave frequencies and directions in the waves.txt file should be chosen such that an integer number of waves "fit" along the offshore boundary. This is not checked. If you do not have this condition met, the periodic conditions will still work, but the model will artificifically lead to more short-crestedness, as wave crests leaving one boundary with not align with crests along the other boundary. > The model and rendering can now handle different dx and dy values. There are no model limits as to the ratio of these grid sizes. A primary recommendation would be, if surf-zone generated vorticity is of particular interest, do not use a ratio of > ~2 (or less than ~0.5), as this will tend to inhibit the generation of rotational flow. The time step …