{"id":360782,"date":"2024-04-05T18:22:25","date_gmt":"2024-04-05T18:22:25","guid":{"rendered":"\/forum\/forums\/reply\/360782\/"},"modified":"2024-04-05T18:22:25","modified_gmt":"2024-04-05T18:22:25","slug":"360782","status":"publish","type":"reply","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/360782\/","title":{"rendered":"Reply To: LS Dyna full deck restart"},"content":{"rendered":"

<p>Hello Ajay,<\/p><p>Do you have the original input file (first_Impact.k) and the restart file (2nd impact; restart.k) in the same folder? You should have results of the first impact (include dynamic relaxation state at time=0) in the d3plot. When you restart, LS-DYNA will continue the d3plot file series as d3plotaa and keep adding results. It should look like this:<\/p><p><\/p><p>So, when you open the d3plot file, you will get results from the first and second impacts.<\/p><p>I recommend doing some tests with a simple cube model. This way you will be able to run quickly and make changes as needed.<\/p><p>Here is the full restart procedure from our knowledge database:<\/p><p>”Changes of a general nature can be made in a full restart, including addition of parts, loads, and contacts.  <\/p><p>\uf06e Sample execution line  <\/p><p>SMP:  lsdyna i=fulldeck.k  r=d3dump01<\/p><p>MPP:  lsdyna i=fulldeck.k  n=d3full01<\/p><p>where fulldeck.k is a complete keyword input deck for the model you want to use moving forward in time.  <\/p><p>Copyright © 2003-2012 by LIVERMORE  SOFTWARE  TECHNOLOGY  CORPORATION                        <\/p><p>Full Restart (cont’d)<\/p><p>\uf06e Guidelines for fulldeck.k <\/p><p>\uf0a7 Include keyword input for anything that is to be retained from the original run… (*PART, *SECTION, *MAT, *CONTACT, *LOAD, etc.).  Normally, you would just copy the original input deck and strip out anything you don’t want to retain.  <\/p><p>\uf0a7 Also include keyword input for new parts, materials, contacts, loads, etc.<\/p><p>\uf0a7 Include all relevant *DATABASE and *CONTROL commands.<\/p><p>\uf0a7 Include the command *STRESS_INITIALIZATION.<\/p><p>\uf06e Signals to LS-DYNA this is a full retart and that stress, strain, displacement, etc. are to be initialized for specified, pre-existing parts.<\/p><p>\uf0a7 Do not use *INITIAL_VELOCITY for nodes carried over from previous run.  Use *CHANGE_VELOCITY_option  to modify velocities of such nodes.<\/p><p>\uf0a7 Preexisting contacts that are to be retained should include the _ID option so that the contact ID numbers in the original input deck match those in the full restart input deck. <\/p><p>\uf06e Regarding output from a full restart:<\/p><p>\uf0a7 Binary output (d3plot) from a full restart will blend seamlessly with previous output.  <\/p><p>\uf0a7 ASCII output (glstat, matsum, etc.) from a full restart appends to pre-existing ASCII output only if *CONTROL_OUTPUT with IASCII=1 in included in the full restart deck.<\/p><p>\uf06e Without this command, ASCII output from full restart overwrites pre-existing ASCII output.<\/p><p>\uf06e Lastly, there may be a suitable alternative to using a full restart.  <\/p><p>\uf0a7 For example, a “dynain” file can be written at the conclusion of the original run by including the command *INTERFACE_SPRINGBACK_LSDYNA in the original input deck.   This dynain file can be included in a subsequent keyword input deck to initialize nodal coordinates and element history variables (stress, strain, etc). “<\/p><p>https:\/\/ftp.lstc.com\/anonymous\/outgoing\/support\/FAQ_docs\/restart.pdf<\/p><p>https:\/\/ftp.lstc.com\/anonymous\/outgoing\/support\/FAQ\/restart<\/p><p> <\/p><p>Let me know how it goes.<\/p><p>Reno.<\/p><\/p>\n","protected":false},"template":"","class_list":["post-360782","reply","type-reply","status-publish","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t