openradioss / openradioss

OpenRadioss is a powerful, industry-proven finite element solver for dynamic event analysis

What is OpenRadioss?

Altair® Radioss® is an industry-proven analysis solution that helps users evaluate and optimize product performance for highly nonlinear problems under dynamic loadings. For more than 30 years, organizations have used Altair Radioss to streamline and optimize the digital design process, replace costly physical tests with quick and efficient simulation, and speed up design optimization iterations.

OpenRadioss is the publicly available open-source code base that a worldwide community of researchers, software developers, and industry leaders are enhancing every day. OpenRadioss is changing the game by empowering users to make rapid contributions that tackle the latest challenges brought on by rapidly evolving technologies like battery development, lightweight materials and composites, human body models and biomaterials, autonomous driving and flight, as well as the desire to give passengers the safest environment possible via virtual testing.

With OpenRadioss, scientists and technologists can focus their research on a stable code base under professional maintenance that benefits from the large library of existing finite element capabilities and the continuous integration and continuous development tools provided to contributors.

For more information on OpenRadioss project, please visit www.openradioss.org

If you have any questions about OpenRadioss, please feel free to contact [email protected].

How to Use OpenRadioss

• How to Build OpenRadioss
• How to Run OpenRadioss
• OpenRadioss Releases

Community and Ways to Participate

git and git-lfs are needed to clone the OpenRadioss repository.

• How to contribute
• Code of conduct

Community Manager Marian Bulla [email protected]

Post Processing tools

Tools are available to convert Radioss formats to VTK and CSV

• Animation files to VTK
• Time History file

Resources

Online Help Documentation:

• Radioss online help

Help Documentation in pdf form:

• reference guide
• user guide
• theory manual

Help for contributors:

• OpenRadioss documentation

openradioss's Issues

h3d files do not contain any Sets as HyperView Player show

Hello!
I have an engine rad-file with (for example):

/H3D/DT
0 0.000275
/H3D/NODA/DT
/H3D/ELEM/DT

Official HVP show that h3d-files has no any Sets. There are only part at every timestep.
I can not to test h3d-files at commercial HyperView, then I don't know if this error lies in HVP or in OpenRadioss engine.

The cross-section properties of a LS-DYNA k-file result in a wrong property in RADIOSS

Describe the bug
The positions and the areas of /PROP/TYPE18 beam do not correspond to the LS-DYNA input.
To Reproduce
Run the k-file attached in starter.
Expected behavior
The static behavior of the LS-DYNA beam should be the same in RADIOSS.
Either the correct values for the integration points should be used or a beam with /PROP/TYPE3 like:

         PROPERTY SETS (HM_READER)
         -------------


Pole    
     BEAM PROPERTY SET 
     PROPERTY SET NUMBER . . . . . . . . . .=         4   
     BEAM AREA . . . . . . . . . . . . . . .=  25600.00000000    
     MOMENT OF INERTIA IYY . . . . . . . . .=  54613333.33333    
     MOMENT OF INERTIA IZZ . . . . . . . . .=  54613333.33333    
     MOMENT OF INERTIA IXX . . . . . . . . .=  109226666.6667    
     NODE 1 LOCAL ROTATION RELEASE X DIR.. .=         0
     NODE 1 LOCAL ROTATION RELEASE Y DIR.. .=         0
     NODE 1 LOCAL ROTATION RELEASE Z DIR.. .=         0
     NODE 2 LOCAL ROTATION RELEASE X DIR.. .=         0
     NODE 2 LOCAL ROTATION RELEASE Y DIR.. .=         0
     NODE 2 LOCAL ROTATION RELEASE Z DIR.. .=         0
     SHEAR FORMULATION (0=YES/1=NO). . . . .=         0
     BEAM STRUCTURAL MEMBRANE DAMPING. . . .=  0.000000000000
     BEAM STRUCTURAL FLEXURAL DAMPING. . . .= 1.0000000000000E-02

Output
The cross-section properties in the LS-DYNA example file describe a straight rectangular cross-section 160x160:

*SECTION_BEAM_TITLE
Pole
$#   secid    elform      shrf   qr/irid       cst     scoor       nsm
         4         1 0.8333333         0         0       0.0       0.0
$#     ts1       ts2       tt1       tt2     nsloc     ntloc     
     160.0     160.0     160.0     160.0       0.0       0.0

The LS-DYNA manual points this out:
For ELFORM=1
TS1: Beam thickness (CST = 0.0, 2.0) or outer diameter (CST = 1.0) in s-direction at node n1
TS2: Beam thickness (CST = 0.0, 2.0) or outer diameter (CST = 1.0) in s-direction at node n2.
TT1: Beam thickness (CST = 0.0, 2.0) or inner diameter (CST = 1.0) in t-direction at node n1.
TT2: Beam thickness (CST = 0.0, 2.0) or inner diameter (CST = 1.0) in t-direction at node n2.

When running the starter with the input file, these values are displayed in the output file:

         PROPERTY SETS (HM_READER)
         -------------


