Design plan for new architecture #18
Closed
jamesmbaazam
started this conversation in
Ideas
Replies: 1 comment
-
Closing this as it is now provided as a vignette here: https://epiverse-trace.github.io/epichains/articles/design-principles.html. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Towards interoperability
transmission.chain
): for handling transmission chains Version number #32:chain_sim()
,stat
= length/size specified,out.type
= if tree = TRUE, 'chain.tree', else, 'chain.notree').transmission_chain
object; Initiates data/output storage and retrieval/subsetting (inherit fromdata.frame
/tibble
).transmission.chain
object else throw error.transmission_chain
objects, depending on whether they are of type "tree" or "notree".- trees/chains plotted as a network Refactor chain_sim() #13
- cluster sizes per onset date (if specified by user) as barplots Add lifecycle badge #9
Utils
bpmodels
and with tagged columns using linelist package.Dependencies
This new architecture might require the following dependencies:
Simulations and post-processing
Package backend
Beta Was this translation helpful? Give feedback.
All reactions