For more details and figures, please see the attached pdf.
Commonly, you got an activation for functional connectivity result based on either REST or SPM or other software. As long as this resultant map is in the MNI standard space, you can review it using REST slice viewer. After several settings such as underlay and overlay images, threshold p value, threshold cluster size and connectivity criterion (this value decides two neighboring voxels are within one cluster or not, typically is set to 5), you will get several activated or functionally connected clusters. Pressing Cl. Report, you will find cluster information in Matlab command window. To report this cluster, following steps you should do:
Step 1. Glimpsing this cluster in REST Slice viewer for a roughly assessment of its location.
Step 2. Open two new Slice Viewer windows showing BA and AAL atlas to roughly define the location of this cluster in BA and AAL.
Step 3. Go through the cl. report information to validate Step 2 and add more information.
Step 4. Form the final report on this cluster location.
Note that either too gross or too small region should not been reported (i.e., you probably need to report the middle section of the table). Important, you cannot rely on the cl. report that was printed in Matlab. The best way is check the location by using “yoke” function and by your own eyes. In lots of cases, “Peak MNI coordinate region” reports “undefined”, you have to do Step 2 and check by your own eyes. Sometimes, the cl. report will get a one big cluster with, for example, more than 5000 voxels. In this case, you should be much careful, because this cluster should cover lots of brain areas. The “Peak MNI coordinate region” only reports one region, which is thus quite wrong! You should increase threshold by using more stringent p value, to make it split into different smaller clusters and then report them separately.
Attachment | Size |
---|---|
how to report result.pdf | 310.83 KB |
- ZHANG_RESTadmin's blog
- Log in or register to post comments
- 11533 reads