Pole    
     INTEGRATED BEAM PROPERTY SET (TYPE 18) 
     PROPERTY SET NUMBER . . . . . . . . . .=         4   
     SMALL STRAIN FLAG . . . . . . . . . . .=         4   
     NODE 1 LOCAL ROTATION RELEASE X DIR.. .=         0   
     NODE 1 LOCAL ROTATION RELEASE Y DIR.. .=         0   
     NODE 1 LOCAL ROTATION RELEASE Z DIR.. .=         0   
     NODE 2 LOCAL ROTATION RELEASE X DIR.. .=         0   
     NODE 2 LOCAL ROTATION RELEASE Y DIR.. .=         0   
     NODE 2 LOCAL ROTATION RELEASE Z DIR.. .=         0   
     BEAM STRUCTURAL MEMBRANE DAMPING. . . .=  0.000000000000    
     BEAM STRUCTURAL FLEXURAL DAMPING. . . .= 1.0000000000000E-02
     SECTION TYPE. . . . . . . . . . . . . .=         1
     NUMBER OF INTEGRATION POINTS. . . . . .=         4   

     INTEGRATION POINTS:

     POINT NO: . . . . . . . . . . . . . =         1   
        LOCAL Y POSITION. . . . . . . . . . = -46.18802070618    
        LOCAL Z POSITION. . . . . . . . . . =-0.2886751294136    
        POINT AREA. . . . . . . . . . . . . =  40.00000000000    
     POINT NO: . . . . . . . . . . . . . =         2   
        LOCAL Y POSITION. . . . . . . . . . = -46.18802070618    
        LOCAL Z POSITION. . . . . . . . . . = 0.2886751294136    
        POINT AREA. . . . . . . . . . . . . =  40.00000000000    
     POINT NO: . . . . . . . . . . . . . =         3   
        LOCAL Y POSITION. . . . . . . . . . =  46.18802070618    
        LOCAL Z POSITION. . . . . . . . . . =-0.2886751294136    
        POINT AREA. . . . . . . . . . . . . =  40.00000000000
     POINT NO: . . . . . . . . . . . . . =         4
        LOCAL Y POSITION. . . . . . . . . . =  46.18802070618
        LOCAL Z POSITION. . . . . . . . . . = 0.2886751294136
        POINT AREA. . . . . . . . . . . . . =  40.00000000000

```[Simple.k.gz](https://github.com/OpenRadioss/OpenRadioss/files/9972599/Simple.k.gz)
**Desktop**
 - Version commit 15ae8bf69ba77442961dfd744c7a7a34112c0067 
- Hardware: Intel(R) Core(TM) i7-5930K CPU
- Configuration: starter with 1 task
- OS: Linux

how to use intel mkl library to accelerate the fortran program on linux os

when I compile the openradioss，I found it can only support gcc+ompi on linux os.but intel mkl library could accelerat sharply the fortran program.
so I want to know how to compile openradioss by intel compiler and intempi.
Look forward to your reply.

The window platform gdb cannot be debugged

Hello everyone：
I have successfully compiled the starter and engine executables under the Windows platform, added the -debug=1 flag when compiling, and the compiled executable file name suffix contains "_db", but when I tried to debug it with gdb, I found that there was no debug flag and could not set breakpoints, as shown below. Why is that? Isn't the compiled debug version?

Segmentation fault

I got some trouble running Radioss(starter) compiled from source.
The compiled program downloaded from github works fine.

Here is my compile options:
-Darch=linux64_gf
-Dprecision=dp
-Ddebug=1
-Dstatic_link=1
-Dsantitize=1

Operating system: Ubuntu 20.04
Compiler: gcc/g++-7.5.0, gfortran-9.4.0. I had tried higher version, but there was no change.

Builing Starter fails (Cent OS 7.9)

Describe the bug

1. gfortran does not know option "fdec-math". Can be solved by deleting this out of "cmake_linux64_gf.txt"
2. After 9% of compilation I get:
   `OpenRadioss/OpenRadioss/starter/share/spe_inc/vectorize.inc:42.6:
   Included at /det07a/BL/OpenRadioss/OpenRadioss/starter/source/elements/sh3n/coquedk/cdkfint_reg_ini.F:215:

