Hi Immanuel

That is perfectly fine, in CONN you would simply define your 'rest' condition entering there the corresponding onset/durations of all of your resting-state period blocks, and that will automatically concatenate all of the appropriate data to compute condition-specific connectivity measures.

A couple of additional comments:

1) if you have already entered all this onset/duration info into SPM (e.g. to perform task-related activation analyses) you may simply import all that info into CONN directly by selecting the Project.Import option and entering there the first-level design SPM.mat files for each subject/session.

2) we typically recommend to enter into CONN, in addition to the above 'rest' condition, all of the task conditions in your experimental design, even if you are not interested in obtaining task-related connectivity measures. That will improve your connectivity measures by removing some potential task-related effects at the beginning of your 'rest' blocks (due to 'spillage' from the preceding task blocks). If you may be interested in task-related connectivity then simply keep those task conditions there (in Setup.Conditions). If you are not interested in task-related connectivity measures, then, after entering those task-condition information in Setup.Conditions, right-click on your task conditions and select the 'move to First-level covariate list' option (that will skip any task-specific connectivity computations, while still modeling the main task-specific BOLD signal effects in your data).

Hope this helps
Alfonso

ps. for questions about the CONN toolbox please use the CONN forum at the NITRC site ( http://www.nitrc.org/forum/forum.php?forum_id=1144 ; or go to http://www.nitrc.org/projects/conn and then select 'support' or 'forums') rather than this more general 'NITRC comunity' forum.


Originally posted by Immanuel Elbau: