User`s guide

MADYMO Coupling Manual Release 7.5
7.4 Restart
For more general information on restart, see the Radioss engine manual and the MADYMO
Reference Manual. Restart is supported for direct coupling only.
To enable restart, the following steps must be taken:
1. Generate restart files for Radioss and MADYMO.
2. Generate a Radioss engine input deck (D02 file). In the D02 file, set the identifier to
/RUN/ROOTNAME/<restart_id>. Change the <restart_id> to select the desired Ra-
dioss restart file. Radioss restart files are cyclic. The number of Radioss restart files is
determined by the /RFILE/n option in the engine file, where n determines the number
of restart files.
3. Generate a MADYMO restart input file (xml file). There is a template restart file in
<madymo_dir>/etc/etc/template_restart.xml.
4. Submit the restart job with the -rst <restart.rst> command line option, where
<restart.rst> points to the restart file generated in step 1. For an example restart startup
script, see section
8.1.4
7.4.1 Restart Control
• All remarks for normal coupling to Radioss are valid for restart (see section 7.2).
• The MADYMO restart file is cumulative. All time points for Radioss are written in one
file.
• The restart frequency is fully MADYMO controlled, and is enabled by the TIME_RESTART
keyword in the MADYMO input deck. The TIME_RESTART and D01 RFILE don’t need
to be synchronized. MADYMO will write a restart file every TIME_RESTART seconds,
and Radioss follows this.
• Please check the log file that both Radioss and MADYMO restart at the same time-point.
Selecting the wrong Radioss restart file (see above) can result in out-of-sync restart runs.
• The restart analysis starts at the first timepoint saved in the restart file that is smaller
than the begin time of the restart analysis.
7.5 Limitations and Known Issues
• The last ANIMATION file may not be written if the simulation end time is a multiple
of the output time step. This situation can be avoided by increasing the simulation end
time point slightly.
35