Hi Daniel -
Thanks for the reply. Here's afni -ver:
Version AFNI_2011_12_21_1014
[[Precompiled binary linux_openmp_64: Jul 10 2014]]
I saved the cluster mask (via 'SaveMask' button) as 'meatball'. Here's some info about that dataset:
Dataset File: meatball_mask+tlrc
Identifier Code: XYZ_MYb8qRwXrst027GDCm93EQ Creation Date: Wed Jul 16 14:41:13 2014
Template Space: MNI
Dataset Type: Func-Bucket (-fbuc)
Byte Order: LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode: BRIK
Storage Space: 927,246 (927 thousand [kilo]) bytes
Geometry String: "MATRIX(-2.5,0,0,90,0,-2.5,0,125.5,0,0,2.5,-72):73,87,73"
Data Axes Tilt: Plumb
Data Axes Orientation:
first (x) = Left-to-Right
second (y) = Posterior-to-Anterior
third (z) = Inferior-to-Superior [-orient LPI]
R-to-L extent: -90.000 [R] -to- 90.000 [L] -step- 2.500 mm [ 73 voxels]
A-to-P extent: -89.500 [A] -to- 125.500 [P] -step- 2.500 mm [ 87 voxels]
I-to-S extent: -72.000 -to- 108.000 [S] -step- 2.500 mm [ 73 voxels]
Number of values stored at each pixel = 1
-- At sub-brick #0 '#0' datum type is short: 0 to 3
The range of data from 0 to 3 makes sense, since there are three clusters at this p-threshold. If I load meatball_mask+tlrc as the overlay, here's the crosshairs over one of the clusters:
[
www.dropbox.com]
I won't bother showing the output of whereami for the display window vs. the cluster report window, since it's the same as described before -- no info when called from clusterize, full atlas info when called from display window. Here's what I get when I solicit the info manually, from the command line:
$ whereami -omask meatball_mask+tlrc.
++ Input coordinates orientation set by default rules to RAI
++ In ordered mode ...
++ Have 4 unique values of:
0 1 2 3
++ Skipping unique value of 0
++ ========================================================================
++ Processing unique value of 1
++ 305 voxels in ROI
++ ========================================================================
++ Processing unique value of 2
++ 26 voxels in ROI
++ ========================================================================
++ Processing unique value of 3
++ 11 voxels in ROI
So you can see that this is the same sort of output that AFNI is bringing up when called from the clustsim report. It's like meatball_mask doesn't contain the info to orient the atlases or something, despite it being in MNI space?
EDIT: doing the above manually made me wonder: how does the command line know which coordinate I'm asking about? I have the cluster mask, but where in the cluster mask am I indicating? So I tried this, adding in the coords in one of the clusters manually:
$ whereami 41 -18 -34 -omask meatball_mask+tlrc.
Which resulted in this (edited):
Original input data coordinates in TLRC space
Focus point (LPI)=
-41 mm [L], 18 mm [A], -34 mm {TLRC}
-41 mm [L], 20 mm [A], -39 mm {MNI}
-41 mm , 16 mm [A], -34 mm {MNI_ANAT}
Atlas TT_Daemon: Talairach-Tournoux Atlas
Focus point: Left Superior Temporal Gyrus
Within 1 mm: Left Brodmann area 38
Within 5 mm: Left Middle Temporal Gyrus
Which is right. So it looks like info on the location of the clusters isn't being passed to whereami from the report? Or something? Not sure how this part is meant to work.
Edited 1 time(s). Last edit at 07/16/2014 04:07PM by shanusmagnus.
