Error loading in UMAP layer
See original GitHub issueHi there,
I am trying to create an h5ad file from a raw expression matrix, a metadata file and UMAP coordinates. I’m getting the following error loading in anndata.obsm[‘X_umap’]:
ValueError: value.index does not match parent’s axis 0 names
the index values for the UMAP tsv and the metadata file used to create .obs are exactly the same, so i’m not sure what’s causing this. I did run .var_names_make unique on the matrix, but from my understanding that doesn’t apply to the index column. let me know if anyone can help!
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Error loading in UMAP layer · Issue #525 · scverse/anndata
Hi there, I am trying to create an h5ad file from a raw expression matrix, a metadata file and UMAP coordinates. I'm getting...
Read more >How to Use UMAP — umap 0.5 documentation
First we will load the dataset from sklearn. digits = load_digits() print(digits.DESCR) .. _digits_dataset: Optical recognition of handwritten digits ...
Read more >umap-project/umap
I have a map with multiple layers. I want to share the map with others via a link, but only one layer should...
Read more >UMAP Error TypeError: a bytes-like object is required, not 'list'
I stumbled upon the same problem, the weird thing being that UMAP just stopped working on the data (same dataframe) overnight.
Read more >umap Documentation
therefore obviously need the umap module loaded. ... By default, Parametric UMAP uses 3-layer 100-neuron fully-connected neural network.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think this has actually been fixed on master, but not in a release yet. I could reproduce @rachadele’s error with 0.7.5, but not with the dev version.
This package could definitely use a bugfix release, so I’m aiming to do that over the long weekend.
Fixed in #461