22.3 - Ditching using Multi-Domain for SPH and ALE

Title

Ditching using Multi-Domain for SPH and ALE

ex_22-3_object

Number

22.3 Brief Description

Impact of a simple object on water using Multi-Domain to approach SPH and ALE.

RADIOSS Options

•	Multi-Domain (/SUBDOMAIN)

•	Rad2rad (/RAD2RAD/ON) in Engine

Compared

•	Results of Mono-Domain and Multi-Domain

Input File

SPH (Multi-Domain): <install_directory>/demos/hwsolvers/radioss/22_Ditching/Ditching_Multi_Domain_SPH/*

ALE (Multi-Domain): <install_directory>/demos/hwsolvers/radioss/22_Ditching/Ditching_Multi_Domain_ALE/*

Technical / Theoretical Level

Skilled

Overview

Physical Problem Description

The problem consists of a simple object falling into water simulating the ditching of a helicopter.

Unit: mm, ms, KN, GPa, kg.

Use Example 22.1 as SPH ditching and Example 22.2 as ALE ditching, then add Multi-Domain approach in SPH ditching and ALE ditching

Analysis, Assumptions and Modeling Description

Modeling Methodology of Multi-Domain (Single Input Format) approach

For Multi-Domain approach, take the model of Mono-Domain and:

1.	Setup /SUBDOMAIN in Starter:

Use /SUBDOMAIN to define sub-domain. In this example part ID 19 is defined as sub-domain.

For SPH ditching:

ex_22-3_ale_subdomain

For ALE ditching:

ex_22-3_sph_subdomain

Note:

The subdomain_title “SPH_SubDomain” (or “ALE_SubDomain”) must be the same as sub-domain Engine name SPH_SubDomain_0001.rad (or ALE_SubDomain_0001.rad).

ex_22-3_sph_ale

Fig 1: Domain description in Multi-Domain approach

2.	Setup in two Engine files:

First Engine file (main-domain):

•	Take the Engine of Mono-Domain and insert /RAD2RAD/ON keyword.

•	Free element time step control for ALE or free nodal time step control for SPH in the first Engine file.

Second Engine file (sub-domain)

•	Take the Engine of Mono-Domain and insert /RAD2RAD/ON keyword.

•	Update the Engine name and also the run name in /RUN. They must match the subdomain_title in Starter /SUBDOAMIN.

•	Set the Lagrange parts (part ID 19) specific time step control

ex_22-3_multidomain_setup

Fig 2: Multi-Domain setup in Starter and Engine (SPH ditching as example)

Contact between main-domain and sub-domain

As of RADIOSS version 14.0, Starter automatically creates coupling links between domains with Multi-Domain Single Input Format. In SPH ditching using /INTER/TYPE7 coupling links between Lagrange sub-domain and SPH main-domain are automatically created. In ALE, ditching using /INTER/TYPE18 coupling links between Lagrange sub-domain and ALE main-domain are automatically created.

Simulation Results and Conclusions

Results between Mono-Domain and Multi-Domain

To compare the results between Mono-Domain and Multi-Domain we take the model with 11m/s in initial velocity in SPH ditching and in ALE ditching.

It shows same results for Mono-Domain and Multi-Domain.

•

Energy

SPH ditching

ALE ditching

ex_22-3_energy_comparison

Fig 3: Energy comparison between Mono-Domain and Multi-Domain

•	Acceleration

SPH ditching

ALE ditching

ex_22-3_acceleration_comparison

Fig 4: Acceleration comparison between Mono-Domain and Multi-Domain

The time step in Multi-Domain is much bigger than in Mono-Domain.

•

Timestep

SPH ditching

ALE ditching

ex_22-3_time_step_comparison

Fig 5: Time step comparison between Mono-Domain and Multi-Domain

Theoretical speedup a formula:

ex_22-3_theoretical_speedup

Where, Ne is the number of elements, Nc is the number of cycles, and C is the the element average time cost/cycle.

Speedup a could also be formulated with following factors:

•	Relative element number:

•	Relative time step (relative cycle numbers): with dt - time step

•	Relative cost per cycle:

Lagrange shell= 1

Lagrange sold ~ 3

ALE solid ~ 6

SPH cell ~ 15

Then speedup a will be:

ex_22-3_elapsed_time_eq

Elapsed times:

SPH ditching

ALE ditching

After comparing the elapsed time, observe Multi-Domain FSI speedups ranging from 6 times to 9 times of the Mono-Domain.

Conclusion

•	The Multi-Domain is particularly adapted to FSI simulations involving a large amount of either ALE elements or SPH cells which the time steps are significantly higher than the one in the much smaller in terms of elements of the Lagrange structure

•	The easiness of setup makes the Multi-Domain applied to FSI much simpler than when applied to purely Lagrange models where the cross-domain contacts need to be minimized as long as this aspect is not automated

•	Due to this setup easiness the Multi-Domain results in FSI give less possibility to deviations when compared to classical mono-domain results

•	FSI simulations often involving large ALE or SPH domains with high time steps the Multi-Domain speedups are significantly higher than in pure Lagrange simulations like in Crash

Comments and Hints

•	For Multi-Domain FSI there is no need to minimize the contacts in TYPE7 interface (SPH) or in TYPE18 or TYPE22 interfaces (ALE) between Fluid and Structure whereas it is needed in pure Lagrange Multi-Domain.

•	For Multi-Domain FSI it is advised to use for the main-domain a free element time step with a scaling factor of 0.5 for ALE and a free nodal time step with a scaling factor of 0.6.

•	When Lagrange parts are assembled using tied contact interface TYPE2. Then poor performances may occur with SPOTflag = 0 or 1.

Set SPOTflag = 26 to switch from kinematic to penalty formulation to solve the problem. In such cases (SPOTflag = 26) contacts become permissive depending on assigned contact stiffness. It is also recommended to check the contacts quality in animation results to make sure no significant penetrations occur.