You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently do not have the ability to assign units to Behavioral Events (such as for Din, Dout, Acceleration, and Gyroscope data). Our metadata files do have the Units section but we currently leave it as 'unspecified'. As far as I understand, even if unit information was provided, it does not populate downstream in the .nwb files.
Suggested modification: Assign a unit to each type of 'behavioral_event' in the metadata. For example:
Din and Dout: the values lie between 0 and 1 and 'unspecified' is a reasonable choice of unit
Accelerometer: spike-gadgets headstages use +/- 2G full range with an in-practice resolution per step 2/32767 g (0.000061 g). The unit should be 'g' and we would need to multiply the recorded values with 0.000061 g.
Gyroscope: spike-gadgets headstages use +/- 2000 degrees per turn (dps) with an in-practice resolution of 0.061 deg/sec. The unit should be 'd/s' and we would need to multiply the recorded values with 0.061 deg/sec.
and ensure that this information is populated downstream in the .nwb files.
The text was updated successfully, but these errors were encountered:
Should separate analog data into separate nwb time series for each type of analog signal.
Should also name the Ain1, etc. in the yaml so people know what they are.
We currently do not have the ability to assign units to Behavioral Events (such as for Din, Dout, Acceleration, and Gyroscope data). Our metadata files do have the Units section but we currently leave it as 'unspecified'. As far as I understand, even if unit information was provided, it does not populate downstream in the .nwb files.
Suggested modification: Assign a unit to each type of 'behavioral_event' in the metadata. For example:
and ensure that this information is populated downstream in the .nwb files.
The text was updated successfully, but these errors were encountered: