In general, you should test run your experiments on me prior to recruitment. If I am too busy, I may assign a senior lab member to run it through prior to receiving approval. Often in the beginning of a lab we are solving complex technical problems. These problems or similar problems have a way to sneaking back up. Thus, keeping thorough documentation is key to ensuring you or other lab members can quickly move through problem solving steps.

PIPELINE STEPS

Experimental Setup

Document the physical setup of the space (use pictures and visuals)
Document the procedure for giving informed consent to participants and how long it takes
- Include your presentation about your instructions to the participants
Document what hardware, software, and scripts need to be initialized, and when setup should start (e.g., arrive 1 hour prior to participant)
- Make reference to standard operating procedures for lab equipment
- Make sure the order of operations is clear

Data Collection

Document the instructions given to participants during each phase of the experiment
Include well-commented scripts for running the equipment used during data collection
Include instructions and notes for common data collection errors and mistakes

<aside> 💡 Be as detailed as necessary in your data collection instructions. A team member may need to collect your data when you are away or if an emergency situation arises

</aside>

Data Analysis

Include instructions and preferably scripts that detail the following:
- The process of converting raw data to analyzed dependent variables
  - What equations were used
  - What filters and filter parameters were used to clean the data
  - What assumptions were made about signal properties
- Going from analyzed dependent variables to reported statistical analysis and figures
  - What statistical tests were used and what results were reported
  - What data were included in each figure
  - Detailed instructions about how each figure was made
    - Wherever possible include code about making the figure