LogoLogo
  • Start Here
    • Introduction to NCIL
      • Welcome
      • Mission Statement
      • Getting Started
      • Make this handbook better!
  • Policies & Expectations
    • Working in NCIL
      • Aaron's Philosophy on Supervision
      • General Policies
      • Roles & Expectations
        • Interpersonal and Working Relationships
        • Lab Director: Aaron Newman
        • Lab Manager: Cindy Hamon-Hill
        • Collaborators
        • Postdocs
        • Lab Research Assistants
        • Graduate Students
        • Undergraduate Students
      • Work Ethic
        • Vacations & Absences
      • Money
        • Employment
        • Undergraduate Research Awards
        • Graduate Student Funding
    • Communication
      • Basecamp
      • Lab Meetings
      • Communication Among Lab Members
      • Communicating with Research Participants
      • Website & Social Media
      • Meetings with Supervisor
      • Response Times
    • Lab Space and Resources
      • Hours of Operation
        • After-Hours Research
      • Safety
    • Intellectual Property
      • Data
      • Authorship
      • Publishing: Where and When
  • Data Management & Analysis
    • Data Science Tools
      • Jupyter
        • JupyterLab
      • Python
      • R
      • How to set up your computer for NCIL data science
    • Servers & Computers
      • Accounts
      • File Server (NCILNAS)
        • Accessing NCILNAS
      • Compute Server
        • Jupyter
        • VS Code - Setup
        • VS Code - Everyday Use
      • GitHub Copilot
    • Data Analysis
      • Behavioural Data
      • EEG Analysis
      • fMRI Analysis
        • Processing fMRI Data with SPM
        • fMRI Analysis in SPM
      • Power analysis with simR in R
    • Data Management
      • Github
      • Open Science
    • Learn Some Coding
  • How To Run Experiments
    • How to Get a Research Study Started
      • Research Ethics
      • Your Research Protocol
        • Components of a Research Protocol
      • Pilot Testing
    • Running a Participant
      • Communicating With Participants
      • Recruiting
      • Before Each Participant Arrives
      • When a Participant is in the Lab
    • Experiment Programming
      • Stimulus Presentation Programs
      • Brain-Computer Interface Programs (BCI)
      • EEG Trigger Codes
        • Lab Streaming Layer
        • Trigger Code Hardware Setup
        • Timing Test
    • Data Storage & Protection
    • Word Similarity Measures
  • Communicating Science
    • Submitting papers to Aaron for review
    • Lab Meeting Talks
    • Independent Study Course
    • Honours Thesis
      • Getting Started
    • Master's Thesis
    • 😓PhD Dissertation
    • PhD Comps
    • Conferences
    • Publications
    • Reviewing Journal Manuscripts
  • Old
    • VS Code on NCIL server
Powered by GitBook
On this page

Was this helpful?

  1. How To Run Experiments

How to Get a Research Study Started

Essential reading. Overview of steps and approvals required prior to real data collection.

  1. Discuss experimental design with your supervisor, and as many other people with relevant expertise as you can find (e.g., committee members).

  2. Apply for research ethics board (REB) approval.

  3. Develop the stimuli for the experiment

  4. Program the experiment.

  5. Run through the entire stimulus program yourself.

  6. Fix any errors (typically an iterative process) until it runs as it should.

  7. Look at the log (output) files from your stimulus program. Check that timing is as you expect it to be. Ensure that all the data you need to analyze the study are in the log files. Great sorrow has befallen those who ran an entire study before checking their log files.

  8. After fixing any bugs you identify when running through yourself, pilot test the program on a friend or lab volunteer. Ask for feedback on the experiment - anything that was hard to understand, hard to see, boring, seemed like an error, etc.. Sometimes people won't give you helpful feedback unless you specifically ask. NOTE: if your study involves neuroimaging (EEG or MRI), you should not include imaging in your pilto testing until you have run through the program with yourself and others, beacuse otherwise you're wasting resources.

  9. Write a complete protocol for your study. This is the "how to" manual for your study. This is critically important, and no one is allowed to begin data collection (or even pilot test using EEG or MRI) until the protocol is complete and approved by Aaron.

  10. Recruit a pilot participant, and go through the entire experimental protocol, being sure that you have the protocol open and are actually following it. This is where you realize things you missed, or that are incorrect, and allows you to fix/update the protocol as necessary. Aaron, Cindy, or another designated senior lab member should be present for this pilot so they can provide feedback.

  11. Copy all data from the pilot run to the server, then open the files and write the basic script(s) you need to read and process the data. Again, this is critical to ensure that you're getting all the data you need, in the format you need, before you invest significant time and resources in collecting multiple data sets.

PreviousLearn Some CodingNextResearch Ethics

Last updated 1 year ago

Was this helpful?