In a time history analysis, the pulse duration is <em>not</em> the same as the load duration. The pulse duration is the last time value specified in the pulse table. The load duration is specified on the Control Parameters Dialog, and is the length of time the analysis runs. For realistic results, the load duration should be greater than the pulse duration.

Once you take your pulse back to zero, you do not need to extend it (at zero magnitude) to the load duration time. CAESAR II will assume this for you. So, in your "item 2" above, for option 1, CAESAR II will assume a pulse magnitude of 1500 from 100 milliseconds through the load duration. For option 2, CAESAR II will use a pulse magnitude of 0 from 101 milliseconds through the load duration. Your last entry "1000 0" is not necessary.

A <font color="#0000ff"><em>really excellent</em></font> article on setting up time history input can be found in the June 1994 issue of our <em>Mechanical Engineering News</em>, beginning on page 8. If you don't have this newsletter, you can view it from this web site at: . I highly recommend this article.

Probably the most difficult dynamic analysis to attempt with CAESAR II is a slug analysis. The difficulty is in determining (actually guessing) the slug size and corresponding force. Since you really don't know whether the slug encompasses the entire cross section, or how long it is, the best thing to do is assume a small slug and a large slug. This way, you envelope that actual slug and the true response of the system.

Richard Ay (COADE, Inc.)

[This message has been edited by rich_ay (edited May 05, 2000).]
Richard Ay