Progress Tab Best Practice
1.In terms of running analyses, only perform full FE analysis runs if necessary. Where you only need to generate post-postprocessing then select the corresponding run post-processing only command as full re-runs are inefficient and can take considerable time if dynamic stages are included. Also, before running an analysis consider optimising the number of installation stages, using the Select Stages function on the Properties tab, as often not all stages need to be included in an analysis.
2.When monitoring the progress of a dynamic analysis it worth noting that the Estimate of remaining CPU time only becomes accurate after the ramp time.
3.When an analysis has completed always check for errors and warnings. Errors are always important, in particular for convergence/indeterminacy issues, whereas some warnings can be ignored with the main exception being warnings about the criteria analysis being unable to achieve the specified criteria; see best practice on Criteria tab for details on how to handle this. Error/warning checking can be done on an individual stage basis using the Stage Section Progress drop down list/area.
4.If convergence/indeterminacy problems occur then identify the corresponding problematic step in the analysis sequence using the Stage Section Progress area. Note that there are various steps in a static installation stage and each of them are outlined in Technical Note 3. When a particular step fails to converge then a unique tip is provided on the Progress tab which outlines what the possible reasons/remedies are for the convergence issue. You should try to follow the tips as much as possible. It is also worth remembering that most convergence issues are a result of not following best practice and so this document should prove a useful reference for debugging and overcoming convergence issues.
5.Automation for running large numbers of different Analysis components can be achieved using the Analysis Queue and Batch Analysis component capabilities. These help maximise the productivity of your machine by running analyses in parallel across the available cores and also running new analyses immediately after existing ones have completed. All of this is useful for overnight or weekend runs, but it is important to check that the Concurrent Analysis Runs setting under Options (on Home tab of ribbon control) is less than or equal to the number of cores on your machine and/or the number cores allowed with your license (this is 8 on a standard license).