Skip to content
This repository has been archived by the owner on Jan 1, 2020. It is now read-only.

Why does RoiResponseSeries only allow a single value per ROI per time? #18

Open
jonc125 opened this issue Mar 22, 2017 · 0 comments
Open

Comments

@jonc125
Copy link
Contributor

jonc125 commented Mar 22, 2017

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?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant