Issues with ingest
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 779
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 27
Description
Hi all,
I am trying to use ingest to integrate different datasets.
I found a couple of issues.
-
ingestrequires that thevar_namesare the same in the reference and the new object. I can select the intersection between the datasets; however, it requires that the genes are in the same orderif not ref_var_names.equals(new_var_names). I think thisifcould be modified usingset(e.g.,len(set(ref_var_names).difference(set(new_var_names))) == 0). I tried to order the.vardataframe, but the.Xremains the same. In such a way, the expression of the genes does not correspond to the correct one. I can generate a dataframe and recreate the.X, but it could be very nice that the.Xwill be modified according to.varor.obsmodifications (i.e., ordering). -
although it is possible to set
embedding_method=umap,ingestrequires the PCA components. I used autoencoders instead of PCA, and I cannot runingestonly considering the UMAP. Can you fix it?
Thank you in advance.
Best,
Andrea
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the ingest entry point and its handling of var_names, .var, .obs, and .X. Reproduce the ordering case and the embedding_method=umap case, then verify that gene expression remains aligned and that ingest can use UMAP without PCA components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100