Yes, the third info break down was from the dataset I posted images for and was from the Z -> R "undoing" atanh step.

And yes I used the [0] subbrik as per Mr. Chen's how-to: "And if you want the correlation coefficient at group level, you can convert the z-score (sub-brick #0 in the output from the group analysis) back to r (the reverse conversion of step 9 above):.

However based on your comments I went and looked at 3dinfo for the output directly from 3dttest++

Dataset File: Ttest_R_InfCere_wbPPI_Z+tlrc
Identifier Code: XYZ_O8IJNw7drx3SkMkULo3MXA Creation Date: Mon Sep 8 19:19:23 2014
Template Space: TLRC
Dataset Type: Func-Bucket (-fbuc)
Byte Order: LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode: BRIK
Storage Space: 583,680 (584 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 = 2
-- At sub-brick #0 'SetA_mean' datum type is float: -0.0541237 to 0.0569921
-- At sub-brick #1 'SetA_Tstat' datum type is float: -4.18336 to 4.23997
statcode = fitt; statpar = 13

From this I think the trick is to do the conversion step on the Tstat or subrik[1] in order to start look at statistical significance, correct? Or would I not specify and thus encorporate both for ease of use?

If that is the case then if I wanted to get a PPI correlation value (my "context dependent R" I think you'd say) between my seed region and a predifined ROI how would I find it? Cluster report and localization, or Masking off the ROI from the A_Mean subbrik? Could I do the same for Tstat for significance?

So much help, thank you rick.

~`Dane