*$OMP SIMD
1
Error: Unclassifiable OpenMP directive at (1)
/det07a/BL/OpenRadioss/OpenRadioss/starter/share/spe_inc/vectorize.inc:42.6:
Included at /det07a/BL/OpenRadioss/OpenRadioss/starter/source/elements/sh3n/coquedk/cdkfint_reg_ini.F:253:
`

To Reproduce
run ./build_script.sh -arch=linux64_gf

Expected behavior
Should compile

[FR] Porting to Windows

Is your feature request related to a problem? Please describe.
Right now it seems like Linux (per the docs) is the only OS compatible with OpenRadioss. Are there plans to port it to another OS?

Describe the solution you'd like
The option for windows users to benefit from OpenRadioss

/INCLUDE_DYNA *RIGIDWALL Unit Issue

Describe the bug
Running the Toyota Camry model using /INCLUDE_DYNA

CamryOpenRadioss.key contains:

Model runs, however rigid wall definitions are not mapped correctly.

Vehicle is correct size

th_to_csv converter tool

The Problem
The th_to_csv tool does not work properly.

1. For global variables and parts: it does not convert the velocities.
2. For interfaces: it does not convert the name of the variables, it indicates "var XX"

Expected behavior
I expect to

1. have the possibility to get the velocities for the whole studied system (global variables) and for the sub-systems (parts).
2. identify the outputs by their names, not by guessing.

Desktop (please complete the following information):

• Version OpenRadioss 20220930
• CentOS 8

radioss cannot recognize lsdyna option *CONSTRAINED_NODE_SET_ID

Describe the bug
when i apply a lsdyna model contains *CONSTRAINED_NODE_SET_ID , radioss error happened

Output
ERROR ID : 100210
** ERROR IN INPUT OPTIONS
DESCRIPTION :
-- BLOCK: *CONSTRAINED_NODE_SET_ID
-- LINE: *CONSTRAINED_NODE_SET_ID
Unrecognized option: *CONSTRAINED_NODE_SET_ID

Element-Deletion when using MUMPS/Implicit+TIED

When using interface type=10 (TIED) the solver deletes
many shell-elements at the beginning of the solution process.

 MUMPS    DIM : NNZ =   1112100 NNZFR =         0
   ------------------------------------------------------------------------------
            Stif. Mat.
      Iter   reformed      |du|/|u|   |r|/|r0|   |dE|/|E| Conv.stat.
   ------------------------------------------------------------------------------
         0      Y             NaN  1.010E+02        NaN
 -- DELETE 3N SHELL ELEMENT :   5705160 AT TIME : 0.1000E-01
 -- DELETE 3N SHELL ELEMENT :   5705274 AT TIME : 0.1000E-01
 -- DELETE 3N SHELL ELEMENT :   5705321 AT TIME : 0.1000E-01
 -- DELETE 3N SHELL ELEMENT :   5705388 AT TIME : 0.1000E-01
 -- DELETE 3N SHELL ELEMENT :   5705486 AT TIME : 0.1000E-01
...
...
...

IDEL in contact-setup is set to 0, no material-failure is activated.
I cannot find any other settings which could be responsible for this behavior.

Then, of course, the solver stops with ** ERROR OF SINGULAR MATRIX

 NC=       0 T= 0.0000E+00 DT= 6.4000E-03 ERR=  0.0% DM/M= 0.0000E+00
     --SUPPLEMENTARY CONTACT STIFFNESS MATRIX IS CREATED--
      WITH DIM. : ND   =    2817 NZ  =   73197
 ** ERROR RETURN ** FROM DMUMPS INFO(1)=  -10
 ** INFO(2)=               0
 ** ERROR RETURN ** FROM DMUMPS INFO(1)=  -10
 ** INFO(2)=               0

    ** LINEAR SOLVER MUMPS ERROR CODE:    -10


    ** ERROR OF SINGULAR MATRIX


MESSAGE ID :         79

 ** ERROR: SOLVER IMPLICIT STOPPED DUE TO SOLVER ERROR **

      ISTOP=-4

     ERROR TERMINATION

I don't know if there is a error in the model or a error in the solver.
I have attached a simplified version of the model in which the error still occurs.
Does anyone have any ideas or hints?
tied_problem_openradioss.zip

th_to_csv_win64 does not convert properly

Bug description
I am running a very simple bouncing ball simulation using LS-Dyna inputs. The simulation seems to run correctly. I can convert the ANIMs to VTK and the ball moves as expected. However, when I convert the th file to csv, it is clear that the conversion is wrong. As you can see in the attached file, all outputs seem to be wrong. This is most clear in the "time" output that shows "0" in multiple lines. Can anybody give me some idea of why this may be happening?

To Reproduce
You can reproduce this just by running the attached file ("Bouncing_Radioss.key") in SMP single precision and applying the th_to_csv_win64 to the T01 output.

Expected behavior
The output signals show be coherent with what is happening in the simulation. The time vector should be ordered and show all the output times.

Desktop (please complete the following information):

• Version [commit id]: 892a60a
• Hardware [which CPU]: Intel(R)_Core(TM)i7-3612QM_CPU@_2.10GHz
• Configuration [number of OpenMP threads, and MPI tasks]: SMP single precission 1 thread

Bouncing_ball.zip

INT_BEAM, typo in Manual, bad response for ISECT=2, NITR=2

Describe the bug
The bending moment in a beam should be the inverse of the reaction moment.
With INT_BEAM, ISECT=2, NITR=2 section, there is a high deviation.
The Radioss Reference Guide has in the description /ANIM/BEAM maybe a typo for the plastic strains.

To Reproduce
Run the model and compare the bending moment of element 2111 as in the figure in the attached pdf.

Expected behavior
Correction of the manual regarding EPSP vs. ESPN/N. Extent the section description, give a warning in
the manual for the mentioned plastic beam.

Output
A pdf file with detailed explanations and the Radioss files are in the archive.

Desktop (please complete the following information):

• Version 6cf5b43
• Hardware Intel
• Configuration SMP with one thread

Additional context

openradioss can not use multi cores in one process

I use export OMP_NUM_THRTEADS=4
and mpirun -np 16 --allow-run-as-root ./engine_linux64_gf_ompi -nt 4 -i CamryOpenRadioss_0001.rad
but when I use top command and find every process only use one core not four cores.
I want to know how to solve the problem.

T01/csv file misses the last timestep data

Describe the bug
The converted csv file misses the last time data, checked the th_to_csv.exe source code, which looks fine for me, so I suspect the T01 file has no such data. A 10-step analysis should have 11 time steps if including the initial time zero step. The animation result file is generated correctly, while the T01 file not.

To Reproduce
Run a small test with /TH/ in the starter file. Or use the attached scripts.

Expected behavior
T01/csv file has the last time step. For the attached case, data at time 0.01 should exist.

Output
Attached.

Desktop (please complete the following information):

• Win64, AMD 7950x, 36 OpenMP threads.

mesh_radioss.inc.txt
radioss_welsim_0000.rad.txt
radioss_welsim_0001.rad.txt
radioss_welsim_0000.out.txt
radioss_welsim_0001.out.txt

radioss_welsimT01.txt
radioss_welsimT01.csv
radioss_welsimA011.txt
radioss_welsim_A011.vtk.txt

Add build flag to enable PGO for Engine build.

My idea is
1st, build with '-addflag="-O2 -fprofile-generate''.
2nd, run a target model to collect profile.
3rd, build with '-addflag="-O2 -fprofile-use"'.

However, the 1st build does not succeed. A lot of the following errors happen,

/bin/ld: CMakeFiles/engine_linux64_gf_ompi.dir/source/coupling/rad2rad/rad2rad_c.c.o: warning: relocation against `__gcov_time_profiler_counter' in read-only section `.text'
/bin/ld: CMakeFiles/engine_linux64_gf_ompi.dir/aur/OpenRadioss/common_source/comm/compress_nnz.F.o: in function `compress_r_nnz_':
/aur/OpenRadioss/common_source/comm/compress_nnz.F:153: undefined reference to `__gcov_indirect_call'

I attach the log file, too.
engine_build.log

Findings and thoughts about OpenRadioss

