Conversation
I noticed errors loading h5mu files from mudata==0.1.2 To generate the test files using this mudata version, uv can be used from within the data archive directory: `uv run create_testfiles.py` The concept of the data archive for legacy files has been modeled from the `anndata` repository.
Modeled after the anndata test for backwards compatibility. Checks if loading of all tests/data/archives/vxxx/mudata.h5mu files can be loaded.
This works around an issue with loading legacy .h5mu files where empty obsp/varp are stored as None instead or missing/empty dict. None values will be converted to emtpy dicts during loading. Fixes: scverse#91
|
PR #87 is required to fix the underlying build failure. Happy to rebase once this PR is merged. |
|
The testfile would be small and would have run as part of CI. If this kind of regression tests make sense depends on the scope of the project: if it is a priority that old (published?) mudata files should be readable by the latest version, tests like these would be valuable. |
|
Thanks, @votti, that's definitely in scope and will be valuable to have.
I am currently not sure we want to start including actual hdf5 files in contrast to generating them, which would not be executed by the CI (if I understand it correctly). We would then also need to include MuData files populated with different attributes beyond the simplest case with two modalities with no annotations. Let's continue discussing that in #92! |
Background
I noticed that mudata currently has issues to load legacy .h5mu files generated
by
mudata==0.1.2Changes
.h5mufrom mudata==0.1.2.h5mufrom mudata==0.1.2