nigeLab_Concepts_FieldType
(Current as of: 2019-11-23)
Each of the Block Fields belongs to a certain FieldType. These parameters are currently configured in nigeLab.defaults.Block, using two cell arrays that must contain the same number of elements. There are currently five unique elements of FieldType.
This FieldType denotes that its associated Field should be linked to each individual electrophysiological recording channel. Common elements are 'Raw' (unfiltered recordings) and 'LFP' (decimated, low-pass-filtered recordings). Note: 'Spikes' and its associated Field entries ('Clusters' etc.) are defined as Channels and not Events FieldType due to this association with each recording channel. They are parsed differently during initiation and extraction by nigeLab due to the different associated FileType (Hybrid for 'Raw' and 'LFP' vs. 'Event' for 'Spike' and 'Clusters').
This FieldType denotes that its associated Field elements are independent of the electrophysiological recording channels, but were still still "streamed" in some way during the recording (for example, an analog or digital channel that is synchronized with the electrophysiological acquisition system).
This FieldType denotes that its associated Field elements are asynchronous entries that occurred at certain instants during the recording. An example would be manually scored behavioral events of interest, or automatically parsed digital "LOW-to-HIGH" events in one of the Streams Field elements. To properly parse these for your experiment, you will need to reconfigure nigeLab.defaults.Event.
This FieldType denotes that its associated Field array elements are members of the nigeLab.libs.VidStreamsType class. Each array element corresponds to a video file from a video detected at pars.VidFilePath during Block initialization. In order to properly detect associated Videos elements, make sure that pars.HasVideo is set to true. and pars.HasVidStreams are both
This FieldType denotes that its associated Field relates to metadata that typically has to be parsed in a unique fashion. By default, the Fields 'Time', 'Notes', and 'Probes' all fall into this FieldType. Links below denote how metadata is structured (by default) for each meta field:
- Make this an
enumerationclass so that it is easier to define (may be more trouble than it's worth).
