Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
{live-template:Test Problem}

{{Test Problem
| name = Saving section cuts in moving load analysis |
| description = Illustration of the option to save section cuts in moving load analysis |
| keyword = section cut; moving load |
| program = SAP2000 |
| version = V14.1.0 |
| status = in progress |
| type = test problem |
| id = ok/section cut 3 - moving load analysis}} |

h1. Model Description

A model of a 2-span continuous girder is setup as shown in the figure below. Each span is 10m long and the girder has a solid cross-section of 0.1m wide and 0.6m deep. The structure is modeled three times: using solid elements, shell elements, and frame elements. It is subjected to unit moving load that travels across the entire structure. Section cuts are defined at the midspan of the second span for all three types of models (solid, shell and area). [Influence-based moving load analysis|kb:Influence-based moving load analysis] with and without saving section cut forces is run to evaluate the section cut forces.

!Saving_section_cuts_in_moving_load_analysis_-_model_overview.png!

h1. Discussion of Results

In order to obtain section cut forces for solid and link elements, you must check the option to save section cuts on the "Moving Load Case Results Saved" form. This may currently (as of V14.1.0) somewhat increase the analysis time, but the analysis speed will be improved under Incident 19192:

* When saving section cuts for moving load analysis analysis is requested, then the section cuts (defined prior to the analysis as well as the section cuts defined or drawn after the analysis) yield the correct values.

* When saving section cuts for moving load analysis analysis is NOT requested, section cuts for solid and link elements will produce zero results, but section cuts for frame and shell elements will produce correct results.

h1. Attachments

* [SAP2000 V14.1.0 model|^SAP2000 V14.1.0 model.zip] (Zipped SDB file, 0.36MB)