Skip to content

Adding camvid dataset - #402

Open
bordesf wants to merge 7 commits into
mila-iqia:masterfrom
bordesf:master
Open

Adding camvid dataset#402
bordesf wants to merge 7 commits into
mila-iqia:masterfrom
bordesf:master

Conversation

@bordesf

@bordesf bordesf commented Sep 14, 2017

Copy link
Copy Markdown

Hi,
I am starting doing some research on image segmentation. So, I was thinking that it could be useful for everyone to add those datasets on fuel. Here we have the camvid dataset [Camvid]. Currently this dataset is only available on a github page (https://github.com/alexgkendall/SegNet-Tutorial/tree/master/CamVid). I was thinking to create a zip file and upload it on the web, in order to make it downloadable by fuel (After asking the permissions of the authors). Is there any ftp server where I could upload it eventually ?

[Camvid] http://mi.eng.cam.ac.uk/research/projects/VideoRec/CamVid/

@charlesreid1

charlesreid1 commented Oct 15, 2017

Copy link
Copy Markdown

Hello,

I am also interested in this data set, and several others that aren't in the fuel examples directory. A few questions/comments.

Questions for fuel maintainers:

The SegNet tutorial and (presumably) CamVid data set the OP linked to are released under a CC non-commercial license. Fuel is released under an MIT license, which is incompatible (allows commercial usage). But since the data itself is not being hosted in fuel, is this a problem? Do the maintainers of fuel have a policy about what kind of license a data set must be released under to include it as an example?

It seems like it is a slippery slope to start adding many data sets to the examples, unless the repository maintainers intended the fuel repo to become a catalog of data sets. I believe the examples are intended to illustrate how to create your own loaders/converters in fuel. Is this a correct interpretation, or do you welcome PRs with new data sets?

Question for maintainers/regular fuel users:

What is the recommended workflow that folks should use to share their own fuel loaders/converters for popular datasets that don't make it into the fuel examples directory - should the fuel repo be forked? Or should we create an external package like camvid_fuel that imports fuel and then defines some loaders/converters, and can then be used like import camvid_fuel; X_train, Y_train = camvid_fuel.load_data()?

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 this pull request may close these issues.

2 participants