Load combination and analysis results extraction for steel i girder design workflow consists of multiple modular library components. These library objects are;
...
Unfactored analysis combination (OBPAnalysisCase)
...
The object is created to define unfactored load case combinations/envelopes. With this object, staged construction/deconstruction and other cyclic/static load cases can be combined. This The object allows user to filter the case results based on the load type, envelope cases, extract incremental/cumulative results, combine cyclic loads to create most critical load effects.
...
The name of the core “Combination” object in the library component is added to the name of app instance of the library component in the results spreadsheet. The name of the core combination object is important for result extraction.
...
...
Limit States (OBPAASHTOLimitState)
...
This object is created to collect the load cases and their max/min load factors accordingly and collects the load modifiers of that limit state. Each instance is a definition of a limit state combination.(Strength/Service/Fatigue/Extreme Event etc.)
...
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 going to be used for result extraction.
...
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. Review library object for better understanding.
...
Results Extraction Object (OBPBase_FECompositeForceExtraction)
...
This library component is developed for OBP worfklow but is not a workflow item. The aim of this object is to extract the analysis results of limit states /- unfactored load cases /- combinations and/or envelopes. The developer must extends this object to input-mapping library objects of code check components.
...
The force() functions to be used while extracting the unfactored/factored analysis results and & the governing results are guarded based on the ComputeFor parameter. The reason behind this logic is to eliminate the unnecessary result extraction operations and to facilitate parallel processing by keeping the output names symmetrical.
...
Governing results also turns to overall critical results of each limit state as well as all limit states. Review library object for better understanding.
...
Load Combination Document Object (OBPDoc_LoadCombination)
Library Link : https://openbrim.org/app/?incubator=1&obj=objidzptu38zopf8086567x9fxod
This library component is developed for OBP worfklow but is not a workflow item. The aim of this object is to tabulate the analysis results systematically and to show transparently which factored result was calculated using which factors and unfactored results.
The Load Combination Document object do not calculate any of the results that are tabulated in the report. All the cases ,enumerations ,factors and results of each limit state combination is an input for the object. And the report tabulates the results only for 1 station or element. If there is a station list or element list, this object must be called in the “Repeat”.
The developer must extends this object to base (2nd layer) object and set the parameters accordingly. (See referencing guide objects ***). Then each DocSection or DocTable of this library component can be referred using “DocRef” in the document of base object.
...
How to use OBPBase_FECompositeForceExtraction & OBPDoc_LoadCombination
Base object representative : https://openbrim.org/app/?incubator=1&author=Harika_Inanc_&obj=objidjil10cnrlrdhm73dgq7me6
Input-mapping object representative : https://openbrim.org/app/?incubator=1&author=Harika_Inanc_&obj=objid4wjpvtluomdfacm7244sqj
These objects are representing the relationship between OBPBase_FECompositeForceExtraction in map object & OBPDoc_LoadCombination in base object. This example shows how to set critical and concurrent for Fx result parameters for 1 station. The main idea is that force extraction object outputs are based on station list but the documentation inputs are based on one station only.