Skip to content

update based on bi improvement #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

update based on bi improvement #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 18 additions & 10 deletions src/sections/absolute-damage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,21 +4,29 @@ Absolute Damage
Introduction
------------

The absolute damage option allows model providers to include absolute damage amounts rather than damage factors in the
damage bin dictionary. If the damage factors are less than or equal to 1 in the damage bin dictionary, the factor will
be applied as normal during the loss calculation, by applying the sampled damage factor to the TIV to give a simulated
loss; but with absolute damage factors, where the factor is greater than 1, the TIV is not used in the calculation at
all, but rather the absolute damage is applied as the loss.
The absolute damage option allows model providers to include absolute damage amounts rather than damage factors in the
damage bin dictionary.

|
The damage bin dictionary supports the column `damage_type` which can be used to specify whether a given row corresponds
to a damage factor or absolute damage.

By default the `damage_type=0`, in this case if the damage factors are less than or equal to 1 in the damage bin dictionary, the factor will
be applied as normal during the loss calculation, by applying the sampled damage factor to the TIV to give a simulated
loss; but when the factor is greater than 1, the TIV is not used in the calculation at all, but rather the absolute
damage is applied as the loss.

**Example**

**Example 1:** if the sampled damage factor is 0.6 and the TIV is 100,000, the sampled loss will be 60,000
**Example 1 (damage factor):** if the sampled damage factor is 0.6 and the TIV is 100,000, the sampled loss will be 60,000

**Example 2:** if the sampled damage factor is 500 and the TIV is 100,000, the sampled loss will be 500
**Example 2 (absolute damage):** if the sampled damage factor is 500 and the TIV is 100,000, the sampled loss will be 500

|
A `damage_type=1` corresponds to the damage bin being treated as a damage factor.

A `damage_type=2` corresponds to the damage bin being treated as an absolute damage.
|
An example toy model with the absolute damage factor option is availible to use from `here <https://github.com/OasisLMF/
OasisModels/tree/develop/PiWindAbsoluteDamage>`_.
OasisModels/tree/develop/PiWindAbsoluteDamage>`_.

A more involved toy model incorporating the use of the `damage_type` in the damage bin dictionary in the context of
business interruption can seen `here <https://github.com/OasisLMF/OasisModels/tree/bi-test_model/PiWindBI>`.