Hello, exploring the OpenRadioss solver and result modules for a few days, I have some thoughts would share here and hope OpenRadioss becomes more exceptional. Overall, OpenRadioss is a great open-source project, I believe that the entire simulation community can benefit from it. This project clearly has the potential to leverage simulation technology to drive more adaption in all sectors of human beings' R&D.

Here are my findings and thoughts:

1. th_to_csv.exe executable works only on the /TFILE/4 generated T01 files. For /TFILE/1-3, the conversion fails.
2. The converted vtk files using anim_to_vtk.exe contain duplicated node ids for Tet4 and Tri3 elements. It looks like the animation file or the conversion assumes the Hex/Quad element in the result files. Although this won't impact the result reading, resolving this can make the vtk files smaller.
3. Since Tet10 has been supported at some areas, SH6N or Tri6 element worth supporting as well.
4. /TH supports the contour results with min and max values at each step, such as the stress on a group of nodes. This feature seems to have the highest priority for me due to its wide usability. I really would try this functionality in the near future.
5. expose an option to output the csv and pvtu files directly, instead of manual conversion afterward. I understand this feature could be difficult to be approved, if so please consider making the license of th_to_csv and anim_to_vtk more friendly, such as BSD, MIT, etc.

6. /TH/TITLE command in the engine file fails the solve.

Since I am still new to OpenRadioss, my thoughts above could be naive, and feel free to correct me. I will be keeping exploring OpenRadioss. Thank you.

The reaktion force via th_to_csv th_to_csv does not show the reaction force.

Describe the bug
The reaktion force via th_to_csv th_to_csv does not show the reaction force.

To Reproduce
Run reakForceIssue_0000.rad, reakForceIssue_0001.rad and th_to_csv_linux64_gf.
In Paraview/Editor you can see the wrong curve.

Expected behavior
The reaction force should be displayed.

Output
An archive with .rad, .out, .T01, .csv and some png files.
If applicable, add screenshots to help explain your problem.
You can also add the *.rad ,*.out files.

Desktop (please complete the following information):
Git ID 6684c24

• see the .out files in the attached archive.

Additional context
In the model, some nodes of a component are moved through a surface and pulled back.
The force should be zero afterwards and visible in the requested diagram. The contact pressure goes correct back to zero.
reakForceIssue.tar.gz

using OpenRadioss without starter, or building starter without hypermesh reader binary blob?

Hello, @OlivierWienholtz

I managed to get OpenRadioss engine working on linux ppc64le (IBM POWER) system, it was simple.

However, OpenRadioss starter does not build, because it seems to depend on a binary blob (libhm_reader) that is not available for this platform.

Is it possible to use OpenRadioss without the starter, or is it possible to build a 'simplified' starter that does not depend on libhm_reader? (Or, is it possible to get a version of libhm_reader for linux ppc64le?)

Is independently developing an open source 'starter' a reasonable project for one person or the community to undertake? Or, is there any plan to open source the code behind libhm_reader?

Visual Studio 2019 compile errors on windows system

Hello, I have installed Visual studio 2019 and intel oneAPI 2022 in my windows system. The environment of openRadioss on windows is built with cygwin, and the make package and perl package are installed in cygwin. The Visual studio solution can be built successfully, however, when the solution is opened for build with vs2019, an MSB8066 error is reported with exit code 9009. I don't know how to fix this error？
thank you!

Initial velocity in a LS-DYNA model is not working

Describe the bug
A LS-DYNA model with initial rotations is not rotating.
In flying_solid_0000.out:
` INITIAL VELOCITIES
-------------------
NODE VX VY VZ VRX VRY VRZ

NUMBER OF NODES WITH INITIAL VELOCITY: 0
`
flying_solid.k.gz

To Reproduce
Run starter and engin

Expected behavior
It should rotate

Output
LS-DYNA file is in the attachment

Desktop (please complete the following information):
Linux 64 bits, GNU compiler
git 96f63c1
Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (x86_64)
NUMBER OF HMPP PROCESSES 1

Additional context
When do an init with velocities, it works.

Serious starter issue, segmentation violation, trap error 760

Describe the bug
The starter abort with the latest git versions with error 760 running "2010 TOYOTA YARIS (CCSA V2j)"

To Reproduce
git checkout c8bef46
run starter

Expected behavior
No failure.

Output

 +=============================================================+
 |     ABNORMAL END                                            |
 |          Segmentation Violation                             |
 |     TRACE BACK :                                            |
 +=============================================================+
   RESTART FILE(S) WRITING
 +=============================================================+

ERROR ID :    760
** ERROR TRAPPED


 RADIOSS STOP DUE TO INPUT ERROR


------------------------------------------------------------------------------------------------------------------------
|            ERROR(S) SUMMARY                               |             WARNING(S) SUMMARY                           |
------------------------------------------------------------------------------------------------------------------------
|                                                           |                                                          |
|  --- RESTART FILE(S) WRITING                1   ERROR(S)  |  --- INTERNAL                               2 WARNING(S) |
|       |                                                   |       |                                                  |
|       |                                                   |       |                                                  |
|       |---     1   ERROR ID :          760                |       |---     2 WARNING ID :         1640               |
|       | ** ERROR TRAPPED                                  |       | ** WARNING IN SPRING MATERIAL SET                |
|       |                                                   |       |                                                  |
|                                                           |                                                          |

Desktop (please complete the following information):

• Version: see below
• Hardware Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (x86_64), 3499 MHz, 64217 MB RAM
• Configuration STARTER RUNNING ON 1 THREAD

Additional context
Add any other context about the problem here.

Last working with 5f471d5
Not working with c8bef46
still not working with b64f5dc

Is there any guide for constitutive developer?

Is your feature request related to a problem? Please describe.
I notice that every Fortran file provides its link to other subroutines.
Yet the project contains so many source files.

