Skip to content

Release 2.3.10
Compare
Choose a tag to compare
@awsbuild awsbuild released this 31 Oct 17:57
2.3.10
4576ad5

Oasis Release v2.3.10

Docker Images (Platform)

Docker Images (User Interface)

Components

Changelogs

OasisPlatform Changelog - 2.3.10

  • #1122 - Update python packages for 2.3.9
  • #1124 - Update docker base images and python packages
  • #1123 - Generate oasis files is not using the pre-analysis adjusted location file for V2 runs
  • #1125 - Support Cyber models on OasisPlatform

OasisLMF Changelog - 2.3.10

  • #1563 - Intensity Adjustments in gulmc for dynamic footprints
  • #1585, #1575 - Fix missing complex keys return without amplification
  • #1578 - fix: point to the correct source in error message for vulnerabiity_id…
  • #1580 - Hazard correlation defaults to 100% if missing
  • #1581 - oasislmf code uses legacy correlation settings location in model settings

ODS_Tools Changelog - 3.2.8

  • #139 - Look for validation files in custom paths
  • #147 - fix fill_empty method for field that end in XX or YYY
  • #157 - Both correlation_settings fields are marked as "Legacy" in desc

Release Notes

OasisPlatform Notes

Update python packages for 2.3.9 - (PR #1122)

Update docker base images and python packages - (PR #1124)

  • Update docker base images to ubuntu LTS 24.04
  • regenerate python package requirements files
  • Load CVE scanning DB from Github actions cache (Trivy)

Fixed pre-analysis exposure files not working in V2 worker runs - (PR #1130)

Add cybermodels support in the OasisAPI - V1 Only - (PR #1133)

  • Only for run_mode = V1 allow input generation to work without posting a location.csv file.
  • Update the check in portfolios to allow execution if Either a location or an account file is attached.

OasisLMF Notes

Fix missing complex keys return without amplification - (PR #1574)

  • Fix from complex keys return when running without PLA
  • Added testing for complex keys return + logging output

Fix vulnerability_id missing error message - (PR #1578)

Fix the error message so it points to the correct source when some vulnerability_id are missing from the vulnerability file.

Fix: undo 100% correlation if no correlation setting provided in model settings - (PR #1584)

The hazard_group_id where not generated if the correlation settings were not provided, causing a 100% correlation across all location.
This fix assure the hazard_group_id are generated and used correctly in gulmc.

Added fix for correlation settings - (PR #1587)

  • Fixed #1581, where oasislmf code was looking for correlation in the legacy location, it now checks both.
  • Added testing to catch problems loading correlation from model settings.

ODS_Tools Notes

Validation files in custom paths - (PR #138)

When a custom path is passed in the configuration file, validation files in that folder will be found and used.

fix default values for field ending in XX or YYY - (PR #147)

Some OED field end with XX or YYY to allow users to specify several type of the same field (for example for GeogSchemeXX)
Because of the mismatch between the column name and the field name (GeogScheme1 vs GeogSchemeXX), default value were not applied.

Fixed 'correlation_settings' description in model settings - (PR #157)

There are two locations of correlation_settings one is Legacy which at the root of the file. The new version is within the model_settings attribute (fixed the description field to avoid confusion

Assets 5
Loading