Product: ABAQUS/Standard
One-way solution transfer between FLUENT and ABAQUS/Standard; and
transfer of normal surface pressure and concentrated forces.
This verification problem illustrates the co-simulation feature used to couple ABAQUS/Standard with FLUENT to perform a fluid-structure interaction (FSI) simulation. The problem consists of a slender cantilever beam placed inside a channel with steady, incompressible, laminar flow. For this case a one-way solution transfer is considered in which pressure computed by FLUENT is imported into ABAQUS as concentrated nodal forces (CF) and normal pressure (PRESS). The problem is simple such that comparison between the numerical and analytical results can be made.
Model:The model consists of a slender cantilever beam inside a channel, as illustrated in Figure 3.17.11. The beam length is 1 m, the thickness is 0.01 m, and the depth is 0.1 m. The FLUENT model contains two fluid domains that are initially distinct but converge at the end of the beam: the top channel height is 0.02 m, and the bottom channel height is 0.04 m. The channel cross-section is uniform along the beam.
Mesh:
A two-dimensional model is used. The mesh consists of incompatible mode plane stress elements: 100 elements along the length, and 4 elements stacked in the thickness direction. No mesh parameter studies were performed on the structural mesh. The fluid-structure interface is defined through a surface definition.
The fluid mesh consists of 200 quadrilateral cells along the channel length and 8 cells and 16 cells stacked in the top and bottom channels, respectively. Quadrilateral fluid cells were used since these generally provide better pressure results than triangular fluid cells at the faces.
Material:The structural model uses linear elastic properties with Young's modulus of 1.09 Pa and a Poisson's ratio of 0.3.
The fluid model assumes incompressible flow with a fluid density of 1000 kg/m3 and a dynamic viscosity of 0.001 kg/ms.
Boundary conditions:
The structure is fixed on the inlet end of the channel and free at the outlet end. The velocity inlet flow corresponds to a Reynolds number of 250 in the upper channel and 354 in the lower channel. A pressure outlet with a zero gauge pressure is specified at the outlet, implying that the fluid of the top and bottom channel merge and have the same pressure condition. A fully developed flow is assumed and is specified through the user-defined function fsi_channel_2d.c.
Loading:
The fluid flow induces both normal pressure and viscous shear forces on the cantilever. The viscous shear forces are relatively small. The cantilever deforms due to the pressure difference in the top and bottom channels.
Analytical results:
A fully developed flow is assumed through the uniform cross-section channel with an incompressible fluid. Thus, the y-velocity component () and the gradient of the x-velocity component () are zero everywhere; and the governing Navier-Stokes equation for the fluid flow is
Substituting the boundary condition and integrating the Navier-Stokes equation leads to the flow solution for each channel:
The deformation of a cantilever beam subjected to a triangular distributed pressure is given by
The tip deflection due to the flow in each channel is
Units:
The SI unit system is used. ABAQUS does not require that the analysis be run with a particular unit system as long as all properties are specified in a consistent manner. However, the unit system used by ABAQUS must coincide with those used by the third-party analysis code.
A one-way coupling scheme, illustrated in Figure 3.17.12, is employed with FLUENT designated to begin the exchange process by sending its exchange information first. FLUENT computes the flow field around the undeformed cantilever (arrow 1) and sends the pressure distribution to ABAQUS (arrow 2). ABAQUS performs an initial increment without any FSI loads, since the synchronization point is located after the solver. ABAQUS computes the deformation corresponding to the pressure field during the second increment (arrow 3). ABAQUS does not send any solution quantities to FLUENT, and the analysis is terminated since this is a one-way simulation.
The following procedure illustrates how to run the co-simulation. It is assumed that FLUENT, MpCCI, and the MpCCI code plug-in for FLUENT are properly installed. ABAQUS and FLUENT should be executed in separate shell windows. It is recommended that each analysis be run in a different directory (e.g., problemDir/ABAQUS, problemDir/FLUENT, problemDir/MpCCI) and that the appropriate input files and the user-defined function exist in these directories.
Start the MpCCI server: the following starts the MpCCI server with the MpCCI configuration file (example.cci). The log file name is specified with the “–o” option. For further details on starting the MpCCI server, see the MpCCI User's Guide.
ccirun -idstrings -server -log -o example example.cci
Start the FLUENT analysis: set the environment variable MPCCI_INITIAL_EXCHANGE=SEND in the shell window where the FLUENT analysis is run. Run the two-dimensional version of FLUENT, and pass it to the FLUENT journal file.
fluent 2d -i "fluent_input.jou"
Start the ABAQUS analysis: set the environment variable MPCCI_INITIAL_EXCHANGE=RECEIVE in the shell window where ABAQUS is run, and then start the ABAQUS analysis as you would normally do.
MPCCI_INITIAL_EXCHANGE is an MpCCI variable that is normally defined by the MpCCI GUI.
Based on the analytical derivation for normal pressure distribution the expected tip deflection is –1.235 × 104 m. The simulation results are shown in Table 3.17.11 for a case in which normal pressure (PRESS) is imported into ABAQUS and a case in which concentrated forces (CF) are imported into ABAQUS.
Table 3.17.11 Results for one-way transfer.
Element | Tip Deflection (m) (PRESS) | Tip Deflection (m) (CF) |
CPS4I | –1.191 × 104 (–3.6%) | –1.202 × 104 (2.7%) |
The pressure difference between the top and bottom channels reported by FLUENT shows a –3.1% difference compared with the analytically predicted pressure difference. This discrepancy is consistent with the differences observed in the tip deflections. Viscous shear forces, which are not consistent with the analytical derivation, are transferred in addition to the normal pressure forces for cases in which concentrated forces are exchanged. These viscous shear forces are relatively small.
ABAQUS input file for one-way transfer with pressure loads imported.
ABAQUS input file for one-way transfer with concentrated forces imported.
MpCCI configuration file for fsi_channel_cps4i_pr_1-way.inp.
MpCCI configuration file for fsi_channel_cps4i_cf_1-way.inp.
FLUENT case file for all two-dimensional models.
FLUENT journal file for all one-way transfers.
FLUENT user-defined function for two-dimensional laminar flow.
Two-way solution transfer between FLUENT and ABAQUS/Standard;
transfer of current coordinates to FLUENT and pressure and concentrated forces to ABAQUS;
two-dimensional and three-dimensional simulations;
serial and parallel coupling schemes; and
nodal transformations.
The two-dimensional model is identical to the model used for the one-way solution transfer. A three-dimensional model is included and described under this section. In addition, two-dimensional and three-dimensional models with nodal transformations specified at the fluid-structure interface are included.
Mesh:
The three-dimensional structural mesh consists of continuum elements: 100 elements along the length, and 4 elements stacked in the thickness direction. No mesh parameter studies were performed on the structural mesh.
The fluid mesh for the three-dimensional model consists of 200 hexahedron cells along the channel length and 8 cells and 16 cells stacked in the top channel and bottom channels, respectively. Quadrilateral fluid cells were used since these generally provide better surface pressures than prismatic fluid cells.
Boundary conditions:
The boundary conditions are identical to the boundary conditions specified for the one-way solution transfer.
Loading:
The fluid flow over the channel induces both normal pressure and viscous shear forces on the cantilever. The viscous shear forces are relatively small. The cantilever deforms in response to the pressure differential between the flow in the top and bottom channels. The deformations are transferred back to FLUENT, and a new flow solution is obtained. This process is repeated until a steady-state condition is established; specifically, until minor changes in deformation and pressure are observed between consecutive coupling steps.
Analytical results:
The formulation derived under the one-way solution transfer holds only if there is no significant cross-flow; i.e., no flow perpendicular to the cantilever. As the deflection of the cantilever increases, the cross-flow becomes more dominant and, thus, the numerical results deviate from the analytical results.
The simulations are run using both serial and parallel coupling schemes illustrated in Figure 3.17.13 and Figure 3.17.14, respectively.
For the serial coupling scheme FLUENT computes the flow field around the undeformed cantilever (arrow 1). The pressure is transferred to ABAQUS (arrow 2). Prior to receiving the data, ABAQUS performs an initial increment without any FSI loads since the synchronization point is located after the solver. ABAQUS computes the deformation corresponding to the pressure field during the second increment and sends the deformed configuration to FLUENT (arrows 3 and 4). This completes one coupling step. FLUENT then computes a new flow solution based on the current configuration of the cantilever (arrow 5), and the steps are repeated until a steady-state solution is obtained. Typically, only a few exchanges are needed until solutions quantities show minor differences between consecutive coupling steps. In this case the problem reaches a steady-state after five coupling steps.
For the parallel coupling scheme FLUENT computes the flow field around the undeformed cantilever (arrow 1) and ABAQUS performs an initial increment without any FSI loads. When the target time is reached, both analysis codes exchange solution quantities (arrow 2). ABAQUS and FLUENT independently proceed to compute a new solution based on the quantities received from the previous coupling step. Typically, only a few exchanges are needed until the solutions quantities show minor differences between consecutive coupling steps. For this problem we have chosen five coupling steps.
The following procedure illustrates how to run the co-simulation. It is assumed that FLUENT, MpCCI, and the MpCCI code plug-in for FLUENT are properly installed. ABAQUS and FLUENT should be executed in a separate shell windows. It is recommended that each analysis be run in a different directory (e.g., problemDir/ABAQUS, problemDir/FLUENT, problemDir/MpCCI) and that the appropriate input files and user-defined function exist in these directories.
Start the MpCCI server: the following command starts the MpCCI server with the MpCCI configuration file (example.cci). The log file name is specified with the “–o” option. For further details on starting the MpCCI server, see the MpCCI User's Guide.
ccirun -idstrings -server -log -o example example.cci
Start the FLUENT analysis: define the environment variable MPCCI_INITIAL_EXCHANGE in the shell window where the FLUENT analysis is run. Set MPCCI_INITIAL_EXCHANGE=SEND for the serial coupling scheme and MPCCI_INITIAL_EXCHANGE=EXCHANGE for the parallel coupling scheme. Run the appropriate version of FLUENT. For a two-dimensional analysis, run
fluent 2d -i "fluent_input.jou" For a three-dimensional analysis, run
fluent 3d -i "fluent_input.jou"
Start the ABAQUS analysis: define the environment variable MPCCI_INITIAL_EXCHANGE in the shell window where the ABAQUS analysis is run. Set MPCCI_INITIAL_EXCHANGE=RECEIVE for the serial coupling scheme and MPCCI_INITIAL_EXCHANGE=EXCHANGE for the parallel coupling scheme. Start the ABAQUS analysis as you would normally do.
MPCCI_INITIAL_EXCHANGE is an MpCCI variable that is normally defined by the MpCCI GUI.
The solution for the two-way transfer is expected to be close to the one-way transfer because of the small tip deflection. The simulation results are shown (see Table 3.17.12) for the case in which normal pressure (PRESS) is imported into ABAQUS and for the case in which concentrated forces (CF) are imported into ABAQUS.
Table 3.17.12 Results for two-way transfer.
Element | Tip Deflection (m) (PRESS) | Tip Deflection (m) (CF) |
CPS4I (serial) | –1.157 × 104 | –1.167 × 104 |
CPS4I (parallel) | –1.157 × 104 | –1.167 × 104 |
C3D8I (serial) | –1.158 × 104 | –1.158 × 104 |
C3D8I (parallel) | –1.158 × 104 | –1.158 × 104 |
C3D20R (serial) | –1.161 × 104 | –1.161 × 104 |
The input files used with nodal transformation on the fluid-structure interface yield the same solution as the case without nodal transformation, thus verifying that the concentrated loads are properly transformed to the local coordinate system prior to applying the loads.
ABAQUS input file using CPS4I elements; two-way transfer with pressure loads imported and current coordinates exported.
ABAQUS input file using CPS4I elements; two-way transfer with concentrated forces imported and current coordinates exported.
ABAQUS input file using C3D8I elements; two-way transfer with pressure loads imported and current coordinates exported.
ABAQUS input file using C3D8I elements; two-way transfer with concentrated forces imported and current coordinates exported.
ABAQUS input file using C3D20R elements; two-way transfer with concentrated forces imported and current coordinates exported.
ABAQUS input file using C3D20R elements; two-way transfer with concentrated forces imported and current coordinates exported.
MpCCI configuration file for fsi_channel_cps4i_pr_crd.inp and fsi_channel_cps4i_pr_crd_par.inp.
MpCCI configuration file for fsi_channel_cps4i_cf_crd.inp and fsi_channel_cps4i_pr_crd_par.inp.
MpCCI configuration file for fsi_channel_c3d8i_pr_crd.inp and fsi_channel_cps4i_pr_crd_par.inp.
MpCCI configuration file for fsi_channel_c3d8i_cf_crd.inp and fsi_channel_c3d8i_cf_crd_par.inp.
MpCCI configuration file for fsi_channel_c3d20r_pr_crd.inp and fsi_channel_c3d20r_pr_crd_par.inp.
MpCCI configuration file for fsi_channel_c3d20r_cf_crd.inp and fsi_channel_c3d20r_cf_crd_par.inp.
FLUENT case file for all two-dimensional problems.
FLUENT journal file for all two-dimensional problems.
FLUENT user-defined function for two-dimensional laminar flow.
FLUENT case file for all three-dimensional problems.
FLUENT journal file for all three-dimensional problems.
FLUENT user-defined function for three-dimensional laminar flow.
ABAQUS input file using CPS4I elements; two-way transfer with pressure loads imported and current coordinates exported.
ABAQUS input file using CPS4I elements; two-way transfer with concentrated forces imported and current coordinates exported.
ABAQUS input file using C3D8I elements; two-way transfer with pressure loads imported and current coordinates exported.
ABAQUS input file using C3D8I elements; two-way transfer with concentrated forces imported and current coordinates exported.
MpCCI configuration file for fsi_channel_cps4i_pr_crd.inp and fsi_channel_cps4i_pr_crd_par.inp.
MpCCI configuration file for fsi_channel_cps4i_cf_crd.inp and fsi_channel_cps4i_cf_crd_par.inp.
MpCCI configuration file for fsi_channel_c3d8i_pr_crd.inp and fsi_channel_c3d8i_pr_coord_par.inp.
MpCCI configuration file for fsi_channel_c3d8i_cf_crd.inp and fsi_channel_c3d8i_cf_crd_par.inp.
FLUENT case file for all two-dimensional problems.
FLUENT journal file for all two-dimensional problems.
FLUENT user-defined function for two-dimensional laminar flow.
FLUENT case file for all three-dimensional problems.
FLUENT journal file for all three-dimensional problems.
FLUENT user-defined function for three-dimensional laminar flow.
ABAQUS input file using CPS4I elements; two-way transfer with concentrated forces imported and current coordinates exported using nodal transformation.
ABAQUS input file using C3D8I elements; two-way transfer with concentrated forces imported and current coordinates exported using nodal transformation.
MpCCI configuration file for fsi_channel_cps4i_cf_crd_trnsf.inp.
MpCCI configuration file for fsi_channel_c3d8i_cf_crd_trnsf.inp.
FLUENT case file for all two-dimensional problems.
FLUENT journal file for all two-dimensional problems.
FLUENT user-defined function for two-dimensional laminar flow.
FLUENT case file for all three-dimensional problems.
FLUENT journal file for all three-dimensional problems.
FLUENT user-defined function for three-dimensional laminar flow.
The following rendezvousing schemes are tested:
exchanges occurring exactly at the target times with the direct time stepping scheme;
exchanges occurring exactly at the target times with an automatic time stepping scheme; and
exchanges occurring loosely at target times with an automatic time stepping scheme.
The problem is identical to the two-dimensional channel problem discussed in the previous sections, with the exception of the time stepping scheme. We use the CCI_RENDEZVOUS variable to specify the target time and to specify whether the exchanges occur in an exact or loose manner. Specifying a target time period allows ABAQUS to subcycle based on its own time stepping scheme while maintaining exchanges with the third-party code at a fixed frequency. ABAQUS/Standard interpolates the imported loads between the previous coupling step and the target values.
Specifying a rendezvousing time period is typically used for transient simulations. It is being employed for this steady-state simulation purely for illustrative purposes. The rendezvous time period is set at 1.0.
The following procedure illustrates how to run the co-simulation. It is assumed that FLUENT, MpCCI, and the MpCCI code plug-in for FLUENT are properly installed. ABAQUS and FLUENT should be executed in separate shell windows. It is recommended that each analysis be run in a different directory (e.g., problemDir/ABAQUS, problemDir/FLUENT, problemDir/MpCCI) and that the appropriate input files and user-defined function exist in these directories.
Start the MpCCI server: the following command starts the MpCCI server with the MpCCI configuration file (example.cci). The log file name is specified with the “–o” option. For further details on starting the MpCCI server, see the MpCCI User's Guide.
ccirun -idstrings -server -log -o example example.cci
Start the FLUENT analysis: set MPCCI_INITIAL_EXCHANGE=SEND, and start FLUENT:
fluent 3d -i "fluent_input.jou"
Start the ABAQUS analysis: set MPCCI_INITIAL_EXCHANGE=RECEIVE, and set CCI_RENDEZVOUS to CCI_RENDEZVOUS="DT=1.0:loose" for the case in which the target times are met in a loose manner and CCI_RENDEZVOUS="DT=1.0:exact" for the case where the target times are met exactly.
The loads are properly interpolated during subcycles, and the rendezvous times are met either in an exact or loose manner as defined by the CCI_RENDEZVOUS variable, which can be verified by plotting a history plot of the variable CF at an interface node.
ABAQUS input file using CPS4I elements; two-way transfer, automatic time stepping scheme, and meeting target times exactly.
ABAQUS input file using C3D8I elements; two-way transfer, automatic time stepping, and meeting target times in a loose manner.
ABAQUS input file using C3D8I elements; two-way transfer, direct user-specified time stepping, and meeting target times exactly.
MpCCI configuration file for fsi_channel_cps4i_autostep_exact.inp, fsi_channel_cps4i_auto_loose.inp, and fsi_channel_cps4i_direct_exact.inp.
FLUENT case file for all two-dimensional problems.
FLUENT journal file for all two-dimensional problems.
FLUENT user-defined function for two-dimensional laminar flow.