CDCgov / CDCgov/PyRenew

Longer running infection feedback process

Open
#458 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

pyrenew
Dominant language
Python
Stars
29
Forks
9
Avg merge
9d 9h
Merged PRs (30d)
8

Description

Goal

Add more options to feedback process on $\log R_t$, described here, which are efficient for longer running inference.

Context

IMO from basic principles fitting on data only from after a peak hospitalisation and before the next peak hospitalisation then the action of the feedback term will be pretty unidentifiable. However, the obvious downside of running the inference over longer time periods is that we would require a very long history of infections within the model to carry for inside scan.

From f2f discussion with @dylanhmorris we had a quick think about easier ways to model this.

IMO, the easiest way to have a long period of effect from feed back whilst avoiding heavy compute is:

F(t) = \gamma \sum_{\tau = 1}^{\infty}I(t-\tau)f(\tau) = \gamma \sum_{\tau = 1}^{\infty}I(t-\tau) \left(\lambda_f\right)^{\tau -1}.

Where $\lambda_f \in [0,1]$ is a forgetting factor, and $T_f = \infty$. Whilst exponential smoothing is pretty simplistic, it is handy because it has an on-line update rule:

F(t+1) = \gamma  I(t) + \lambda_f F(t).

This means that scan only has to carry forward the feedback strength $F(t)$ rather than a long vector of past infections, in addition to the recent infections required for the new infection calculation.

NB:

  • This approach would very likely work better with infection on a per capita scale and $F(0)$ is likely to be a parameter that needs inference.
  • @dylanhmorris pointed out that more complicated models that exponential decay are possible e.g. a multi-stage Erlang decay.

Required features

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read equations.md#infections and pyrenew/latent/infection_functions.py at new_double_convolve_scanner. Work out the additional scanner option from the stated online feedback update, then confirm it supports longer-running inference without carrying the full infection history. Done means the new scan function is available as another option.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.