-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create demo tables #25
Milestone
Comments
wleoncio
added a commit
that referenced
this issue
Jun 7, 2022
- lampasona_2013 - ritland_2007 - perondi_2004 - singh_2010 - ligarden_2010 - tea - peterson_2007 - bentur_2009 - cavo_2012 - ear_infection - fontanella_2008 - lydersen_2012a - doll_hill_1950 - hine_1989 - hypothetical - mills_graubard_1987 - indredavik_2008 - table_7.5 - table_7.6
wleoncio
added a commit
that referenced
this issue
Jun 7, 2022
wleoncio
added a commit
that referenced
this issue
Jun 7, 2022
- ezra_2010 - fleiss_2003 - snp6498169
wleoncio
added a commit
that referenced
this issue
Jul 20, 2022
wleoncio
added a commit
that referenced
this issue
Jul 20, 2022
wleoncio
added a commit
that referenced
this issue
Jul 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most of the function examples are from the same few tables, properly documented with references as comments in the examples themselves. These would looks better as package-level tables that users can call directly.
table_*.*
objects (to also use the reference name)Adding a bit more explanation, the proposal is to create data objects for the literature examples: for example, Singh et al. (2010) provides the (X=250, n=533) pair of values that is used by several functions. I imagine it would be useful for the package to come with an object like
singh_et_al_2010
that would contain those values that could then be used across the package and by the users themselves. This comes with the added benefit of smaller code footprint and a dedicated documentation page forsingl_et_al_2010
.The text was updated successfully, but these errors were encountered: