Amy and I figured out after the video that the reason I couldn't see the screen
after logging in again is that the screen instance is connected with the
particular vm that you're ssh'd into when you run the screen command.

So, when you login to the hw server, you'll see something like:

# (here matt@... is my home system)
matt@DESKTOP-L0J06D1: ssh mrussell@homework.cs.tufts.edu

# now logged in to halligan homework server
vm-hw00{mrussell}182:

# you should then login to red-giant, by typing something like:
vm-hw00{mrussell}182: ssh mrussell@red-giant.cs.tufts.edu

# now you'll see something like
dell27{mrussell}182:

if you run the screen command here, then detach (ctrl+a, d) and exit the hw
server completely, you'll have to ssh back to that vm to access the screen'd
shell.

in other words, you ssh back to the hw server, and then do the following:

vm-hw04{mrussell}182: ssh mrussell@dell27.cs.tufts.edu

Note that you don't really have to do this unless you want to check up on
whether your processes have finished, or to kill the screen sessions.

Please post on piazza with any more questions!

Thanks, as always,
Matt