Describe the solution you'd like
It would be great to provide linking trees so that the developer can gain a whole picture of this project.
Also, simple examples for development, similar to UMAT and UEL in ABAQUS, can also be provided to draw the attention of more users.

** ERROR IN INPUT FORMAT

Describe the bug
Run successfully in commercial version of radioss 2021.2,but no in openradioss

ERROR ID : 55
** ERROR IN INPUT FORMAT
DESCRIPTION :
-- OPTION:
-- BLOCK:
-- LINE:
To Reproduce
run starter_win64.exe -i **\ult_0000.rad

Output

change .txt to .out
ult_0000.txt

Desktop (please complete the following information):

• Version [commit id] [20221118]
• Hardware [which CPU] Xeon Sliver 4120R*2
• Configuration [number of OpenMP threads, and MPI tasks]
• nt 1
• set OMP_NUM_THREADS=[N]

Additional context
model in here,has been morphed due to censor requirement
change .txt to .rad
ult_0000.txt
ult_0001.txt

”undefined reference to symbol“ when compiling starter

Describe the bug
When I compile the starter in ubuntu 20.04 WSL, it fails in linking Fortran executable starter_linux64_gf

To Reproduce
run ./build_script.sh -arch=linux64_gf in starter folder

Desktop (please complete the following information):
gcc version = 9.4.0
gfortran version = 9.4.0
cmake version = 3.16.3

Additional context
No

Issue with linking libmetis_linux64_gcc.a

Describe the bug
When I compile the starter in ubuntu 20.04, it fails in linking libmetis_linux64_gcc.a

To Reproduce
run ./build_script.sh -arch=linux64_gf

Desktop (please complete the following information):
gcc version = 10.3.0
gfortran version = 9.4.0
cmake version = 3.16.3

Additional context
No

add topics

I suggest adding topics such as finite-elements, fem in the About section at https://github.com/OpenRadioss/OpenRadioss.

typo in engine/build_script.sh

Describe the bug
Seems to by a type of environment variable scalapack_root:
@@ -154,7 +154,7 @@ else
if [ "$arg" == "-scalapack_root" ]
then
scalapack_root=echo $var|awk -F '=' '{print $2}'

•    scalapack_root="-Dsclapack_root=${scalapack_root}"
  

•    scalapack_root="-Dscalapack_root=${scalapack_root}"
    fi
  
    if [ "$arg" == "-addflag" ]
  

Expected behavior
Correct to run the sh-script

cmake files for ompi libraries in engine build

In the directory ...OpenRadioss/engine/CMake_Compilers the files cmake_linux64_AOCC.txt and cmake_linuxa64.txt the mpi_lib has the option "-I" instead of "-L" in line 43

`--- a/engine/CMake_Compilers/cmake_linux64_AOCC.txt
+++ b/engine/CMake_Compilers/cmake_linux64_AOCC.txt
@@ -40,7 +40,7 @@ if ( DEFINED MPI )
set (mpi_inc "-I${mpi_incdir}")
endif()
if ( DEFINED mpi_libdir )

•        set (mpi_lib "-I${mpi_libdir} -lmpi -lmpi_mpifh")
  

•        set (mpi_lib "-L${mpi_libdir} -lmpi -lmpi_mpifh")
     endif()
  
   endif()`
  

Engine executable help message contains "Starter" for -input

Describe the bug
Engine executable help message shows "Starter" input file for the -input argument

To Reproduce
run the engine_win64.exe with no argument.

Expected behavior
Show the word of "Engine" instead of "Starter".

Output
A screen capture is attached.

Desktop (please complete the following information):

• Official build Dec. 12. 2022

Additional context
This is minimal.

ANIM_SHELL_THIN card

Hello!
For metalforming processes simulations I have try to include to results database a thinning of sheets in simulation with the card
/ANIM/SHELL/THIN .
Solver is working with it, but when I've open with windows ParaView 5.9.1 any vtk-files, converted from A-files, the thinning results always return an error "Could not determine array range", and the name of such results has undefined symbol: "2DELEM_?inning". At the same time the older ParaView versions (5.4.0 for example) have no any thinning results.

How to define UMAT?

Hey, I am learning how to develop UMAT using OpenRadioss.
Based on the official document, I put LECM29.F in starter/source/mat/mat029 and sigeps.F in engine/source/materials/mat029.
These subroutines are used for elastic constitutive relations. When I compiled the source code and run the starter, the error msg was given below:

ERROR ID :   1130
 ** ERROR IN USER INTERFACE
DESCRIPTION :
   OPTION: /MAT/USER01
   USER INTERFACE OPTION USED, BUT NO USER INTERFACE ROUTINE IS FOUND
 RADIOSS STOP DUE TO INPUT ERROR
     ERROR TERMINATION
     ------------------
              1ERROR(S)
 ** ERROR: FILE elasticity_0000_0001.rst NOT FOUND
     ERROR TERMINATION
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 2.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.

Could anyone let me know how to solve this problem? Many thanks in advance!

Serious Issue: The Starter crashed with segfault in a 2D model with /INTER/TYPE11

Describe the bug
The Starter crashed with segfault.

To Reproduce
Run the starter with the "lee_0000.rad" out of the attached archive
issue.tar.gz

Expected behavior
Should not crash.

Output
'''
+=============================================================+
| ABNORMAL END |
| Segmentation Violation |
| TRACE BACK : |
+=============================================================+
INTERFACES
+=============================================================+

ERROR ID : 760
** ERROR TRAPPED

RADIOSS STOP DUE TO INPUT ERROR
###########
With dbg the following information is given:

.. INTERFACE BUFFER INITIALIZATION

Program received signal SIGSEGV, Segmentation fault.
inint0 (x=..., irect=..., nseg=..., nod2seg=..., nsv=..., msr=..., iloc=..., nmn=3, nsn=3, nrt=2) at /opt2/OpenRadioss/starter/source/interfaces/interf1/inint0.F:80
80 IF(NOD2SEG(L)/=0) II=II+1
'''
Desktop (please complete the following information):

