fmk - updating to latest

docs/_sources/common/user_manual/releases/eeReleaseNotes.rst.txt

@@ -8,7 +8,7 @@ Release Notes
 Version 3.5.0 (Current)
 -----------------------
 
-**Release date:** Apr. 2024
+**Release date:** March. 2024
 
 **Highlights**
 

docs/_sources/common/user_manual/releases/pbeReleaseNotes.rst.txt

@@ -8,7 +8,52 @@ Release Notes
 Version 3
 =========
 
-   .. dropdown::    Version 3.3 (:blue:`Current`)
+   .. dropdown::    Version 3.4 (:blue:`Current`)
+      :open:
+
+      **Release date:** March 2024
+
+      **Major updates:**
+
+      - Ability to select from Physics based ground motions generated by M9 project
+
+      - Update the Pelicun3 Damage and Loss engine to v3.3:
+
+          - Changes affecting backwards compatibility
+
+              - Remove "bldg" from repair consequence output filenames: The increasing scope of PBE now covers simulations for transportation and water networks. Hence, labeling repair consequence outputs as if they were limited to buildings no longer seems appropriate. The bldg label was dropped from the following files: DV_bldg_repair_sample,DV_bldg_repair_stats,DV_bldg_repair_grp, DV_bldg_repair_grp_stats, DV_bldg_repair_agg, DV_bldg_repair_agg_stats.
+
+              - Decision variable types in the repair consequence outputs are named using CamelCase: Earlier they used all capitals. This change was made to be consistent with other parts of the codebase. For example, we use "Cost" instead of "COST". This might affect post-processing scripts.
+
+              - "ea" units were replaced with "unitless" where appropriate for clarity: There should be no practical difference between the calculations due to this change. Interstory drift ratio demand types are one example.
+
+              - Weighted component block assignment is no longer supported: We recommend using more versatile approach of defining the same component type multiple times to achieve the same effect.
+
+              - Damage functions are no longer supported: Damage functions were used to assign quantity of damage as a function of demand. Contrast this with fragility curves that assign probability of limit state exceedance as a function of demand. We recommend using the new multilinear CDF type fragility functions to develop theoretically equivalent, but more efficient models.
+
+          - Deprecation warnings
+
+              - Remove Bldg from repair settings label in DL configuration file: Following the changes above, we dropped Bldg from BldgRepair when defining settings for repair consequence simulation in a configuration file. The previous version (i.e., BldgRepair) will keep working until the next major release, but we encourage everyone to adopt the new approach and simply use the Repair keyword in the input files.
+
+	  - New features
+
+              - Location-specific damage processes: This new feature is useful when you want damage to a component type to induce damage in another component type at the same location only. For example, damaged water pipes on a specific story can trigger damage in floor covering only on that specific story. Location-matching is performed automatically without you having to define component pairs for every location using the following syntax: '1_CMP.A-LOC', {'DS1': 'CMP.B_DS1'} , where DS1 of CMP.A at each location triggers DS1 of CMP.B at the same location.
+
+              - Multilinear CDF random variable: allows using a multilinear approximation of any CDF in the tool.
+
+              - Allow multiple definitions of the same component type at the same location and direction in the asset model. (If needed, we can later add a feature to propagate these as separate instances to model, e.g., components used by various tenants.)
+
+              - Update JSON outputs to follow new standard SimCenter output format
+
+              - Include unit information in every CSV and JSON output file.
+
+              - Several minor efficiency improvements that lead to faster runtimes - major improvments in that area are coming in the next minor release
+
+              - Several error and warning messages added to provide more meaningful information when something goes wrong in a simulation.
+
+              - A lot of minor bugs fixed and robustness of the Pelicun engine ensured by bringing back continuous integration.
+
+   .. dropdown::    Version 3.3 
       :open:
 
       **Release date:** Jan 2024

docs/_sources/common/user_manual/releases/r2dReleaseNotes.rst.txt

@@ -9,7 +9,7 @@ Release Notes
 Version 4.1.0 (Current)
 -----------------------
 
-**Release date:** April 2024
+**Release date:** March 2024
 
 **Highlights**
 

docs/common/user_manual/releases/eeReleaseNotes.html

