I was wondering if we could differentiate two types of pipelines: 1) task, 2) rest.
If so, I would condense all the task related analysis together. And leave the more general ones in common, that could be applied to both. I was thinking about '03-make_epochs.py' and '06-ptp_reject.py', but in rest you could also make epochs of a specific length of you want, so these may apply also to them. But you wouldn't require the events, etc.
We could then have sensor-task/sensor-rest and source-task/source-rest. Thinking about this two possible paths could be useful, when more advanced analysis will be merged
Hi!
I was wondering if we could differentiate two types of pipelines: 1) task, 2) rest. If so, I would condense all the task related analysis together. And leave the more general ones in common, that could be applied to both. I was thinking about '03-make_epochs.py' and '06-ptp_reject.py', but in rest you could also make epochs of a specific length of you want, so these may apply also to them. But you wouldn't require the events, etc. We could then have sensor-task/sensor-rest and source-task/source-rest. Thinking about this two possible paths could be useful, when more advanced analysis will be merged