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
{{ message }}
This repository has been archived by the owner on Jan 1, 2020. It is now read-only.
I'm trying to represent data from an AOL microscope in NWB. It supports acquiring data directly from defined ROIs (which may be points, line segments, planes or volumes). I was thus thinking that using RoiResponseSeries within a Fluorescence interface would be most appropriate for storing the recordings, having defined the ROIs within ImageSegmentation with reference to an initial Z stack acquisition. However, the RoiResponseSeries only allows a single value per ROI per time point, so cannot store the full data from a 1d, 2d or 3d ROI, only a summary such as mean.
Is this deliberate, or was this kind of imaging just not anticipated?
Would I be better storing the data within /acquisition/timeseries, using a separate TwoPhotonSeries group for each ROI and channel?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to represent data from an AOL microscope in NWB. It supports acquiring data directly from defined ROIs (which may be points, line segments, planes or volumes). I was thus thinking that using
RoiResponseSeries
within aFluorescence
interface would be most appropriate for storing the recordings, having defined the ROIs withinImageSegmentation
with reference to an initial Z stack acquisition. However, theRoiResponseSeries
only allows a single value per ROI per time point, so cannot store the full data from a 1d, 2d or 3d ROI, only a summary such as mean.Is this deliberate, or was this kind of imaging just not anticipated?
Would I be better storing the data within
/acquisition/timeseries
, using a separateTwoPhotonSeries
group for each ROI and channel?The text was updated successfully, but these errors were encountered: