RequestsForRoutineStudies - Methods
location: RequestsForRoutineStudies

Requests for routine methods studies

Sometimes there will be a genuine empirical question about differences in acquisition or analysis methods that can only be well answered by acquiring data across several subjects and comparing techniques.

As with all studies, this has to be of significant interest and importance to someone, in order justify scanning and analysis time. In practice this means that if we think the parameters under study are likely to have a significant effect on our analysis pipeline, then we will perform the study. Otherwise, we are very happy to support both analysis and acquisition, but will expect the interested researcher to take the lead in analysis.

We will use this page to put up ideas for such studies, and comment on their importance. Please send requests for studies to MatthewBrett, or another member of the AdminGroup for this wiki.

Suggested studies

Comparison of acquisition with Siemens PACE enabled and disabled

We feel that this is unlikely to be of much benefit - see TipsForDataAcquisition for a discussion. The problem with assessing PACE is that we would expect the problems to depend on the location and size of activation, so a single study will be unable to answer the question as to whether this is worthwhile or not.

Comparison of interleaved and sequential slice acquisition in FMRI

As a result of work by RhodriCusack, we have recently changed the default FMRI slice acquisition from interleaved to sequential. See TipsForDataAcquisition for discussion. There are theoretical and practical reasons to think that the sequential method is less prone to artefacts, and we think it most unlikely that there would be an easily measurable difference between the techniques in favour of interleaved.

There are well worked out methods of assessing a design for optimum jittering - see my event-related analysis poster and abstract and DesignEfficiency and references therein. A rule of thumb is that the effect of jittering is predictable from the design until events come close to 1 second apart, at which point there are significant non-linearities, which will render the standard models of design efficiency invalid.


None: RequestsForRoutineStudies (last edited 2013-03-08 10:28:27 by localhost)