User Tools

Site Tools


ephys_pipeline:8_sorted_neurons_table

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
ephys_pipeline:8_sorted_neurons_table [2022/01/11 13:22] – [Automatically created entries] lukas.schneiderephys_pipeline:8_sorted_neurons_table [2022/01/11 13:23] (current) – removed lukas.schneider
Line 1: Line 1:
-====== Sorted neurons excel table ====== 
-Find/create the Sorted neurons excel table corresponding to your monkey in the following location: 
-C:\Users\username\Dropbox\DAG\phys\Monkey_phys_dpz\Mon_sorted_neurons.xlsx 
-(replace username with your username, Monkey with the monkey's name and Mon with the first three letters of the monkey's name).  
- 
-There are two main sheets in this excel file: 
-  * automatic_sorting 
-  * final_sorting 
-The idea is, that a large part of the information can be updated automatically (**see...**), while some information has to be added manually in the final_sorting sheet.  
-For both sheets, each line represents one unit recorded in one block (and run) AND/OR the corresponding LFP site 
- 
- 
- 
-===== Manually added entries ===== 
-^SNR_rank ^Single_rank ^Stability_rank ^Set ^Target ^Hemisphere ^Grid ^x ^y ^ 
-| 1 | 1 | 0 | 1 | dPul|left|22.5|-5|8| 
-| 3 | 2 | 1 | 1 | dPul|left|22.5|-5|8| 
- 
-The first three entries should be taken from your notes during sorting.  
-  * SNR_rank: Signal to noise ratio assessment (1 - best SNR to 3 - marginal SNR) 
-  * Single_rank: Multiunit or single unit (1 - Single unit (SU) to 3 - Multiunit (MU) ) 
-  * Stability_rank: How stable were the features across time (0 - unit appeared or disappeared during the course of the run; 1 - stable) 
- 
-The other entries typically don't change within a session and can be taken from the handwritten log (notes taken during recording, to be found in Y:\Logs\Phys 
-  * Set: Dataset, relevant for assigning to specific project (see [[ephys_pipeline:dataset_convention|dataset convention]]) 
-  * Target: Area 
-  * Hemisphere: left/right 
-  * Grid: grid identifier (diameter.number) 
-  * x: grid hole coordinate x 
-  * y: grid hole coordinate y 
- 
-===== Electrode travel ===== 
-Last, but not least, there is another entry which is typically calculated inside the table using different approaches per experimenter: Electrode_travel. Several columns serve the purpose of calculating the electrode travel (from top of the grid). 
- 
-===== Dataset convention ===== 
- 
-^ Numeric code ^ Meaning ^ 
-|General notes |Neuron set IDs with no decimals correspond to the ones in which the task had the desired characteristics for a given dataset, e.g. set =2 gaze modulation with 3 initial starting locations 15° horizontal eccentricity and 10° vertical eccentricity; set=2.1 even when recorded before than 2, it contains a different eccentricity that was not used for the final dataset | 
-|Additional notes |when unit ID has a termination "a" e.g Lin_20160506_05a it means for that neuron the saccade target size matched the reach target size | 
-|1| Direct-visually- and memory-guided saccade dataset| 
-|2| Gaze modulation dataset, i.e. memory saccades, rectangular grid of targets starting at -15°, 0°, +15°| 
-|2.1| Memory saccades center-out / out-center 12° and 24° eccentricity (blocked per run)| 
-|2.2| Memory saccades center-out & out-center 12° and 24° eccentricity (interleaved in the same run)| 
-|2.3| Memory saccades, rectangular grid of targets starting at -12°, 0°, +12°, saccading 12° peripherally. In this dataset there were trials in which fixation was required instead of a saccade. From this dataset onwards ITI was recorded as well| 
-|2.4| Memory saccades, rectangular grid of targets starting at -12°, 0°, +12°, or  -15°, 0°, +15° In this dataset there were trials in which fixation was required instead of a saccade | 
-|3| Reach dataset| 
-|3.1| Reach dataset, joint reach task| 
- 
-To differentiate inactivation from control runs, we also indicate this by assigning a different data(sub-)set. Ideally, following the logic above, this would mean something like 3.5 for control and 3.6 for inactivation. Currently 31 and 32 are used respectively. For convention, Inactivation data(sub-)set value should always be higher than the respective control. 
- 
- 
-===== Other entries ??? ===== 
-^Difficult_sorting_or_unstable_ ^Other_potential_reasons_to_ignore_or_check ^Runcomplete ^Usable ^Comments ^task ^ 
  
ephys_pipeline/8_sorted_neurons_table.1641907333.txt.gz · Last modified: 2022/12/29 07:15 (external edit)