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

OncoPrint tooltip needs to indicate the altered gene in merged tracks #4493

Closed
schultzn opened this issue Jul 23, 2018 · 13 comments
Closed

OncoPrint tooltip needs to indicate the altered gene in merged tracks #4493

schultzn opened this issue Jul 23, 2018 · 13 comments

Comments

@schultzn
Copy link
Contributor

In a merged OncoPrint track, the tooltip should indicate which gene is altered.

We can consider to always show the gene symbol to make things simpler?

image

@jjgao
Copy link
Member

jjgao commented Jul 23, 2018

@fedde-s would you be able to help with this?

@jjgao jjgao added the frontend label Jul 23, 2018
@fedde-s
Copy link
Member

fedde-s commented Jul 23, 2018

This seems to be more of a feature request than a refactoring.

@fedde-s
Copy link
Member

fedde-s commented Jul 23, 2018

We designed it this way because the information on whether each individual gene is altered can be accessed by expanding the track (via the ⫶ track menu). Although for these sequence mutations, I agree that referencing the glycine at position 13 doesn't make a lot of sense.

@schultzn
Copy link
Contributor Author

I think the point is not having to expand the track - the tooltip should show which gene the mutations was found in.

@fedde-s
Copy link
Member

fedde-s commented Jul 23, 2018

Would that be only the most ‘significant’ alteration of a type, that determines the colour, or possibly a list of several genes that are all amplified? Currently the tooltips show all alterations relevant to a square, just like a single-gene square that displays alterations for all of a patient's samples would do.

@fedde-s
Copy link
Member

fedde-s commented Jul 23, 2018

The question I just asked might be a separate issue. Prepending the gene to each alteration is a pretty clear requirement. Although by “always show the gene symbol,” do you mean being consistent and doing that for single-gene tracks as well?

@jjgao
Copy link
Member

jjgao commented Jul 23, 2018

@fedde-s I think it'd be important to have the gene displayed. We missed it when reviewing it initially. Can you still help?

@adamabeshouse
Copy link
Contributor

@jjgao @schultzn it should be a very simple change. the tooltip generating function has access to the full mutation object which includes the gene. it wont take more than a few minutes of work, if you just want to show the gene for every mutation in the list (and we should also do this for other alterations, i.e. mrna, prot, cna). it would probably make sense only to show it in merged tracks, right?

@fedde-s
Copy link
Member

fedde-s commented Jul 24, 2018

Nice! I didn't remember the code well enough off the top of my head to know whether it would be trivial or slightly awkward. But indeed, the question still stands. Consistently for all tooltips, only for merged tracks, or consistently within Oncoprints that contain at least one merged track. The last option is probably the trickiest to implement.

@jjgao
Copy link
Member

jjgao commented Jul 24, 2018

It may be ok to always include gene symbol in the tooltip. @schultzn?

@schultzn
Copy link
Contributor Author

schultzn commented Jul 24, 2018 via email

@adamabeshouse adamabeshouse added this to the 1.15.0 milestone Jul 24, 2018
@fedde-s
Copy link
Member

fedde-s commented Jul 25, 2018

Could you make the PR, @adamabeshouse? I'm a bit busy at the moment, and you seem to recall exactly which line of code to change :)

@jjgao
Copy link
Member

jjgao commented Aug 7, 2018

@adamabeshouse thanks for the fix. Please also apply this to other data types (CNA, mRNA, protein).

image

Please also add a space after comma (,).

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants