An *.rcps file stores ROI condition patterns for Turbo-BrainVoyager. It is a plain text file that contains one or more ROIs, the conditions used for the pattern data, and one line per ROI voxel with condition-specific pattern values.
RCPS files can be used to save, inspect, edit, or reuse multivoxel ROI patterns, for example in simulation workflows or for reviewing condition-specific ROI responses after a run.
General structure
An *.rcps file starts with a short global header:
Version: 1 Type: Beta-PSC NrOfROIs: 1 NrOfConds: 3
The header is followed by one block per ROI. Each ROI block contains:
ROI-Name: "ROI-1" NrOfVoxels: 4 CondNames: "Faces" "Houses" "Objects" EffectMeans: 0.000 0.000 0.000 EffectSDs: 0.000 0.000 0.000
After this, each following row describes one voxel in the ROI:
x y z value_for_condition_1 value_for_condition_2 value_for_condition_3
The first three numbers are the voxel coordinates. The remaining numbers are the condition-specific pattern values for that voxel.
Example
Version: 1 Type: Beta-PSC NrOfROIs: 1 NrOfConds: 3 ROI-Name: "ROI-1" NrOfVoxels: 4 CondNames: "Faces" "Houses" "Objects" EffectMeans: 0.000 0.000 0.000 EffectSDs: 0.000 0.000 0.000 12 34 5 0.812 0.143 -0.052 13 34 5 0.735 0.201 -0.014 12 35 5 0.690 0.167 0.021 13 35 5 0.774 0.188 -0.040
Field descriptions
| Field | Description |
|---|---|
Version | File format version. |
Type | Describes the type of pattern values stored in the file. For post-run files this is typically Beta-PSC. |
NrOfROIs | Number of ROI blocks in the file. |
NrOfConds | Number of conditions stored for each voxel. |
ROI-Name | Name of the ROI block. |
NrOfVoxels | Number of voxel rows in the ROI block. This must match the number of voxel lines that follow. |
CondNames | Names of the conditions. The order is important because the voxel values follow this same order. |
EffectMeans | Condition-wise summary values. In post-run files these may be set to 0.000; the voxel rows contain the actual pattern values. |
EffectSDs | Condition-wise standard deviation values. In post-run files these may be set to 0.000. |
| Voxel rows | Each row starts with x y z voxel coordinates, followed by one pattern value per condition. |
Important notes
The number of condition names in CondNames must match NrOfConds. Each voxel row must also contain exactly one value for each condition.
The number of voxel rows in an ROI block must match NrOfVoxels.
The condition order is important. For example, if the condition names are:
CondNames: "Faces" "Houses" "Objects"
then each voxel row must follow the same order:
x y z Faces_value Houses_value Objects_value
If the protocol contains a baseline condition, the baseline may not appear as one of the condition predictors in the RCPS file. The listed conditions correspond to the condition patterns stored in the file.
Use a plain text editor when editing *.rcps files manually. Do not edit the file in a word processor, because formatting characters can make the file unreadable by TBV.
Files generated after a run are typically saved with the same base name as the run or document, using the .rcps extension. In some cases, a generic name such as ConditionPatterns.rcps may be used.