If you think of the Classic Piping Input as a book, the input dialogs/sections are like multiple pages, in which each page relates to an element and all the pages (all the elements) comprise the book. The sequence of the pages (input dialogs/sections) in Classic Piping Input determine if the book is sophisticated or basic in structure.

Share this newsletter & let others get their own copy by clicking here to subscribe!

Every once in a while, a CAESAR II user wishes to model friction on a spring can. This illustration shows one way of doing it.

Here, the can slides at the base (node 21) rather than between pipe and spring, but the response would be similar either way. The CNode/Restraint combinations are the trick here as these “relative” restraints relate the horizontal movement of node 20 to the friction point at node 21.

One
important rule of thumb when building a model is to construct the model
by paragraphs and chapters, which can be easily recognized line by
line. In other words, the first chapter would be main header, succeeding
to all the branches, and finally the dummy supports (trunnion
supports), and so on.

Another best practice when entering piping input details is to work in a traversable or sequential way. Going back to the book analogy, in the case of changes needed for revisions, you may need a virtual piping model bookmark to easily get back to elements and sections of the model you need to change.

Try using the Line Numbers feature, which lets you conveniently search and filter to display only what you want to change. Viewing by line numbers, you can also avoid unfavorable input errors in a data sequence, such as adding a bend without the entering or exiting elements.

Using these built-in features of CAESAR II, you are on your way towards quicker piping input and optimized modeling and analysis.