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

Name for the time between infection and hosptial visit #44

Closed
athowes opened this issue Sep 20, 2024 · 5 comments
Closed

Name for the time between infection and hosptial visit #44

athowes opened this issue Sep 20, 2024 · 5 comments

Comments

@athowes
Copy link
Collaborator

athowes commented Sep 20, 2024

Can we call this total_delay rather than delay?

My reasoning: everything is a delay. I don't love "total delay" but it's more specific than "delay". Suppose we are having a meeting and someone says "the delay for COVID-19" wouldn't we expect them to clarify which delay?

Is it called delay because of something to do with EpiNow2?

@athowes
Copy link
Collaborator Author

athowes commented Sep 26, 2024

Again this is a bit of an issue about consistency. I don't mind too much what you do here, but I'd prefer to be calling it total_delay at my end

@zsusswein
Copy link
Collaborator

EpiNow2 calls it delay as in delay_opts(). I don't like that name either -- I feel good about total_delay

@athowes
Copy link
Collaborator Author

athowes commented Sep 26, 2024

When EpiNow2 calls it delay as in delay_opts() is that because delay refers to a generic delay and we happen to using the total delay in there?

@zsusswein
Copy link
Collaborator

No -- it's distinguishing from generation_time_opts() and truncation_opts(). The delay is meant to be the total delay from infection to case observation.

@athowes
Copy link
Collaborator Author

athowes commented Oct 2, 2024

It seems like it's OK to call total_delay in cfa-parameter-estimates so from my POV I think we can close this issue.

@zsusswein zsusswein closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2024
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