You can use predefined templates to create the configuration file for the
coupling schemes described above.
Table 1
describes the predefined templates available for electromagnetic to transient
heat transfer analyses and for electromagnetic to stress-displacement analyses
and lists example configuration files that you can review.
Table 1. Templates for electromagnetic co-simulation.
Electromagnetic to transient heat transfer
co-simulation
|
Coupling scheme:
|
template_em_std_export
|
Example file: exa_em_std_export
|
Coupling scheme:
|
template_em_std_fixed
|
Example file: exa_em_std_fixed
|
Coupling scheme:
|
template_em_std_iterative
|
Example file: exa_em_std_iterative
|
Electromagnetic to
Abaqus/Standard
stress/displacement co-simulation
|
Coupling scheme:
-
Electromagnetic analysis leads
-
Step size is determined based on the minimum suggested step size
of the electromagnetic and
Abaqus/Standard
stress/displacement analyses.
-
Either analysis can subcycle
-
Body forces are transferred from the electromagnetic to
Abaqus/Standard
stress/displacement analysis. No other co-simulation transfer occurs.
|
template_em_std_force_oneway
|
Example file: exa_em_std_force_oneway
|
To obtain an example configuration file, you can use the abaqus fetch
utility. For example, to obtain the example for which the heat transfer analysis serves as
the main analysis in determining the coupling step size, use the following command:
abaqus fetch job=exa_em_std_export
The example file exa_em_std_export.xml is shown below.
<?xml version="1.0" encoding="utf-8"?>
<CoupledMultiphysicsSimulation>
<template_em_std_export>
<EM_Job>em_job_name</EM_Job>
<HeatTransfer_Job>ht_job_name</HeatTransfer_Job>
<duration>duration_value</duration>
</template_em_std_export>
</CoupledMultiphysicsSimulation>
In certain cases you may need to use co-simulation configuration features
that are not described in the predefined templates. For example, you may wish
to change the dissimilar mesh mapping search tolerances; these tolerances are
available generally in the configuration file but are not described in the
predefined templates. For these cases, you must create an elaborated
configuration file; for more information, see
Using Elaborated Configuration Files.