Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 16 Next »

This object serves multiple purposes, including defining unfactored result cases for AASHTO-based combinations, filtering staged construction results by load type, extracting incremental/cumulative results from staged construction analysis, and combining transient loads such as wind loads, live loads to identify the most critical load effects.

The Result Extraction Cases generated through this process will be utilized in the "Limit States" section.


When selecting result cases from a Staged Construction Analysis, there are several options available to extract results :

Incremental[Yes/No]: If "no" is selected, the cumulative results from the selected stage will be extracted. If "yes" is selected, the incremental results from the selected stage will be extracted.

Filter By Load Type[None/Dead Load/Imposed Dead ….]: If the "Filter By Load Type" option is set to "None," the component will extract the incremental or cumulative results from the selected stage without filtering it according to load types. However, if it is set to "Dead Load," the component will extract only the incremental or cumulative dead load results and exclude other load types such as imposed dead or wearing surface results from the selected stage. This option filters the results according to the load type. It is crucial to ensure that the load types are correctly assigned to the stages for accurate results extraction.

Result Extraction

Construction Stage

Prior Construction Stage

Load Type

Incremental Result Extraction

Cumulative Result Extraction filter by Dead Load

Cumulative Result Extraction filter by Imposed Dead Load

Cumulative Result Extraction filter by Wind Load

SubstrConstStage

NULL

Dead

25

25

0

0

GirderStage

SubstrConstStage

Dead

30

55

0

0

SIPFormworkStage

GirderStage

Dead

12

67

0

0

Cast1PourStage

SIPFormworkStage

Dead

28

95

0

0

Cast2PourStage

Cast1PourStage

Dead

33

128

0

0

Cast3PourStage

Cast2PourStage

Dead

30

158

0

0

Cast123GainStiffStage

Cast3PourStage

Change

0

158

0

0

Cast4PourStage

Cast123GainStiffStage

Dead

29

187

0

0

Cast5PourStage

Cast4PourStage

Dead

31

218

0

0

Cast45GainStiffStage

Cast5PourStage

Change

0

218

0

0

FBarrierStage

Cast45GainStiffStage

Imposed Dead

18

218

18

0

FutureWearingStage

FBarrierStage

Wearing Surface

26

218

18

0

LLStage

FutureWearingStage

Live (Vehicular + Impact)

40

218

18

0

WSStage

FutureWearingStage

Wind on Structure

32

218

18

32

TUExpStage

FutureWearingStage

Temperature

18

218

18

0

TUContrStage

FutureWearingStage

Temperature

16

218

18

0

BRStage

FutureWearingStage

Braking

22

218

18

0

CentStage

FutureWearingStage

Centrifugal

10

218

18

0


Once results are extracted from a staged construction analysis using the incremental and filter by load type options, the envelope and extreme effect options can be used to specify how the results will be combined in a combination.

Envelope[Yes/No]: If the "Envelope" option is set to "Yes," the component will find the critical case from the cases specified in the "Cases and Factors" column. However, if only one result case is defined in this column, selecting "Yes" or "No" for the envelope will not affect the results. For example, when dealing with temperature loads, there are usually two cases to consider: expansion and contraction. The user has the option to add these cases to single result extraction case and choose the envelope as "Yes." Another scenario to take into account is the deck pouring sequence, which may consist of multiple stages. Some of these stages might have a maximum bending moment greater than the final stage. To consider those maximum values, the user can combine all deck pouring stages into a single result extraction case and select the envelope option as "Yes" to identify and utilize the critical one. You can observe both examples in the screenshot below.

If the "Envelope" option is set to "No," the linear result combinations will operate by summing the results of multiple cases specified in the "Cases and Factors" column. Factors can be applied to the cases to achieve a weighted linear combination, but it is recommended to increase the loads according to the factors defined in AASHTO under limit states part. These factors should only be used if any increase needs to be made to compute the unfactored loads, such as including splice and other steel girder attachments by increasing the dead load by 5 percent. However, if only one result case is defined in this column, selecting "Yes" or "No" for the envelope will not affect the results.

Extreme Effects(Transient Loads)[Yes/No]: Selecting this option will exclude the selected result case from the combination if its value in the enveloped column is positive for minimums or negative for maximums. It is recommended to select "No" for permanent loads(Dead, Wearing Surface…) and "Yes" for transient loads(Temperature, Wind on Structure, Wind on Live, Live Load, Braking, Centrifugal…). Choosing EE=Yes for permanent loads may lead to incorrect results since the result may be excluded from the maximum or minimum results.

Additional points to consider when defining result extraction cases for live loads(LL), braking loads(BR), centrifugal loads(CE), wind load on structure(WS), and wind load on live load(WL)

  • When the user employs influence surface-based definitions for live load (LL), braking (BR), and centrifugal (CE) loads, stages are used for influence surface coefficient calculations, but not for specific live load cases. Defining result extraction cases by selecting these stages will yield incorrect results, showing zero forces. So the user should use the cases defined under live load cases, as seen in the figure below, for result extraction purposes.

  • If the user employs WS - WL AASHTO for wind load on the structure and wind load on live load, there is no need to define additional result extraction cases. The library component automatically generates the result extraction cases by enveloping them for each limit state. Users can then navigate to the limit state section and assign these cases directly.

  • No labels