History of AFNI updates  

|
September 09, 2014 05:50PM
Ok, so not sure which dataset exactly you wanted info for. Will include major ones, sorry for so much info.

so this is for the bucket dataset I got from 3dDeconvolve using the motion regressors, the raw ROI timeseries, and the contrast Interaction term. I used the R^2 and Coeff ie. '[16] and [14] from this dataset to do the 3dcalc R->Z transform and atahn.


Template Space: TLRC
Dataset Type: Func-Bucket (-fbuc)
Byte Order: LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode: BRIK
Storage Space: 4,961,280 (5.0 million [mega]) bytes
Geometry String: "MATRIX(4,0,0,-78,0,4,0,-79,0,0,4,-64):40,48,38"
Data Axes Tilt: Plumb
Data Axes Orientation:
first (x) = Right-to-Left
second (y) = Anterior-to-Posterior
third (z) = Inferior-to-Superior [-orient RAI]
R-to-L extent: -78.000 [R] -to- 78.000 [L] -step- 4.000 mm [ 40 voxels]
A-to-P extent: -79.000 [A] -to- 109.000 [P] -step- 4.000 mm [ 48 voxels]
I-to-S extent: -64.000 -to- 84.000 [S] -step- 4.000 mm [ 38 voxels]
Number of values stored at each pixel = 17
-- At sub-brick #0 'Full_R^2' datum type is float: 0 to 0.799205
statcode = fibt; statpar = 2.5 421
-- At sub-brick #1 'Full_Fstat' datum type is float: 0 to 670.266
statcode = fift; statpar = 5 842
-- At sub-brick #2 'Strg#0_Coef' datum type is float: -86.5742 to 71.0841
-- At sub-brick #3 'Strg#0_Tstat' datum type is float: -9.41834 to 11.9158
statcode = fitt; statpar = 842
-- At sub-brick #4 'Strg_R^2' datum type is float: 0 to 0.144298
statcode = fibt; statpar = 0.5 421
-- At sub-brick #5 'Weak#0_Coef' datum type is float: -90.7754 to 73.1648
-- At sub-brick #6 'Weak#0_Tstat' datum type is float: -11.1925 to 12.9921
statcode = fitt; statpar = 842
-- At sub-brick #7 'Weak_R^2' datum type is float: 0 to 0.166993
statcode = fibt; statpar = 0.5 421
-- At sub-brick #8 'Slnc#0_Coef' datum type is float: -60.5484 to 139.503
-- At sub-brick #9 'Slnc#0_Tstat' datum type is float: -7.8426 to 7.09511
statcode = fitt; statpar = 842
-- At sub-brick #10 'Slnc_R^2' datum type is float: 0 to 0.0680751
statcode = fibt; statpar = 0.5 421
-- At sub-brick #11 'RawROI#0_Coef' datum type is float: -13.9542 to 9.67911
-- At sub-brick #12 'RawROI#0_Tstat' datum type is float: -19.4582 to 51.6023
statcode = fitt; statpar = 842
-- At sub-brick #13 'RawROI_R^2' datum type is float: 0 to 0.759758
statcode = fibt; statpar = 0.5 421
-- At sub-brick #14 'Interaction#0_Coef' datum type is float: -107.753 to 1557.99
-- At sub-brick #15 'Interaction#0_Tstat' datum type is float: -4.17871 to 5.13503
statcode = fitt; statpar = 842
-- At sub-brick #16 'Interaction_R^2' datum type is float: 0 to 0.0303657
statcode = fibt; statpar = 0.5 421

--------------------------------------------------------------------------------------------------
Then this is the 3dinfo for what got put into onesample ttest (I believe at this point it is technically a Z score):

Template Space: TLRC
Dataset Type: Func-Bucket (-fbuc)
Byte Order: LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode: BRIK
Storage Space: 291,840 (292 thousand [kilo]) bytes
Geometry String: "MATRIX(4,0,0,-78,0,4,0,-79,0,0,4,-64):40,48,38"
Data Axes Tilt: Plumb
Data Axes Orientation:
first (x) = Right-to-Left
second (y) = Anterior-to-Posterior
third (z) = Inferior-to-Superior [-orient RAI]
R-to-L extent: -78.000 [R] -to- 78.000 [L] -step- 4.000 mm [ 40 voxels]
A-to-P extent: -79.000 [A] -to- 109.000 [P] -step- 4.000 mm [ 48 voxels]
I-to-S extent: -64.000 -to- 84.000 [S] -step- 4.000 mm [ 38 voxels]
Number of values stored at each pixel = 1
-- At sub-brick #0 'Interaction_R^2' datum type is float: -0.143515 to 0.176054
statcode = fibt; statpar = 0.5 421
-----------------------------------------------------------------------------------------------------

Unfortunately all the 3dinfos look pretty much the same after ttesting. this was final one once I did the Z->R conversion after 3dttest++ :

Identifier Code: XYZ_LzSsYYk7_zBLY_5FoiN0Uw Creation Date: Mon Sep 8 19:14:59 2014
Template Space: TLRC
Dataset Type: Func-Bucket (-fbuc)
Byte Order: LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode: BRIK
Storage Space: 291,840 (292 thousand [kilo]) bytes
Geometry String: "MATRIX(4,0,0,-78,0,4,0,-79,0,0,4,-64):40,48,38"
Data Axes Tilt: Plumb
Data Axes Orientation:
first (x) = Right-to-Left
second (y) = Anterior-to-Posterior
third (z) = Inferior-to-Superior [-orient RAI]
R-to-L extent: -78.000 [R] -to- 78.000 [L] -step- 4.000 mm [ 40 voxels]
A-to-P extent: -79.000 [A] -to- 109.000 [P] -step- 4.000 mm [ 48 voxels]
I-to-S extent: -64.000 -to- 84.000 [S] -step- 4.000 mm [ 38 voxels]
Number of values stored at each pixel = 1
-- At sub-brick #0 'Interaction_R^2' datum type is float: -0.143515 to 0.176054
statcode = fibt; statpar = 0.5 421

-----------------------------------------------------------------------------------------------

Notably there is only a single subbrik in the output of all these stages once onesample ttesting is completed. Any idea where I got waylaid?

~`Dane




Edited 2 time(s). Last edit at 09/09/2014 05:54PM by d6anders.
Subject Author Posted

Context Dependent FC / PPI Analysis Help

d6anders September 04, 2014 11:09PM

Re: Context Dependent FC / PPI Analysis Help

d6anders September 07, 2014 11:30PM

Re: Context Dependent FC / PPI Analysis Help

gang September 08, 2014 10:21AM

Re: Context Dependent FC / PPI Analysis Help

d6anders September 08, 2014 11:33PM

Re: Context Dependent FC / PPI Analysis Help

rick reynolds September 09, 2014 10:11AM

Re: Context Dependent FC / PPI Analysis Help

d6anders September 09, 2014 01:53PM

Re: Context Dependent FC / PPI Analysis Help

rick reynolds September 09, 2014 02:07PM

Re: Context Dependent FC / PPI Analysis Help

d6anders September 09, 2014 05:50PM

Re: Context Dependent FC / PPI Analysis Help

rick reynolds September 09, 2014 09:05PM

Re: Context Dependent FC / PPI Analysis Help

d6anders September 09, 2014 10:31PM

Re: Context Dependent FC / PPI Analysis Help

rick reynolds September 09, 2014 11:22PM