Hi, Jim-

Hmm, the *.netcc output makes it look like there is only 1 ROI there. What does your powerrois_264.txt file look like---does it have 3 columns (namely, x-, y- and z-coord values), or 4 columns (x-, y- and z-coord values *and* an ROI value to be bestowed)?

If that *.txt file has three columns, then each ROI created with have a default value of 1. And it is the integer value of voxel that decides in which ROI it belongs---so, even non-connected voxels that all have the same value will be part of the same ROI.

Is that what might be happening here?

Also note: that is a lot of ROIs to pack in, and if the created spheres overlap, then I *think* that the later ones overwrite the voxels of previous ones (that is, the ordering of the ROIs in the text file would matter). I *think* that is the case... I also think the program will warn you if there is overlap, with messages like the following (but with different index values):

*+ WARNING: Overwrite short voxel 32 40 17

--pt