GithubHelp home page GithubHelp logo

Automated data downloading about fuel HOT 4 CLOSED

mila-iqia avatar mila-iqia commented on June 18, 2024
Automated data downloading

from fuel.

Comments (4)

vdumoulin avatar vdumoulin commented on June 18, 2024

Here's an idea: we could require that all datasets provide a list of files in the $FUEL_DATA_PATH root directory which they need as their data source along with checksums for these files. Optionally, the datasets could also point to a method that can be used to retrieve missing files.

We would then write a module that checks whether all required files for a given dataset are available, and do one of the following:

  • If all files are present and their checksums check out, everything's fine.
  • If some existing files' checksums do not check out, rename them (e.g. by appending ".old") and attempt to re-download them.
  • If some files are not present, attempt to download them.
  • If there's not script provided to download missing or damaged files, raise an error.

Some of the module's behaviour could be configured. For instance, files that do not check out could raise a warning without being re-downloaded, and that warning could also completely be disabled.

from fuel.

bartvm avatar bartvm commented on June 18, 2024

I think that pretty much covers everything. I agree that it's important that everything should be configurable: Whether datasets should be automatically downloaded, whether or not to accept files when the checksum doesn't match, etc.

Downloading should be pretty straightforward with e.g. the requests library. For some datasets we might want to have checksums without being able to provide a download source though (e.g. for datasets that aren't public, like Penn Treebank).

One question to raise is whether we should also automatically process the data. For MNIST we can just read the image files directly, because there is little overhead, but for larger image datasets it might make sense to load them into an HDF5 file once, and from thereon read that file instead. Should we do that automatically? It might be harder to checksum these files, because a different h5py version might just result in a different file.

from fuel.

vdumoulin avatar vdumoulin commented on June 18, 2024

Are fuel-download and fuel-convert considered sufficient to solve this issue, or do we still want fully-automated downloading?

from fuel.

bartvm avatar bartvm commented on June 18, 2024

Nope, I think this is good enough. Doing everything automagically just makes things needlessly complicated (e.g. what if you launch multiple jobs and they all start downloading simultaneously, or it might just end up downloading things whenever you set the data path incorrectly).

from fuel.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.