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

Post analysis node size is disproportionate #187

Open
risserlin opened this issue May 9, 2017 · 3 comments
Open

Post analysis node size is disproportionate #187

risserlin opened this issue May 9, 2017 · 3 comments
Assignees
Labels
Milestone

Comments

@risserlin
Copy link
Contributor

I think that the post analysis gene set might not be filtered according to the dataset which is making a much larger set

@risserlin risserlin added the bug label May 9, 2017
@risserlin risserlin added this to the 3.0_release milestone May 9, 2017
@mikekucera mikekucera self-assigned this May 10, 2017
@risserlin
Copy link
Contributor Author

@veroniquevoisin would like to keep the node size to reflect the size of the post analysis set including the genes that are not in any dataset so the user can see what overlapped and what didn't.

This works fine with a post analysis set that is ~500 but for sets that contained 1000s of genes it might not be.

Maybe a feature to hide genes not in dataset would be helpful.

@mikekucera
Copy link
Contributor

It looks like in EM2 the size of a signature gene set node is constant (in fact the gene set size attribute is blank).

How should it work in EM3? Options:

  • Constant size like EM2
  • Size of signature set
  • Size of signature set after filtering out genes not in the base EM

@veroniquevoisin
Copy link

veroniquevoisin commented Jun 2, 2017 via email

@mikekucera mikekucera modified the milestones: 3.0_release, 3.1_release Oct 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants