-
Notifications
You must be signed in to change notification settings - Fork 95
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
[DOC] Reporting documentation #465
Conversation
enh:initial commit of dynamic plots
Codecov Report
@@ Coverage Diff @@
## master #465 +/- ##
=======================================
Coverage 93.53% 93.53%
=======================================
Files 26 26
Lines 1965 1965
=======================================
Hits 1838 1838
Misses 127 127 Continue to review full report at Codecov.
|
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.
Only reviewed docs instead of code since I'm not familiar with the python-JS cross-talk employed with this PR.
docs/reporting.rst
Outdated
------------------------- | ||
This view provides detailed information about an individual | ||
component (selected in the summary view, see below). It includes three different | ||
interactive plots. |
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.
So should we just not list the plot as interactive?
Co-authored-by: Joshua Teves <[email protected]>
Co-authored-by: Joshua Teves <[email protected]>
Thank you so much for the review @jbteves ! I'm not sure I understand what you mean by this though: "So should we just not list the plot as interactive?" I added a link to the OHBM demo to the very top of the reporting page, so people can play around with it. The images in the docs are all static. |
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 again, @eurunuela and @javiergcas ! I think this will be a huge help to users.
I've made a few comments / suggestions to bring the docs in line with the current reporting functionality.
The image below shows a representative report, which has two sections: a) the summary view, | ||
and b) the individual component view. | ||
|
||
.. image:: /_static/rep01_overallview.png |
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.
I don't think this reflects the state of the reports any more, unfortunately, since we removed the individual component view. The figure should be updated
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.
1b59407 should take care of this.
I included the individual component view section in the end, as we do show a static view of individual components.
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.
That looks right, thanks !! Should we note that the individual component view will be empty by default, since no component is pre-selected ?
|
||
* **Kappa Scree Plot:** This scree plots provides a view of the components ranked by `Kappa` | ||
As in the previous plot, each dot represents a component. The color of the dot inform us | ||
about classification status. In this plot, size is not related to variance explained. |
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.
Should we explain what the axes are ?
docs/reporting.rst
Outdated
========================= | ||
|
||
As previously mentioned, all plots in the report allow user interactions. The list of permitted | ||
interactions vary by plot, but can be easily infered by the toolbar that accompanies each plot |
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.
In the current view, the toolbar is only on the Kappa-Rho plot, so we likely need to rephrase this section accordingly.
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.
1b59407 should take care of this.
Co-authored-by: Elizabeth DuPre <[email protected]>
Co-authored-by: Elizabeth DuPre <[email protected]>
Co-authored-by: Elizabeth DuPre <[email protected]>
Co-authored-by: Elizabeth DuPre <[email protected]>
docs/reporting.rst
Outdated
:align: center | ||
:height: 150px | ||
|
||
.. note:: |
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.
This is what I was thinking of 😸 Maybe let's move it up around L19 ?
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.
Yes! That's a great idea. Thank you!
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.
One small suggestion from me, and I think this looks great. Thanks again !
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.
Found a few typos, but otherwise looks good with the continuous-docs render.
Co-authored-by: Joshua Teves <[email protected]>
Co-authored-by: Joshua Teves <[email protected]>
Co-authored-by: Joshua Teves <[email protected]>
Thank you! I thought I had already corrected those. |
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.
LGTM, thanks @eurunuela and @javiergcas !
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.
LGTM ! 🚀 Merging now. Thanks again !!
Closes None.
Changes proposed in this pull request: