AdSec API Release Notes
Version 2.0.0
Breaking Changes
- API now depends on OasysUnits package instead of UnitsNet package. This implies a namespace change is required from
UnitsNet
and Oasys.Units
to OasysUnits
[1574,1552]
- For C# users:
using UnitsNet
must be replaced by using OasysUnits
using UnitsNet.Units
must be replaced by using OasysUnits.Units
using Oasys.Units
must be replaced by using OasysUnits
- For Python users:
from UnitsNet import *
must be replaced by from OasysUnits import *
from UnitsNet.Units import *
must be replaced by from OasysUnits.Units import *
from Oasys.Units import *
must be replaced by from OasysUnits import *
Version 1.1.0
New features
- API section with standard materials can now be exported to .ads file [1245]
- Sections from .ads file can now be imported to API sections. [1246]
- Geometric properties like area, elastic modulus, radius of gyration etc can now be extracted from section profiles [1430]
- API now uses PythonNet from released version as a dependent package. i.e. users not required to download the development version of PythonNet to work with API [1281]
- AdSec API and GSA .NET API can now be used in the same session [1433]
Documentation improvements
- The documentation has been updated to include code samples and example snippets on .ads interoperability feature [1424, 1422]
- Python stubs now include missing information related to remarks [1435]
- The documentation has been updated to include code samples and example snippets on export section to image feature [1434]
- The documentation site search results have been improved [1431]
Bug fixes
- API no longer reports different load utilization values before and after flattening a section [1283]
- The issue of reinforcement single bars not being generated beyond certain bar count has now been fixed [1206]
- Updates have been made to the solver to fix moment capacity underestimation [1259, 1129]
- AdSec no longer experiences problems when trying to create sections that contain sub-components with Catalogue profiles [1272]
- Updates have been made to fix moment capacity calculations to the Australian Code for circular sections with perimeter reinforcement layout [1366]
Known issues
- API section with non-standard materials are not supported to export as .ads file. [1323]
- Section with Recto-Ellipse profiles are not supported for .ads import or export. [1450]
Version 1.0.2
New features
- OAA-244 AdSec can save an image of a section (svg, which can be converted to other format e.g. png)
- OAA-340 Concrete sections can now contain template reinforcement (top, bottom, side and perimeter bars) and links
- OAA-337 Concrete sections can now define the cover to reinforcement (uniform for all faces) defined
- OAA-390 Deformations can now return the resulting longitudinal strain at a given position
- OAA-246 The documentation website now splits class properties and methods into separate pages
- OAA-251 AdSec can flatten a section definition into its canonical form
- OAA-325 Installation instructions for users without administrator privilege are now documented
- OAA-341 Python Stubs now include documentation of exceptions
- OAA-369 The documentation now includes an example of creating a compound section
Bug fixes
- OAA-388 UnitsNet marshalling behaviour is now properly documented
- OAA-387 Oasys Units not returning abbreviations
- OAA-392 IPopovic material curves returns NaN when trying to get stress at strain = 0
Version 1.0.1
New features
- OAA-262 Tooltips for Python users now include help for properties.
- OAA-273 The API now supports .NET Framework 4.7.2 or later.
Breaking changes
- OAA-277 The RecordTime property on AdSec.IWarning has changed from a string to a System.DateType object
- OAA-302 Section analysis is now only performed when required (making it much faster if only carrying out strength analysis).
- OAA-305 Sections defined with perimeter profiles now analyse faster.
Bug fixes
- OAA-294 Exception cases are not documented.
- OAA-311 Crack width calculations not possible when using a custom concrete material.
- OAA-316 Unhandled error occurs if
null
is used where an object reference is expected.
- OAA-331 If the same solver object is used to analyse more than one section, it always returns solution for the first section.
- OAA-343 Serviceabilty check fails for the section with PD6687 concrete material.
Known issues
- OAA-259 Python tooltips: ‘See’ and ‘SeeAlso’ references are not handled well.
- OAA-342 Python tooltips: Some docstring includes SVGs
Version 1.0.0
New Features
This first release of the AdSec API allows users to:
- Define structural cross-sections
- Custom and pre-defined standard materials (steel, concrete, FRP and reinforcement bars/tendons)
- Standard, geometric and catalogue profile shapes
- Reinforcement (for concrete sections)
- Single bars, line, arc and circular bar groups
- Preload (force, stress or strain)
- Configure AdSec to use one of a selection of international design codes
- Carry out strength (ULS) and serviceability (SLS) analysis of sections, including
- Check response to an applied load (axial force and biaxial bending)
- Check response to an applied deformation (axial strain and biaxial curvature)
- Calculate crack widths (reinforced concrete sections)
- Extract chart data (force-moment and moment-moment interaction diagrams)
We have published a comprehensive documentation website and a selection of sample projects that use the API in both C# and Python.
The API is available on Nuget (for .NET development) and PyPi (for Python development) as self-contained packages.
Known issues
- OAA-294 Exception cases are not documented.
- OAA-311 Crack width calculations not possible when using a custom concrete material.
- OAA-316 Unhandled error occurs if
null
is used where an object reference is expected.
- OAA-331 If the same solver object is used to analyse more than one section, it always returns solution for the first section.