feat: base without X_#4076
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #4076 +/- ##
==========================================
+ Coverage 79.74% 79.91% +0.16%
==========================================
Files 120 121 +1
Lines 12852 12928 +76
==========================================
+ Hits 10249 10331 +82
+ Misses 2603 2597 -6
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Are these the only two places that this is the case anymore i.e., prepend _X? It seems to have been done for PCA, but not UMAP:
scanpy/src/scanpy/tools/_umap.py
Line 147 in d96d91d
There was a problem hiding this comment.
My only real comment is both concrete and exploratory - I think stronger types make sense here regardless of what I say below (after all, it should be nicer than indexing into a tuple with an integer?).
Furthermore, if we have more strongly typed returns, we could also investigate differing key names more cleanly. So instead of the present controlling one central key i.e., adata.varm["pca"] and adata.obsm["pca"] being identical, it could control all the keys (maybe?). This is really high-level, but my motivating thought here is that the different keys currently have the nice property of being a bit more readable. For example, adata.varm["PCs"], while a little clunky, represents "principal components in gene space" meaningfully (compared to adata.varm["pca"]).
Thoughts?
I agree,
So the question boils down to:
Or did I miss something? |
This applies to diffmap too, for example: i.e., |
"X_"#3188TODO:
scanpy/src/scanpy/plotting/_tools/scatterplots.py
Line 858 in e6e9647
scanpy/src/scanpy/plotting/_utils.py
Line 1034 in e6e9647