(WIP) TFDSv4 Migration Robust Documentation#1859
Open
jprokos26 wants to merge 23 commits intotwosixlabs:tfdsv4from
Open
(WIP) TFDSv4 Migration Robust Documentation#1859jprokos26 wants to merge 23 commits intotwosixlabs:tfdsv4from
jprokos26 wants to merge 23 commits intotwosixlabs:tfdsv4from
Conversation
… branch to original repo
…ng shapes of examples to highlight dimensions prior to any preprocessing
…uctured each data section such that info about the dataset sits at the top separate from info about specific examples
…at split labels are not necessarily standardized - some splits are probably determined by the individual scripts that were copied and pasted in the process of building with tfds and uploading to S3
…o for carla_obj_det_dev
…mage examples for carla_over_obj_det_train
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right now it is very difficult to understand what the shapes of each dataloader/scenario/attack/exporter expect. This PR hopes to increase the verbosity of our documentation here - particularly to clarify issues like #1836 (comment).