Finding the experiment you want to work on in a complex project can be hard. To understand how to do it on DAGsHub, you should read the discovering experiments section.
The One Experiment
Once you've found the one (the experiment, not Neo), you want to get it on your working system to start contributing to it. DAGsHub and DVC make this easy.
Checking Out Experiments Using Git and DVC¶
We're assuming here that you already have a cloned repository on your local system. If not, then first follow the note below. We're also assuming you've discovered the experiment you'd like to start working on. If not, go back to the discovering experiments section.
Cloning the repository
Once you found the project you'd like to clone just copy the address in the top right side of the file view. Then, in a terminal pointing to the relevant folder you'd like to have the project in, type in
git clone <DAGsHub-repo-address>.
The clone address for the repository
Now, wherever you find the experiment, it has a unique ID, which is the commit hash. In the experiment view, this appears with a copy button next to it. This is important for what we'll do next.
A unique experiment ID, AKA Git commit hash
We're going to set up our local system to be on the specific experiment we want, and to start a new branch there, so that we can use it as a starting point for new experiments, and eventually contribute improved results back to the project.
To do this, we perform the following commands (after clicking the copy button on the unique experiment ID).
1 2 3 4
$ git checkout -b <myExperiment> <uniqueExperimentId> Switched to a new branch '<myexperiment>' $ dvc pull -r <projectRemote>
Now we're ready to start contributing to the project and trying out your own experiments, starting with the experiment we wanted.