Skip to content

Latest commit

 

History

History
258 lines (129 loc) · 15.2 KB

File metadata and controls

258 lines (129 loc) · 15.2 KB

Learning Objectives:

LO3a: Learn about the nature of reproducible research, workflow design, data management and manipulation, dynamic reporting, what the key requirements are, and which resources are available to support these (knowledge).

LO3b: Be able to use available resources to create a workflow for reproducible research (task).

Key components:

  • Factors that affect reproducibility of research.

  • Principles of reproducibility, and integrity and ethics in research.

  • What is the 'reproducibility crisis', and meta-analyses of reproducibility.

  • Open materials, reagents and hardware, including resources, repositories and standards.

  • Electronic lab notebooks.

  • Data analysis documentation and open research workflows.

  • Living figures, turning scripts into reproducible documents, and Markdown.

  • Pre-registration and prevention of p-hacking/HARK-ing (Hypothesising After Results are Known).

  • Reproducible analysis environments (virtualization).

  • What are the computing options and environments that allow collaborative and reproducible set up.

Who to involve:

  • Individuals: Andy Byers, Anna Krystalli, Julien Colomb, Rutger Vos, Brian Nosek, Lorena Barba, Karl Broman, Victoria Stodden, John Ioannidis, Chris Chambers.

  • Organisations: FOSTER, Center for Open Science, COPE, Protocols.io, ROpenSci, Addgene, BITSS, Project TIER.

  • Other: GOSH Community, Software and Data Carpentry communities.

Key resources:

Tools

Research Articles and Reports

Key Posts

Other

Tasks:

  • Find a core data set that is used throughout the examples.

    • If possible, the dataset should have a diverse set of formats and styles for different types of analysis.
  • Designing a reproducible research workflow.

    • Create a flowchart of options to help get you started Check if your collaborators, colleagues or supervisors are using the same tools.

    • This can be created as a Google doc and shared for collaboration.

    • Use validated, standardized reagents where possible.

    • Use an electronic lab notebook and best practices for recording protocols and actual steps, reagents used.

  • How well annotated are your code scripts? As a general rule of thumb, try and include one comment for every three lines of code. Bear in mind, the primary audience is future you and other people less familiar with your code.

  • Posting raw and cleaned data files.

    • Post your data (raw and/or treated) online in a non-proprietary format.

    • Make sure it is in a place where you can get a unique identifier for it.

  • Write a study plan or protocol.

  • Set up a reproducible project using an electronic lab notebook to help organise and track your research.

    • Track changes as your research develops using a version control system such as GitHub.

    • Document everything done by creating a README file.

    • Make sure to select an appropriate license for your repo.

    • Convert the notebook into a standard research manuscript.

    • In this manuscript, include all necessary code to reproduce any figures and tables in their respective captions.