Create light dataset that can be used as demo with `workflow-calcium-imaging`
Closed this issue · 8 comments
- Should include
scanbox
andscanimage
as examples
The scanbox data we have is a single 23GB sbx file. Is it possible to trim it (e.g. down to 3-5GB because that's the case for the scanimage data)?
The only solution that comes to mind for me would be a hacky local instal of sbxreader
where you set max frames to your own value.
The scanbox data we have is a single 23GB sbx file. Is it possible to trim it (e.g. down to 3-5GB because that's the case for the scanimage data)?
The only solution that comes to mind for me would be a hacky local instal of
sbxreader
where you set max frames to your own value.
I wasn't very clear in my question. I'm able to read the data and it has a shape of (7530, 4, 1, 512, 796). The first number in the list is the number of images. The rest shows the plane number, dimensions, etc. If I slice this matrix to get (500, 4, 1, 512, 796), would that be appropriate? Am I breaking anything? Are there any raw data that depends on this? Is 500 images enough to test our workflows?
Am I breaking anything? Are there any raw data that depends on this?
I don't know for sure. If you're able to save and reload, I think it would we worth running the light data through the imaging schema. Kabi or Dimitri could then take a look to see if the results look on-part with having a truncated dataset.
Thanks @tdincer @CBroz1. I have not worked with Scanbox files enough to know the nuances. Suite2p requires at least 200 frames (see suite2p/registration/register.py). Not sure if CaImAn has a minimum requirement. If this light dataset will be for the task_mode=trigger
demo and pytests, I don't see an issue with slicing the dataset and resaving. If this light dataset will also be used for the task_mode=load
, then you will have to rerun Suite2p or CaImAn because the processed data that is hosted on djarchive should correspond to the same raw data.
Updated my response above.
We have now created a light dataset for ScanImage and Suite2p. On djarchive, see workflow-calcium-imaging-data-v2
. We do not currently have a need for the other data formats.