I'm looking to implement NHWAVE, in the future for the purpose of considering landslide generated tsunamis. We've had a first pass at setting up HYPRE and NHWAVE, both have compiled, and I've subsequently gone to run some of the supplied example cases - periodic wave over submerged bar and the Enet-Grilli lab slide. In both cases, the model ran to completion. However, the water level time series for both appear to be indicating the input surface deformations are not propagating rapidly through the grid, see the attached plot which indicates the surface water level near the left linear wave boundary condition, sampled at 1s intervals (period = 2s)

The appearance is similar to an overdamped vibrating string for example. I'm wondering if you've seen this issue pop up before, and if you might have any suggestions for its resolution? I was also wondering whether there might be an issue with the performance of the solver as it's been set up, as it is difficult to see how the problem could be attached to the nhwave source code.
Thanks and regards
Zac Couper
I'm looking to implement NHWAVE, in the future for the purpose of considering landslide generated tsunamis. We've had a first pass at setting up HYPRE and NHWAVE, both have compiled, and I've subsequently gone to run some of the supplied example cases - periodic wave over submerged bar and the Enet-Grilli lab slide. In both cases, the model ran to completion. However, the water level time series for both appear to be indicating the input surface deformations are not propagating rapidly through the grid, see the attached plot which indicates the surface water level near the left linear wave boundary condition, sampled at 1s intervals (period = 2s)
The appearance is similar to an overdamped vibrating string for example. I'm wondering if you've seen this issue pop up before, and if you might have any suggestions for its resolution? I was also wondering whether there might be an issue with the performance of the solver as it's been set up, as it is difficult to see how the problem could be attached to the nhwave source code.
Thanks and regards
Zac Couper