...
This page explains the workflow for deriving default settings for a new version of XBeach.
Default settings are important for users with limited experience with XBeach.
For these users the number of exposed settings should be limited, preferably to case related input, like waterlevels, bathymetry and wave conditions, only.
The occasion of setting up this workflow is the preparation of XBeach as assessment model for the Dutch coast.
In line with the current WTI project leading this preparation, this workflow is limited to application for the Dutch coast and 1D.
Different default settings for different applications may be derived by using this workflow.
...
Several topics within this workflow are still being discussed.
These discussions are briefly mentioned below.
...
XBeach allows a variety of performance indicators to be used to compare the performance of one set of settings against another.
For example, a profile comparison with measured data may be used by computing a BSS score.
The BSS score itself, however, is subject to discussion for this purpose.
Moreover, comparison data is often obtained from flume experiments on scale.
These experiments use scaling rules that are derived by comparing erosion profiles rather than profile shape.
The profile shape for these tests can thus not be used.
For now, we use the erosion volume above SSL as performance indicator.
Another advantage of this indicator is that it relates well to other calibration studies for dune assessment models in the Netherlands.
...
Comparison with data is often done using data obtained from flume experiments.
These experiments are performed on scale.
XBeach allows us to simulate the experiment at the scale of the experiment rather than on a 1:1 scale.
As for now, this is not done for two reasons.
First, the scaling within XBeach is still subject to discussion.
Second, other calibration studies for dune assessment models also first scaled the experiment results and then performed the calibration.