Skip to content
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.

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

Postprocessor: do we need killed count #3356

Open
Charlotte-Morgan opened this issue Oct 27, 2016 · 3 comments
Open

Postprocessor: do we need killed count #3356

Charlotte-Morgan opened this issue Oct 27, 2016 · 3 comments
Assignees

Comments

@Charlotte-Morgan
Copy link
Member

Charlotte-Morgan commented Oct 27, 2016

maybe we need this for earthquake analysis?

@Gustry
Copy link
Contributor

Gustry commented Jan 24, 2017

We have now a fatality count in the EQ on population function.
Do we need it only in this hazard ?

@Charlotte-Morgan
Copy link
Member Author

for now yes - but with the work @samnawi is doing and that he showed in his work on population repoorting for contingency plans; there are fatality estimates for other hazards too

@timlinux
Copy link
Contributor

As with the displacement rate, I think we should take the same implementation path and assign fatality rates per hazard class / threshold. I would suggest to default them to 0 and have a note indicating that the fatality rate is not defined. See similar notes in this vein for displacement here: #3664 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants