STY-File and User Variables

Altair Forum User

Hello,

I want to make 2 consecutive simulations :

1 traction, stop it, get back the result of this first simulation

1 bending on the result of the first simulation

So, as it was wrote on the help, I used STY-File

 

The problem is that I use User’s Material Law and I want to initialize the variable USER1 of the second simulation by the final variable USER1 of the first simulation.

To do that, I tried to put '/OUTP/BRIC/USER1' in the 'Runname_0001.rad' of the first simulation.

But, when I put the' Runname_run#.sty' in the '/INISTA' of 'Runname_0000.rad' of the second simulation, that only initialize the node coordinates and not USER1 as I would want. I have USER1 = 0 and not USER1 got at the end of the first simulation.

Then, on the help, I saw that If I used /INISTA with User’s Material Law, users variables should be initialized with the '/OUTP/SOLID/USERS/FULL' option in the STY-File.

So, I put '/OUTP/SOLID/USERS/FULL' in the 'Runname_0001.rad' of the first simulation. But, when I launch the first simulation, I get the error messages :

In the 'slurm.out' file :

' ERROR TERMINATION
[cli_0]: aborting job:
application called MPI_Abort(MPI_COMM_WORLD, 2) - process 0
rank 0 in job 1  eoscomp605_40248   caused collective abort of all ranks
  exit status of rank 0: killed by signal 9 '

In the 'Runname_0001.out' file :

' ABNORMAL END                                           

Segmentation Violation '

 

Can I help me on this problem, because I don't understand how to correct this error ?

 

Than you

Altair Forum User

Hi Rogani,

Can you share the files to the dropbox (Runname_0000.rad, Runname_0001.rad, .0000.out and .0001.out files)?

Altair Forum User

Hi Johson,

 

Thanks for your answer.

I shared you the files to the dropbox.

Altair Forum User

Hi Rogani,

Please share the starter out file also (_0000.out)?

Altair Forum User

It's done

Altair Forum User

Hi Rogani,

Can you try the same in the latest version of HyperWorks?. That is, HW14.

The version you are using is 10, which is very old. Please try the same in the latest build..