...
| File | Structure | Fields | Subfields | Description |
|---|---|---|---|---|
| phys[protocol_id].mat | phys | .study_id | link to study in database | |
| .name | name | |||
.start_time (optional) | date-time: precise start time of recording
Optional because for some fMRI physiology we don't have this, or it's not synced with scanner. | |||
| .num_channels | ||||
| .channel{1:N} | cell array of channels | |||
| .name | channel name | |||
| .type | "rec" (recorded) or "calc" (calculated) | |||
| .filename | mat file of timeseries object; variable has channel name. File is located in phys folder). The channels are synchronized such that the time is equivalent (this is critical for events). The time should start at 0. Time is in seconds. | |||
| .sample_rate | empty for asynchronous | |||
| .offset | time offset from phys.start_time | |||
| .calc_sourcechans | for calculated channels; cell array of "rec" channel names used to calculate "calc" channel | |||
| .descr | description (optional) | |||
| .units | units (optional) | |||
| .num_events | ||||
| .event{1:N} | Cell array of events; note that these are all events, not only those in the database. For analysis, we will use the database events and select segments of the timeseries. For this reason, the names don't matter too much, as we can select events for analysis and classify them at the same time we incorporate them into the database. | |||
| .time | time in seconds, relative to phys.start_time | |||
| .event_id | event_id from database | |||
| .duration | often empty, or 0 | |||
| .type (optional?) |
Example
CSPM functions that read/write in this format
...