Book is rendered here: https://vickysteeves.gitlab.io/2018-uutah-repro
Monday-Thursday, June 11-14, 2018 10am-4pm & Conference Friday
Location: Carolyn Tanner Irish Humanities Building Auditorium, University of Utah
Cost: FREE; CME available
Various fields in the natural and social sciences face a ‘crisis of confidence’. Broadly, this crisis amounts to a pervasiveness of non-reproducible results in the published literature. For example, in the field of biomedicine, Amgen published findings that out of 53 landmark published results of pre-clinical studies, only 11% could be replicated successfully. This crisis is not confined to biomedicine. Areas that have recently received attention for non-reproducibility include biomedicine, economics, political science, psychology, as well as philosophy. Some scholars anticipate the expansion of this crisis to other disciplines.
This course explores the state of reproducibility. After giving a brief historical perspective, case studies from different disciplines (biomedicine, psychology, and philosophy) are examined to understand the issues concretely. Subsequently, problems that lead to non-reproducibility are discussed as well as possible solutions and paths forward.
This 5-day course provides an opportunity to explore issues of research reproducibility in-depth in a seminar-type setting, followed by hands-on sessions to learn actionable, practical solutions to make your own work more reproducible. You can choose to attend some or all of the sessions. The final day of the workshop is the conference Building Research Integrity through Reproducibility which requires a separate registration.
install.packages(c("rmarkdown", "bookdownplus", "tinytex"))
tinytex::install_tinytex()You can also click Tools > Install Packages and type the package names (make sure "install dependencies" is checked) separated by commas.
_bookin the project folder and click
index.htmlto view the book locally in your browser.
If you'd like to contribute, that would be amazing! I will try my best to be on top of merge requests and issues. If you aren't comfortable with coding or git, you can email me (vicky dot steeves at nyu dot edu) changes you'd like to see and I will open an issue for you or, if it's quick enough, make the change and give you attribution on this README.
Pease follow the Contributor Covenant in all your interactions with the project. If you would like to contribute to this project by modifying/adding to the code or data, please feel free to follow the standard GitLab workflow:
git clone https://gitlab.com/<USERNAME>/2018-uutah-repro.git
git remote add upstream https://@gitlab.com:VickySteeves/2018-uutah-repro.git
git checkout -b my-feature-branch-name
git add <FILE-NAMES>
git commit -m "A descriptive commit message"
git fetch upstream
git merge upstream/master
git push origin my-feature-branch-name
Before you start coding, open an issue so that the community can discuss your change to ensure it is in line with the goals of the project and not being worked on by someone else. This allows for discussion and fine tuning of your feature and results in a more succent and focused additions.
Merge Requests are eventually merged into the codebase. Please ensure they are:
If your code is untested, log heavy, or incomplete, you can use GitLab's Work In Progress (WIP) feature on your merge request so others know it is still being tested and shouldn't be considered for merging yet. This way we can still give you feedback or help finalize the feature even if it's not ready for prime time.
That's it! Thanks for your contribution!
You are welcome to email me at vicky dot steeves at nyu dot edu if you have questions or concerns, or raise an issue on this repository and I will do my best to respond quickly!