scverse / scverse/scanpy

ingest after bbknn produces poor results

Open
#1,833 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Question
Dominant language
Python
Stars
2.6k
Forks
779
Avg merge
1d 4h
Merged PRs (30d)
27

Description

Hi,
I tried ingest using the reference made with BBKNN. As @ivirshup said, ingest was worked by adding adata_ref.uns['neighbors']['params']['metric'] = 'euclidean'. However, the result was quite poor.

image

In contrast, if I merge all datasets (eg references and query), it worked well, but when we want to take over the reference embedding, I actually want to use ingest rather than run bbknn again. Is there any option to feed in this case? or should I ask this in the BBKNN repo?

image

This is the notebook can reproduce the problem.
https://nbviewer.jupyter.org/github/yyoshiaki/ingest_after_bbknn/blob/main/notebook.ipynb
https://github.com/yyoshiaki/ingest_after_bbknn/blob/main/notebook.ipynb

Originally posted by @yyoshiaki in https://github.com/theislab/scanpy/issues/1122#issuecomment-838476193

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running notebook.ipynb from the linked ingest_after_bbknn repository to reproduce the poor ingest result, then inspect how the BBKNN reference and its neighbors parameters are passed to ingest. Done means establishing whether this combination is supported and recording a reproducible fix or limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
bioinformatics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.