You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Super nice to have this code here. I will probably spend much more time with it, but at first I tried to see simply if it will run on my laptop. Your docker one-liner does eventually give the /workspace prompt, though I'm not sure where to go from there, if some data is already in or not. At least I did discover the scripts are meant to run from inside /workspace ,I thought some of them might be useful straight after cloning the repo but not. I am not entirely sure what black magic you've done but I should probably study it and copy it for my own "reproducible" ML experiments.
It would be nice if someone who's more in touch with the tech did a couple of walkthroughs and even timed them, so we would know if we're on the right path or not!
The text was updated successfully, but these errors were encountered:
Hi @c0demon ,
Thank you for your question. The data are not in the docker - they are included in the repository. You will need to pull the docker image and this repo to make it work.
The docker one-liner appends a /workspace to all paths - so it initiates you at root directory '/'. To run the code, go to /workspace/path/to/repo' and run bash bash/task_train.sh`.
Super nice to have this code here. I will probably spend much more time with it, but at first I tried to see simply if it will run on my laptop. Your docker one-liner does eventually give the /workspace prompt, though I'm not sure where to go from there, if some data is already in or not. At least I did discover the scripts are meant to run from inside /workspace ,I thought some of them might be useful straight after cloning the repo but not. I am not entirely sure what black magic you've done but I should probably study it and copy it for my own "reproducible" ML experiments.
It would be nice if someone who's more in touch with the tech did a couple of walkthroughs and even timed them, so we would know if we're on the right path or not!
The text was updated successfully, but these errors were encountered: