Reply To: Mathematical model generation stuck at 10%

[pedram.samadian]

Hi,

Thanks for contacting us. The provided information is not enough to identify the problem. Such an occurrence typically points to issues with the solver version, model setup, memory allocation, or configuration. Would you please let me know which version of the LS-DYNA solver did you use? I recommend running the model with newer versions of LS-DYNA. It is also worth trying to run the input.k file gerenated by Mechanical using LS-RUN.

Here are some other tips to troubleshoot and possibly resolve the problem:

 Check for Errors in the Input File:

• Review the message files, the D3HSP files, and the D3KMP files, which can contain valuable information for diagnosing the issue.
• Analyze binary outputs such as the DTI2 file and any results in the D3PLOT file and BINOUT file 
• Use built-in checkers in pre-processors (e.g. the Model check option in keyword manager within the LS-PrePost software) to review your keyword file and get feedback that might indicate the cause of non-convergence or other issues leading to the crash.

Verify Memory Allocation:

• LS-DYNA may need more memory for model generation. Try increasing the allocated memory in the command line or control settings.

Review Contact Definitions:

• Improper contact definitions can cause simulation hang-ups, especially in complex models. Check your contact settings, particularly for initial penetrations or mismatched surfaces.

 Set Up Initial Debugging Output:

• Enable *DATABASE_BINARY_D3PLOT and *DATABASE_GLSTAT output at a higher frequency, so you can capture initial calculations and troubleshoot where the problem might arise.
• Look into the GLSTAT file output for any warning or error messages generated before the crash.

Use Reduced Element Count for Testing:

• Simplify the model by reducing the number of elements or constraints temporarily to isolate the issue. This can help identify whether the model complexity itself is causing memory or stability issues.

Check Boundary Conditions and Loads:

• Verify that all loads and constraints are properly applied and ensure nodes aren’t double-constrained. Incorrect or conflicting boundary conditions can cause instability during model generation.

I hope the provided guidance helps.

Thanks,

Pedram