Aquaveo & Water Resources Engineering News

CMS-Flow and CMS-Wave are two of the principal components of the Coastal Modeling System. Rubble mounds are an important part of some coastal modeling projects. They are a common engineering structure used as jetties, breakwaters, seawalls, and groins for shoreline protection as well as flow and sediment transport control.

The way rubble mounds are implemented in the Surface-water Modeling System (SMS) is different depending on which CMS model you pick. Rubble mounds in CMS-Flow simulations focus primarily on sediment transport and morphology changes, while CMS-Wave focuses on wave processes. Both of these CMS models have their own coverages and sets of requirements in order to add rubble mounds to the project.

Rubble mounds can be added to CMS-Flow simulations through the CMS-Flow Rubble Mound Jetties coverage. Once this coverage is added, you can create a polygon in the Graphics Window that represents the rubble mound. Double-clicking on the rubble mound polygon opens the Rubble Mound Jetty Attributes dialog where you can define the parameters of the rubble mound structure. This dialog includes inputs for the name, the rock diameter, the porosity, the base depth, and the calculation method. After defining all the parameters, the coverage is ready to be added to the CMS-Flow simulation. Finally, make sure that Calculate sediment transport is turned on in the Model Control , otherwise your rubble mound is just a random polygon that has no effect on the final simulation.

Rubble mounds in CMS-Wave simulations work a little differently than CMS-Flow. CMS-Wave doesn't have a specific rubble mound coverage like CMS-Flow does. Instead, rubble mounds are defined on a CMS-Wave structures coverage. This behaves somewhat similarly to materials coverages that you may be familiar with in other SMS models. Double-click the polygon representing the rubble mound to bring up the Assign Structure dialog. Then you'll add a structure with the green plus sign, select "Rubble-mound" from the structures dropdown, and then whether or not you want to modify the rubble mound by elevation. If you'd like, you have the option of customizing the color and texture SMS will use to fill your polygon structure to something that best suits your project.

CMS-Flow and CMS-Wave each require their own simulations, but you have the option to couple them using inline steering. This is a great option if you're building a comprehensive coastal model.

Head over to SMS and try out adding rubble mounds to your CMS project today!

In the Surface-water Modeling System, you have the option of adding either a 2D or a 3D bridge to your SRH-2D model. But what are the differences between 2D and 3D bridges, and how can you know which one is the best fit for your SMS project? There are pros and cons to each, so we will briefly explore each option, and hopefully by the end you’ll have a better idea of what works best for you.

Starting in SMS 13.3, the 3D Bridge component that was used in previous versions was retired in favor of 3D Structures. 3D Structures can be used to build 3D bridges as well as culverts, and can also be used to calculate overtopping, an option that wasn’t available with 3D Bridges.

For 2D bridges, you have many options to help you customize your bridge, such as setting the bridge width, type and number of piers, abutments, etc.. (For the full list, go to this page of our wiki). All of the options that exist for 2D bridges are also available when building a 3D bridge. Using the 3D structures coverage to build your bridge allows for even more customization, including being able to shape the bridge ceiling so there is variation rather than being a constant along the full length.You can also use the 3D structures dialog to add a UGrid to the Project Explorer so that you can see what the bridge will look like with the mesh. The 3D structures coverage dialogue is able to generate a mesh footprint for your bridge, which automatically includes voids in the mesh for your piers so you don’t have to create them manually.

If you have questions about the specifics of building a 3D bridge, check out the new 3D Structures tutorials, or our wiki page on 3D Structures to get a more thorough introduction.

Building a 3D bridge into your project is an excellent option when you want to go the extra mile with the visual representation of the bridge. Although the idea of using a 3D bridge for everything may sound great because of the extra visualization options, a 3D bridge isn’t going to be necessary, or even practical, for every project. SMS’s calculations will turn out the same regardless of which bridge type you pick. 2D bridges are often a better choice if you’re looking for just a quick representation for your bridge, or if you’re modeling multiple bridges at the same time. Having multiple 3D bridges can slow down the processing speed in a way that having multiple of their 2D counterparts wouldn’t.

Head over to SMS and try out the 2D and 3D bridge building tools in 13.3 today!

The Ground-water Modeling System (GMS) 10.8 beta includes a model interface that is brand new to the software. HydroGeoSphere (HGS) is a unique three-dimensional control-volume finite element simulator developed by Aquanty that is meant to be able to handle all parts of the terrestrial water cycle. It uses a globally-implicit approach to simultaneously solve the 2D diffusive-wave equation for overland/surface water flow and the 3D form of Richards’ equation for variably saturated groundwater flow. This is different from the many other models that simulate only a portion of the hydrologic cycle. HGS includes components for precipitation, evaporation, overland flow, infiltration, recharge, and more. HGS can simulate both surface and subsurface water flow simultaneously for each time step.

In GMS, the base components for an HGS model include: an unstructured (UGrid), HGS coverages, and an HGS simulation. GMS allows multiple HGS simulations to exist in a single GMS project. A 3D UGrid of the project area is required before building an HGS simulation. There can also be multiple UGrids in one project, although only one UGrid can be assigned to each simulation.

The coverages specific to HGS are boundary conditions, observations, and hydrographs. GMS uses feature objects to define the boundary conditions on an HGS boundary conditions coverage. This includes points, arcs, and polygons. The observations coverage allows you to set observation points that will collect time series information during the simulation run. The hydrograph coverage records hydrograph data during the simulation run.

HGS defines materials with domains and zones. The domain contains information about the type of material. The domain is then assigned a zone number, which is then assigned to a polygon. Multiple domains can be assigned to the same zone.

There’s a lot more to HydroGeoSphere than we can cover in one blog post. If you’d like to learn more about HGS, Aquanty has numerous resources on their website. You can look at the HGS Theory Manual or the HGS Reference Manual. They regularly post webinars on their blog and on their LinkedIn. You can also find videos about how to use HydroGeoSphere as well as presentations that have been made by Aquanty’s staff on their YouTube page. We also have our own HGS tutorials that can walk you through the steps of building an HGS model.

We hope you’re excited about the addition of HydroGeoSphere into GMS 10.8, because we certainly are! Download GMS 10.8 to try out HGS today!

When creating a surface-water model, your model will make use of bathymetry data as either elevation or depth. Knowing how the Surface-water Modeling System (SMS) represents depth versus elevation is vital when it comes to creating, running, and understanding a model. SMS uses several different numerical models, and some models require that depth be negative and elevations be positive, while other models require the opposite.

It can become confusing when trying to remember what is needed for each model, which is why the decision was made to standardize how SMS treats elevation and depth across all models. SMS treats all depth values as negative and all elevation values as positive. That way you don’t have to remember how data needs to be entered for each model. If depth data is entered with positive values, SMS will read the data as part of the land elevations, which will produce incorrect calculations.

Some of the most used models where you may see that the elevation values have been changed to fit SMS’s conventions after importing are CMS-FLOW, CMS Wave, and CGWAVE. If you’re not sure whether or not the imported elevation data has been changed and would like to check, then this is a great time to make use of the Mesh module’s find function. Under both the Nodes menu and the Elements menu you’ll see a Find… option listed. You can use this to quickly locate a specific node or element inside of SMS to compare the elevation data with the model’s files outside of SMS.

If SMS has changed the values of the elevation data to account for the required negative depth value, there is no need to be concerned about how this will affect the end result for your model. SMS automatically adjusts the data to match the convention of the model when the project information is exported to the model executable.

Take this information and head over to SMS, more confident that your project’s elevation data will be handled correctly.