Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

Segmentation Violation

Hi,

I'm trying to run an implicit nlgeom analysis and keep running into the same Error Termination:

*** ERROR # 4002 ***
Running RADIOSS engine, 1 ERROR and 0 WARNINGs have been detected.
They are listed below.

ENGINE ERROR:
** ERROR : ABNORMAL END
       +=============================================================+
       |          Segmentation Violation                             |
       +=============================================================+
       | TRACE BACK :                                                |
       +=============================================================+
       | + RADIOSS ENGINE
       | +   SOLUTION PHASE: Processor=    1/   16
       +=============================================================+

NLGEOM subcase        1, engine finished

The analysis contains 2D and 3D elements and two contact definitions. But the same error occures when I just use 3D elements.

Can anybody help me solve my problem?

Thanks in advance!

Find more posts tagged with

English

Radioss

Accepted answers

All comments

Altair Forum User

Hi Niwi,

Please share the all .out file(s) (you will also see <filename>_0000.out and _0001.out files in working directory) to check what the problem is.

Altair Forum User

Somehow I'm not permitted to upload the files.

Altair Forum User

Niwi,

Please use the dropbox link in the signature below to share the files.

Altair Forum User

Niwi,

could you please share the model?

Altair Forum User

Hello everybody,

I'm still struggling with my analysis. Any ideas so far?

Thanks in advance,

niwi

Rahul_P1

Run it from a local drive instead of a network drive if that is what you are doing,

Try and reduce the element number if it is too large,

check the out file for more information about the error etc

Altair Forum User

I did run it on a local drive and got the same Error message. The .out file dowosn't deliver any new clues, either.

It seems I'll have to try and reduce the model as much as possible.

Altair Forum User

Hi Niwi,

I think the error is due to the table definition.

Please have a look at the comments for TABLED1 entry and change the table accordingly.

<?xml version="1.0" encoding="UTF-8"?>

Altair Forum User

Hi,

I don't really get the mistake. x_i is allways ascending and there are no discontinuities, since y_i doesn't have to be either continually ascending or descending.