Closed jmsmkn closed 7 years ago
Hi, sorry that the documentation is a little bit confusing, we are working on updating it. There are two things:
--data SyccinddLDdS7p3vzcwGQ2:foo --data Gbya2j64ApqjSHt3vDpdSh:bar
. Then you should be able to access them at "/foo" and "/bar" directory.We will be releasing a new documentation this week to clarify this.
I've seen that single data sets can have mountpoints again too, thank you for fixing it so quickly!
Three problems here:
/input
and not/<ID>
In the docs it shows us how to mount datasets to specific directories, but doing this with the CLI results in an error. If we take for example, the public kaggle cats and dogs dataset with id:
SyccinddLDdS7p3vzcwGQ2
Command:
$ floyd run --data SyccinddLDdS7p3vzcwGQ2:dataset
Expected output: The experiment launches with the data mounted at
/dataset
Actual output:
If I take away the
dataset
key it works:However, the dataset is not mounted at
/<ID>
as stated in the docs, but at/input
. On the instance, the data is there:Now, if I add a second dataset, say the public MNIST dataset with ID
Gbya2j64ApqjSHt3vDpdSh
, this gets mounted at/input
, and takes precedent over the first dataset (so I never actually have access to theSyccinddLDdS7p3vzcwGQ2
data):Then on the instance:
Note that
test
andtrain
from the kaggle dataset is missing.System info: floyd-cli 0.9.9, Python 3.5, see #51