#1 2021-11-01 04:32:16

DougAtMcGill

Member

Registered: 2021-10-12

Posts: 3

max_base error in Code_Aster 15.4?

While running a very long DYNA_NON_LINE analysis in two steps I get the following error after about 12 hours:

<EXCEPTION> <JEVEUX_42>                                                                       

Fichier saturé, le nombre maximum d'enregistrement 61440 de la base GLOBALE est atteint
il faut relancer le calcul en passant une taille maximum de base sur la ligne de commande
argument "--max_base" suivi de la valeur en Mo. 

<EXCEPTION> <CATAMESS_55>                                                                     

Recursive calls of error messages or warnings.                                             

EXECUTION_CODE_ASTER_EXIT_10723=134

<I>_EXIT_CODE = 134

I tried adding the line this line to my .export file:
A args -max_base 300000

but still got the same error.

Another forum post mentioned that as of Code_Aster version 14, it should no longer be necessary increase the max_base argument and that instead the program will do it automatically. When I try running as_run with a "-max_base" argument it doesn't seem to accept it. I am using Code_Aster version 15.4 that comes packaged with Salome Meca in a Singularity container, if that makes any difference.

Does anyone have any ideas about how to fix this error? It is very difficult to troubleshoot when each attempted model run takes 12 hours to reproduce the error. I'm relatively new to Code_Aster and completely new to Singularity.

Ect

Member

From: Switzerland

Registered: 2008-05-15

Posts: 103

Re: max_base error in Code_Aster 15.4?

Hello,

I had the same issue yesterday with version 14.6, and played a bit with the parameters and it seems that max_base cannot be greater than memjeveux.

For example max_base is effectively doing something on the maximum number of records:

A args -max_base 1000000000000
Le nombre d'enregistrements maximum de la base GLOBALE sera modifié
de 125828 a 1280000000000

or

A args -max_base 10000000000
Le nombre d'enregistrements maximum de la base GLOBALE sera modifié
de 125828 a 12800000000

but then you get error messages that you can not exceed the maximum memory:

   !---------------------------------------------------------------------------!
   ! <EXCEPTION> <JEVEUX_62>                                                   !
   !                                                                           !
   !  Erreur lors de l'allocation dynamique. Il n'a pas été possible d'allouer !
   !  une zone mémoire de longueur 9765625 Mo, on dépasse la limite maximum    !
   !  fixée à 122396 Mo et on occupe déjà 1 Mo.                                !
   !  La dernière opération de libération mémoire a permis de récupérer 0 Mo.  !
   !---------------------------------------------------------------------------!

or

   !---------------------------------------------------------------------------!
   ! <EXCEPTION> <JEVEUX_62>                                                   !
   !                                                                           !
   !  Erreur lors de l'allocation dynamique. Il n'a pas été possible d'allouer !
   !  une zone mémoire de longueur 292968 Mo, on dépasse la limite maximum     !
   !  fixée à 122396 Mo et on occupe déjà 97658 Mo.                            !
   !  La dernière opération de libération mémoire a permis de récupérer 0 Mo.  !
   !---------------------------------------------------------------------------!

If you increase memjeveux beyond the available memory you then get another error:

<INFO> Parameters : memory 307200 MB - time limit 18000000 s

<E>_INCORRECT_PARA Requested memory (307200.0 MB) is higher than the limit (128745 MB)

Finally the only cure was to move to a node with 256 Gb of memory, max_base was effectively automatically increased in my case.

It seems that you have 64 Gb, you probably need more.

Best,
Ect

PS: don't waste time on memjob and memory_limit parameters, it looks like they're only used for queuing systems, that's memjeveux which is passed to the aster runtime.