Bug affecting 971 R3.2: tsay on 2008-08-23 at 09:08:19 Revision 47195 Fixed missing all ascii file for any restart run. _______________________________________________________________________ http://ftp.lstc.com/anonymous/outgoing/jday/restart.pdf addresses restarts in LS-DYNA. Simple changes can be accomodated as a "small restart" in which case an input deck with just a few lines can be used, e.g., *keyword *control_termination 0.1 <<< new termination time *database_binary_d3plot 1e-4 <<< new output interval *control_timestep , 0.6 <<< new time step scale factor *end See the *RESTART section of the User's Manual for the commands (excluding *stress_initialization) that can be used for a small restart. If more complicated changes are necessary in the restart, a "full deck restart" could be used. In this case, the input deck would be basically the original input deck with the changes included AND a *stress_initialization command added. Assuming you're running a non-MPP LS-DYNA executable, either type of restart can be launched from a command prompt as follows... ls971 i=restart_input_filename r=d3dump_filename On Windows-based PCs, you have the option of launching the job in the above manner (from a DOS window) or via the LS-DYNA Manager. Using the Manager, select Solvers > Restart LS-DYNA analysis from the top menu bar and then enter the filenames in the I= and R= boxes. The output frequency for d3dump or runrsf should be given as an integer number representing number of time steps. It is not a time value. Runrsf is just like d3dump except that previous runrsf file(s) can be overwritten by newer runrsf files. The number of runrsf files retained is controlled by the parameter NR in *database_binary_runrsf. If NR is greater than 1, the runrsf files are written in cyclical fashion. For example if CYCL=1000 and NR=3, runrsf01, runrsf02, and runrsf03 are written after the 1000th, 2000th, 3000th time steps, resp. After the 4000th time step, runrsf01 is overwritten; after the 5000th time step, runrsf02 is overwritten, and so on. d3dumpxx files will accumulate where xx is incremented by 1 each write interval. Note regarding ASCII output data from a restart: Data is APPENDED to ASCII files, e.g., glstat, elout Example: http://ftp.lstc.com/anonymous/outgoing/jday/overwrite_ascii_files_in_restart.k followed by res_overwrite_ascii_files_in_restart.k (restarting from runrsf)