The columns attribute specifies which data columns to record to the data file.
Applies to
<data>
Syntax
/ columns = [columnname, columnname, columnname, "string", property, property, property]Parameters
| property | Any property of any element may be listed as a data column. This includes custom properties defined in the values and expressions elements. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| columnname |
A predefined data column. Any of the following predefined columns are allowed:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| "string" | A literal string value. This can be used, for example, to mark data as having been produced by a particular script. |
Remarks
The columns attribute specifies the data values to be recorded to file and the column in which they are written. There are three types of columns that can be listed: 1) user-defined strings appearing in quotes, 2) a reserved keyword representing a particular data value, and 3) any property of any element defined in the script. The data values may be specified in any order. On each trial, Inquisit will write a single line of data consisting of each data value specified by the column. Columns will appear in the data file in the specified order.
Stimulusnumber, stimulusitem, stimulusonset, trialdata, and "string" receive special treatment.
The first stimulusnumber specified in the columns attribute indicates that the item number of the first stimulus appearing on the current trial should be recorded. The second stimulusnumber indicates that the item number of the second stimulus presented on the trial should be recorded, and so on. If no 1st, 2nd, 3rd, etc. stimulus is presented on a given trial, a '0' is recorded.
Similarly, the first stimulusitem specified in the columns attribute indicates that the actual item presented by the first stimulus appearing on the current trial should be recorded. If the stimulus is <text> or <port>, the actual item is recorded. If the stimulus is a <sound>, <picture>, or <video>, the item’s filename is recorded. If the stimulus is a <shape>, the name of the shape is recorded. Like stimulusnumber, each successive stimulusitem records the item from each successive stimulus presented on the trial. If no 1st, 2nd, 3rd, etc. stimulus is presented on a given trial, a '0' is recorded.
Similarly, the first stimulusonset specified in the columns attribute indicates that the onset time of the first stimulus appearing on the current trial should be recorded. Like stimulusnumber, each successive stimulusonset records the onset time for each successive stimulus presented on the trial. If no 1st, 2nd, 3rd, etc. stimulus is presented on a given trial, a '0' is recorded.
Similarly, the first trialdata specified in the columns attribute indicates that the first item specified in the trialdata attribute of the current trial should be recorded, the second occurrence of trialdata indicates that the second item in the trialdata attribute of the current trial should be recorded, and so on. If no 1st, 2nd, 3rd, etc. item is defined in the trialdata attribute, a '0' is recorded. (Note: if trialdata is not specified in this command, or if no <data> is defined, the trialdata attribute of each trial element is ignored.)
Finally, each text string within quotes in the columns attribute is recorded to the data file verbatim.
Examples
The following records 10 columns to the data file:
<data>
/ columns=["1.0.2", subject, computer.ipaddress, blockcode, trialcode, trialnum, latency, response, stimulusitem, stimulusitem, values.totalearnings, values.dprime, script.elapsedtime]
</data>