Skip to content

Implementing deaths #46

Draft
erik-rosenstrom wants to merge 4 commits intopgv5_clinical_statusfrom
etr-deaths
Draft

Implementing deaths #46
erik-rosenstrom wants to merge 4 commits intopgv5_clinical_statusfrom
etr-deaths

Conversation

@erik-rosenstrom
Copy link
Collaborator

@erik-rosenstrom erik-rosenstrom commented Mar 11, 2026

This PR implements the effects of a dead symptom status. This involves disallowing future plans that are scheduled to happen for dead individuals and removing them from settings.

Changes

  • A death module was created with event subscription to listen for dead symtpom status progression. Upon death the alive person property is set to false. A context extension was created with the method to ergonomically check the alive status.
  • Tests were add to the death module to ensure all functionality of death occurs how we expect.
  • A method is added to settings context extension to remove individuals from settings
  • Checks were add to multiple places in the infection_manager and infection_propagation_loop modules to check if the person is alive before proceeding

This may be refactored depending if it is worthwhile to cancel plans by person id. This would be implemented in ixa

@erik-rosenstrom erik-rosenstrom marked this pull request as draft March 11, 2026 15:11
@erik-rosenstrom erik-rosenstrom linked an issue Mar 11, 2026 that may be closed by this pull request
@erik-rosenstrom erik-rosenstrom changed the base branch from main to pgv5_clinical_status March 11, 2026 21:21
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

Successfully merging this pull request may close these issues.

Implementing deaths upon a Dead symptom status

1 participant