-
Notifications
You must be signed in to change notification settings - Fork 138
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
[WIP] Add new docs with Sphinx (.md) #885
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #885 +/- ##
===========================================
- Coverage 78.49% 78.49% -0.01%
===========================================
Files 206 206
Lines 24939 24939
Branches 5007 5007
===========================================
- Hits 19577 19575 -2
- Misses 4236 4237 +1
- Partials 1126 1127 +1
Flags with carried forward coverage won't be shown. Click here to find out more. see 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
datum export --format tf_detection_api -- --save-images | ||
|
||
- Annotate MS COCO dataset, extract image subset, re-annotate it in | ||
`CVAT <https://github.com/openvinotoolkit/cvat>`_, update old dataset: |
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.
we may be possible to remove re-annotate part in CVAT
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.
Is there a reason you want to delete the re-annotate part? It explains how to update the new annotation in Datumaro, and I think it's good to have one. e.g., datum project update reannotation-upd
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.
We agreed to merge the doc-related PRs to docs-rework
branch first, don't we?
docs/source/docs/get-started/quick-start-guide/installation.rst
Outdated
Show resolved
Hide resolved
docs/source/docs/reference/jupyter_notebook_examples/generate.rst
Outdated
Show resolved
Hide resolved
docs/source/docs/reference/jupyter_notebook_examples/filter.rst
Outdated
Show resolved
Hide resolved
docs/source/docs/reference/jupyter_notebook_examples/transform.rst
Outdated
Show resolved
Hide resolved
docs/source/docs/reference/jupyter_notebook_examples/validate.rst
Outdated
Show resolved
Hide resolved
docs/source/docs/reference/jupyter_notebook_examples/visualizer.rst
Outdated
Show resolved
Hide resolved
Yes, but the work in the form of the previous copy was already in progress there, so I got confused and took a branch again from the latest develop. You can also delete the existing docs-rework branch and rename it to that one. |
To exclude 'tab-in-indent' error from whitespace checking on Makefile
…into sphinx-docs-rework
…it/datumaro into sphinx-docs-rework
<!-- Contributing guide: https://github.com/openvinotoolkit/datumaro/blob/develop/CONTRIBUTING.md --> ### Summary ![image](https://user-images.githubusercontent.com/89109581/229419480-c4835066-9253-4a48-8a98-6630e951c34b.png) <!-- Resolves #111 and #222. Depends on #1000 (for series of dependent commits). This PR introduces this capability to make the project better in this and that. - Added this feature - Removed that feature - Fixed the problem #1234 --> ### How to test <!-- Describe the testing procedure for reviewers, if changes are not fully covered by unit tests or manual testing can be complicated. --> ### Checklist <!-- Put an 'x' in all the boxes that apply --> - [ ] I have added unit tests to cover my changes. - [ ] I have added integration tests to cover my changes. - [ ] I have added the description of my changes into [CHANGELOG](https://github.com/openvinotoolkit/datumaro/blob/develop/CHANGELOG.md). - [ ] I have updated the [documentation](https://github.com/openvinotoolkit/datumaro/tree/develop/docs) accordingly ### License - [ ] I submit _my code changes_ under the same [MIT License](https://github.com/openvinotoolkit/datumaro/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. - [ ] I have updated the license header for each file (see an example below). ```python # Copyright (C) 2023 Intel Corporation # # SPDX-License-Identifier: MIT ```
<!-- Contributing guide: https://github.com/openvinotoolkit/datumaro/blob/develop/CONTRIBUTING.md --> ### Summary <!-- Resolves #111 and #222. Depends on #1000 (for series of dependent commits). This PR introduces this capability to make the project better in this and that. - Added this feature - Removed that feature - Fixed the problem #1234 --> ### How to test <!-- Describe the testing procedure for reviewers, if changes are not fully covered by unit tests or manual testing can be complicated. --> ### Checklist <!-- Put an 'x' in all the boxes that apply --> - [ ] I have added unit tests to cover my changes. - [ ] I have added integration tests to cover my changes. - [ ] I have added the description of my changes into [CHANGELOG](https://github.com/openvinotoolkit/datumaro/blob/develop/CHANGELOG.md). - [ ] I have updated the [documentation](https://github.com/openvinotoolkit/datumaro/tree/develop/docs) accordingly ### License - [ ] I submit _my code changes_ under the same [MIT License](https://github.com/openvinotoolkit/datumaro/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. - [ ] I have updated the license header for each file (see an example below). ```python # Copyright (C) 2023 Intel Corporation # # SPDX-License-Identifier: MIT ```
Changes reviewed on the PR was applied #917 and merged. |
Summary
This PR contain the restructured documentation with Sphinx.
How to test
Checklist
License
Feel free to contact the maintainers if that's a concern.