Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while running the 1M element neon model #1721

Closed
gkaf89 opened this issue Jul 20, 2023 · 2 comments
Closed

Error while running the 1M element neon model #1721

gkaf89 opened this issue Jul 20, 2023 · 2 comments

Comments

@gkaf89
Copy link

gkaf89 commented Jul 20, 2023

I am trying to run the HPC 1M element neon benchmark model, and the solution terminates early with the error message:

MESSAGE ID :        205  

 ** RUN KILLED: ENERGY ERROR LIMIT REACHED


MESSAGE ID :        207  

 ** RUN KILLED: TOTAL MASS ERROR LIMIT REACHED

 NC=  124700 T= 6.0001E-02 DT= 1.6117E-09 ERR= 99.9% DM/M= 5.0701E+29
 ELAPSED TIME=        524.74 s  REMAINING TIME=        174.90 s
     ANIMATION FILE: NEON1M11A014 WRITTEN

The output file from the starter and engine executable is the following: SLURM_NEON1M11_868775.out.txt

The issue was detected in the following releases:

The execution scripts used are the following:

The bug appears in the following 2 clusters:

  1. Intel cluster (Skylake CPUs):
  • 4 nodes
  • 8 MPI processes
  • 14 threads per process
  1. AMD cluster:
  • 4 nodes
  • 32 MPI processes
  • 16 threads per process

The attached output is from the AMD cluster.

@roguic
Copy link
Contributor

roguic commented Jul 21, 2023

Hi @gkaf89 ,

Unfortunately the Neon model is a sensitive model. According to the hardware/openradioss version, you need to play with the /DT/NODA/CST parameter in the *1.rad.

You can try :
/DT/NODA/CST/0
0.6 5e-007

or
/DT/NODA/CST/0
0.67 6e-007

If you want to test the scalabity/performance of OpenRadioss, maybe the Taurus 10M element model is more convenient (https://openradioss.atlassian.net/wiki/download/attachments/47546369/Taurus10M.7z?api=v2).

Best,
Romain

@gkaf89
Copy link
Author

gkaf89 commented Jul 22, 2023

Hi @roguic,

Thank you very much! I will close the issue given that this behavior is known.

Best,
Georgios

@gkaf89 gkaf89 closed this as completed Jul 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants