Expand Benchmarks Doc to Include Dataset Utils
See original GitHub issueAt the moment the focus in the benchmark chapter is on the benchmarks. However, I think we should better expand the doc about the support we give to the datasets and dataset creation.
In particular we should expand the discussion about the AvalancheDataset
and related utils which offer a lot of goodies on top of basic pytorch datasets we should include.
Many users may be particularly interested in how to create a pytorch or avalanche dataset from their different data format and how to add transformations. IMHO this should be the main focus of the doc improvement.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Loading methods - Hugging Face
List all the datasets scripts available on the Hugging Face Hub. ... They define the citation, info and format of the dataset, contain...
Read more >github/CodeSearchNet: Datasets, tools, and benchmarks for ...
CodeSearchNet is a collection of datasets and benchmarks that explore the problem of code retrieval using natural language. This research is a continuation ......
Read more >torch.utils.data — PyTorch 1.13 documentation
At the heart of PyTorch data loading utility is the torch.utils.data.DataLoader class. It represents a Python iterable over a dataset, with support for....
Read more >Performance Comparison of Dimension Reduction ... - UMAP
For this performance comparison we'll default to the now standard benchmark of manifold learning: the MNIST digits dataset. We can use scikit-learn's ...
Read more >Updating dataset properties | BigQuery - Google Cloud
Update default table expiration times · In the Explorer panel, expand your project and select a dataset. · Expand the more_vert Actions option...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think they should be “How-To Guides” more than tutorials. Tutorials are learning oriented (FZTH), while how-to guides are problem-oriented.
What about creating a new section “Additional Tutorials” addressing some specific topics (maybe something we realize is a strong need and recurrent question)? Would that work for you?