-
Notifications
You must be signed in to change notification settings - Fork 70
Description
The problem
Our napari loader widget can currently load files from the supported third-party formats, but not from netCDF files—our recommended format for natively saving movement datasets.
In practice, this means that if users load data from DeepLabCut, SLEAP, etc., clean it with movement
, and then save the processed dataset to a netCDF file (as we recommend), they have no straightforward way to explore the data in napari
. This is a gap we should address.
Possible solution
- Add netCDF (or rather movement) as an option in the "source software" dropdown selector.
- On "Load", attempt to open the file with
xarray.open_dataset()
, looking for variables namedposition
,confidence
, andshape
. At minimum,position
should be required, with informative errors raised if it is not found. - Load
position
andconfidence
as we currently do for pose datasets, i.e. intoPoints
andTracks
layers. If ashape
variable is present, also load it as aShapes
layer for bounding boxes.
This approach assumes the standard naming convention (position
, confidence
, shape
) used in movement datasets. However, users may have saved data under different names (e.g. position_filtered
or something unrelated). A more general solution would be to allow users to manually map variables in the netCDF file to the expected ones, but that could be implemented separately after we have a minimal working version.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status