About
This is an effort to create a general template for most projects
To resolve
-
The minimal amount of library/package info
-
Narrative overview of code and the order it is ought to be run in
- Would a README be a good place to put that info? But one README per directory is unlikely to be enough
-
What should the
run_all_analyses.Rscript and its outputs look like? -
Different type of projects: e.g. theoretical/simulation based, meta-analyses
-
Data version control
- Do we want to use tools designed for ML https://neptune.ai/blog/best-data-version-control-tools
- Or something that is more focused on research https://www.datalad.org/
-
Linking files in raw_data to code/collection procedure that collected it in experiment
- How about adding column to raw_data that contains at least the script name and preferably some sort of hash associated with the version experiment code script
- What would this look like for the different methods we use e.g. Gorilla vs. Psychopy vs. Psychtoolbox etc.
Resources
Chapter on project management from open textbook on Experimental Methods
A practical guide for transparency in psychological science
The Practice of Reproducible Research: Case Studies and Lessons from the Data-Intensive Sciences
Stanford CORES: Open By Design
- Brief descriptions with links to many resources
NASA: Transform to Open Science
Easing Into Open Science: A Gudie for Graduate Students and their Advisors - Short paper with step by step guide
TIER: Teaching Integrity in Empirical Reasearch
- Specifically the protocol
- Lots of teaching materials as well