Error # 192 when running a large file in Radioss

Altair Forum User
Altair Forum User
Altair Employee
edited October 2020 in Community Q&A

Hello...,

Currently, I have an ERROR # 192 when running a large file in Radioss (~500mb *.fem).

My system is workstation Intel® Xeon® CPU W3680 @3.33 GHz

Ram: 12 GB

64Bit OS

The details as follows:

NONLINEAR ITERATION SUMMARY FOR Subcase 1

LOAD STEP: 0.1000

---------------------------------------------------------------

Nonlinear Error Measures Gap/Contact Status

ITER EUI EPI EWI Open Closed

---------------------------------------------------------------

1 9.9000E+01 7.5286E-05 7.5286E-05 222 44

2 3.0544E-02 6.9100E-06 4.3588E-06 231 35

3 1.9160E-03 1.1238E-07 1.2106E-08 235 31

4 1.4125E-04 0.0000E+00 0.0000E+00 235 31

LOAD STEP: 0.2000

---------------------------------------------------------------

Nonlinear Error Measures Gap/Contact Status

ITER EUI EPI EWI Open Closed

---------------------------------------------------------------

1 4.9675E+01 8.3937E+03 4.1805E+03 164 102

*** ERROR # 192 ***

Possible programming Error :

Unexpected error condition from subroutine 'xdslvf'

ioerr(1) = -404

ioerr(2) = 1

***** PROGRAMMING ERROR *****

***** INTERNAL PROGRAMMING ERROR *****

in file 'nlstatslv.F', at location # 1033

ioerr(1) = 0

ioerr(2) = 0

ioerr(3) = 577

**** ABORTING RUN DUE TO AN INTERNAL ERROR ****

************************************************************************

RADIOSS/OptiStruct error termination report:

RAM: 8046 MB total, 1 MB used.

Data arrays: 235 total, 176 allocated.

DATA SET size 0 MB, ram_disk 2 MB

DATASET USAGE: ndirs: 1, nfiles 1, nsets: 7, nblocks: 8, mode: 8

DIR: 0, size 3987[MB], path 'D:/Congviec/21-08/' num_files 1

---

OptiStruct traceback info at: 08/21/11 19:55:17

Trace point: 10:694

( 0) 10 optist.F:694

( -1) 20 prpdrv.F:9146

( -2) 10 optist.F:449

( -3) 14 flim.F:204

( -4) 10 optist.F:429

( -5) 21 prp1drv.F:1657

( -6) 10 optist.F:416

( -7) 29 prp0drv.F:725

( -8) 10 optist.F:395

( -9) 11 readnew.F:6485

(-10) 16 reorder.F:467

(-11) 11 readnew.F:3505

(-12) 10 optist.F:113

Internal Trace

( 0) 10 optist.F:694

( 20) prpdrv.F:9146

CPU times[sec]: user 27148.697, system 565.270, Wall clock 27713.967

Command line arguments:

D:\Congviec\21-08\mam_xoay_Final.fem

-nproc=6

-exec=RD

File stats with output file root: mam_xoay_Final

Work directory: './' Free size 86.1 GB

243333192 mam_xoay_Final.3988_00st.scr

22856 mam_xoay_Final.3988_scr.s40

57137288 mam_xoay_Final.3988_scr.s44

0 mam_xoay_Final.3988_scr.w41

0 mam_xoay_Final.3988_scr.w42

Work directory: 'D:/Congviec/21-08/' Free size 31.7 GB

473935231 mam_xoay_Final.fem

109400747 mam_xoay_Final.hm

10119 mam_xoay_Final.out

1959 mam_xoay_Final.stat

4093791024 mam_xoay_Final_3988_00.scr

Anybody can tell me what the error is and how to fix this problem.

Thanks you very much

