Download Possible Causes of a MADYMO abort

Possible Causes of a MADYMO abort
MADYMO R7.6
Question
When I submit my MADYMO calculation, the job aborts randomly without a clear reason. What could be the cause
of this behaviour?
Answer
Despite the stringent QA process that TASS enforces on its products, there are various reasons calculations may
abort. The list below is a compilation of reasons for aborting calculations based on the history of TASS support.
Please check if any of the following reasons may apply to your situation:

A distinction can be made between an 'abort' caught by the MADYMO Solver and echoed as 'MADYMO
terminated abnormally' and cases where the solver aborts without message.
o When the message 'MADYMO terminated abnormally' is given, the simulation has run into a problem
that prohibits continuation of the calculation. The time integration may become unstable because of a
too large time step, the velocity of finite element nodes may become too large, the number of
separate contact detections becomes too large, etc. The reason is often found in modelling errors. In
such cases, contact TASS support for assistance.
o When the solver aborts without a message, a bug in the code may be the cause and you may want to
contact TASS support to report the problem. In this case not all system information is echoed in the
log file and it is highly appreciated when you share the entire screen output with the TASS support
organization.

Anti-aliasing, as implemented for example in the Hybrid-III series, is a feature that demands more
intermediate output for the filtering algorithms. The output is written in temporary files, stored in the location
set by the environment variable TMPDIR. If the directory set by TMPDIR is limited in its size, MADYMO cannot
write the intermediate output and aborts. For windows the environment variable could be either TMPDIR ,
TMP or TEMP. Advised to define all of them to the same path.

Simulations that generate a large amount of output data, either because the time duration of the simulation
equals several seconds or a large set of output signals or a small time step is used, may terminate with the
following error message before the end time is reached:
** ABORT ** ID=(MPS3D2/3D/FLTOTH)
Could not expand storage to 90000180 .
Your system does not have enough memory for your model.
The reason for the abort is that the size of the output files becomes too large for the filtering routines to
handle. The output requests can be split over separate output files to circumvent this abort. An example is
given below where several output requests for a system are grouped in a separate output request and send to
a separate file:
<TIME_HISTORY_MB
FILENAME="Head_Neck"
SYSTEM="/HumanMale50%"
JOINT_CONSTRAINT_OUTPUT_LIST= "NeckUp_lce_F NeckUp_lce_T HeadOC_lce_F HeadOC_lce_T"
/>
<TIME_HISTORY_MB
FILENAME="Lumbar"
SYSTEM="/HumanMale50%"
JOINT_CONSTRAINT_OUTPUT_LIST="L1_lce_F L1_lce_T L2_lce_F L2_lce_T L3_lce_F L3_lce_T"
/>

You may be trying to launch a 64-bit application on a 32-bit operating system. This generally does not work.
An example error message for such a situation is given below:
Running /appl/madymo6.4.1/madymo_641/ibmrs51/bin/bsaf 'a_frontalfc.xml'
'a_frontalfc.saf'
Could not load program bsaf:
Symbol resolution failed for bsaf because:
Symbol _GetCatName__FiPCc (number 135) is not exported from dependent
module /usr/vacpp/lib/libC.a[ansi_64.o].
1
Questions? Please contact your local MADYMO support office
www.tassinternational.com
Possible Causes of a MADYMO abort
MADYMO R7.6
Symbol __ct__Q2_3std8_LocinfoFPCci (number 204) is not exported from dependent
module /usr/vacpp/lib/libC.a[ansi_64.o].
Examine .loader section symbols with the 'dump -Tv' command.
** ABORT ** ID=(INPI41/3D/CMDL3D)
Failed to parse the XML input file. Use the MADYMO Reference Manual to assist with
correction of the errors in the input deck.
MADYMO TERMINATED ABNORMALLY, because of ERRORS.
Error: Job Execution Failed.
The reverse often works, i.e. a 32-bit application can be run on a 64-bit OS

You may be trying to launch a Linux 2.6 kernel application on a Linux 2.4 kernel OS. This generally does not
work, i.e. there is no 'forward' compatibility between Linux kernel versions. In general, the Linux community
does provide backwards compatibility, i.e. a Linux 2.4 kernel application runs on a Linux 2.6 kernel OS. Error
messages from the OS may be similar to:
/lib64/tls/libc.so.6: version `GLIBC_2.3.4' not found
To summarise the last two bullets:
MADYMO installer
OS
kernel
Linux2.4-X86
Linux2.4-x86_64*
Linux2.6-x86_64
32-bit
2.4
2.6
2.4
2.6
OK
OK
OK
OK
Not OK
Not OK
OK
OK
Not OK
Not OK
Not OK
OK
64-bit

Calculations have been known to crash in MPP mode because of incorrect cluster configuration. Possible
causes have been identified as:
o Incorrect or incomplete information in the host files of the nodes of the cluster (often located in
/etc/hosts). For example, the nodes may be named incorrectly causing a problem in looking up the IP
address of the node.
o Limits set to stack size or memory usage. Calculations done in MPP coupling may exceed the limits
causing MPP processes to die without proper message of the cause, for example:
MPI Application rank 0 exited before MPI_Finalize() with status 0
Put the command unlimit in the .cshrc file when using a csh or tcsh shell to eliminate this problem. For bash
shells the commands ulimit -s unlimited and ulimit -v unlimited should be put in the .bashrc file to eliminate
size limits on stack and virtual memory respectively.

The MADYMO/Solver uses a system call to retrieve information about the user identity that is logged in the
MADYMO log and reprint file. This function call may fail when the name service caching daemon (e.g. nscd) is
not running. When the system call fails (segmentation fault), MADYMO calculations in SMP mode will abort
and calculations in MPP mode may stall because of failing MPP processes. Consult your IT department. Note:
result files may not be correct (e.g. not filtered properly).

Install patches of a MADYMO release sequentially if they are not provided as a complete installer - first pl1
and then the next one. If not, essential files might be missing.

MADYMO abort messages like the one listed beneath are generally resolved by a smaller (MB) time step if the
closed chain message originates from the dummy.
** ABORT ** ID=(CLSE03/3D/ITTCL3)
Dependent constraint equations in the closed chain formulation resulting
in an ill conditioned constraint coefficient matrix.
The reciprocal condition of 0.29E-04 occured at TIME = 0.840000E-03 s.
Hint: Define proper independent dofs or alter joints inside the closed chains.

Security software (sandboxing) might inhibit the normal running of MADYMO software. Please contact your IT
department.
2
Questions? Please contact your local MADYMO support office
www.tassinternational.com
Possible Causes of a MADYMO abort
MADYMO R7.6
Additional Comments
Error messages vary for different operating systems and their versions. When in doubt, contact your local
MADYMO Support organization.
* Only applicable for MADYMO releases prior to R741.
3
Questions? Please contact your local MADYMO support office
www.tassinternational.com