epiverse-trace / epiverse-trace/simulist

More epidemic models to generate cases?

Open
#34 5 comments 0 reactions 0 assignees View on GitHub
discussion
Dominant language
R
Stars
11
Forks
1
Avg merge
3d 1h
Merged PRs (30d)
2

Description

The MVP of {simulist} uses a single-type branching process to simulate cases and the contacts between them. This model is imported from [{bpmodels}](https://github.com/epiverse-trace/bpmodels).

The initial pitch of the {simulist} package on the [Epiverse-TRACE discussions board](https://github.com/orgs/epiverse-trace/discussions/46) stated (emphasis mine):

> This R package would provide tools to simulate epidemic's raw case data in the form of line lists, using model outputs, such as ***compartmental models, branching processes, or network models***.

For future development should we consider also including compartmental model or network models to generate epidemiological data (line list and contacts) using {simulist}?

Contributor guide

Open the contributing guide

Research direction

Start by reviewing how simulist currently imports and uses the single-type branching process from bpmodels, then compare that scope with the package pitch linked in the issue. The issue does not name files, tests, or a decided model; completion would require an agreed scope for compartmental or network model support and defined outputs for line lists and contacts.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.