.. _hdro-0006:
===============================================================================
Debris Group Motion Over a Frictional Bed - Digital Flume (OSU DWB) - MPM
===============================================================================
+---------------+----------------------------------------------+
| Problem files | :github:`Github ` |
+---------------+----------------------------------------------+
.. contents:: Table of Contents
:local:
:backlinks: none
.. _hdro-0006-overview:
Overview
--------
.. figure:: figures/hdro-0006.gif
:align: center
:width: 600
:alt: HydroUQ GUI configured as a digital flume for the Oregon State University's Directional Wave Basin; debris containers, harbor apron, and obstacle rows visible.
:figclass: align-center
This example examines **tsunami-driven debris spreading on a flat, frictional testbed** and compares **HydroUQ + MPM** simulations to the laboratory findings of **Park et al. (2021)** [Park2021]_. In the experiments, debris elements of **two densities** (HDPE plastic and wooden material) were released in groups with varied **starting orientations**, then driven by a **piston-generated solitary wave** across a dry, frictional bed toward **two square obstacles**. Optical measurements tracked **final dislocations**, **local debris velocities**, and **collision events**, alongside the background **flow velocity**.
.. figure:: figures/hdro-0006_Schematic.png
:align: center
:width: 600
:alt: Plan view of the numerical setup showing debris pair/group placement regions, obstacle locations, and sampling lines for displacements and velocities.
:figclass: align-center
We build a matching **digital flume** in HydroUQ and use the **Material Point Method (MPM)** (ClaymoreUW, multi-GPU [Bonus2025ClaymoreUW]_) to:
- Reproduce the **wave forcing** (tsunami-like wave) and **bed friction** conditions in the OSU DWB flume.
- Initialize **debris groups** with **HPDE plastic-like properties** in **arrayed orientations**.
- Record **wave gauge elevations**, **debris motion**, and **fluid-debris loads on obstacles**.
While this example restricts itself to a subset of behaviors explored in Park et al. 2021, a motivated user could assemble a simulation campaign which targets the following behaviors for comparison:
1. **Asymmetric pair interaction**: observe if higher-density debris influences the **mean longitudinal displacement** of the lighter mate, whereas the lighter element exerts **negligible influence** on the heavier one.
2. **Orientation insensitivity**: verify whether initial group orientation shows **any measurable effect** on final displacement.
3. **Obstacle effects**: check if obstacle rows alter **passage and collision probability**; if lighter debris tends toward **more collisions** than heavier debris—except in **mixed groups**, where lighter debris might show **reduced** collision probability.
4. **Field context**: examine if the **reflected wave** and **debris-debris interactions** modulate spreading and collision statistics, and whether **element density** remains the dominant predictor of collision risk.
.. figure:: figures/hdro-0006_Debris_Configuration.png
:align: center
:width: 600
:alt: Plan view of the numerical setup showing debris pair/group placement regions, obstacle locations, and sampling lines for displacements and velocities.
:figclass: align-center
.. _hdro-0006-set-up:
Set-Up
------
Step 1: UQ
~~~~~~~~~~
Configure **Forward** sampling to explore structural/material uncertainty under a fixed hydrodynamic signal.
- **Engine**: Dakota
- **Forward Propagation**: Sampling method (e.g., **LHS**) with ``samples`` (e.g., ``20``) and a reproducible ``seed`` (e.g., ``1``).
.. figure:: figures/hdro-0006_UQ.png
:align: center
:alt: HydroUQ UQ panel with Dakota Forward selected, sample count and seed set.
:figclass: align-center
Step 2: GI
~~~~~~~~~~
Set **General Information** and **Units** consistent with experiments (length, time, density, gravity). Record project metadata.
- Structure name: ``Concrete Obstacles @ OSU Directional Wave Basin``
- Units: choose a consistent set (e.g., N-m-s or kips-in-s)
.. figure:: figures/hdro-0006_GI.png
:align: center
:alt: General Information panel with project name, metadata, and unit selections.
:figclass: align-center
.. note::
Keep **GI**, **SIM**, **EVT**, and **FEM** units consistent. Match MPM's length/time scales and OpenSees integration settings (e.g., time step). Verify any force/unit conversions used during load mapping.
Step 3: SIM
~~~~~~~~~~~~~~~~~~~~~~~
The structural model is as follows: a single-story Multi-Degree-of-Freedom system (MDOF, see :ref:`lblMDOFSIM`) replicating a structural box in the experimental tests.
.. figure:: figures/hdro-0006_Structure.png
:align: center
:alt: Schematic of a single-story MDOF structure representing a structural box undergoing deflection from MPM derived hydrodynamic loading.
:width: 200
:figclass: align-center
Schematic of a single-story MDOF structure representing a structural box undergoing deflection from MPM derived hydrodynamic loading.
.. note::
The structure will be represented initially as a **rigid boundary** in MPM to recover local hydrodynamic forces at grid nodes for direct comparison with **load-cell** data. Structural dynamic response is added later by mapping these loads onto an **OpenSees** model defined here in the SIM panel with analysis options set in the FEM panel.
**Uncertain structural properties** (treated as RVs; see Step 7):
- ``w``: Weight. Mean ``144``, stdev ``12``
Bind parameters via setting alphabetic characters in the variable input boxes (e.g., ``w``) so the **RV** panel recognizes and manages them automatically.
.. figure:: figures/hdro-0006_SIM.png
:align: center
:alt: SIM panel showing a single story MDOF system with uncertain variables w.
:figclass: align-center
While not necessary to have, we show the template OpenSees model for your reference. The script generated in the backend by the MDOF module resembles the following, `MDOF.tcl `_:
.. raw:: html
Click to expand the OpenSees input file used for this example
.. literalinclude:: src/MDOF.tcl
:language: tcl
:linenos:
.. raw:: html
Step 4: EVT
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In this walk-through we will give a detailed step-by-step configuration of the MPM EVT module.
**Settings**
Open ``Settings``. Here we set the simulation time, the time step, and the grid resolution, among other pre-simulation decisions.
.. figure:: figures/GUI_Settings.png
:align: center
:width: 600
:alt: HydroUQ Settings panel where simulation time, time step, and grid resolution are configured.
:figclass: align-center
**Bodies**
**Geometry**
- **Fluid geometry**
Open ``Bodies`` / ``Fluid`` / ``Geometry``. Here we set the geometry of the flume's fluid. Note that it is simply a rectangular prism which will be automatically modified to be flush with the defined bathymetry coordinates.
.. figure:: figures/GUI_Bodies_Fluid_Geometry.png
:align: center
:width: 600
:alt: Example of geometry fields for the flume, debris region, and structure location in the GI/SIM context.
:figclass: align-center
- **Debris geometry**:
Open ``Bodies`` / ``Debris`` / ``Geometry``. Here we set the debris properties, such as the number of debris, the size of the debris, and the spacing between the debris. Rotation is another option, though not used in this example. We've elected to use an 4 x 5 grid of debris (longitudinal axis parallel to long-axis of the flume).
.. figure:: figures/GUI_Bodies_Debris_Geometry.png
:align: center
:width: 600
:alt: HydroUQ Debris Geometry panel showing an ordered 4x5 array specification.
:figclass: align-center
**Material**
- **Fluid material**:
Open ``Bodies`` / ``Fluid`` / ``Material``. Here we set the material properties of the fluid. You may choose to use a realistic bulk modulus value of 2.1 GPa for the water, or you may soften it to 0.21 GPa to accelerate the simulation and reduce numerical stiffness with fairly minimal changes in our final results.
.. figure:: figures/GUI_Bodies_Fluid_Material.png
:align: center
:width: 600
:alt: HydroUQ Fluid Material panel for setting water material parameters.
:figclass: align-center
- **Debris material**:
Moving onto the creation of an ordered debris array, we set the debris properties in the ``Bodies`` / ``Debris`` / ``Material`` tab. We will assume debris are made of HDPE plastic, as in experiments by Park et al. 2021 [Park2021]_, Mascarenas 2022 [Mascarenas2022]_, and Shekhar et al. 2020 [Shekhar2020]_, and set properties accordingly. Motivated readers are encouraged to try to replicate the wooden debris from Park et al. 2021 as well. Note that both the wooden and HDPE debris were given HDPE base-plates so that friction coefficients against the flume floor remained constant.
.. figure:: figures/GUI_Bodies_Debris_Material.png
:align: center
:width: 600
:alt: HydroUQ Debris Material panel with HDPE properties.
:figclass: align-center
**Algorithm**
Open ``Bodies`` / ``Fluid`` / ``Algorithm``. Here we set the algorithm parameters for the simulation. This is an advanced feature of the MPM module, it is best not to alter it too much. We choose to apply F-Bar antilocking to aid in the pressure field's accuracy on the fluid. The associated toggle must be checked, and the antilocking ratio set to 0.9, loosely. For full bulk modulus water, you may need to increase this value to alleviate numerical stiffness.
.. figure:: figures/GUI_Bodies_Fluid_Algorithm.png
:align: center
:width: 600
:alt: HydroUQ Algorithm panel with F-Bar anti-locking toggled on and tuned ratio.
:figclass: align-center
In ``Bodies`` / ``Debris`` / ``Algorithm`` we set debris for compatibility with the fluid as follows: ASFLIP is turned on and F-Bar antilocking is turned off. We keep ASFLIP tuning values at their default of zero as we do not need advanced behavior in this example.
.. figure:: figures/GUI_Bodies_Debris_Algorithm.png
:align: center
:width: 600
:alt: HydroUQ Algorithm panel for debris compatibility with fluid.
:figclass: align-center
**Partitions**:
Open ``Bodies`` / ``Fluid`` / ``Partitions``. This is an advanced feature of the MPM module which allows us to partition material bodies across hardware devices to optimize simulations. These may be kept as their default values, which have already been set for compatibility on the remote HPC system.
.. figure:: figures/GUI_Bodies_Fluid_Partitions.png
:align: center
:width: 600
:alt: HydroUQ Partitions panel for multi-GPU decomposition.
:figclass: align-center
Next, ``Bodies`` / ``Debris`` / ``Partitions`` defines a partition where the debris may exist in our flume domain and defines the hardware device (i.e., GPU) that they will be simulated on. Keep this as the default unless you are an advanced user.
.. figure:: figures/GUI_Bodies_Debris_Partitions.png
:align: center
:width: 600
:alt: HydroUQ Partitions panel for multi-GPU decomposition.
:figclass: align-center
**Structure**:
Finally, open ``Bodies`` / ``Structures``. Uncheck the box that enables this body. We will not model the structure as a deformable MPM material body in this example, instead, we will approximate it as a rigid MPM boundary a few steps from now. After the MPM simulation we will map loads from the boundary to an OpenSees structure for structural analysis, see Steps 3 and 5 for configuration.
.. figure:: figures/GUI_Bodies_Structure.png
:align: center
:width: 600
:figclass: align-center
HydroUQ Bodies Structures GUI
**Boundaries**
- **Wave Flume boundary**:
Open ``Boundaries`` / ``Flume Facility``. We will set the flume boundary to be a rigid body, with a fixed separable velocity condition. Bathymetry joint points should be identical to the ones used in ``Bodies`` / ``Fluid`` / ``Geometry``. Note that we set static and dynamic friction coefficients to be 0.66. This is approximately as seen in the experiments, but neglects finer-aspects of wetted vs non-wetted contact, etc.
.. figure:: figures/GUI_Boundaries_Flume.png
:align: center
:width: 600
:alt: HydroUQ boundary setup for the flume facility.
:figclass: align-center
- **Wave Generator**:
Open ``Boundaries`` / ``Wave Generator``. Fill in the appropriate file-path for the wave generator paddle motion, ``wmdisp_TWB_Amp2_SF375_twm10sec_1200hz_16052023.csv``. It is designed to produce tsunami-like waves after broaching the bathymetry crest.
.. figure:: figures/GUI_Boundaries_WaveGenerator.png
:align: center
:width: 600
:alt: HydroUQ Wave Generator panel.
:figclass: align-center
- **Rigid Structure**:
Open ``Boundaries`` / ``Rigid Structure``. This is where we will specify the structure as a boundary condition. By doing so, we can determine the exact loads on the rigid boundary grid-nodes, which automatically map to the model defined in the SIM and FEM tab in Steps 3 and 5 for potentially nonlinear UQ structural response analysis.
.. figure:: figures/GUI_Boundaries_RigidStructure.png
:align: center
:width: 600
:alt: HydroUQ Rigid Structure boundary panel for the structure.
:figclass: align-center
- **Rigid Walls**:
Open ``Boundaries`` / ``Rigid Walls``. Set to encompass the flume domain.
.. figure:: figures/GUI_Boundaries_RigidWalls.png
:align: center
:width: 600
:alt: HydroUQ Rigid Walls panel.
:figclass: align-center
**Sensors**
- **Wave Gauges**:
Open ``Sensors`` / ``Wave Gauges``. Set the ``Use these sensor?`` box to ``True`` so that the simulation will output results for the instruments we set on this page.
Four wave gauges will be defined. The first is located prior to the bathymetry ramp, the second at the foot of the ramp, the third near the bathymetry crest, and the fourth near the debris and structures.
Set the origins and dimensions of each wave gauge to encompass at least one grid-cell in each direction as in the table below. To match experimental conditions, we also apply a 30 Hz sampling rate to the wave gauges.
.. figure:: figures/GUI_Sensors_WaveGauges.png
:align: center
:width: 600
:alt: HydroUQ Wave-Gauge sensor configuration with sampling rate and gauge extents.
:figclass: align-center
These wave gauges will read all numerical bodies (i.e. particles) within their defined regions at every sampling step and will report the highest elevation value (Position Y) of a contained body as the free-surface elevation at that gauge. The results are written into our sensor results files which we will later analyze.
- **Load Cells**:
Open ``Sensors`` / ``Load Cells``. Set the ``Use these sensor?`` box to ``True`` so that the simulation will output results for the instruments we set on this page. Two load cells are defined so that we may map loads onto two nodes of our OpenSees structural model which we defined in Steps 3 and 5. Output frequency is set to 120 Hz to capture primary load phenomena. Note that the experiments themselves were not concerned with measuring structural load, as we do here.
.. figure:: figures/GUI_Sensors_LoadCells.png
:align: center
:width: 600
:alt: HydroUQ Load-Cell sensor configuration at the structure boundary.
:figclass: align-center
**Outputs**
Open ``Outputs``. Here we set the non-physical output parameters for the simulation, e.g. attributes to save per frame and file extension types. The particle bodies' output frequency is set to 2 Hz, meaning the simulation will output results every 0.5 seconds. This is to save disk space and reduce I/O load, but it may be increased if you wish to make animations (e.g., 10 - 30 Hz). Fill the rest of the data in the figure into your GUI to ensure all your outputs match this example. You may alter output attributes if you are an advanced user familiar with ClaymoreUW attributes and wish to perform more advanced analysis.
.. figure:: figures/GUI_Outputs.png
:align: center
:width: 600
:alt: HydroUQ Outputs panel with file types and output frequency.
:figclass: align-center
Step 5: FEM
~~~~~~~~~~~~~~~~~~~~~~
This example insofar focused on **hydrodynamic forces** measured on rigid structures. To perform true structural response analysis, map recovered boundary loads to an **OpenSees** model in **SIM** and configure dynamic analysis here as in other HydroUQ tutorials.
**Solver**: OpenSees dynamic analysis. Check:
- Integration step compatible with MPM sensor output interval.
- Algorithm/convergence tolerances suitable for expected nonlinearity.
- Damping model as needed (e.g., Rayleigh).
.. figure:: figures/hdro-0006_FEM.png
:align: center
:alt: FEM panel with integration, algorithm, solver, and damping settings.
:figclass: align-center
Step 6: EDP
~~~~~~~~~~~
Select **Engineering Demand Parameters (EDPs)** to summarize response:
- Peak Floor Acceleration (PFA)
- Root Mean Square Acceleration (RMSA)
- Peak Floor Displacement (PFD)
- Peak Interstory Drift (PID)
.. figure:: figures/hdro-0006_EDP.png
:align: center
:alt: EDP panel with standard selections enabled.
:figclass: align-center
Note that other quantities of interest (QoI) are theoretically obtainable from HydroUQ, if the custom EDP module is configured. E.g.:
- Wave: free-surface elevation η(t) at gauges.
- Debris motion: **longitudinal displacement** (forward/back), **lateral spreading angle**, **stack interaction metrics** (contact counts/overturns).
- Loads: **obstacle force time histories** (impact peaks, impulses).
Step 7: RV
~~~~~~~~~~~~~~~~~~~~~
Define distributions for structural RV:
**Structural**
- ``w``: **Normal** (mean ``144``, stdev ``12``)
.. figure:: figures/hdro-0006_RV.png
:align: center
:alt: RV panel listing weight (w) with Normal distributions and parameters.
:figclass: align-center
For future UQ, consider:
- Debris: mass variance, friction coefficients (debris-apron, debris-debris).
- Wave: amplitude/period tolerance relative to piston motion.
- Obstacles: small misalignment/placement tolerance.
.. _hdro-0006-simulation:
Simulation
----------
This case was executed on **TACC Stampede3** using **2x NVIDIA H100** GPUs on a single node (queue: ``h100``).
Simulated physical time: **30 seconds**. Wall time: **180 minutes** (allow ample **Max Run Time** in job settings).
.. important::
Provide generous **Max Run Time**, on the order of 180 minutes, to complete the run and post-processing before scheduler limits are reached.
.. warning::
Keep sensor regions, counts, sampling rates, and output frequencies reasonable—excess I/O can dominate runtime.
**Outputs**
- Sensor CSVs (gauges, debris CoM, loads) at your chosen rates.
- Particle/field snapshots (e.g., BGEO/VTK) for visualization/diagnostics.
.. _hdro-0006-analysis:
Analysis
--------
**Accessing Results and Simulation Files**
When the simulation job has been completed, the results and simulation files will be available on the remote system for retrieval or remote post-processing.
Retrieving the ``results.zip``, ``templatedir.zip``, ``workdir.tar.gz``, and ``MPM`` folders will allow you to analyze all of the simulation output (e.g., hydrodynamic, structural, uncertainty quantification).
- ``results.zip``: Contains primary uncertainty quantification output and MPM sensor files. This will be the primary place for analysis.
- ``templatedir.zip``: Contains template and workflow files for the job. This is an important resource for debugging your workflows.
- ``workdir.tar.gz``: Contains the working directories in which each unique simulation was ran. This is where structural response uncertainty is expanded on typically.
- ``MPM``: Contains all the MPM simulation files. Includes the raw particle output frames which can be used to create animations or to perform more advanced post-processing.
The most straightforward way to retrieve the most important files, ``results.zip`` and ``templatedir.zip``, is by clicking the ``GET From DesignSafe`` button in ``HydroUQ``.
.. figure:: figures/getFromDesignSafe.png
:align: center
:width: 400
:figclass: align-center
HydroUQ ``GET From DesignSafe`` button, which opens up a jobs table of all your remote simulations.
Then, right-click on your job (if it is finished) and select ``Retrieve Data``. This will download ``results.zip`` and ``templatedir.zip``.
.. figure:: figures/retrieveData.png
:align: center
:width: 400
:figclass: align-center
Locating the ``Retrieve Data`` button in the HydroUQ remote jobs table.
HydroUQ will then automatically unzip them into ``results`` and ``templatedir``, which will be located in ``{your_path}/HydroUQ/RemoteWorkDir/tmp.SimCenter``. On most systems, this will be ``~/Documents/HydroUQ/RemoteWorkDir/tmp.SimCenter``, but you can check by clicking on ``Files`` / ``Preferences`` on the upper-left corner of HydroUQ.
To retrieve ``workdir.tar.gz`` and ``MPM``, there are two approaches:
(1) You can right-click on your job within HydroUQ and select ``Open Job Folder`` to be taken directly to the Design Safe web-page displaying all remote files.
.. figure:: figures/openJobFolder.png
:align: center
:width: 400
:figclass: align-center
Locating the ``Open Job Folder`` button in the HydroUQ remote jobs table.
(2) You can manually navigate to the designsafe-ci.org website. For the latter, login and go to ``Upper-right Drop-down`` / ``Job Status``.
.. figure:: figures/DSToolsAndAppsJobsStatus.png
:align: center
:width: 600
:figclass: align-center
Locating the job files on DesignSafe
Check if the job has finished in the central vertical drawer by refreshing the page. If it has, click ``View Details``.
.. figure:: figures/DSToolsAndAppsJobsStatusFinished.png
:align: center
:width: 600
:figclass: align-center
Job status is finished on DesignSafe
Once the job is finished, the output files should be available in the directory which the analysis results were sent to
Find the files by clicking ``View Output``.
.. figure:: figures/DSToolsAndAppsJobsStatusViewFiles.png
:align: center
:width: 600
:figclass: align-center
Viewing the job files on DesignSafe
After navigating to your job folder by one of two ways, it is time to move files for processing. Move important files to somewhere in ``My Data/`` for easier processing. Use the extractor tool available on DesignSafe to unzip the ``results.zip``, ``workdir.tar.gz``, and ``templatedir.zip`` folders natively on DesignSafe.
.. figure:: figures/extractonDS.png
:align: center
:width: 600
:figclass: align-center
Extracting the ``results.zip`` folder on DesignSafe
Alternatively, you may directly download the zipped folders to your PC, which will require you to use the DesignSafe zip tool on the ``MPM`` folder prior.
.. figure:: figures/downloadResults.png
:align: center
:width: 600
:figclass: align-center
Download button on DesignSafe shown in red
Locate the downloaded zip folders and extract them somewhere convenient. The HydroUQ local or remote work directory on your computer is a good option.
.. warning::
Files in the HydroUQ local and remote working directories may be erased if another simulation is set up in HydroUQ, so keep a backup if you wish to maintain the files.
Particle geometry files often have a ``BGEO`` extension and are located in the ``MPM`` folder. Open with Side FX Houdini Apprentice (free to use) to look at MPM results in high-detail, or use the PartIO library.
HydroUQ's sensor/probe/instrument output is available in ``{your_path}/HydroUQ/RemoteWorkDir/tmp.SimCenter/results/`` as ``CSV`` files. You may process these files as you wish, most opt to use custom Python scripts or Excel due to their simplicity.
.. note::
For convenience, HydroUQ also includes basic plotting of all sensors files in the ``EVT`` / ``Results`` tab. Click ``Post-Process Sensors``, configure the drop-down boxes for the sensor you wish to view, and then click ``Plot``.
Plotting the wave gauges shows the development of a tsunami-like wave as it propagates from the piston wave maker and over the harbor bathymetry.
.. figure:: figures/hdro-0006_EVT_Results_WG.png
:align: center
:width: 600
:alt: Simulated free-surface elevations at the wave gauges in MPM.
:figclass: align-center
Simulated free-surface elevations at the wave gauges in MPM.
Compared against experiments we see, as in [Bonus2023Dissertation]_, the following free-surface signals:
.. figure:: figures/hdro-0006_WaveGauges.png
:align: center
:width: 600
:alt: Simulated free-surface elevations at the wave gauges in MPM from Bonus 2023 against Park et al. 2021.
:figclass: align-center
Simulated free-surface elevations at the wave gauges in MPM from Bonus 2023 against Park et al. 2021.
Load-cell data shows an initially high peak force from debris impact, followed by some damming forces and eventually just hydrodynamic drag.
.. figure:: figures/hdro-0006_EVT_Results_LC.png
:align: center
:width: 600
:alt: Simulated load-cell forces in MPM. These are later mapped onto an OpenSees structure for dynamic response analysis.
:figclass: align-center
Simulated load-cell forces in MPM. These are later mapped onto an OpenSees structure for dynamic response analysis.
**Structural Analysis**
Returning to our primary HydroUQ workflow, which concerns uncertainty in structural response, we may now view the final results in the **RES** tab. Clicking ``Summary`` on the top-bar, a statistical summary of results is shown below:
.. figure:: figures/hdro-0006_RES_Summary.png
:align: center
:width: 600
:alt: RES panel summary of structural response statistics.
:figclass: align-center
Clicking ``Data Values`` on the top-bar shows detailed histograms, cumulative distribution functions, and scatter plots relating the dependent and independent variables:
.. note::
In the **Data Values** tab, left- and right-click column headers to change plot axes; selecting a single column with both clicks displays frequency and CDF plots.
.. figure:: figures/hdro-0006_RES_Histogram.png
:align: center
:width: 600
:alt: RES panel histogram of dependent variable.
:figclass: align-center
.. figure:: figures/hdro-0006_RES_Cumulative.png
:align: center
:width: 600
:alt: RES panel cumulative distribution function of dependent variable.
:figclass: align-center
.. figure:: figures/hdro-0006_RES_Scatter.png
:align: center
:width: 600
:alt: RES panel scatter plot of dependent vs independent variable.
:figclass: align-center
.. note::
Use **consistent Froude similitude scaling** when comparing numerical simulations, experiments, and full-scale scenarios. For cross-method comparisons, adopt **identical debris footprints**, **friction models**, **probe placement**, and other pertinent parameters to reduce bias.
For more advanced analysis, export results as a CSV file by clicking ``Save Table`` on the upper-right of the application window. This will save the independent and dependent variable data. I.e., the **Random Variables** you defined and the **Engineering Demand Parameters** determined from the structural response per each simulation.
To save your simulation configuration with results included, click ``File`` / ``Save As`` and specify a location for the HydroUQ JSON input file to be recorded to. You may then reload the file at a later time by clicking ``File`` / ``Open``. You may also send it to others by email or place it in an online repository for research reproducibility. This example's input file is viewable at :ref:`hdro-0006-reproducibility`.
To directly share your simulation job and results in HydroUQ with other DesignSafe users, click ``GET from DesignSafe``. Then, navigate to the row with your job and right-click it. Select ``Share Job``. You may then enter the DesignSafe username or usernames (comma-separated) to share with.
.. important::
Sharing a job requires that the job was initially ran with an ``Archive System ID`` (listed in the ``GET from DesignSafe`` table's columns) that is **not** ``designsafe.storage.default``. Any other ``Archive System ID`` allows for sharing with DesignSafe **members on the associated project**. See :ref:`lbl-jobs` for more details.
.. _hdro-0006-conclusions:
Conclusions
-----------
HydroUQ's **MPM** implementation reproduced the **incoming wave signal** and **qualitative trends in debris motion on a frictional bed** reported by Park et al. (2021) for the subset case examined, which was concerned with HDPE plastic debris in an array orientation mobilizing into two fixed structural boxes by a tsunami-like wave.
As a next step, motivated readers may seek to reproduce other findings from Park et al. (2021), including:
- **Density-driven asymmetry**: does the **heavier** element in a pair **bias** the longitudinal displacement of the **lighter** one, while the reverse influence was **negligible**?
- **Initial orientation of debris groups**: do they show **no meaningful effect** on final dislocation in runs, or is there an underlying trend not seen in experiments due to the limited parameter space?
- **Obstacle interactions**: do baseline cases show **higher collision probability** for **lighter** debris; in **mixed-density groups**, do the lighter debris exhibit a **lower** collision probability than in single-density runs?
- **Reflections and interactions**: do these phenomena (wave reflection off boundaries and debris-debris contact) **modulate** local spreading and collisions, or does **element density** remain the **dominant factor** governing collision likelihood?
.. _hdro-0006-references:
References
----------
.. [Park2021] Park, H., Koh, M.-J., Cox, D. T., Alam, M. S., & Shin, S. (2021). Experimental study of debris transport driven by a tsunami-like wave: Application for non-uniform density groups and obstacles. Coastal Engineering, 166, 103867. https://doi.org/https://doi.org/10.1016/j.coastaleng.2021.103867
.. [Bonus2023Dissertation] Bonus, Justin (2023). "Evaluation of Fluid-Driven Debris Impacts in a High-Performance Multi-GPU Material Point Method." PhD thesis. University of Washington, Seattle.
.. [Bonus2025ClaymoreUW] Bonus, J., & Arduino, P. (2025). ClaymoreUW. Zenodo. https://doi.org/10.5281/zenodo.15128706
.. _hdro-0006-reproducibility:
Reproducibility
---------------
- Random seed(s): ``1`` (set in UQ)
- App version: HydroUQ v4.2.0 (or current)
- Solver: MPM (ClaymoreUW, multi-GPU)
- Hardware: TACC Lonestar6 or Stampede3, **3x A100** or **4x H100** (single node, ``gpu-a100`` or ``h100`` queue)
- Simulated time: **30 seconds**; Wall time: **3 hours**
- Sensor sampling: wave-gauges **120 Hz**; particle output **2-10 Hz**
- Input: The HydroUQ input file is as follows: `input.json `_ , is used:
.. raw:: html
Click to expand the HydroUQ input file used for this example
.. literalinclude:: src/input.json
:language: json
:linenos:
.. raw:: html