Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • L losscalculator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Dynamic Exposure
  • Global Dynamic Exposure
  • losscalculator
  • Issues
  • #24

Closed
Open
Created Jan 26, 2021 by Tara Evaz Zadeh@taraMaintainer0 of 18 tasks completed0/18 tasks

Epic: Steps to an improved losscalculator (To mention in the roadmap)

Tasks to be done in 2021

Damage calculator

  • Run the calculator using data of other regions to make sure it works in a generic way
  • Separate input-reading part from the rest of the calculator for probable future input format change
  • Have the calculator run successfully in case of a mixed exposure model (when the exposure-type is not cell (residual in fact) nor building)
  • Have tests running for the calculator
  • Improve calculation speed
  • Make the calculator run with inputs stored in a '.ini' file
  • Have logging used in the calculator
  • Remove the input files if they can be created within extra coding inside the script (such as --cell-ids)
  • Have post-processings of the results as python scripts to create ready-to-map damage files
  • Make it more user-friendly, such as adding the ability to use fragility functions with any damage states, not only four
  • Run the calculations using different cores (running in parallel)

visualization

  • Create a nice template for plotting:
    • Damage and risk results
    • Exposure models
    • Differences in either results or exposure models
  • Find the best way to visualize either results or exposure models of types:
    • Cell(residual)
    • Building
    • Aggregated
  • Find out new plots to better compare the results of different distributions (different exposure models)
  • Add scripts to the calculator to automatically create initial plots of necessary maps or figures

loss calculator

  • Compute losses using a vulnerability model
  • Compute losses after a damage calculation using a consequence model
  • Write a function to create a vulnerability function using a fragility and consequence given

More sub-tasks will be added.

Please everyone feel free to add to the tasks or comment.

\fyi @fd @cnievas @marius @ds @shinde

Edited Jan 29, 2021 by Tara Evaz Zadeh
Assignee
Assign to
Time tracking