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

Documentation for targeting durations #358

Open
RomeshA opened this issue Sep 5, 2019 · 2 comments
Open

Documentation for targeting durations #358

RomeshA opened this issue Sep 5, 2019 · 2 comments

Comments

@RomeshA
Copy link
Contributor

RomeshA commented Sep 5, 2019

Durations used for transitions may not behave as expected when averaging. In particular, consider the case where half of the population has zero probability of a transition, and the other half has a nonzero probability. Working with probabilities, the overall population probability would be half of the nonzero probability. But the durations can't be averaged, because one of them is infinite. More generally, the conceptual issue is that the zero probability/infinite duration is on the assumption that that portion of the population is never eligible for any other transitions, whereas with probabilities, it's like sampling a different group of people to have zero probability at each timestep (so in the duration conceptualization, there is no mixing between the individuals, whereas with probabilities, there is).

In general, this means that targeting duration parameters may produce unexpected results if there are large differences in the durations across the baseline and program outcome values. This may not always be relevant in cases where the duration parameter is not associated with any transitions, so the resolution is to document this behaviour properly

@Rowanmh
Copy link
Contributor

Rowanmh commented Sep 5, 2019

In general the recommendation would be that where programs target a duration parameter that will be used for transitions, converting that parameter to a probability and targeting the probability should be strongly considered to produce the expected results.

@RomeshA
Copy link
Contributor Author

RomeshA commented Sep 23, 2019

This could be an ideal use case for an optional warning as per #351 to be raised if the framework targets a transition parameter that is in duration units

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

2 participants