Difference between revisions of "Piloting"
From SpinozaWiki
(→Phase 2: MRI pilot) |
(→Phase 1: Developing experimental paradigm and stimuli) |
||
| Line 12: | Line 12: | ||
==Phase 1: Developing experimental paradigm and stimuli == | ==Phase 1: Developing experimental paradigm and stimuli == | ||
| − | Developing experimental paradigms and stimuli are the responsibility of the experimenter. However, we try to help when we can. | + | Developing experimental paradigms and stimuli are the responsibility of the experimenter. You can contact support if you have specific questions about the available [[Research_pages#Peripheral_equipment|peripheral equipment]].However, we try to help when we can. |
| − | When piloting at the scanner, you are expected to already have a fully functional behavioral experiment that responds adequately to button presses and TTL pulses (which arrive as USB keyboard 't' button presses). So before planning a dry run at the MRI scanner, plan a test session at the mock scanner to check whether your tasks work correctly. If a task runs at the mock scanner (it displays correctly on the screen, button presses and 't's are properly registered), it should be transferable to the actual scanner environment with little to no modifications | + | When piloting at the scanner, you are expected to already have a fully functional behavioral experiment that responds adequately to button presses and TTL pulses (which arrive as USB keyboard 't' button presses). So before planning a dry run at the MRI scanner, plan a test session at the mock scanner to check whether your tasks work correctly. If a task runs at the mock scanner (it displays correctly on the screen, button presses and 't's are properly registered), it should be transferable to the actual scanner environment with little to no modifications. |
==Phase 2: MRI pilot== | ==Phase 2: MRI pilot== | ||
Revision as of 13:27, 18 July 2023
Contents
Policy
New studies will generally require a certain amount of piloting before "real" data can be acquired. We split this into two phases; the first is the programming, debugging, and piloting of your behavioural task. This part does not depend on interaction with the scanner or peripherals other than button presses. The second is the setup of the MRI scanning protocol, sequences, durations, etc. At this stage a pilot would also involve testing a full 'dry run' of your imaging session to check stimulus timing, data consistency etc.
Both these stages occur before actual data collection starts and before hours are charged.
For questions about experimental and project design we have reserved a weekly timeslot where all staff members are available for consultation, for more complicated questions or issues that need to be discussed in person.
- This time-slot is every Tuesday from 10:30-11:00.
- Please reserve this time-slot by sending an email to [email protected].
Phase 1: Developing experimental paradigm and stimuli
Developing experimental paradigms and stimuli are the responsibility of the experimenter. You can contact support if you have specific questions about the available peripheral equipment.However, we try to help when we can.
When piloting at the scanner, you are expected to already have a fully functional behavioral experiment that responds adequately to button presses and TTL pulses (which arrive as USB keyboard 't' button presses). So before planning a dry run at the MRI scanner, plan a test session at the mock scanner to check whether your tasks work correctly. If a task runs at the mock scanner (it displays correctly on the screen, button presses and 't's are properly registered), it should be transferable to the actual scanner environment with little to no modifications.
Phase 2: MRI pilot
The SC staff is happy to help you set up your MRI protocol. Let Diederick know when you are preparing a study and require assistance or advice. We have defined a default set of protocols at 3T and 7T that can be used 'as is' or tweaked for the specific research question. Please make sure to check your pilot data carefully.
Custom projects
In some cases, more time might be required. There can be several reasons for this, e.g. because
- a study requires MRI protocols that are not part of the default protocol set, or
- a study uses a custom experimental set-up that requires optimization in the scanning environment.
If you think this applies to your situation, get in touch with Diederick to discuss how much time is reasonable. One factor taken into account when determining how much pilot time is provided is to what extent sequences or a set-up might be useful in a broader context, i.e. for other projects / Spinoza partners. Agreed upon pilot time is booked as project time but will not or only partially count towards scanning quota. Note: when booking the scanner for pilot purposes indicate this with the remark 'pilot' in the summary field.