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.

Sign up for GitHub

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

Jump to bottom

EpiData is inconsistent with current code structure #69

Closed
SamuelBrand1 opened this issue Feb 23, 2024 · 1 comment
Closed

EpiData is inconsistent with current code structure #69

SamuelBrand1 opened this issue Feb 23, 2024 · 1 comment
Labels
EpiAware
Milestone
EpiAware 0.1.0

Comments

@SamuelBrand1
Copy link
Collaborator 

          I think this sounds good. Just a note whilst we are here but I think currently that `EpiData` is inconsistent as it includes data on the delays for the observation process in a way that doesn't seem to make sense?

Another tangent but why do we have Abstract in the name of just one parent struct (i.e and not in LatentProcess etc.)?

Originally posted by @seabbs in #64 (comment)
@SamuelBrand1
Copy link
Collaborator Author

SamuelBrand1 commented Feb 27, 2024 •
edited
Loading

As of #79 EpiData is now only used in the latent infection generating process, which makes more sense.

@seabbs seabbs added this to the EpiAware 0.1.0 milestone Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
EpiAware
Projects
None yet
Milestone
EpiAware 0.1.0
Development

No branches or pull requests
2 participants
@seabbs @SamuelBrand1