• Version [2a35aba]
• Hardware [which CPU]
  Linux: Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (x86_64), 3498 MHz, 64217 MB RAM, 0 MB swap
  STARTER RUNNING ON 1 THREAD

Additional context
None.

call for source code manual

At present, there is no relevant description of the code, which is unfavorable for users to use the program

OpenRadioss build with OpenMPI on UBUNTU 20.04.4 LTS fails

Describe the bug
During building of OpenRadioss engine, an ERROR occures at the end of the compilation process, when adding OpenMPI.

To Reproduce
Using this command to start the building process:
./build_script.sh -arch=linux64_gf -mpi=ompi -nt=1

Expected behavior
The compiler should finish creating an executable without any error.

Output
Screenshot add to this Bug report.

Desktop (please complete the following information):

• Windows10 / WSL Ubuntu 20.04.4 LTS
• Intel 7 CPU laptop
• (see above To Reproduce)

Additional context
Without OpenMPI engine compiles correctly and executable runs fine.

*** buffer overflow detected ***: terminated

Describe the bug
when i start with h3d output in *****_0001.rad ,this bug is coming
i use the last version OpenRadioss

To Reproduce

Expected behavior

Output
If applicable, add screenshots to help explain your problem.
2023-01-12 13:35:58.111 [10.20.42.69:27777] INFO *** buffer overflow detected ***: terminated
2023-01-12 13:35:58.521 [10.20.42.69:27777] INFO ERROR TERMINATION
2023-01-12 13:35:58.557 [10.20.42.69:27777] INFO --------------------------------------------------------------------------
2023-01-12 13:35:58.557 [10.20.42.69:27777] INFO MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
2023-01-12 13:35:58.557 [10.20.42.69:27777] INFO with errorcode 3.
2023-01-12 13:35:58.557 [10.20.42.69:27777] INFO
2023-01-12 13:35:58.558 [10.20.42.69:27777] INFO NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
2023-01-12 13:35:58.558 [10.20.42.69:27777] INFO You may or may not see output from other processes, depending on
2023-01-12 13:35:58.558 [10.20.42.69:27777] INFO exactly when Open MPI kills them.

Desktop (please complete the following information):

• Version [commit id]
• Hardware [which CPU]
• Configuration [number of OpenMP threads, and MPI tasks]

Additional context

fixing AMD AOCC-4.0.0 build issues

Hi All

I have forked the repo and have a branch that fixes the build problems with AMD's newly released AOCC-4.0.0
I will submit a pull request shortly.
I opened this issue to follow the steps as you required per contributing.md document.

Thanks

LS-DYNA input etype selection and /TFILE parameter setting is not working

Describe the bug
Some problems occur when running with LS-DYNA input files.

1. a fully integrated hex element cannot be selected.

2. neither loading nor the /TFILE parameters work with *INCLUDE_TRANSFORM
   /TFILE/4
   0
   /RFILE
   0
   /RFILE
   0

3. in the output file the *CONTROL_UNITS is not reported
   WORK UNIT SYSTEM . . . . . . ( N.A, N.A, N.A ) 1.0000000000000E+00 1.0000000000000E+00 1.0000000000000E+00
   INPUT UNIT SYSTEM . . . . . ( N.A, N.A, N.A ) 1.0000000000000E+00 1.0000000000000E+00 1.0000000000000E+00
   UNIT SYSTEM, ID = 1000000001 ( N.A, N.A, N.A ) 1.0000000000000E+00 1.0000000000000E+00 1.0000000000000E+00

To Reproduce
Run the job
$OPENRADIOSS_SOURCE_PATH/exec/engine_linux64_gf -i Start.k -nt 1
and look into Start_0001.rad and Start_0000.out

Expected behavior
1.
The LS-DYNA element type 2 should translatet into Isolid 14/18
2.
/TFILE/4
0.0005
3.
WORK UNIT SYSTEM . . . . . . ( Mg , mm , s ) 1.0000000000000E+03 1.0000000000000E-03 1.0000000000000E+00
INPUT UNIT SYSTEM . . . . . ( Mg , mm , s ) 1.0000000000000E+03 1.0000000000000E-03 1.0000000000000E+00

Output
The input files are in the attached archive.

Desktop (please complete the following information):

• Version: 3a18bf2
• Hardware: Intel with gcc on linux
• Configuration: 1 OpenMP threads, and 1 MPI tasks

Additional context
The include conrad_0000.rad and conrad_0001.rad show a possible solution
elemissue.tar.gz

Trying to get the first OpenRadioss starter script worked

Hello OpenRadioss community, my first program-generated starter file failed to pass the check, I read the Reference Guide but could not quickly figure out the solutions. Could you experts please identify all issues in the scripts, and show me the correction? Thank you so much.

The model is a simplified ice sliding case, with only one icy cube (brick tet4) and one slider (shell 3n). The output errors show below. The model picture, input scripts, and output file are attached.

************************************************************************
**                                                                    **
**                                                                    **
**                        OpenRadioss Starter                         **
**                                                                    **
**            Non-linear Finite Element Analysis Software             **
**                                                                    **
**                                                                    **
**                                                                    **
**                  Windows 64 bits, Intel compiler                   **
**                                                                    **
**                                                                    **
**                                                                    **
** CommitID: 02469f63d91a0a2b3dd8aa3507d5cf0961ac9d04                 **
************************************************************************
** OpenRadioss Software                                               **
** COPYRIGHT (C) 1986-2022 Altair Engineering, Inc.                   **
** Licensed under GNU Affero General Public License.                  **
** See License file.                                                  **
************************************************************************


