[VoxBo] vbdumpstats and timeseries question

[Ranjani Prabhakaran]

Thanks so much for your help, Dan!

I'll try re-preprocessing and see if that makes things better.

- Ranjani
On Jun 23, 2009, at 12:23 AM, Daniel Kimberg wrote:

> Ranjani  wrote:
>> I'm trying to use vbdumpstats to get ROI beta values.  I saved a
>> functional mask for a subject and then used vbdumpstats to get the
>> beta value for the voxels in that mask.  According to vbdumpstats,
>> there are 48 voxels in that mask.  But when I loaded my .prm file
>> using idl, applied the mask, and checked the number of voxels - there
>> are supposed to be 101 voxels in the mask.
>
> The numbers can disagree if the mask includes voxels that lie  
> outside your functional coverage, as they do in this case.  I took  
> a look in the directories you indicated, and found a mask that  
> contains 101 voxels, but apparently only has a 20 voxel overlap  
> with your functional coverage (as indicated by vbdumpstats, and I  
> double-checked it another way).  I couldn't get the number 48 to  
> pop out, maybe that's from a different mask or different subject?   
> Note that vbdumpstats will include a voxel only if its represented  
> in all of your image data files.
>
> It's possible something went wrong in the preprocessing here,  
> because I took a look at the prm file, and there's a distinct  
> pattern that suggests at least one of your tes files was out of  
> alignment with the rest.
>
>> Also, when I use the idl "Find All" tool to find out how many voxels
>> are in the mask, I've been getting the following message:
>>
>> (21) No time-series available for requested region
>> [called from: READTIMESERIES
>> </usr/local/VoxBo/pros/VoxBo_10.pro(1712)>]
>>
>> The glm for the subject ran without any problems and I can load
>> the .prm file in idl, so I'm not sure what the source of this problem
>> is.
>
> Sounds like it's probably just because your mask includes voxels  
> for which at least one of your tes files has no data.
>
> dan