4.3. Retrace and reenact

“Thanks a lot for sharing your dataset with me! This is super helpful. I’m sure I’ll catch up in no time!”, your room mate says confidently. “How far did you get with the DataLad commands yet?” he asks at last.

“Mhh, I think the last big one was datalad run. Actually, let me quickly show you what this command does. There is something that I’ve been wanting to try anyway.” you say.

The dataset you shared contained a number of datalad run commands. For example, you created the simple podcasts.tsv file that listed all titles and speaker names of the longnow podcasts.

Given that you learned to create “proper” datalad run commands, complete with --input and --output specification, anyone should be able to datalad rerun these commits easily. This is what you want to try now.

You begin to think about which datalad run commit would be the most useful one to take a look at. The creation of podcasts.tsv was a bit dull – at this point in time, you didn’t yet know about --input and --output arguments, and the resulting output is present anyway because text files like this .tsv file are stored in Git. However, one of the attempts to resize a picture could be useful. The input, the podcast logos, is not yet retrieved, nor is the resulting, resized image. “Let’s go for this!”, you say, and drag your confused room mate to the computer screen.

First of all, find the commit shasum of the command you want to run by taking a look into the history of the dataset (in the shared dataset):

# navigate into the shared copy
$ cd ../mock_user/DataLad-101
# lets view the history
$ git log --oneline
a1f2c3f add note on clean datasets
baf4fc5 [DATALAD RUNCMD] Resize logo for slides
a84115d [DATALAD RUNCMD] Resize logo for slides
66b01ae add additional notes on run options
3219d48 [DATALAD RUNCMD] convert -resize 450x450 recordings/longn...
8ffbc4a resized picture by hand
e8e2e95 [DATALAD RUNCMD] convert -resize 400x400 recordings/longn...
523a6b1 add note on basic datalad run and datalad rerun
c3623d0 add note datalad and git diff
c317c6f [DATALAD RUNCMD] create a list of podcast titles
2dd044a BF: list both directories content
4bf7418 [DATALAD RUNCMD] create a list of podcast titles
42387da Add short script to write a list of podcast speakers and titles
72f6a7d Add note on datalad clone
9bb3629 [DATALAD] Recorded changes
12ced25 add note on datalad save
63d50c8 Add notes on datalad create
8d3b831 add beginners guide on bash
393f24f add reference book about git
44aa3e2 add books on Python and Unix to read later
c74e2b7 Instruct annex to add text files to Git
dbaf9fa [DATALAD] new dataset

Ah, there it is, the second most recent commit. Just as already done in section DataLad, Re-Run!, take this shasum and plug it into a datalad rerun command:

$ datalad rerun baf4fc53bc1e2f68ab8d36ca56aa9b86f9b37482
[INFO] Making sure inputs are available (this may take some time) 
[WARNING] no content present; cannot unlock [unlock(/home/me/dl-101/mock_user/DataLad-101/recordings/salt_logo_small.jpg)] 
[INFO] == Command start (output follows) ===== 
[INFO] == Command exit (modification check follows) ===== 
get(ok): recordings/longnow/.datalad/feed_metadata/logo_salt.jpg (file) [from origin...]
remove(ok): recordings/salt_logo_small.jpg
add(ok): recordings/salt_logo_small.jpg (file)
action summary:
  add (ok: 1)
  get (notneeded: 1, ok: 1)
  remove (ok: 1)
  save (notneeded: 2)

“This was so easy!” you exclaim. DataLad retrieved the missing file content from the subdataset and it tried to unlock the output prior to the command execution. Note that because you did not retrieve the output, recordings/salt_logo_small.jpg, yet, the missing content could not be unlocked. DataLad warns you about this, but proceeds successfully.

Your room mate now not only knows how exactly the resized file came into existence, but he can also reproduce your exact steps to create it. “This is as reproducible as it can be!” you think in awe.