WARNING ID : 100214
** WARNING IN INPUT OPTIONS
DESCRIPTION :  
-- BLOCK: /PROP/SHELL/12/3
-- LINE: 0.01                0.01                0.01                0.01                   0
unsupported field exits
SOLUTION :     
    Please check input format and fields description defined in the Reference Guide.

WARNING ID : 100217
** WARNING IN INPUT OPTIONS
DESCRIPTION :  
-- BLOCK: /PROP/SHELL/12/3
-- LINE: /PROP/SOLID/13/3
card is missing
SOLUTION :     
Please check input format and fields description defined in the Reference Guide.

WARNING ID : 100217
** WARNING IN INPUT OPTIONS
DESCRIPTION :  
-- BLOCK: /PROP/SOLID/13/3
-- LINE: /FUNCT/21
card is missing
SOLUTION :     
Please check input format and fields description defined in the Reference Guide.

 .. UNITS SYSTEM                                                                         
 .. CONTROL VARIABLES                                                                    
 .. STARTER RUNNING ON   32 THREADS
 .. FUNCTIONS & TABLES
 .. MATERIALS                                                                            
 .. NODES                                                                                
 .. SUBMODELS
 .. PROPERTIES                                                                           
 .. 3D SOLID ELEMENTS                                                                    
 .. 3D SHELL ELEMENTS                                                                    
 .. SUBSETS
 .. ELEMENT GROUPS
 .. PART GROUPS
 .. SURFACES 
 .. NODE GROUP
 .. BOUNDARY CONDITIONS                                                                  
 .. DOMAIN DECOMPOSITION
 .. ELEMENT GROUPS                                                                       
 .. INTERFACES                                                                           
 .. INTERFACE BUFFER INITIALIZATION                                                      
 .. RETURNS TO DOMAIN DECOMPOSITION FOR OPTIMIZATION
 .. DOMAIN DECOMPOSITION
 .. ELEMENT GROUPS                                                                       
 .. INTERFACES                                                                           
 .. INTERFACE BUFFER INITIALIZATION                                                      
 .. ELEMENT BUFFER INITIALIZATION                                                        

ERROR ID :    245
** ERROR: ZERO OR NEGATIVE 3D SOLID VOLUME
DESCRIPTION :  
   ZERO OR NEGATIVE VOLUME 3D ELEMENT ID=179

ERROR ID :    245
** ERROR: ZERO OR NEGATIVE 3D SOLID VOLUME
DESCRIPTION :  
   ZERO OR NEGATIVE VOLUME 3D ELEMENT ID=180

ERROR ID :    245
** ERROR: ZERO OR NEGATIVE 3D SOLID VOLUME
DESCRIPTION :  
   ZERO OR NEGATIVE VOLUME 3D ELEMENT ID=181

ERROR ID :    245
** ERROR: ZERO OR NEGATIVE 3D SOLID VOLUME
DESCRIPTION :  
   ZERO OR NEGATIVE VOLUME 3D ELEMENT ID=182

ERROR ID :    245
** ERROR: ZERO OR NEGATIVE 3D SOLID VOLUME
DESCRIPTION :  
   ZERO OR NEGATIVE VOLUME 3D ELEMENT ID=183

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=77 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=79 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=115 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=116 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=128 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=129 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=130 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=131 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=132 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=133 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=134 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=135 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=136 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=137 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=138 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=139 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=140 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=141 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=142 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=143 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=144 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=145 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=146 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=147 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=148 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=149 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=150 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=151 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=152 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=153 HAS NEGATIVE OR NULL SURFACE

ERROR ID :     21
** ERROR IN SHELL DEFINITION
DESCRIPTION :  
   SHELL ID=154 HAS NEGATIVE OR NULL SURFACE

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION

ERROR ID :    495
** ERROR IN SHELL DEFINITION
 .. GEOMETRY PLOT FILE                                                                   
 .. ERROR ==> NO RESTART FILE                                                            
  
------------------------------------------------------------------------
  
                   ** COMPUTE TIME INFORMATION **
  
 EXECUTION STARTED      :      2022/12/13  20:34:49
 EXECUTION COMPLETED    :      2022/12/13  20:34:49
  
 ELAPSED TIME...........=          0.31 s
                               00:00:00
  
------------------------------------------------------------------------



     ERROR TERMINATION                  
     ------------------                                                                  
            134 ERROR(S)            
              6 WARNING(S)          




PLEASE CHECK LISTING FILE FOR FURTHER DETAILS

radioss_welsim_0000.rad.txt
mesh_radioss.inc.txt
radioss_welsim_0000.out.txt

*** buffer overflow detected ***: terminated

Discussed in https://github.com/orgs/OpenRadioss/discussions/625

^{Originally posted by ZdendaH October 15, 2022}
Hello OpenRadioss,

I got this message when I run the ice_cube and tensile_test examples:

***** buffer overflow detected *: terminated

Maybe it can be caused by computer memory, I only have 16GB.

Thank you for your answer.

Starter can not find libhm_reader_linux64.so

I have made starter with -arch=linux64_gf. But when I run it, it notices as fellow. Even if I download and run the release exec, it also notices this.

./starter_linux64_gf: error while loading shared libraries: libhm_reader_linux64.so: cannot open shared object file: No such file or directory

And I can find this file in OpenRadioss/extlib/hm_reader/linux64/. Whether any package I haven't install?
I'm using wsl2 ubuntu 22.04 on win10.

Syntax for /INCLUDE_DYNA

Hi,

I'm having an issue getting /INCLUDE_DYNA to process in starter. I'm using the most recent starter engine binary at the time of writing. Is there any syntax that I am missing/using incorrectly?

Rename anim Axxx file index from 1-based to 0-based

Describe the bug
The generated Axxx file starts with A001, which isn't intuitive since the first anim file is about time 0.

