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

Example data and scripts not unified #132

Closed
MedericFourmy opened this issue Feb 16, 2024 · 2 comments · Fixed by #139
Closed

Example data and scripts not unified #132

MedericFourmy opened this issue Feb 16, 2024 · 2 comments · Fixed by #139

Comments

@MedericFourmy
Copy link
Collaborator

There are 2 ways to download the "crackers" example:

Those two have confusingly slightly different structures.

Should we remove one of them?
Or both and keep only the barbecue-sauce example?

@nim65s
Copy link
Collaborator

nim65s commented Feb 16, 2024

The structure of those examples (if we have multiple ones) should be unified.
I think using the script to download the data is better than providing manual instructions

@MedericFourmy
Copy link
Collaborator Author

I agree with both, it's even simpler to keep only the barbecue-sauce example that has a more complete set of data (bounding box detection, depth).

@MedericFourmy MedericFourmy changed the title Confusing crackers Example data and scripts not unified Feb 19, 2024
@MedericFourmy MedericFourmy linked a pull request Feb 21, 2024 that will close this issue
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 a pull request may close this issue.

2 participants