Page Comparison

...

Beware that the name of core combination object "Comb" is originated from OBPAnalysisCase object and is necessary for result extraction. Thus, if the name “Comb” changes, the CaseObjName parameter must be updated accordingly.

...

The object exports a list of [load case, load type enumeration, modified maximum factor, modified minimum factor, description of load type enumeration] for each load case input. Then, sorts these lists based on their load type enumeration. This sorted list 'SortedStateList' is to be used for result extraction.

Load Combination Table (OBPAASHTOLimitStateTable)

Library Link : https://openbrim.org/objid75uxbqmoluk9xqssjqiu7m.libobj?values=StrengthI_Input:null%7CStrengthII_Input:null%7CStrengthIII_Input:null%7CStrengthIV_Input:null%7CStrengthV_Input:null%7CExtremeEventI_Input:null%7CExtremeEventII_Input:null%7CServiceI_Input:null%7CServiceII_Input:null%7CServiceIII_Input:null%7CServiceIV_Input:null%7CFatigueI_LL_IM_CE_Input:null%7CFatigueII_LL_IM_CE_Input:null%7C

This library component is a workflow item and is developed for OBP workflow.

This object collects the OBPAASHTOLimitState as input for each limit state combination.

...

This object is created to collect the previously defined limit states. These limit state inputs are based on AASHTO. Two core combination objects (Max/Min) are created for each limit state input. Overall limit state envelopes are created for each strength-service-fatigue-extreme event limit states. Overall envelope is created using all the combination that are created in the object. The name of each core combination is exported as text for result extraction object.