Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QUESTION] How can non-overlapping embeddings be handled smoothly? #2659

Open
nictru opened this issue Feb 22, 2024 · 0 comments
Open

[QUESTION] How can non-overlapping embeddings be handled smoothly? #2659

nictru opened this issue Feb 22, 2024 · 0 comments
Labels
question request for help/clarification

Comments

@nictru
Copy link

nictru commented Feb 22, 2024

In my use case, there is one embedding for all cells and multiple embeddings for subsets of cells, which are non overlapping and of various sizes. Let's assume a structure like this:
Embedding A: 100 cells
Embedding B: 50 cells
Embedding C: 10 cells

After using the embedding switcher to cycle through the embeddings and going back to A, I now have A: 10 out of 50 cells, with no straightforward option to undo this. A hacky solution is to click the subset and undo subset buttons, which basically removes the history of visited embeddings and thus makes all cells in A active again. I don't think this is a great solution.

I have been digging through the source code a bit today, and found out that basically for all embeddings (dimensions) that have been visited, the intersection is built here. I was able to prevent the creation of a history of visited embeddings by commenting out this line.

So now my question is:
Why does it make sense to build an intersection like this? Can this be solved in any other way?

I understand that this is a problem which would not come up if all embeddings have the same size, which is probably the case for most users.

@nictru nictru added the question request for help/clarification label Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question request for help/clarification
Projects
None yet
Development

No branches or pull requests

1 participant