Hi Matt,

Indeed, there is some problem in 3dDeconvolve, possibly with the combination of global timing and IM. The problem seems to happen before 3dDeconvolve even detects that the timing is global. Based on that, you should be able to fix the problem simply by specifying the timing type BEFORE any timing files are given:

-global_times

So add that option before any -stim_times_IM option is listed.

To some degree, I have been thinking that we should move towards always using local timing. Within 3dDeconvolve, having the 2 cases makes life much more difficult (both for 3dDeconvolve and for users), but that is for another day.

So either specify -global_times, or change the timing to local via "timing_tool.py -global_to_local".

Please let me know how it goes.

Thanks,

- rick