Skip to content
GitLab
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 17
    • Issues 17
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Dynamic ExposureDynamic Exposure
  • Global Dynamic ExposureGlobal Dynamic Exposure
  • losscalculator
  • Issues
  • #78
Closed
Open
Issue created Aug 10, 2022 by Tara Evaz Zadeh@taraMaintainer

Changing `damage_calculator.py` to match new result database table name changes

By adding loss computation to the losscalculator there was a need to change the database structure (the database in which the damage and loss results are written to).

one of the steps towards this change was to Rename DamageAssessment table of the result database to Assessment(exposure-lib#36 (closed)), because this table can also be used for losses and not only for damage.

Now the damage_calculator.py needs to adjust to this change and write to the table named Assessment and not DamageAssessment. I will address this problem in this issue.

Assignee
Assign to
Time tracking