Metadata Processing #113
orenbenkiki
started this conversation in
Ideas
Replies: 3 comments 2 replies
-
Additional thoughts:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
DAF point of view would be to have everything in one dataset and MCView on top of it. We'll need to discuss. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is a big topic. Main issue is per-cell metadata.
Functionally, we need to project the per-cell metadata to per-metacell metadata in one of several ways:
Note we can compute several same per-metacell properties for the same per-cell property.
(The MC2 python package has functions that do this)
Main options:
metacells.h5ad
. Downside: Create a process where someone can go back to MC2, compute additional per-metacell properties, and export just them into MCView.metacells.h5ad
) - this is just per-cell data, not the per-cell-per-gene data, so it isn't too bad. Then within MCView, allow the user to create the projections he needs.Usage:
Either way, MCView should allow visualizing the per-metacell annotations (on the UMAP) and possibly also allow using them for thing-thing projections (where "thing" could be either a gene or a per-metacell property) and for thing-on-UMAP projection (where "thing" could be either a gene or a per-metacell property). This would allow selecting groups of metacells using properties as well as (and in combination of) genes.
Beta Was this translation helpful? Give feedback.
All reactions