Tagged:

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2011

    Hello...,

    Currently, I have an ERROR # 192 when running a large file in Radioss (~500mb *.fem).

    My system is workstation Intel® Xeon® CPU W3680 @3.33 GHz

    Ram: 12 GB

    64Bit OS

    The details as follows:

    NONLINEAR ITERATION SUMMARY FOR Subcase 1

    LOAD STEP: 0.1000

    ---------------------------------------------------------------

    Nonlinear Error Measures Gap/Contact Status

    ITER EUI EPI EWI Open Closed

    ---------------------------------------------------------------

    1 9.9000E+01 7.5286E-05 7.5286E-05 222 44

    2 3.0544E-02 6.9100E-06 4.3588E-06 231 35

    3 1.9160E-03 1.1238E-07 1.2106E-08 235 31

    4 1.4125E-04 0.0000E+00 0.0000E+00 235 31

    LOAD STEP: 0.2000

    ---------------------------------------------------------------

    Nonlinear Error Measures Gap/Contact Status

    ITER EUI EPI EWI Open Closed

    ---------------------------------------------------------------

    1 4.9675E+01 8.3937E+03 4.1805E+03 164 102

    *** ERROR # 192 ***

    Possible programming Error :

    Unexpected error condition from subroutine 'xdslvf'

    ioerr(1) = -404

    ioerr(2) = 1

    ***** PROGRAMMING ERROR *****

    ***** INTERNAL PROGRAMMING ERROR *****

    in file 'nlstatslv.F', at location # 1033

    ioerr(1) = 0

    ioerr(2) = 0

    ioerr(3) = 577

    **** ABORTING RUN DUE TO AN INTERNAL ERROR ****

    ************************************************************************

    RADIOSS/OptiStruct error termination report:

    RAM: 8046 MB total, 1 MB used.

    Data arrays: 235 total, 176 allocated.

    DATA SET size 0 MB, ram_disk 2 MB

    DATASET USAGE: ndirs: 1, nfiles 1, nsets: 7, nblocks: 8, mode: 8

    DIR: 0, size 3987[MB], path 'D:/Congviec/21-08/' num_files 1

    ---

    OptiStruct traceback info at: 08/21/11 19:55:17

    Trace point: 10:694

    ( 0) 10 optist.F:694

    ( -1) 20 prpdrv.F:9146

    ( -2) 10 optist.F:449

    ( -3) 14 flim.F:204

    ( -4) 10 optist.F:429

    ( -5) 21 prp1drv.F:1657

    ( -6) 10 optist.F:416

    ( -7) 29 prp0drv.F:725

    ( -8) 10 optist.F:395

    ( -9) 11 readnew.F:6485

    (-10) 16 reorder.F:467

    (-11) 11 readnew.F:3505

    (-12) 10 optist.F:113

    Internal Trace

    ( 0) 10 optist.F:694

    ( 20) prpdrv.F:9146

    CPU times[sec]: user 27148.697, system 565.270, Wall clock 27713.967

    Command line arguments:

    D:\Congviec\21-08\mam_xoay_Final.fem

    -nproc=6

    -exec=RD

    File stats with output file root: mam_xoay_Final

    Work directory: './' Free size 86.1 GB

    243333192 mam_xoay_Final.3988_00st.scr

    22856 mam_xoay_Final.3988_scr.s40

    57137288 mam_xoay_Final.3988_scr.s44

    0 mam_xoay_Final.3988_scr.w41

    0 mam_xoay_Final.3988_scr.w42

    Work directory: 'D:/Congviec/21-08/' Free size 31.7 GB

    473935231 mam_xoay_Final.fem

    109400747 mam_xoay_Final.hm

    10119 mam_xoay_Final.out

    1959 mam_xoay_Final.stat

    4093791024 mam_xoay_Final_3988_00.scr

    Anybody can tell me what the error is and how to fix this problem.

    Thanks you very much

    if you could send me your model as a zip file i can check it in our cluster, maybe than we can understand that it is a hardware problem or not.

    other option is, if it is possible could you please put the check run results here ?