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

INaturalist #5343

Open
Tracked by #5336
pmeier opened this issue Feb 3, 2022 · 2 comments
Open
Tracked by #5336

INaturalist #5343

pmeier opened this issue Feb 3, 2022 · 2 comments

Comments

@pmeier
Copy link
Contributor

pmeier commented Feb 3, 2022

cc @pmeier @bjuncek

@federicopozzi33
Copy link
Contributor

Hi @pmeier,

I'd like to work on this.

@pmeier
Copy link
Contributor Author

pmeier commented May 26, 2022

Hey @federicopozzi33 and thanks for the interest. Unfortunately, we are currently not looking for contributions on porting more datasets. We need to make sure that the new architecture works well in an end-to-end setting. For that we are still running benchmarks.

Furthermore, torchdata is in the process of introducing a new data loader: https://github.com/pytorch/data/tree/main/torchdata/dataloader2. Before that is not stable-ish, we cannot run our own reference scripts and thus have little idea if our current dataset design is sufficient or not.

If all these blockers are resolved, we will happily accept a PR porting this dataset to the new API. I'll ping you here when this is the case and if you are still interested then, you can pick it up.

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

No branches or pull requests

3 participants