-
Notifications
You must be signed in to change notification settings - Fork 317
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
Mutational signature plot with cosmic reference signature #4771
Mutational signature plot with cosmic reference signature #4771
Conversation
@inodb this PR should extend the current mutational signature plot with the cosmic reference. Maybe we can update the current mutational signature plot after code review on the private instance (for the pancan study)? |
e52e1b7
to
6a27001
Compare
6a27001
to
cc6755d
Compare
@TJMKuijpers Looks great! Product feedback
Other thoughts:
Code ReviewThe cosmic reference files are stored directly in the frontend. That seems ok, as it's only 9.9MB and they stay pretty static:
We also have some other reference files that are stored in the repo:
Just wondering if we should organize this a bit better, so it's clear both of these use a similar mechanism (e.g. they are stored in some shared |
6104ab1
to
d48fa60
Compare
✅ Deploy Preview for cbioportalfrontend ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
93200a6
to
30511e0
Compare
Thanks @TJMKuijpers ! One more minor thing:
Other thoughts:
|
Thanks @TJMKuijpers I agree with Ino's comments above. Some other thoughts:
|
I agree with Ino & Niki's comments, and have a few additional notes:
|
@inodb I'm able to download the plot as PDF in Chrome, Brave and FireFox. Is this a Safari issue? |
how to switch samples for a patient with multiple samples, e.g. this one. The sample selector disappears when not all samples are profiled for mutational signatures (which is the case for DO46329). I added a banner to make this more clear. |
I think it does make sense if you want to compare the sample profile versus the reference profile. I think it would be more difficult to compare the two if the y-axis match the data (for example when sample mutational profile is between 0-50% and the reference plot between 0-10%) |
b31781b
to
3e433b2
Compare
updated progress bar tooltip Fixed change version error Update color signature class unknown Updated the labels to COSMIC style Change spacing between the plot and reference Updated the data store Updated bar chart and table Updated mutational signatures table Fixed highlighting of the mutational signature table Updated click behavior table Revmoved commented code Removed unnecessary imports updated number of top signatures Removed spaces Update with community feedback Update mutational signature plot with new tooltip and annotation Removed <text> tag Updated bar chart Align contribution values in table to the right Update the indel label with counting from 1-6+ for insertion and microhomology Update the MutationalSignatureBarChart test SBS labels COSMIC style format Bar width responsive to screen size Updated d3 scaleBand to scalePoint Updated screenshot Updated the tooltip to show significant signatures Updated tooltip significant mutational signatures Updated the tooltip, Sample not profiled banner label padding and theme
3e433b2
to
f3937f4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much for fixing all the feedback! Great job! Updated some localdb screenshots, will merge shortly
This PR adds the cosmic reference signatures to the mutational signature plot. This will add a new graph to the existing mutational signature graph to show the percentage of a mutation (SBS, DBS, or ID) in a signature of interest.
It also fixes the following issues:
selectedSignature
--> empty string is not a good default value is fixed.Checks
Any screenshots or GIFs?
If this is a new visual feature please add a before/after screenshot or gif
here with e.g. Giphy CAPTURE or Peek
Notify reviewers
Read our Pull request merging
policy. It can help to figure out who worked on the
file before you. Please use
git blame <filename>
to determine thatand notify them either through slack or by assigning them as a reviewer on the PR