@@ -216,7 +216,7 @@
 <span id="lbl-release-eeuq"></span><h1>Release Notes<a class="headerlink" href="#release-notes" title="Permalink to this heading">¶</a></h1>
 <div class="section" id="version-3-5-0-current">
 <h2>Version 3.5.0 (Current)<a class="headerlink" href="#version-3-5-0-current" title="Permalink to this heading">¶</a></h2>
-<p><strong>Release date:</strong> Apr. 2024</p>
+<p><strong>Release date:</strong> March. 2024</p>
 <p><strong>Highlights</strong></p>
 <ol class="arabic simple">
 <li><p>Physics-based ground motion simulations generate by the <a class="reference external" href="https://sites.uw.edu/pnet/m9-simulations/">M9 project</a>.</p></li>

docs/common/user_manual/releases/pbeReleaseNotes.html

@@ -219,7 +219,58 @@ <h2>Version 3<a class="headerlink" href="#version-3" title="Permalink to this he
 <blockquote>
 <div><details class="sphinx-bs dropdown card mb-3" open="open">
 <summary class="summary-title card-header">
-Version 3.3 (<span class="blue">Current</span>)<div class="summary-down docutils">
+Version 3.4 (<span class="blue">Current</span>)<div class="summary-down docutils">
+<svg version="1.1" width="24" height="24" class="octicon octicon-chevron-down" viewBox="0 0 24 24" aria-hidden="true"><path fill-rule="evenodd" d="M5.22 8.72a.75.75 0 000 1.06l6.25 6.25a.75.75 0 001.06 0l6.25-6.25a.75.75 0 00-1.06-1.06L12 14.44 6.28 8.72a.75.75 0 00-1.06 0z"></path></svg></div>
+<div class="summary-up docutils">
+<svg version="1.1" width="24" height="24" class="octicon octicon-chevron-up" viewBox="0 0 24 24" aria-hidden="true"><path fill-rule="evenodd" d="M18.78 15.28a.75.75 0 000-1.06l-6.25-6.25a.75.75 0 00-1.06 0l-6.25 6.25a.75.75 0 101.06 1.06L12 9.56l5.72 5.72a.75.75 0 001.06 0z"></path></svg></div>
+</summary><div class="summary-content card-body docutils">
+<p class="card-text"><strong>Release date:</strong> March 2024</p>
+<p class="card-text"><strong>Major updates:</strong></p>
+<ul>
+<li><p class="card-text">Ability to select from Physics based ground motions generated by M9 project</p></li>
+<li><p class="card-text">Update the Pelicun3 Damage and Loss engine to v3.3:</p>
+<blockquote>
+<div><ul>
+<li><p class="card-text">Changes affecting backwards compatibility</p>
+<blockquote>
+<div><ul class="simple">
+<li><p class="card-text">Remove “bldg” from repair consequence output filenames: The increasing scope of PBE now covers simulations for transportation and water networks. Hence, labeling repair consequence outputs as if they were limited to buildings no longer seems appropriate. The bldg label was dropped from the following files: DV_bldg_repair_sample,DV_bldg_repair_stats,DV_bldg_repair_grp, DV_bldg_repair_grp_stats, DV_bldg_repair_agg, DV_bldg_repair_agg_stats.</p></li>
+<li><p class="card-text">Decision variable types in the repair consequence outputs are named using CamelCase: Earlier they used all capitals. This change was made to be consistent with other parts of the codebase. For example, we use “Cost” instead of “COST”. This might affect post-processing scripts.</p></li>
+<li><p class="card-text">“ea” units were replaced with “unitless” where appropriate for clarity: There should be no practical difference between the calculations due to this change. Interstory drift ratio demand types are one example.</p></li>
+<li><p class="card-text">Weighted component block assignment is no longer supported: We recommend using more versatile approach of defining the same component type multiple times to achieve the same effect.</p></li>
+<li><p class="card-text">Damage functions are no longer supported: Damage functions were used to assign quantity of damage as a function of demand. Contrast this with fragility curves that assign probability of limit state exceedance as a function of demand. We recommend using the new multilinear CDF type fragility functions to develop theoretically equivalent, but more efficient models.</p></li>
+</ul>
+</div></blockquote>
+</li>
+<li><p class="card-text">Deprecation warnings</p>
+<blockquote>
+<div><ul class="simple">
+<li><p class="card-text">Remove Bldg from repair settings label in DL configuration file: Following the changes above, we dropped Bldg from BldgRepair when defining settings for repair consequence simulation in a configuration file. The previous version (i.e., BldgRepair) will keep working until the next major release, but we encourage everyone to adopt the new approach and simply use the Repair keyword in the input files.</p></li>
+</ul>
+</div></blockquote>
+</li>
+<li><p class="card-text">New features</p>
+<blockquote>
+<div><ul class="simple">
+<li><p class="card-text">Location-specific damage processes: This new feature is useful when you want damage to a component type to induce damage in another component type at the same location only. For example, damaged water pipes on a specific story can trigger damage in floor covering only on that specific story. Location-matching is performed automatically without you having to define component pairs for every location using the following syntax: ‘1_CMP.A-LOC’, {‘DS1’: ‘CMP.B_DS1’} , where DS1 of CMP.A at each location triggers DS1 of CMP.B at the same location.</p></li>
+<li><p class="card-text">Multilinear CDF random variable: allows using a multilinear approximation of any CDF in the tool.</p></li>
+<li><p class="card-text">Allow multiple definitions of the same component type at the same location and direction in the asset model. (If needed, we can later add a feature to propagate these as separate instances to model, e.g., components used by various tenants.)</p></li>
+<li><p class="card-text">Update JSON outputs to follow new standard SimCenter output format</p></li>
+<li><p class="card-text">Include unit information in every CSV and JSON output file.</p></li>
+<li><p class="card-text">Several minor efficiency improvements that lead to faster runtimes - major improvments in that area are coming in the next minor release</p></li>
+<li><p class="card-text">Several error and warning messages added to provide more meaningful information when something goes wrong in a simulation.</p></li>
+<li><p class="card-text">A lot of minor bugs fixed and robustness of the Pelicun engine ensured by bringing back continuous integration.</p></li>
+</ul>
+</div></blockquote>
+</li>
+</ul>
+</div></blockquote>
+</li>
+</ul>
+</div>
+</details><details class="sphinx-bs dropdown card mb-3" open="open">
+<summary class="summary-title card-header">
+Version 3.3<div class="summary-down docutils">
 <svg version="1.1" width="24" height="24" class="octicon octicon-chevron-down" viewBox="0 0 24 24" aria-hidden="true"><path fill-rule="evenodd" d="M5.22 8.72a.75.75 0 000 1.06l6.25 6.25a.75.75 0 001.06 0l6.25-6.25a.75.75 0 00-1.06-1.06L12 14.44 6.28 8.72a.75.75 0 00-1.06 0z"></path></svg></div>
 <div class="summary-up docutils">
 <svg version="1.1" width="24" height="24" class="octicon octicon-chevron-up" viewBox="0 0 24 24" aria-hidden="true"><path fill-rule="evenodd" d="M18.78 15.28a.75.75 0 000-1.06l-6.25-6.25a.75.75 0 00-1.06 0l-6.25 6.25a.75.75 0 101.06 1.06L12 9.56l5.72 5.72a.75.75 0 001.06 0z"></path></svg></div>

docs/common/user_manual/releases/r2dReleaseNotes.html

@@ -227,7 +227,7 @@
 <span id="lbl-release"></span><h1><span class="section-number">7. </span>Release Notes<a class="headerlink" href="#release-notes" title="Permalink to this heading">¶</a></h1>
 <div class="section" id="version-4-1-0-current">
 <h2><span class="section-number">7.1. </span>Version 4.1.0 (Current)<a class="headerlink" href="#version-4-1-0-current" title="Permalink to this heading">¶</a></h2>
-<p><strong>Release date:</strong> April 2024</p>
+<p><strong>Release date:</strong> March 2024</p>
 <p><strong>Highlights</strong></p>
 <ol class="arabic simple">
 <li><p>Upgrade the earthquake event generation toolbox to support simulation of Peak Ground Velocity (PGV) and liquefaction induced Permanent Ground Deformation (PGD).</p></li>