To Reproduce
Any engine file that contains /ANIM/, or uses the scripts attached.

Expected behavior
The first generated anim file should be like xxxA000, and the last generated anim file index matches the number of the time steps.

Output
A screenshot is attached.

Desktop (please complete the following information):
Win64, AMD 7950x, 32 OpenMP threads.

radioss_welsimA001.txt
radioss_welsim_A001.vtk.txt

mesh_radioss.inc.txt
radioss_welsim_0000.rad.txt
radioss_welsim_0001.rad.txt

Parallel run of OpenRadioss Build e10539f is confusing

I am trying to run OpenRadioss in parallel. First thing confusing me is that starter has a "-nt" flag according to its help output. However, only -np is uses for starter, according to the explanation given here:
https://openradioss.atlassian.net/wiki/spaces/OPENRADIOSS/pages/19628079/Running+OpenRadioss

I propose to clear out "-nt" in the starter help.

Following the explanation I am getting MPI parallelization to run. However, OpenMP does not work. Every time I do
export OMP_NUM_THREADS=N
with N>0 before calling the starter I get a crash (core dumped) from the starter. What's wrong there, how can this be debugged?

Is "libhm_reader_linux64.so" open sourced?

If not, it seems that no one else can build OpenRadioss. At least my Ubutun 20.04 gcc9 shows linking errors about it. No mention of Windows VS+ ifort compilers.

How to debug the code?

Hey, debugging may be an excellent way to understand the structure of OpenRadioss. I have installed GDB.
With the following command, I can obtain the executable for debugging.

./build_script.sh -arch=linux64_gf -debug=1 -nt=4

However, when I set the breakpoint in 'starter.F' and ran the starter with *0000.rad, the program did not stop at the breakpoint.
Could you please let me know the correct way to debug?

Include Implicit Solver

I get different compiler errors on different systems when I follow the instructions in the cmake text file (version with AND without MPI).
I am probably still doing something wrong when compiling the required packages lapack scalapack and mumps.

I think it would be a good idea to include the implicit solver in general. Traditionally, this is the other big solver world, which is always needed - even if the solver comes from the explicit world ;-)

Node contact forces are all written as "0" into all anim files

Describe the bug
Node contact forces are all written as "0" into al anim files

To Reproduce

1. Run a OpenRadioss-Job with output to animation-files
2. Post-process nodal contact forces - they are "0" for all nodes in all animation files

Expected behavior
Should write the correct nodal contact forces to animation files

[FR] Add `.git-blame-ignore-revs` to omit commits that may be considered to pollute the repo git log/blame

Is your feature request related to a problem? Please describe.
Certain commits may pollute the git log output or at least irk some folks who view it that way.

Describe the solution you'd like
Github allows the use of a .git-blame-ignore-revs file. Here's the background (link). Essentially the file consists of commit hashes that the project would prefer to be omitted from the repo git blame.

I'll be submitting a PR that will address past typo fixes to be included in said .git-blame-ignore-revs
JFYI, the command I used to ascertain said commits was:

$ git log --oneline --no-abbrev-commit | grep typos
ec64eee54bab8d011ebf024a0e052a43a6617be2 Fix typos in starter/source/interfaces subdir
f22ff42b348f2a4031489975611849422aa37f7f Fix typos in starter/source/properties subdir
6e9837361fcee23e6c6cd39b8b4a421e5f406cc3 Fix typos in starter/source/elements subdir
591fcb9df0f8aacfddd5c3f08437f512e4bf96ce Fix typos in starter/source/materials subdir

Unit issue in "2010 TOYOTA YARIS (CCSA V2j)"

Describe the bug
The GAS CHARACTERISTICS of "2010 TOYOTA YARIS (CCSA V2j)" are a factor 1000 to small.

To Reproduce
Run the starter with the "2010 TOYOTA YARIS (CCSA V2j)" demo model and look into the output file.

Expected behavior

MOLECULAR WEIGHT  . . . . . . . . . . .=  0.2897E-04
UNIVERSAL GAS CONSTANT. . . . . . . . .=  0.8314E+04

Output
In "YarisOpenRadioss.key" is the unit definition:

 10 *CONTROL_UNITS
 11 $LENGTH   TIME      MASS      TEMP
 12 $#  length      time      mass      temp
 13 mm        sec       mtrc_ton  k

In "YarisOpenRadioss_0000.out" is the units system:

   57457     WORK UNIT SYSTEM . . . . . . ( N.A, N.A, N.A ) 1.0000000000000E+00 1.0000000000000E+00 1.0000000000000E+00
   57458     INPUT UNIT SYSTEM  . . . . . ( N.A, N.A, N.A ) 1.0000000000000E+00 1.0000000000000E+00 1.0000000000000E+00
   57459     UNIT SYSTEM, ID = 1000000001 ( N.A, N.A, N.A ) 1.0000000000000E+00 1.0000000000000E+00 1.0000000000000E+00

and then:

   97907        GAS CHARACTERISTICS
   97908        -------------------
   97909
   97910
   97911      GAS TYPE. . . . . . . . . . . . . . . .=  User
   97912      SPECIFIC HEAT AT CONSTANT PRESSURE CP .=  0.1004E+10
   97913      SPECIFIC HEAT AT CONSTANT VOLUME CV. . =  0.7170E+09
   97914      MOLECULAR WEIGHT  . . . . . . . . . . .=  0.2897E-07
   97915      UNIVERSAL GAS CONSTANT. . . . . . . . .=  0.8314E+01

Desktop (please complete the following information):

• Version [42e2b4c]
• Hardware [which CPU]
  Linux:Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (x86_64), 3498 MHz, 64217 MB RAM, 0 MB swap
  STARTER RUNNING ON 1 THREAD

Additional context
This seems to be a consequence error of /UNITS in connection with *INCLUDE.