When a steel material is chosen for the frame section, the generated linked bridge model will treat the alignment of the top and bottom flanges similarly to how they are treated for st[r]
(1)SAP2000 Version 14.1.0 Release Notes
© Copyright Computers and Structures, Inc., 2009 Release Date: 2009-07-29
This file lists all changes made to the SAP2000 since the previous version Most changes not affect most users. Incidents marked with an asterisk (*) in the first column of the tables below are more significant and are included in the ReadMe file
Changes from V14.0.0 (Released 2009-05-05) User Interface and Display
Enhancements Implemented * Incident Description
* 17537 The Rotate 3D View command has been enhanced to rotate about the center coordinate of the current view, accounting for zoom and pan Previously the rotation was always about the center of the structure for perspective views, and about the origin for orthographic views
Modeling
Enhancements Implemented * Incident Description
14341 The IBC2006 Auto Seismic Load case has been updated as per Supplement # to ASCE 7-05 where the minimum Cs value is revised
16297 17406
The API 4F implementation has been enhanced to include a Shielding Factor The factor applies to the overall wind load on the structure, but does not apply to the load on the member itself Only members that are transversely supported in both directions at both ends will be shielded, otherwise they will transfer the full (unshielded) wind load to the rest of the structure
18441 The Norwegian national parameters have been implemented for the EC8-2004 auto seismic load and response spectrum functions In addition, air density has been added as a new parameter to the EC1-2005 auto wind load for use with different countries
* 18152 Automated wind lateral loading for Australia and New Zealand has been implemented according to the AS/NZS 1170.2 2002 code
18385 The Chinese auto lateral wind load has been updated to account for reduction in wind loads for the special case of a uniformly tapered building
18531 A new section-property database file, ChineseGB08.pro, has been added This file contains hot-rolled sections for code “GB/T 706-2008”, hot-hot-rolled and cut-T sections for code “GB/T 11263-2005”, welded steel H sections for code “YB 3301-11263-2005”, and high-frequency welded light-gauge H steel sections for code “JG/T 137-2007” The previous file, Chinese.pro, is still available
Section Designer
Enhancements Implemented * Incident Description
(2)* Incident Description
18338 The calculation of Caltrans frame hinges has been made more efficient by not repeating the calculations for hinges assigned to identical cross sections This affects the time it takes to assign hinges and to create the analysis model
Bridge Modeler
Enhancements Implemented * Incident Description
18166 The creation of frame objects to model bridge bent columns has been changed as follows: (1) The frame objects are now equally divided over the clear height from the bottom of the column to the bottom of the cap beam, and the top frame object is extended with an end offset to the bent cap centerline Previously they were divided equally over the total height, except for short columns This change should have no effect on the static behavior of the model, and very little or no effect on the dynamical response (2) Columns shorter than the half depth of the bent cap are now set equal in height to the half depth of the bent cap Previously they were discarded
* 18523 The U-girder frame section can now be used to model steel tubs in the Bridge Modeler When a steel material is chosen for the frame section, the generated linked bridge model will treat the alignment of the top and bottom flanges similarly to how they are treated for steel I-girders: The haunch distance is measured to the bottom of the top steel flange, rather than to the top of the top flange as is the case for concrete girders One or two bearings will be created for each steel U-girder depending on the definition of the frame section A single bearing is used for concrete sections Significant further specializations for steel U-girders are under current development 18524 Constraints have been added to the linked model that is generated for steel-girder diaphragms used
in conjunction with area (shell) models of steel I-girder bridge deck sections The purpose of the additional constraint is to assure that the diaphragm provides the expected stability to the lower flange of the longitudinal I-girders
Analysis
Enhancements Implemented * Incident Description
14718 Additional hysteresis models are now available for the single degree-of-freedom frame hinges with uncoupled P, V2, V3, T, M2 and M3 behavior The choices include: Isotropic, Kinematic, Takeda, and Pivot types of behavior The Isotropic model gives the hysteresis behavior that was provided in the previous versions of SAP2000, and this is still the default The three new types of hysteresis are identical to those offered for the multilinear plastic link element Hysteresis primarily affects time-history results with load reversal, although small changes in monotonic pushover behavior may also be seen between the original Isotropic model and the new hysteresis models The Isotropic model is optimized for pushover analysis, and is recommended if time-history analysis is not important The new models add a very small amount of elastic flexibility the frame element, which the Isotropic hinge does not
Frame Design
Enhancements Implemented * Incident Description
* 17972 “AASHTO LRFD 1997” concrete frame design, which had been removed with Version 12, has now been reinstated after updating it to “AASHTO LRFD 2007”
* 18008 Steel frame design has been added for “NORSOK N-004”, including punching checks The design of non-tubular sections is in accordance with Eurocode 3-2005 with the Norwegian National Annex The SAP2000 Offshore add-on license is required to use this feature
(3)* Incident Description
18504 For steel frame design using codes “API RP2A-LRDF 97” and “API RP2A-WSD2000”, the design overwrite previously called “Internal Pressure” has been changed to “Additional External Pressure”, and the sign of the value changed accordingly A positive value for Additional External Pressure will cause compressive hoop stress Negative values are permitted, which indicate internal pressure Whether it is positive or negative, this overwrite value acts in addition to the external pressure produced by any wave loading included in the design load combinations When old data files are opened or imported, this overwrite value will be set to zero and a warning given that the value must be re-assigned Any external programs using the OpenAPI functions to set or get this value must be modified to account for the change in sign of this value
Bridge Design
Enhancements Implemented * Incident Description
* 17922 Detailed design checking has been implemented for multi-cell prestressed concrete box-girder bridge superstructures according to the “AASHTO LRFD 2007” code Separate design checks are available for stress, flexural capacity, and shear capacity using MCFT (modified compression field theory) Live-load distribution factors can be automatically calculated using code formulae, specified by the user, or determined from detailed 3-D live-load analysis Results are reported for each girder, and include plots of stress, moment demand and capacity, shear demand and capacity, and shear-rebar requirements Detailed tables showing all results and intermediate values are available for display, printing, and export to Excel or Access These new checks are in addition to the whole-section checks that were previously released
17952 Bridge seismic design has been enhanced to provide more information when the design fails due to inadequate axial capacity of the columns Previously the reason for the failure was not always obvious
Database Tables
Enhancements Implemented * Incident Description
* 18280 The “Floating Point Number Format” and “Units” settings have both been removed from the database table format file Now all displayed tables, printed tables, and tables in formatted reports will use the corresponding settings that are controlled using the menu command Options > Set Program Default Display Units This makes it easier to format the tables and provides more consistent formatting
Application Programming Interface (API)
Enhancements Implemented * Incident Description
17944 The following API functions were added which supersede older functions in order to implement new features in this version See file “SAP2000_API_Documentation.chm” in the SAP2000 installation folder for more information:
• SapObject.SapModel.LoadPatterns.AutoWind.GetAPI4F2008_1 • SapObject.SapModel.LoadPatterns.AutoWind.GetChinese2002_1 • SapObject.SapModel.LoadPatterns.AutoWind.GetEurocode12005_1 • SapObject.SapModel.LoadPatterns.AutoSeismic.GetEurocode82004_1 • SapObject.SapModel.Func.FuncRS.GetEurocode82004_1
(4)External Import/Export
Enhancements Implemented * Incident Description
* 18155 The capability to export a model to SAFE V12 has been implemented A single global-Z elevation is chosen, and all objects connected to joints within a tolerance of that elevation are exported Linear static and response-spectrum load cases and associated data are also exported
User Interface and Display
Incidents Resolved * Incident Description
17172 An incident was resolved in which the option “Glue to Grid Lines” worked when accessed using the Define > Coordinate Systems/Grid menu command, but did not work accessed by right-clicking with the mouse on a grid line
* 18157 An Incident was resolved in which the license was sometimes lost during creation of the analysis model for certain types of models This only affected network licenses
Modeling
Incidents Resolved * Incident Description
17272 An Incident was resolved in which analysis would fail if bridge lane loads were applied to a frame, shell, or other object when its property was set to "None." This has been changed so that bridge lane loads applied to an object with its property set to "None" will be ignored
17657 An Incident was resolved in which an exception (runtime error) could be generated in rare cases when calculating the apparent period for certain models having wave loading
17927 An Incident was resolved for the New Zealand response-spectrum function and auto-generated static lateral loads in which the near-fault factor, N(T,D), was being applied uniformly across all periods rather than non-uniformly as a function of period The specification has been changed from the near-fault factor to the near-fault distance
* 18376 An Incident was resolved in which some of the “Uniform to Frame” loading was lost when assigned to an area object that could not be meshed by cookie-cutting into 3- and 4-noded areas the using existing frame objects Now a warning message is given to the user if this problem is detected while assigning the load or while creating the analysis model If the warning is issued when creating the analysis model, the user is given the option of either converting the load to a uniform area load, in which case no load is lost, or canceling the creation of the analysis-model
Section Designer
Incidents Resolved * Incident Description
17325 18057
An Incident was resolved for Section Designer in which the Caltrans idealized moment-curvature curve could not be plotted for sections that contained only tendons and no rebar This has been resolved so that rebar and tendons, when present, are checked for failure against their respective ultimate strains
18090 An Incident was resolved for Section Designer in which the calculation for the plastic neutral axis could give incorrect results for section shapes having sudden changes in the section dimensions near the plastic axis
(5)Bridge Modeler
Incidents Resolved * Incident Description
16543 18127
An Incident was resolved in which bridge girders were not always being included when assigned to a staged-construction group for a bridge object The problem only occurred in Steel girder, precast-I and precast-U bridges modeled as area objects with the girders modeled as line objects The girders were not included in the group if the specified station range to include in the group did not include station zero
17912 An Incident was resolved in which the torsional constant J calculated for bridge deck sections, precast-U sections, and precast-I sections could differ from the correct value by 5% or more, especially for the precast-U girder This has been resolved by internally using a more refined mesh to calculate the torsional constant
17954 An Incident was resolved in the Bridge Deck Section form in which entering a formula in certain cells, and then clicking in a another cell, would enter the calculated value in the second or both cells rather than in just the first cell
17977 An Incident was resolved in which an exception (runtime error) was sometimes generated when right-clicking on a solid element joint with springs created from the Bridge Modeler
18021 An Incident was resolved in which it was possible to delete frame sections that were being used to define bridge deck sections, resulting in an error when accessing the definition of the bridge section 18102
18115
An Incident was resolved in which, under rare circumstances, an out of memory error message was generated when creating the analysis model for a bridge model with tendons Memory use has been optimized
18233 An Incident was resolved in which the connection of abutment bearings to solid models of a bridge superstructure sometimes formed an unstable mechanism for certain geometric configurations Now additional connections are made to assure stability
18392 An Incident was resolved in which an exception (runtime error) was sometimes generated when adding bents to a bridge object to which deck width parametric variations had been assigned 18415 An Incident was resolved for the Bridge Modeler in which the area (shell) objects representing the
bottom flange of built-up I girders were not being generated This did not affect spine models of the superstructure, or area models in which the girders were represented as frames
18468 An Incident was resolved in which the linked SAP2000 model could not be created from a bridge object in certain rare cases where curve or skew in the bridge created two or more discretization points that were too close together, failing a tolerance check Now the more significant
discretization point is used
18470 An Incident was resolved for the bridge modeler in which nonprismatic steel girders did not properly change cross sectional shape at double-bearing (discontinuous) bents
Analysis
Incidents Resolved * Incident Description * 15873
15953 17970 18058
An Incident was resolved for bridge moving-load cases in which the vehicle axle loads were not being restricted to remain within the lane-edge distances specified for the vehicle, but instead were allowed to move to the edge of the lane The effect of this was conservative
15878 An Incident was resolved for bridge moving-load cases in which vehicles were not always restricted to remain fully within the length of the lane when this option was specified for the vehicle The effect of this was conservative
17967 An Incident was resolved in which the advanced solver would, in rare cases, generate an error when solving a model with internal instabilities and could not complete the analysis
17978 18217
(6)BrIM – Bridge Information Modeler
Incidents Resolved * Incident Description
15044 An Incident was resolved in which the horizontal tendon profile generated for a curved bridge was obviously not correct for a particular configuration
15086 An Incident was resolved in which values entered into one cell were sometimes transferred to a different cell on the BrIM Deck Section forms
15264 An Incident was resolved in which a runtime error could be generated when the tendon discretization was very small
Analysis
Incidents Resolved * Incident Description
12678 An Incident was resolved in which the creation of the analysis model for large structures with automatic meshing and many load patterns could take much longer than in Version 10
Results Display and Output
Incidents Resolved * Incident Description
10533 An Incident was resolved in which the unit conversion was not correct for displaying stress arrows for shells and solids
12472 An Incident was resolved in which a runtime error sometimes occurred when Display > Show Hinge Results > Show Individual Fiber Data was showing the backbone curve
13394 An Incident was resolved in which relative displacements were shown when the absolute
displacements resulting from rotational ground acceleration were requested Absolute displacements due to rotational ground acceleration are now available for direct-integration time-history analysis For modal time-history analysis, only relative displacements are available
Design
Incidents Resolved * Incident Description
12426 Minor updates were made to the Design manuals
13129 An Incident was resolved in the computation of Acp and Aoh for ACI design codes where the program was imposing the flange limit for L-shaped section while user has explicitly defined the shape as T-Shaped beam
13746 An Incident was resolved in which the design of auto-select sections for the Indian steel frame design code did not always work
13806 An Incident was resolved in which the computed time period was not enforcing the limiting period as per cl 4.1.8.11-3(d) of NBCC 2005 auto seismic loads
* 13867 An Incident was resolved in which the flexural capacity of box and rectangular sections was not correct for the Canadian steel frame design code “CAN/CSA-S16-01”
13972 An Incident was resolved in which the classification of angles/double-angles for steel frame design code “BS5950 2000” was overly strict, resulting in a Class section being Classified as Class 14093 Same as 13746
* 14469 An Incident was resolved in which the unit conversion for calculating the PMM ratios for code “API RP 2A-LRFD 97” was incorrect
(7)* Incident Description
15297 The menu command Design > Lateral Bracing was changed to be enabled only when frame objects are selected, and to only apply to straight frame objects, not cables, tendons, or curved frames 15411 An Incident was resolved in which design is being performed for Section Designer sections even if
the no design option is chosen
Database Tables
Incidents Resolved * Incident Description
14241 An Incident was resolved in which the database tables for the assignment of bridge variations to the Precast U, Precast I, and Advanced Concrete Box deck sections were missing
15181 An Incident was resolved in which the strain values for user-defined material stress-strain curves was incorrectly exported to tables
15231 An Incident was resolved in which the Excel sheet name for the ACI 318-05 concrete design summary table had illegal characters
15259 An Incident was resolved in which database tables for shell stresses not print when repeated columns take up the whole page width This was detected by the program and the tables did not pint Fixed by reducing the width of the repeated columns
External Import/Export
Incidents Resolved * Incident Description
12452 An Incident was resolved in which certain Dimension and Tolerance Preference values were being set to zero when importing a DXF file in metric units
12677 An Incident was resolved in which the UNIT command is not recognized within the second level load commands, JOINT LOAD, MEMBER LOAD, and FLOOR LOAD for importing STAAD files
13215 An Incident was resolved in which a runtime error occurred when importing a STRUDL model with more than 10,000 supports
13646 An Incident was resolved in which a runtime error occurred when importing a STAAD model with prismatic section properties defined with some parameter values equal to zero
15271 An Incident was resolved in which DXF import units were not being utilized
Miscellaneous
* Incident Description
12223 Minor cosmetic changes were made throughout the program 12564 Tips of the Day have been updated
14129 The splash screen now appears before rather than after the license is found
14133 Warning messages that are shown on the screen when opening models from previous versions are stored in the project log under menu command File > Project Log
14169 Version number changed to 12.0.0
14795 The analysis $OG file has been combined with the LOG file, and they are saved in a single file with extension LOG
14960 The SAP2000 Getting Started, Basic Analysis Reference, and Introductory Tutorial manuals have been updated