1.3 Phase: session analysis - shunnnli/NeuroDAP GitHub Wiki
Overview
During this phase, relevant behavior events and neural signals will be extracted, stored, and plotted. Although you need to write your own version of analyzeSessions_XXX(), building block functions are provided and the whole struct will be as follows:
- Load all session-related data
- Filled in key information of the session if needed.
- (Optional) further signal preprocessing
- Generate trial table
- Extract all important events worthy of analysis (
analysisEvents). Also find their corresponding trial number (eventTrialNum) and define their corresponding name (analysisLabels) - Run
analyzeTraces(analysisEvents,analysisLabels,eventTrialNum=eventTrialNum) - (Optional but highly recommend) Design session summary plots and loop through all signals
After running, relevant files/plots will be stored within the same session folder. You can use a script to preprocess & analysis batch of sessions together. See Shun_loadSessionData.m
Requirements
- Your own version of method
analyzeSessions_XXX()should contain inputs for details about task structures, stimulation params, and other necessary information for future reference. These metadata will be stored inparamsstruct insync_sessionName.mat - Use function
createDatajointFiles()for generating files that is required for ingestion into the Sabatini Datajoint pipeline. - Although not strictly required, running
analyzeTraces()is highly recommended to facilitate future analysis across animals and sessions (see "Phase 4: experiment analysis").
Action items
- Copy file
analyzeSessions_template.min the tutorials folder. Modified the copied version to create your own version ofanalyzeSessions_XXX(). - Copy file
getTrialTable_template.min the tutorials folder. Modified the copied version to create your own version ofgetTrialTable_XXX(). - Follow the instruction in each section of
analyzeSessions_template.mto create your own analysis pipeline.