ephys_pipeline:dataset_convention
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| ephys_pipeline:dataset_convention [2017/10/25 12:47] – lukas.schneider | ephys_pipeline:dataset_convention [2017/11/23 12:41] – lukas.schneider | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| |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. | ||