Bending the rules

Bending the rules - how to make dBSea work smarter a description of a workaround for SEL calculations
As is often the case, my blog posts are based on conversations with dBSea users, and this is no different. In underwater noise propagation modelling we are often tasked with finding both zero-to-peak, peak-to-peak and impulse-SEL (z-p, p-p, iSEL) for scenarios involving impulsive noise sources such as impact pile driving or seismic surveys (see ISO 18405- 2017 for details on sound metrics [1]).

To calculate z-p and p-p levels we have to use a propagation method that allows us to take into account arrival times and phase for the arriving signal (Figure 1). In dBSea that means using the dBSeaRay solver that uses raytracing to find arrival times, transmission loss and phase of the impulse at all receiver positions in a scenario.

This type of calculation becomes very resource intensive as many paths need to be calculated for each receiving point and each receiving point has to store info…

One size fits all?


Update 2.2 - Focus on getting your data in and out

Importing bathymetry, the basis of your model

A side-on view

dBSea 2.1

Dolphins in Greece

On the bottom

one, one hundred, one thousand or ten thousands?

Catch you on the flip side (of sound) - Updated!

Underwater noise course Belfast

Making it move