@cvalenzuela pointed out that data currently lives in /docs/assets/, though it looks like /data mostly holds trained output or something and /img looks mostly like singular images. How does everyone feel about adding /datasets under /assets to hold entire datasets?
Since we are moving to a new github handle, maybe having a repo just for datasets can be useful
I'm game for a datasets repo! However, I wonder if having them in the "examples" repo would make sense -- do we imagine having datasets that don't pair with an example?
Maybe a repo with Training and Datasets would make more sense? moving the current /training folder to a separate repo makes sense to me
Also if you put datasets in a repo they could be included as a dependency in non-ML5 projects.
Sold! Should we call it:
??
+1 for ml5-data-and-training
I like that too! Or ml5-training-data, though ml5-data-and-training is a
little bit clearer.
On Tue, Mar 6, 2018 at 5:14 PM, Cristóbal Valenzuela <
[email protected]> wrote:
+1 for ml5-data-and-training
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ml5js/ml5-library/issues/85#issuecomment-370948168,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUjXMpnS1fyTNvuBs9Q0sXoKvcg2iyVks5tbwpBgaJpZM4Sdyw5
.
The repo is live! (@handav you should have admin privileges but feel free to add datasets via pull requests so we get notified. For simple and quick changes like README updates, etc. I think writing directly to master is a-ok! And happy to sit down and go through this with you of course.)
(Will leave this issue open until we move some of the data itself.)
All data has been moved!
I still have to put my dataset up though! I just have to weed out the ones that people tagged as being flawed, and then I'll get it up. Aiming to do that and the music LSTM by Thursday.
cool! we can follow this on #56 too.
Most helpful comment
Maybe a repo with Training and Datasets would make more sense? moving the current
/trainingfolder to a separate repo makes sense to me