The role of computational fluid dynamics in understanding shipwreck site formation processes

Thomas Smyth, Rory Quinn

    Research output: Contribution to journalArticlepeer-review

    24 Citations (Scopus)

    Abstract

    Studies indicate that physical processes commonly dominate the initial stages of wreck site formation. Detailed knowledge and understanding of hydro- and sediment- dynamics are therefore imperative for studies dealing with site formation and in-situ preservation. In this investigation, the results of computational fluid dynamic modelling over a shipwreck site are presented, using a high-resolution surface derived from multi-beam echo-sounder data and boundary conditions constrained by field measurements (sediment samples and flow measurements). Simulation of the 3-dimensional flow velocity field around the wreck site, and secondary products derived from the computational model, confirm that flow velocity and turbulence are both amplified by the presence of the wreck, causing changes in the morphology of the flow regime. Flow contraction, the formation of lee-wake vortices behind the structure (accompanied by vortex shedding) and increased turbulence are all observed. Shear-stress and TKE amplification three to four times greater than ambient values are recorded downstream of the wreck structure. Benefits of this approach for studies of site-formation and in-situ conservation include the inexpensive, open-source, and desk-based nature of the investigation.

    Original languageEnglish
    Pages (from-to)220-225
    Number of pages6
    JournalJournal of Archaeological Science
    Volume45
    Issue number1
    DOIs
    Publication statusPublished - May 2014

    Keywords

    • Computational fluid dynamics
    • Hydrodynamics
    • Multi-beam echo-sounder
    • Shipwreck
    • Site formation processes

    Fingerprint

    Dive into the research topics of 'The role of computational fluid dynamics in understanding shipwreck site formation processes'. Together they form a unique fingerprint.

    Cite this