Closed hanhou closed 5 months ago
See a weird bug:
nwb is generated successfully and can be loaded locally
after uploading to S3 (by "registering an external data asset" from the result folder of Run 2450362
), the file can still be opened if downloaded from S3
however, nwb cannot be loaded if I attached the data aasset that is a LINK to S3.
ConstructError: (root/acquisition/bpod_backup_BehavioralEvents/choice GroupBuilder {'attributes': {'comments': 'no comments', 'description': 'time (second) relative to the first trial start (aligned with ephys)', 'namespace': 'core', 'neurodata_type': 'TimeSeries', 'object_id': 'dbfd1c57-8e24-4177-8943-5e5ba8d8933f'}, 'groups': {}, 'datasets': {}, 'links': {}}, "Could not construct TimeSeries object due to: either 'timestamps' or 'rate' must be specified")
I'm trying
IMPORT
, not LINK
, a new data asset to aind-behavior-data/foraging_nwb_bpod/
(doesn't work!)Run 2450362
as an CO internal asset directly... (doesn't work!)Seems like some weird interaction between nwb and CO data asset:
/data/foraging_nwb_bpod
, it doesn't work/scratch
, it works!But other nwbs in /data/foraging_nwb_bonsai
always work...
Has something to do with the total size of a folder?
fileN = '473360_2021-08-12_16-52-05.nwb'
nwb_file = '/root/capsule/data/foraging_nwb_bpod/' + fileN
io = NWBHDF5IO(nwb_file_copy, mode='r')
nwb = io.read()
import shutil
nwb_file_copy = '/root/capsule/scratch/' + fileN
shutil.copy(nwb_file, nwb_file_copy)
io = NWBHDF5IO(nwb_file_copy, mode='r')
nwb = io.read()
All above problems only exist in VS Code cloud workstation...
TL;DR: working with nwb is sooooooooo frustrating...
27
29
31