Besides, I wrote a batch file to be called in subroutine UMAT in order to run the restart work. Because I know that subroutines need to be specified again when submitting a restart job since they are not stored as part of restart information. So I'm not sure if there is something wrong in my input file. When we start the "restart computation" by using the R_re_0010.inp, the errors come out. The sta file of RVE's initial and 1st increment analysis's content is as follows:Ībaqus/Standard 6.13-1 DATE 2 TIME 00:08:11 The attachment is the message file of the macro analysis, and the sta file of macro analysis's content is as follows:Ībaqus/Standard 6.13-1 DATE 2 TIME 00:11:50 RE: abaqus restart problem Mustaine3 (Mechanical) 23 Mar 15 11:28 So, is there anyone can help me get rid of this problem? It's a little urgent to me, many thanks! *Substructure Generate,Type=Z1,Library=R_re_0010,Overwrite Restart RVE's input file(name is R_re_0010.inp, used in Nth increment(N>1) of "STEP: apply") *Substructure Matrix Output,Stiffness=YES, *Substructure Generate,Type=Z1,Library=R_0010,Overwrite *Step, name=SubstructureGeneration, nlgeom=YES ** Name: BC-5 Type: Displacement/Rotation ** Name: Translation stop corner_node_1 Type: Displacement/Rotation *Solid Section, elset=part-c-1_PickedSet2, material=Material-1 *Elset, elset=part-c-1_PickedSet2, generate *Nset, nset=part-c-1_PickedSet2, generate *Preprint, echo=NO, model=NO, history=NO, contact=NO Original RVE's input file(name is R_0010.inp, used in initial step and 1st increment of "STEP: apply") So why there is a sentence "***ERROR: USER SUBROUTINE DISP IS MISSING" in the restart message file? where is the problem coming from? Is there anything wrong with my input file? So now I'll list the original RVE's input file and RVE's restart input file. This is so strange! Because you can see the RVE's initial job's message file, everything is good: ***ERROR: USER SUBROUTINE DISP IS MISSING So I check the RVE's restart job's message file, it says: ***ERROR: TOO MANY ATTEMPTS MADE FOR THIS INCREMENTīecause when RVE's analysis comes to increment n (n>1), the RVE's restart job will begin. ***NOTE: THE SOLUTION APPEARS TO BE DIVERGING. the macro input model's message file says: However, when the next "real" loading step comes to increment 2, the whole running process has been abort due to the errors. When abaqus running the RVE's initial step which has the identity deformation gradient loaded, everything goes fine. At first, I met a small problem- overwrite the old files(y/n)?-which has been solved by adding a "abaqus_v6.env" file whose content is as follows in the abaqus working direction:īut another bigger problem has come. I've been facing a very strange problem now when I'm using abaqus to finish RVE multiscaling simulation: so far, what I've done is successfully linking fortran and abaqus to run the whole calculation.
0 kommentar(er)
