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
This is a meta-issue compiling many individual ones; with the current round of work on the GUIDE coming to an end, the individual issues will be closed for bookkeeping but may be re-opened when/if they are tackled in the future
A frontend UX for adding experiment-specific metadata to the NWBFile level, and a Flask endpoint that uses LabMetadata to achieve it. Unsure how to locally bundle/pack the namespace without creating a full extension
A way to read a data array from any 'generic' source (binary, TIFF, HDF5, Zarr, xarray, npy, etc.) and choose which neurodata type (and field) to map it onto
Hard technological problem; would require dev mode almost certainly; would also require a global registration process for DataInterface classes on NeuroConv side, similar to NWB Inspector checks
Hard to implement since DANDI doesn't use TQDM (they have an in-house project used only by them), also because the upload API process is very messy to track iterative progress of, especially over multiple processes
This is a meta-issue compiling many individual ones; with the current round of work on the GUIDE coming to an end, the individual issues will be closed for bookkeeping but may be re-opened when/if they are tackled in the future
NWBFile
level, and a Flask endpoint that uses LabMetadata to achieve it. Unsure how to locally bundle/pack the namespace without creating a full extensionDataInterface
classes on NeuroConv side, similar to NWB Inspector checksupload
API process is very messy to track iterative progress of, especially over multiple processesThe text was updated successfully, but these errors were encountered: