Wallace:fMRI: Difference between revisions
Sarah Baum (talk | contribs) No edit summary |
Sarah Baum (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
== Experiment Design == | == Experiment Design == | ||
=== Types of fMRI design === | |||
There are 3 main types of scan series that you will use in an fMRI experiment. | |||
==== Rapid Event-Related ==== | |||
==== Block Design ==== | |||
==== Resting State ==== | |||
=== Creating Code === | === Creating Code === | ||
To run an fMRI experiment you'll need to write some code that will interface with the scanner and present stimuli in the right order at the right time. For the most part, creating new code will involve taking someone's old code and updating the stimulus array variable. It's a good idea to test things out at the mock scanner in case the scanner software was updated in a way that no longer works well with the code, or if an errant comma or semi-colon found its way into the the code. | |||
When creating a stimulus array for a rapid event-related fMRI experiment, you'll need to pseudo-randomize the stimulus order in a way that is compatible for deconvolution analysis. The best way to do this is a program called optseq2. | When creating a stimulus array for a rapid event-related fMRI experiment, you'll need to pseudo-randomize the stimulus order in a way that is compatible for deconvolution analysis. The best way to do this is a program called optseq2. | ||
Revision as of 10:28, 30 January 2014
<html><style type='text/css'> .tabs {
width: 640px; font-family: arial; color:#ffffff;
}
.tabs strong{
color: #851e21;
} </style></html>
Wallace Lab
|
Experiment DesignTypes of fMRI designThere are 3 main types of scan series that you will use in an fMRI experiment. Rapid Event-RelatedBlock DesignResting StateCreating CodeTo run an fMRI experiment you'll need to write some code that will interface with the scanner and present stimuli in the right order at the right time. For the most part, creating new code will involve taking someone's old code and updating the stimulus array variable. It's a good idea to test things out at the mock scanner in case the scanner software was updated in a way that no longer works well with the code, or if an errant comma or semi-colon found its way into the the code. When creating a stimulus array for a rapid event-related fMRI experiment, you'll need to pseudo-randomize the stimulus order in a way that is compatible for deconvolution analysis. The best way to do this is a program called optseq2. AFNIAFNI is a software package for processing, analyzing, and displaying fMRI data. It is freely available from the NIH. Other packages for fMRI data analysis exist, but Sarah can't help you with them. It's a good idea to get AFNI up and running before you begin data collection and analysis. You can download the latest version of AFNI at http://afni.nimh.nih.gov/afni/download/afni/releases/latest When the file finishes downloading, you will need to double click the file to un-zip the tar file. Drag the newly created folder to the Applications directory. To more easily access the folder, rename it "afni". Set upYou'll need to update your .cshrc file in order to have all the correct paths set when you open terminal. To open your .cshrc file, enter the following command into terminal: open -e ~/.cshrc
UpdatingMany problems can occur if your afni verion is not up to date. To update, first type the following command into terminal: afni -version If your afni version is more than a month old, it's time to update. To update, type: @update.afni.binaries -defaults Finally, after you update you must enter the command rehash
Data AnalysisGetting raw data from the scannerAfter a scan you will need to get the data from the scanner to our server. |
