ephys_pipeline:dataset_convention
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
ephys_pipeline:dataset_convention [2017/10/25 12:46] – lukas.schneider | ephys_pipeline:dataset_convention [2017/11/23 12:41] – lukas.schneider | ||
---|---|---|---|
Line 5: | Line 5: | ||
|2| Gaze modulation dataset, i.e. memory saccades, rectangular grid of targets starting at -15°, 0°, +15°| | |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.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.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.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 | | |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| Reach dataset| | ||
|3.1| Reach dataset, joint reach task| | |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. | ||