**fScan Reference Manual, Chapter 1 (Introduction): textformats** ===== Text Formats -- File formats recognized in fScan ===== ==== Mult-column tables ==== Task condition lists - Multi-column timing file (with optional column header line) Onset Code (default format) Onset - time in seconds when this condition started Code - number or name of this condition By default, each condition is assumed to continue until the next onset time unless a duration is specified. If the first line of the file is non-numeric it is treated as a column header line. If a header line is specified, columns can be in whichever order is specified in the header. Valid column names are: onset, code, duration Physiological data files - 2-column waveform recordings Time Value Time - time in seconds for this data value Value - waveform data value Matrix file - single or multi-column numerical data The dimensions of the data object are taken from the column format of the file itself. The meaning of the data table depend on its usage context. Examples: Convolution kernel - NxN weighting table used in "-expr convolve" command. Map lookup table - 2-column table used in "-expr map" command. Color lookup table - 4-column color lookup table Index Red Green Blue Index - the voxel value associated with this color Red - Amount of red in this color (0-255) Green - Amount of green in this color (0-255) Blue - Amount of blue in this color (0-255) All values in the file are numbers. Lines in the table should be in order of increasing Index values. Index values do not need to be continuous -- colors will be automatically interpolated for any index value between those appearing in the table. Any voxel values higher than the highest index value will be shown with the highest value's color. FSL schedules - 3-column event timing file describing a single task parameter Onset Duration Weight Onset - time in seconds when the condition/parameter started Duration - duration of the condition in seconds Weight - a weighting factor for this condition epoch (typically 1.0) All values in the file are numbers. Each line in the schedule file describes an epoch of the given parameter. Multiple schedule files are used to describe the timing of multiple parameters. ==== XML files ==== BXH - Image header files XCEDE - Image header files EVENTS - List of individual task-related events MENU - Interactive dialog command descriptor GLOSSARY - Atlas data set region descriptor TABLE - Relational database table descriptor plus data