Generate types for nwb-schema 2.11.0

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: ehennestad

+types/+core/AbstractFeatureSeries.m

@@ -1,5 +1,5 @@
 classdef AbstractFeatureSeries < types.core.TimeSeries & types.untyped.GroupClass
-% ABSTRACTFEATURESERIES - Abstract features, such as quantitative descriptions of sensory stimuli. The TimeSeries::data field is a 2D array, storing those features (e.g., for visual grating stimulus this might be orientation, spatial frequency and contrast). Null stimuli (eg, uniform gray) can be marked as being an independent feature (eg, 1.0 for gray, 0.0 for actual stimulus) or by storing NaNs for feature values, or through use of the TimeSeries::control fields. A set of features is considered to persist until the next set of features is defined. The final set of features stored should be the null set. This is useful when storing the raw stimulus is impractical.
+% ABSTRACTFEATURESERIES - Abstract features, such as quantitative descriptions of sensory stimuli. The TimeSeries::data field is a 2-D array, storing those features (e.g., for a visual grating stimulus this might be orientation, spatial frequency and contrast). Null stimuli (e.g., uniform gray) can be marked as being an independent feature (e.g., 1.0 for gray, 0.0 for actual stimulus) or by storing NaNs for feature values, or through use of the TimeSeries::control fields. A set of features is considered to persist until the next set of features is defined. The final set of features stored should be the null set. This is useful when storing the raw stimulus is impractical.
 %
 % Required Properties:
 %  data, features
@@ -26,19 +26,19 @@
         % Input Arguments (Name-Value Arguments):
         %  - comments (char) - Human-readable comments about the TimeSeries. This second descriptive field can be used to store additional information, or descriptive information if the primary description field is populated with a computer-readable string.
         %
-        %  - control (uint8) - Numerical labels that apply to each time point in data for the purpose of querying and slicing data by these values. If present, the length of this array should be the same size as the first dimension of data.
+        %  - control (uint8) - Numerical labels that apply to each time point in data for the purpose of querying and slicing data by these values. If present, the length of this array should be the same as the length of the first dimension of data.
         %
         %  - control_description (char) - Description of each control value. Must be present if control is present. If present, control_description[0] should describe time points where control == 0.
         %
         %  - data (numeric) - Values of each feature at each time.
         %
         %  - data_continuity (char) - Optionally describe the continuity of the data. Can be "continuous", "instantaneous", or "step". For example, a voltage trace would be "continuous", because samples are recorded from a continuous process. An array of lick times would be "instantaneous", because the data represents distinct moments in time. Times of image presentations would be "step" because the picture remains the same until the next timepoint. This field is optional, but is useful in providing information about the underlying data. It may inform the way this data is interpreted, the way it is visualized, and what analysis methods are applicable. For storing instantaneous event information, it is recommended to use an EventsTable instead of a TimeSeries with continuity set to "instantaneous".
         %
-        %  - data_conversion (single) - Scalar to multiply each element in data to convert it to the specified 'unit'. If the data are stored in acquisition system units or other units that require a conversion to be interpretable, multiply the data by 'conversion' to convert the data to the specified 'unit'. e.g. if the data acquisition system stores values in this object as signed 16-bit integers (int16 range -32,768 to 32,767) that correspond to a 5V range (-2.5V to 2.5V), and the data acquisition system gain is 8000X, then the 'conversion' multiplier to get from raw data acquisition values to recorded volts is 2.5/32768/8000 = 9.5367e-9.
+        %  - data_conversion (single) - Scalar to multiply each element in data to convert it to the specified 'unit'. If the data are stored in acquisition system units or other units that require a conversion to be interpretable, multiply the data by 'conversion' to convert the data to the specified 'unit'. For example, if the data acquisition system stores values in this object as signed 16-bit integers (int16 range -32,768 to 32,767) that correspond to a 5V range (-2.5V to 2.5V), and the data acquisition system gain is 8000X, then the 'conversion' multiplier to get from raw data acquisition values to recorded volts is 2.5/32768/8000 = 9.5367e-9.
         %
         %  - data_offset (single) - Scalar to add to the data after scaling by 'conversion' to finalize its coercion to the specified 'unit'. Two common examples of this include (a) data stored in an unsigned type that requires a shift after scaling to re-center the data, and (b) specialized recording devices that naturally cause a scalar offset with respect to the true units.
         %
