Project Chrono libraries linked to GPUSPH

Dear GPUSPH

If understood correctly, the Project Chrono (PCh) is a collection of several libraries that tackle specific situations in body dynamics. Accordingly, the coupling of a SPH solvers with PCh means, concretely, the individual coupling with such component libraries.

From the list in the Feature pages https://www.gpusph.org/features/ I gather the following functionalities have been implemented:

Floating objects
Objects with joints
Moving objects (imposed motion)
Collision detection
Planes

If the question makes sense, would it be possible to know a more specific list of PCh libraries that have been linked with GPUSH? Are these native libraries connected to GPUSPH with open-source wrappers?

Hello @sph_tudelft_nl,

GPUSPH 5.0 uses Project Chrono to solve for the motion rigid bodies and their reciprocal interaction, whereas GPUSPH itself takes care of the coupled interaction of the rigid bodies with the fluid. The Project Chrono libraries that we use in GPUSPH are mainly those defining ChBody and ChLink, to handle floating bodies, optional joints and body collisions (for the latter, user callbacks can be defined in GPUSPH to interact with Chrono as preferred). GPUSPH interacts with Project Chrono without using any wrappers, and the underlying Chrono objects are available for manipulation by the user.

We are also currently working on the development within GPUSPH of a coupled SPH-FEM model that will allow simulating deformable solid bodies and their interaction with fluids. The Finite Elements analysis is executed by Project Chrono using the chrono_fea libraries.

Thank you for your interest in GPUSPH

Hi, can the current version of GPUSPH support mooring line simulations? When the deformable bodies can be used? Do you have any estimate now?

Hello @James, with the current version of GPUSPH mooring lines can be implemented semi-analytically. We’re currently working on adding an example on how to do it to the repository. For an approach based on deformable bodies we first have to finalize the integration with the Chrono/FEA module. I’m afraid we do not have an estimate on when these will be completed.