Skip to content

Metrics as autosummary tables#4774

Closed
SkafteNicki wants to merge 8 commits intoLightning-AI:masterfrom
SkafteNicki:metrics/doc_update
Closed

Metrics as autosummary tables#4774
SkafteNicki wants to merge 8 commits intoLightning-AI:masterfrom
SkafteNicki:metrics/doc_update

Conversation

@SkafteNicki
Copy link
Copy Markdown
Collaborator

What does this PR do?

Reformat metric docs to use autosummary.
Requested by @tchaton on slack :]

Before submitting

  • Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
  • Did you make sure to update the documentation with your changes?
  • Did you write any new necessary tests?
  • Did you verify new and existing tests pass locally with your changes?
  • If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In in short, see following bullet-list:

  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?

Make sure you had fun coding 🙃

@SkafteNicki SkafteNicki added the docs Documentation related label Nov 19, 2020
@SkafteNicki SkafteNicki added this to the 1.1 milestone Nov 19, 2020
@codecov
Copy link
Copy Markdown

codecov bot commented Nov 19, 2020

Codecov Report

Merging #4774 (af2c631) into master (6e788d2) will increase coverage by 3%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #4774    +/-   ##
=======================================
+ Coverage      90%     93%    +3%     
=======================================
  Files         117     117            
  Lines        8968    8968            
=======================================
+ Hits         8084    8335   +251     
+ Misses        884     633   -251     

Copy link
Copy Markdown
Collaborator

@Borda Borda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we add screenshot of the new one?

@SkafteNicki
Copy link
Copy Markdown
Collaborator Author

Untitled

@SkafteNicki SkafteNicki changed the title [WIP] Metrics as autosummary tables Metrics as autosummary tables Nov 20, 2020
@jeffydc jeffydc added the ready to be merged PRs ready to be merged label Nov 20, 2020
Copy link
Copy Markdown
Contributor

@tchaton tchaton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @SkafteNicki, looks great ! Thanks !

Copy link
Copy Markdown
Contributor

@rohitgr7 rohitgr7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Just some comments.

SkafteNicki and others added 2 commits November 20, 2020 11:01
Co-authored-by: Rohit Gupta <rohitgr1998@gmail.com>
Co-authored-by: Rohit Gupta <rohitgr1998@gmail.com>
Copy link
Copy Markdown
Contributor

@williamFalcon williamFalcon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

before merging can i clarify something?

the metric summary tables remove the menus on the right that make it super easy to search for stuff without having to scroll endlessly through the page.

is that menu gone now?

if so, can we undo all these summary tables? they make quickly scanning to see what’s available impossible.

to see how useful this menu is, try finding any trainer flag. now imagine if the menu ok the right didn’t exist and you instead had to scroll the full page just to see what flags are available.

remember that our docs are as much about discovery as they are about referencing

@SkafteNicki
Copy link
Copy Markdown
Collaborator Author

The menu is not all gone, it still expands to the individual types of metrics:
Untitled2
If the user is aware what type of metric they are looking for (classification, regression, ect) I would argue that it requires much less scrolling now.

@williamFalcon
Copy link
Copy Markdown
Contributor

right. this is exactly what i think is not a great user experience.

we now remove the ability for the user to discover what is available by just glancing at the right since all the metrics are gone from the menu.

i also want to remove these tables from the rest of the docs.

this approach assumes people know what they are looking for but makes it impossible for people who are just browsing to see what’s available... and actually the menu on the right showing the list of metrics is much much faster to find the metric you are looking for.

@tchaton, @edenafek can we remove these tables from the docs and do it exactly like we do for trainer flags?

@tchaton
Copy link
Copy Markdown
Contributor

tchaton commented Nov 20, 2020

Hey @SkafteNicki,

After chatting with Will,
we thought it is better to keep the Metric as they are, but make the right slide panel bigger instead and take inspiration from Trainer.

I deeply apologise as you invested time working on this and it won't get integrated.
I will be very careful when suggesting this kind of changes in the future.

Best regards,
Thomas Chaton.

@SkafteNicki
Copy link
Copy Markdown
Collaborator Author

@tchaton it is completely fine, I did not spend that much time on this PR :]
Closing this pr.

@SkafteNicki SkafteNicki deleted the metrics/doc_update branch March 2, 2021 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation related ready to be merged PRs ready to be merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants