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

count result is not what is expected #338

Closed
mhrlittle opened this issue Aug 1, 2019 · 2 comments
Closed

count result is not what is expected #338

mhrlittle opened this issue Aug 1, 2019 · 2 comments

Comments

@mhrlittle
Copy link

Many thanks for creating this package. I've noticed the count produced by run_model to not be what would be expected. In the introduction example the initial count puts 1000 in state A with a transition probability of 0.1 to state B. Therefore, I would expect a count of 900 in the first cycle but the bottom the example shows a count of 950. I'm not sure if this is intended or not. Could you let me know how the count of 950 is arrived at.

@jrdnmdhl
Copy link
Contributor

jrdnmdhl commented Aug 1, 2019

This is a result of the half-cycle correction method, which defaults to life-table (i.e. averaging the counts from adjacent times).

@KZARCA KZARCA closed this as completed Aug 1, 2019
@mhrlittle
Copy link
Author

Thanks

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

3 participants