diff --git a/docs/search/search_index.json b/docs/search/search_index.json
index 2b0e433..c7883d9 100644
--- a/docs/search/search_index.json
+++ b/docs/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"],"fields":{"title":{"boost":1000.0},"text":{"boost":1.0},"tags":{"boost":1000000.0}}},"docs":[{"location":"","title":"ERA Software","text":"<p>Tools from the Engineering Risk Analysis (ERA) community for uncertainty quantification, reliability, and Bayesian inference in engineering.</p> <p> Contributor guidelines  GitHub org</p>"},{"location":"#whats-here","title":"What\u2019s here","text":"<ul> <li> <p> Software developments</p> <p>Core research software and methodological toolchains developed within ERA. Includes the four current development paths:</p> <ul> <li>UQ &amp; probabilistic modeling  </li> <li>Reliability &amp; rare-event estimation  </li> <li>Bayesian inference &amp; decision-making  </li> <li>Surrogate modeling</li> </ul> <p>tooling</p> </li> <li> <p> Teaching (Tutorials)</p> <p>Educational material, hands-on tutorials, and course notebooks. Designed for engineering students and researchers working with uncertainty quantification and decision-making.</p> <p>teaching</p> </li> <li> <p> Code associated with publications</p> <p>Reproducible research repositories linked to journal and conference papers. Includes benchmark scripts, experiment pipelines, and archived datasets when available.</p> <p>Open publication code template</p> <p>publication</p> </li> <li> <p> Experimental &amp; ongoing projects</p> <p>Prototypes, benchmarking environments, and early-stage research ideas under active development.</p> <p>tooling</p> </li> </ul>"},{"location":"contributor-guidelines/","title":"Contributor guidelines","text":"<p>This page explains how members of the ERA group should publish and maintain repositories within the ERA-Software organization.</p> <p>The goal is simple:</p> <p>Make research code reproducible, structured, and easy to reuse.</p>"},{"location":"contributor-guidelines/#what-belongs-on-era-software","title":"What belongs on ERA-Software?","text":"<p>According to the GitHub workshop slides :contentReference[oaicite:1]{index=1}, repositories should typically contain:</p> <ul> <li>Supporting code for lectures</li> <li>Supporting software associated with the chair (e.g. ERADist \u2192 eraUQ)</li> <li>Code / algorithms associated with papers</li> <li>Reusable research tools</li> </ul>"},{"location":"contributor-guidelines/#what-should-not-be-uploaded","title":"What should NOT be uploaded?","text":"<p>GitHub is optimized for tracking text files :contentReference[oaicite:2]{index=2}.</p> <p>Do not upload:</p> <ul> <li>Word documents</li> <li>PDFs</li> <li>Large datasets</li> <li>Notebook outputs</li> <li>Cache folders (e.g. <code>__pycache__</code>)</li> <li>Secrets, passwords, API keys</li> <li>Large binary files</li> </ul> <p>Keep repositories clean and lightweight.</p>"},{"location":"contributor-guidelines/#how-to-publish-a-new-repository","title":"How to publish a new repository","text":""},{"location":"contributor-guidelines/#1-prepare-your-local-project","title":"1. Prepare your local project","text":"<p>Your repository should contain:</p> <ul> <li><code>.gitignore</code></li> <li><code>LICENSE</code></li> <li><code>README.md</code></li> </ul> <p>Use the ERA paper template as reference if needed :contentReference[oaicite:3]{index=3}.</p>"},{"location":"contributor-guidelines/#2-create-a-repository","title":"2. Create a repository","text":"<p>You can:</p> <ul> <li>Create it under your personal account or</li> <li>Create it directly under <code>ERA-Software</code></li> </ul> <p>Repositories should normally be:</p> <ul> <li>Private during development</li> <li>Made public once stable and documented</li> </ul>"},{"location":"contributor-guidelines/#3-push-your-code","title":"3. Push your code","text":"<p>Basic workflow:</p> <pre><code>git init\ngit add .\ngit commit -m \"Initial commit\"\ngit push\n</code></pre> <p>Or use GitHub Desktop if preferred.</p>"},{"location":"contributor-guidelines/#4-fork-if-necessary","title":"4. Fork if necessary","text":"<p>If you created the repository in your personal account:</p> <ul> <li>Fork it into <code>ERA-Software</code></li> </ul> <p>If it was created in ERA-Software:</p> <ul> <li>Keep development via branches or forks.</li> </ul>"},{"location":"contributor-guidelines/#minimal-repository-standards","title":"Minimal repository standards","text":"<p>Every ERA repository should include:</p>"},{"location":"contributor-guidelines/#readmemd","title":"README.md","text":"<p>Must contain:</p> <ul> <li>Short description</li> <li>Installation instructions</li> <li>Minimal usage example</li> <li>Citation information (if linked to a paper)</li> </ul>"},{"location":"contributor-guidelines/#license","title":"License","text":"<p>Choose an appropriate open-source license.</p>"},{"location":"contributor-guidelines/#clean-structure","title":"Clean structure","text":"<p>Organize clearly:</p> <pre><code>project/\n\u2502\n\u251c\u2500\u2500 src/\n\u251c\u2500\u2500 tests/\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 LICENSE\n\u2514\u2500\u2500 .gitignore\n</code></pre>"},{"location":"contributor-guidelines/#collaboration-rules","title":"Collaboration rules","text":"<ul> <li>Use branches for new features</li> <li>Use pull requests for merging</li> <li>Keep commit messages meaningful</li> <li>Do not push directly to main for major changes</li> </ul>"},{"location":"contributor-guidelines/#final-goal","title":"Final goal","text":"<p>We use GitHub to:</p> <ul> <li>Track intermediate code states</li> <li>Collaborate</li> <li>Share reproducible research</li> </ul>"},{"location":"software/","title":"Software catalog","text":"<p>A curated set of ERA-Software tools for uncertainty quantification, reliability analysis, Bayesian inference, and surrogate modeling.</p> <ul> <li> <p> eraUQ</p> <p>Base library for uncertainty quantification and reliability workflows: probability distributions (e.g., <code>ERADist</code>, <code>EmpDist</code>), dependence models (e.g., Nataf/Gaussian copula), and related utilities.  Repo \u00b7  PyPI \u00b7  Notebook</p> </li> <li> <p> Reliability analysis tools (Python)</p> <p>Methods for reliability analysis and rare-event probability estimation. Includes classic workhorses such as FORM, Cross-Entropy / iCE, Subset Simulation, Sequential Importance Sampling, and Line Sampling variants.  Listed in Overview</p> </li> <li> <p> Bayesian inference tools (Python)</p> <p>Sampling-based Bayesian inference methods, including BUS (Bayesian Updating with Structural reliability methods), Adaptive BUS, iTMCMC, and SMC-style algorithms.  Listed in Overview</p> </li> <li> <p> Surrogate modelling (Python)</p> <p>Surrogate modelling tools for UQ, including Partial-Least-Squares-based Polynomial Chaos Expansion (PLS-PCE) (as listed in your org overview).  Listed in Overview</p> </li> </ul>"},{"location":"software/#how-these-pieces-fit-together","title":"How these pieces fit together","text":"<p>A typical workflow looks like:</p> <ol> <li>Define uncertainty (marginals + dependence) with <code>eraUQ</code></li> <li>Approximate expensive models with surrogate modelling (optional but often essential)</li> <li>Estimate failure probability with reliability tools</li> <li>Update with data using Bayesian inference tools (e.g., BUS / iTMCMC)</li> <li>Use results for decisions (risk, inspection, design, etc.)</li> </ol>"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"],"fields":{"title":{"boost":1000.0},"text":{"boost":1.0},"tags":{"boost":1000000.0}}},"docs":[{"location":"","title":"ERA Software","text":"<p>Tools from the Engineering Risk Analysis (ERA) community for uncertainty quantification, reliability, and Bayesian inference in engineering.</p> <p> Contributor guidelines  GitHub org</p>"},{"location":"#whats-here","title":"What\u2019s here","text":"<ul> <li> <p> Software developments</p> <p>Core research software and methodological toolchains developed within ERA. Includes the four current development paths:</p> <ul> <li>UQ &amp; probabilistic modeling  </li> <li>Reliability &amp; rare-event estimation  </li> <li>Bayesian inference &amp; decision-making  </li> <li>Surrogate modeling</li> </ul> <p>tooling</p> </li> <li> <p> Teaching (Tutorials)</p> <p>Educational material, hands-on tutorials, and course notebooks. Designed for engineering students and researchers working with uncertainty quantification and decision-making.</p> <p>teaching</p> </li> <li> <p> Code associated with publications</p> <p>Reproducible research repositories linked to journal and conference papers. Includes benchmark scripts, experiment pipelines, and archived datasets when available.</p> <p>Open publication code template</p> <p>publication</p> </li> <li> <p> Experimental &amp; ongoing projects</p> <p>Prototypes, benchmarking environments, and early-stage research ideas under active development.</p> <p>tooling</p> </li> </ul>"},{"location":"contributor-guidelines/","title":"Contributor guidelines","text":"<p>This page explains how members of the ERA group should publish and maintain repositories within the ERA-Software organization.</p> <p>The goal is simple:</p> <p>Make research code reproducible, structured, and easy to reuse.</p>"},{"location":"contributor-guidelines/#what-belongs-on-era-software","title":"What belongs on ERA-Software?","text":"<p>According to the GitHub workshop slides, repositories should typically contain:</p> <ul> <li>Supporting code for lectures</li> <li>Supporting software associated with the chair (e.g. ERADist \u2192 eraUQ)</li> <li>Code / algorithms associated with papers</li> <li>Reusable research tools</li> </ul>"},{"location":"contributor-guidelines/#what-should-not-be-uploaded","title":"What should NOT be uploaded?","text":"<p>GitHub is optimized for tracking text files.</p> <p>Do not upload:</p> <ul> <li>Word documents</li> <li>PDFs</li> <li>Large datasets</li> <li>Notebook outputs</li> <li>Cache folders (e.g. <code>__pycache__</code>)</li> <li>Secrets, passwords, API keys</li> <li>Large binary files</li> </ul> <p>Keep repositories clean and lightweight.</p>"},{"location":"contributor-guidelines/#how-to-publish-a-new-repository","title":"How to publish a new repository","text":""},{"location":"contributor-guidelines/#1-prepare-your-local-project","title":"1. Prepare your local project","text":"<p>Your repository should contain:</p> <ul> <li><code>.gitignore</code></li> <li><code>LICENSE</code></li> <li><code>README.md</code></li> </ul> <p>Use the ERA paper template as reference if needed.</p>"},{"location":"contributor-guidelines/#2-create-a-repository","title":"2. Create a repository","text":"<p>You can:</p> <ul> <li>Create it under your personal account or</li> <li>Create it directly under <code>ERA-Software</code></li> </ul> <p>Repositories should normally be:</p> <ul> <li>Private during development</li> <li>Made public once stable and documented</li> </ul>"},{"location":"contributor-guidelines/#3-push-your-code","title":"3. Push your code","text":"<p>Basic workflow:</p> <pre><code>git init\ngit add .\ngit commit -m \"Initial commit\"\ngit push\n</code></pre> <p>Or use GitHub Desktop if preferred.</p>"},{"location":"contributor-guidelines/#4-fork-if-necessary","title":"4. Fork if necessary","text":"<p>If you created the repository in your personal account:</p> <ul> <li>Fork it into <code>ERA-Software</code></li> </ul> <p>If it was created in ERA-Software:</p> <ul> <li>Keep development via branches or forks.</li> </ul>"},{"location":"contributor-guidelines/#minimal-repository-standards","title":"Minimal repository standards","text":"<p>Every ERA repository should include:</p>"},{"location":"contributor-guidelines/#readmemd","title":"README.md","text":"<p>Must contain:</p> <ul> <li>Short description</li> <li>Installation instructions</li> <li>Minimal usage example</li> <li>Citation information (if linked to a paper)</li> </ul>"},{"location":"contributor-guidelines/#license","title":"License","text":"<p>Choose an appropriate open-source license.</p>"},{"location":"contributor-guidelines/#clean-structure","title":"Clean structure","text":"<p>Organize clearly:</p> <pre><code>project/\n\u2502\n\u251c\u2500\u2500 src/\n\u251c\u2500\u2500 tests/\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 LICENSE\n\u2514\u2500\u2500 .gitignore\n</code></pre>"},{"location":"contributor-guidelines/#collaboration-rules","title":"Collaboration rules","text":"<ul> <li>Use branches for new features</li> <li>Use pull requests for merging</li> <li>Keep commit messages meaningful</li> <li>Do not push directly to main for major changes</li> </ul>"},{"location":"contributor-guidelines/#final-goal","title":"Final goal","text":"<p>We use GitHub to:</p> <ul> <li>Track intermediate code states</li> <li>Collaborate</li> <li>Share reproducible research</li> </ul>"},{"location":"software/","title":"Software catalog","text":"<p>A curated set of ERA-Software tools for uncertainty quantification, reliability analysis, Bayesian inference, and surrogate modeling.</p> <ul> <li> <p> eraUQ</p> <p>Base library for uncertainty quantification and reliability workflows: probability distributions (e.g., <code>ERADist</code>, <code>EmpDist</code>), dependence models (e.g., Nataf/Gaussian copula), and related utilities.  Repo \u00b7  PyPI \u00b7  Notebook</p> </li> <li> <p> Reliability analysis tools (Python)</p> <p>Methods for reliability analysis and rare-event probability estimation. Includes classic workhorses such as FORM, Cross-Entropy / iCE, Subset Simulation, Sequential Importance Sampling, and Line Sampling variants.  Listed in Overview</p> </li> <li> <p> Bayesian inference tools (Python)</p> <p>Sampling-based Bayesian inference methods, including BUS (Bayesian Updating with Structural reliability methods), Adaptive BUS, iTMCMC, and SMC-style algorithms.  Listed in Overview</p> </li> <li> <p> Surrogate modelling (Python)</p> <p>Surrogate modelling tools for UQ, including Partial-Least-Squares-based Polynomial Chaos Expansion (PLS-PCE) (as listed in your org overview).  Listed in Overview</p> </li> </ul>"},{"location":"software/#how-these-pieces-fit-together","title":"How these pieces fit together","text":"<p>A typical workflow looks like:</p> <ol> <li>Define uncertainty (marginals + dependence) with <code>eraUQ</code></li> <li>Approximate expensive models with surrogate modelling (optional but often essential)</li> <li>Estimate failure probability with reliability tools</li> <li>Update with data using Bayesian inference tools (e.g., BUS / iTMCMC)</li> <li>Use results for decisions (risk, inspection, design, etc.)</li> </ol>"}]}
\ No newline at end of file