-        %  - data_resolution (single) - Smallest meaningful difference between values in data, stored in the specified by unit, e.g., the change in value of the least significant bit, or a larger number if signal noise is known to be present. If unknown, use -1.0.
+        %  - data_resolution (single) - Smallest meaningful difference between values in data, stored in the specified unit, e.g., the change in value of the least significant bit, or a larger number if signal noise is known to be present. If unknown, use -1.0.
         %
         %  - data_unit (char) - Since there can be different units for different features, store the units in 'feature_units'. The default value for this attribute is "see 'feature_units'".
         %
@@ -52,7 +52,7 @@
         %
         %  - starting_time_rate (single) - Sampling rate, in Hz.
         %
-        %  - timestamps (double) - Timestamps for samples stored in data, in seconds, relative to the common experiment master-clock stored in NWBFile.timestamps_reference_time.
+        %  - timestamps (double) - Timestamps for samples stored in data, in seconds, relative to the common experiment master clock stored in NWBFile.timestamps_reference_time.
         %
         % Output Arguments:
         %  - abstractFeatureSeries (types.core.AbstractFeatureSeries) - An AbstractFeatureSeries object

+types/+core/AnnotationSeries.m

@@ -1,5 +1,5 @@
 classdef AnnotationSeries < types.core.TimeSeries & types.untyped.GroupClass
-% ANNOTATIONSERIES - DEPRECATED. Use an `EventsTable` instead, placed in the top-level `/events` group of the `NWBFile`. The `timestamps` field maps to the `timestamp` column, and the `data` field (annotation strings) maps to the `annotation` column on `EventsTable`. Use the `source_description` attribute on the `EventsTable` to record where the annotations came from (e.g., "Manual video review"). Original definition: Stores user annotations made during an experiment. The data[] field stores a text array, and timestamps are stored for each annotation (ie, interval=1). This is largely an alias to a standard TimeSeries storing a text array but that is identifiable as storing annotations in a machine-readable way.
+% ANNOTATIONSERIES - DEPRECATED. Use an `EventsTable` instead, placed in the top-level `/events` group of the `NWBFile`. The `timestamps` field maps to the `timestamp` column, and the `data` field (annotation strings) maps to the `annotation` column on `EventsTable`. Use the `source_description` attribute on the `EventsTable` to record where the annotations came from (e.g., "Manual video review"). Original definition: Stores user annotations made during an experiment. The data[] field stores a text array, and timestamps are stored for each annotation (i.e., interval=1). This is largely an alias to a standard TimeSeries storing a text array but that is identifiable as storing annotations in a machine-readable way.
 %
 % Required Properties:
 %  data
@@ -18,15 +18,15 @@
         % Input Arguments (Name-Value Arguments):
         %  - comments (char) - Human-readable comments about the TimeSeries. This second descriptive field can be used to store additional information, or descriptive information if the primary description field is populated with a computer-readable string.
         %
-        %  - control (uint8) - Numerical labels that apply to each time point in data for the purpose of querying and slicing data by these values. If present, the length of this array should be the same size as the first dimension of data.
+        %  - control (uint8) - Numerical labels that apply to each time point in data for the purpose of querying and slicing data by these values. If present, the length of this array should be the same as the length of the first dimension of data.
         %
         %  - control_description (char) - Description of each control value. Must be present if control is present. If present, control_description[0] should describe time points where control == 0.
         %
         %  - data (char) - Annotations made during an experiment.
         %
         %  - data_continuity (char) - Optionally describe the continuity of the data. Can be "continuous", "instantaneous", or "step". For example, a voltage trace would be "continuous", because samples are recorded from a continuous process. An array of lick times would be "instantaneous", because the data represents distinct moments in time. Times of image presentations would be "step" because the picture remains the same until the next timepoint. This field is optional, but is useful in providing information about the underlying data. It may inform the way this data is interpreted, the way it is visualized, and what analysis methods are applicable. For storing instantaneous event information, it is recommended to use an EventsTable instead of a TimeSeries with continuity set to "instantaneous".
         %
