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

Add table of issue type info and relevant column name descriptions #1100

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

elisno
Copy link
Member

@elisno elisno commented Apr 15, 2024

Addresses #1081

This PR improves the Datalab Issue Types guide.

It adds a table for the different tasks that Datalab supports. It lists out the

  • Names of the issues it can find.
  • Whether it is searched by default (otherwise it's accessible via the issue_types argument in Datalab.find_issues().
  • A collection of relevant columns in the Datalab.issues dataframe.
  • A column that lists out what types of inputs to Datalab.find_issues() are required to successfully run the issue check.

Here's a screenshot of the table (still WIP):
image

@elisno elisno marked this pull request as draft April 15, 2024 23:28
@elisno elisno marked this pull request as ready for review April 17, 2024 18:54
Comment on lines +14 to +16
.. include:: table.rst


Copy link
Member Author

Choose a reason for hiding this comment

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

If the table is outside the scope of the PR, it should be enough to just remove this line so it won't appear in the docs.

@@ -56,6 +59,80 @@ To handle mislabeled examples, you can either filter out the data with label iss

Learn more about the method used to detect label issues in our paper: `Confident Learning: Estimating Uncertainty in Dataset Labels <https://arxiv.org/abs/1911.00068>`_

.. testsetup:: *
Copy link
Member Author

Choose a reason for hiding this comment

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

This testsetup block will be executed for all doctests blocks (..testcode), they just won't run the doctest until we set it up in CI.

Copy link
Member Author

Choose a reason for hiding this comment

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

These testsetup cells are not visible in the docs.

@@ -46,6 +46,7 @@
"sphinx.ext.napoleon",
"nbsphinx",
"sphinx.ext.autodoc",
"sphinx.ext.autosectionlabel",
Copy link
Member Author

Choose a reason for hiding this comment

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

This is added to allow us to link to local section headings.

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

Successfully merging this pull request may close these issues.

None yet

1 participant