parresu,,moreload! For further load step, we want to apply table TEMTBL
! as body force. NOTE: table TEMTBL is not in *.RDB. Therefore,
! we have to use PARRESU command. APDL file "moreload" is
! saved earlier.
*status! List all the ADPL information available at this point
bf,all,TEMP,%temtbl%! Apply temperature table load TEMTBL
bflist
time,4! Solve up to TIME = 4.0 because the load step ENDSTEP only
! carries up to TIME = 3.5
solve
fini
/post1
set,last
prdis
prrsol
finiThe following example input demonstrat es a restart after changing boundary conditions.
Example 5.4: Restarting after Changing Boundary Conditions
/prep7
et,1,21
r,1,1,1,1,1,1,1
n,1
e,1
fini
/solu
antyp,trans
timint,off
time,.1
nsub,2
kbc,0
d,1,ux,100! to apply initial velocity (IC command is preferred)
solvetimint,on
ddele,1,ux! this requires special handling by multi-frame restart
! if a reaction force exists at this dof, replace it with an equal
! force using the endstop option
time,.2
nsub,5
rescontrol,define,all,1! request possible restart from any substep
outres,nsol,1
solve
fini
/solu
antyp,,restart,2,3! this command resumes the .rdb database created at the start of solution
! (restart from substep 3)
d,1,ux,100! re-specify boundary condition deleted during solution
solve
fini/post26
nsol,2,1,ux
prvar,2! results show constant velocity through restart
finishNoteIf you are using the Solution Controls dialog box to do a static or full transient analysis, you
can specify basic multiframe restart options on the dialog's Sol'n Options tab. These options
include the maximum number of restart files that you want to write for a load step, as wellRelease 15.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential informationRestarting an Analysis