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
I think it would be good to have arguments giving some control over which features are moved to/ from shared mappings in the mudata object, as opposed to being anndata specific.
Decisions on copies vs views would be good as well.
Use cases
The main use case here is easing transition for libraries that only work with one of the types. I think it would also make it much easier to play around with which representation fits a particular use case better.
It also does a good job of advertising the connectedness of the objects, but that's very secondary.
The text was updated successfully, but these errors were encountered:
The API should come in v0.3. As the split_by PR hasn't been merged, the to_mudata functionality might be a bit basic but should cover the main use case.
gtca
linked a pull request
Sep 11, 2023
that will
close
this issue
I'd like to propose some utility methods for converting back and forth between MuData and AnnData objects.
Implementations would look something like:
With
split_by
being: scverse/anndata#613Additional needs
I think it would be good to have arguments giving some control over which features are moved to/ from shared mappings in the mudata object, as opposed to being anndata specific.
Decisions on copies vs views would be good as well.
Use cases
The main use case here is easing transition for libraries that only work with one of the types. I think it would also make it much easier to play around with which representation fits a particular use case better.
It also does a good job of advertising the connectedness of the objects, but that's very secondary.
The text was updated successfully, but these errors were encountered: