Trouble downloading the entire notebook and associated files of W2A1

I had successfully followed this guide to download the code for other assignments but failed to do so with W2A1.
The terminal that I open to download the files also looked a bit different and behave a bit strange. I was able to execute commands and the zip file wouldn’t appear after I go back to the browser. Anyone experience this issue?

1 Like

Sorry, I don’t have any experience with downloading the notebooks.

I took a look at those generic instructions from Coursera and the ones that they point to for the “Coursera Labs”. I think you’ll need to do some work to modify them to be successful with these courses. Notice for example, that the directory “~/work” that they refer to is not useful for our exercises here. You will need some linux shell skills in order to succeed at this, but once you have a terminal window try this to find where the files actually are:

find / -name "*.ipynb"

One other point is that this exercise has a symlink for the big h5 file containing the ResNet50 model. The tar command they give on the Coursera site does not “chase” symlinks, so you either have to make sure to copy the full file tree including the “tf-ro” subtree that contains the target of the symlink. Or use the “h” command to tar (as in “tar czhf …”) to automatically “chase” the symlinks and include the real file.

If anything I said there sounds mysterious, then please realize that this is beyond the scope of the course. This is not a course about how to use the linux shell. If you want to play these games, then you’ll also need to avail yourself of the training that is out there on the web on topics like that.

Hi Paul,
Thanks for the tips. I was able to download these files with your pointer to use the ‘find’ command. Somehow, ‘ls’ didn’t show the folders inside the work folder for this particular assignment. Maybe there’re something wrong with the permission? Anw, thanks again for the help!

No, it’s just that the folks who set up the Docker images for these notebooks chose to define the file tree structure differently. In other words, there is nothing magic about the directory “~/work”. I have no knowledge of the tools they use for authoring these notebooks and the corresponding Docker containers, so I don’t know if this is a choice they consciously made or just a side effect of the particular tools they chose to use. But in any case, if you know how to use the linux shell tools like “ls -R” and “find”, then you can find the subtree(s) that you need.