-        %  - data_conversion (single) - Scalar to multiply each element in data to convert it to the specified 'unit'. If the data are stored in acquisition system units or other units that require a conversion to be interpretable, multiply the data by 'conversion' to convert the data to the specified 'unit'. e.g. if the data acquisition system stores values in this object as signed 16-bit integers (int16 range -32,768 to 32,767) that correspond to a 5V range (-2.5V to 2.5V), and the data acquisition system gain is 8000X, then the 'conversion' multiplier to get from raw data acquisition values to recorded volts is 2.5/32768/8000 = 9.5367e-9.
+        %  - data_conversion (single) - Scalar to multiply each element in data to convert it to the specified 'unit'. If the data are stored in acquisition system units or other units that require a conversion to be interpretable, multiply the data by 'conversion' to convert the data to the specified 'unit'. For example, if the data acquisition system stores values in this object as signed 16-bit integers (int16 range -32,768 to 32,767) that correspond to a 5V range (-2.5V to 2.5V), and the data acquisition system gain is 8000X, then the 'conversion' multiplier to get from raw data acquisition values to recorded volts is 2.5/32768/8000 = 9.5367e-9.
         %
         %  - data_offset (single) - Scalar to add to the data after scaling by 'conversion' to finalize its coercion to the specified 'unit'. Two common examples of this include (a) data stored in an unsigned type that requires a shift after scaling to re-center the data, and (b) specialized recording devices that naturally cause a scalar offset with respect to the true units.
         %
@@ -36,7 +36,7 @@
         %
         %  - starting_time_rate (single) - Sampling rate, in Hz.
         %
-        %  - timestamps (double) - Timestamps for samples stored in data, in seconds, relative to the common experiment master-clock stored in NWBFile.timestamps_reference_time.
+        %  - timestamps (double) - Timestamps for samples stored in data, in seconds, relative to the common experiment master clock stored in NWBFile.timestamps_reference_time.
         %
         % Output Arguments:
         %  - annotationSeries (types.core.AnnotationSeries) - An AnnotationSeries object

+types/+core/BehavioralEpochs.m

@@ -1,5 +1,5 @@
 classdef BehavioralEpochs < types.core.NWBDataInterface & types.untyped.GroupClass & matnwb.mixin.HasUnnamedGroups
-% BEHAVIORALEPOCHS - TimeSeries for storing behavioral epochs.  The objective of this and the other two Behavioral interfaces (e.g. BehavioralEvents and BehavioralTimeSeries) is to provide generic hooks for software tools/scripts. This allows a tool/script to take the output one specific interface (e.g., UnitTimes) and plot that data relative to another data modality (e.g., behavioral events) without having to define all possible modalities in advance. Declaring one of these interfaces means that one or more TimeSeries of the specified type is published. These TimeSeries should reside in a group having the same name as the interface. For example, if a BehavioralTimeSeries interface is declared, the module will have one or more TimeSeries defined in the module sub-group 'BehavioralTimeSeries'. BehavioralEpochs should use IntervalSeries. BehavioralEvents is used for irregular events. BehavioralTimeSeries is for continuous data.
+% BEHAVIORALEPOCHS - TimeSeries for storing behavioral epochs. The objective of this and the other two Behavioral interfaces (e.g., BehavioralEvents and BehavioralTimeSeries) is to provide generic hooks for software tools/scripts. This allows a tool/script to take the output of one specific interface (e.g., UnitTimes) and plot that data relative to another data modality (e.g., behavioral events) without having to define all possible modalities in advance. Declaring one of these interfaces means that one or more TimeSeries of the specified type are published. These TimeSeries should reside in a group having the same name as the interface. For example, if a BehavioralTimeSeries interface is declared, the module will have one or more TimeSeries defined in the module sub-group 'BehavioralTimeSeries'. BehavioralEpochs should use IntervalSeries. BehavioralEvents is used for irregular events. BehavioralTimeSeries is for continuous data.
 %
 % Required Properties:
 %  intervalseries

+types/+core/ClusterWaveforms.m

@@ -1,16 +1,16 @@
 classdef ClusterWaveforms < types.core.NWBDataInterface & types.untyped.GroupClass
-% CLUSTERWAVEFORMS - DEPRECATED The mean waveform shape, including standard deviation, of the different clusters. Ideally, the waveform analysis should be performed on data that is only high-pass filtered. This is a separate module because it is expected to require updating. For example, IMEC probes may require different storage requirements to store/display mean waveforms, requiring a new interface or an extension of this one.
+% CLUSTERWAVEFORMS - DEPRECATED. The mean waveform shape, including standard deviation, of the different clusters. Ideally, the waveform analysis should be performed on data that is only high-pass filtered. This is a separate module because it is expected to require updating. For example, IMEC probes may require different storage requirements to store/display mean waveforms, requiring a new interface or an extension of this one.
 %
 % Required Properties:
 %  clustering_interface, waveform_filtering, waveform_mean, waveform_sd
 
 
 % REQUIRED PROPERTIES
 properties
