Reproducible Research with R (rOpenSci community call)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Community Call:
Tuesday, July 30, 9am PDT / 5pm BST. Everyone welcome. No RSVP needed.
Details: https://ropensci.org/blog/2019/07/11/commcall-jul2019/
-
Ben Marwick will introduce you to a research compendium (rrtools), which accompanies, enhances, or is a scientific publication providing data, code, and documentation for reproducing a scientific workflow.
-
From Karthik Ram you will learn about holepunch, an R package that will take any GitHub repo with R scripts and R markdown files and quickly turn it in into a free, live RStudio server where anyone can run your code!
-
Anna Krystalli will talk about the ReproHack series of one day reproducibility hackathons where participants try to reproduce papers from published code and data. (edited)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked rOpenSci blog post and the referenced rrtools, holepunch, and ReproHack resources. The issue provides no repository file, test, requested change, or completion criterion, so there is no defined implementation path or way to verify that the work is done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100