-    clustering_interface; % REQUIRED (Clustering) Link to Clustering interface that was the source of the clustered data
+    clustering_interface; % REQUIRED (Clustering) Link to Clustering interface that was the source of the clustered data.
     waveform_filtering; % REQUIRED (char) Filtering applied to data before generating mean/sd
-    waveform_mean; % REQUIRED (single) The mean waveform for each cluster, using the same indices for each wave as cluster numbers in the associated Clustering module (i.e, cluster 3 is in array slot [3]). Waveforms corresponding to gaps in cluster sequence should be empty (e.g., zero- filled)
-    waveform_sd; % REQUIRED (single) Stdev of waveforms for each cluster, using the same indices as in mean
+    waveform_mean; % REQUIRED (single) The mean waveform for each cluster, using the same indices for each wave as cluster numbers in the associated Clustering module (i.e., cluster 3 is in array slot [3]). Waveforms corresponding to gaps in cluster sequence should be empty (e.g., zero-filled).
+    waveform_sd; % REQUIRED (single) Stdev of waveforms for each cluster, using the same indices as in mean.
 end
 
 methods
@@ -23,13 +23,13 @@
         %  clusterWaveforms = types.core.CLUSTERWAVEFORMS(Name, Value) creates a ClusterWaveforms object where one or more property values are specified using name-value pairs.
         %
         % Input Arguments (Name-Value Arguments):
-        %  - clustering_interface (Clustering) - Link to Clustering interface that was the source of the clustered data
+        %  - clustering_interface (Clustering) - Link to Clustering interface that was the source of the clustered data.
         %
         %  - waveform_filtering (char) - Filtering applied to data before generating mean/sd
         %
-        %  - waveform_mean (single) - The mean waveform for each cluster, using the same indices for each wave as cluster numbers in the associated Clustering module (i.e, cluster 3 is in array slot [3]). Waveforms corresponding to gaps in cluster sequence should be empty (e.g., zero- filled)
+        %  - waveform_mean (single) - The mean waveform for each cluster, using the same indices for each wave as cluster numbers in the associated Clustering module (i.e., cluster 3 is in array slot [3]). Waveforms corresponding to gaps in cluster sequence should be empty (e.g., zero-filled).
         %
-        %  - waveform_sd (single) - Stdev of waveforms for each cluster, using the same indices as in mean
+        %  - waveform_sd (single) - Stdev of waveforms for each cluster, using the same indices as in mean.
         %
         % Output Arguments:
         %  - clusterWaveforms (types.core.ClusterWaveforms) - A ClusterWaveforms object

+types/+core/Clustering.m

@@ -1,13 +1,13 @@
 classdef Clustering < types.core.NWBDataInterface & types.untyped.GroupClass
-% CLUSTERING - DEPRECATED Clustered spike data, whether from automatic clustering tools (e.g., klustakwik) or as a result of manual sorting.
+% CLUSTERING - DEPRECATED. Clustered spike data, whether from automatic clustering tools (e.g., klustakwik) or as a result of manual sorting.
 %
 % Required Properties:
 %  description, num, peak_over_rms, times
 
 
 % REQUIRED PROPERTIES
 properties
-    description; % REQUIRED (char) Description of clusters or clustering, (e.g. cluster 0 is noise, clusters curated using Klusters, etc)
+    description; % REQUIRED (char) Description of clusters or clustering (e.g., cluster 0 is noise, clusters curated using Klusters, etc.).
     num; % REQUIRED (int32) Cluster number of each event
     peak_over_rms; % REQUIRED (single) Maximum ratio of waveform peak to RMS on any channel in the cluster (provides a basic clustering metric).
     times; % REQUIRED (double) Times of clustered events, in seconds. This may be a link to times field in associated FeatureExtraction module.
@@ -23,7 +23,7 @@
         %  clustering = types.core.CLUSTERING(Name, Value) creates a Clustering object where one or more property values are specified using name-value pairs.
         %
         % Input Arguments (Name-Value Arguments):
-        %  - description (char) - Description of clusters or clustering, (e.g. cluster 0 is noise, clusters curated using Klusters, etc)
+        %  - description (char) - Description of clusters or clustering (e.g., cluster 0 is noise, clusters curated using Klusters, etc.).
         %
         %  - num (int32) - Cluster number of each event
         %