Skip to content

Lesson 2: Help session

Lesson recap

In this lesson, the following were accomplished.

  • We obtained an understanding of limitations to tasks that we can perform in the various Biowulf spaces such as
    • Log in versus compute nodes
    • Home, data, and scratch directories
  • Explored the Biowulf user dashboard
  • We started to learn how to navigate Biowulf by
    • Checking the present working directory (pwd)
    • Listing directory content (ls)
    • Moving to different directories (cd)

Practice questions

Question 1:

What are some of the information that we can find from the Biowulf user dashboard?

Solution

  • Group affiliation
  • Disk storage usage and request storage quota increase for the user's data directory
  • Information on submitted jobs

Question 2:

True or False: Upon logging into Biowulf, we land in a compute node where we can start to do compute intensive tasks.

Solution

False. Upon logging into Biowulf, we are taken to the login node where we can do the following

  • Submit jobs
  • Edit/compile code
  • Manage files
  • Transfer files
  • Briefly test code

Question 3:

True or False: We should store our data and analysis outputs in our Biowulf home directory.

Solution

False. A user's home directory is only 16 GB in size and cannot be increased. The home directory is meant for storing config files, code, state files, cache, etc. Store data and analysis output in the data directory.

Question 4:

True or False: We are doomed if we removed something that should not be removed.

Solution

False. We can try to restore from the user's snapshot.

Question 5:

What command do we use to check which directory we are currently in on Biowulf?

Solution

pwd

Question 6:

What command do we use to view the content of a directory in Biowulf?

Solution

ls

Question 7:

What command do we use to navigate to different directories in Biowulf?

Solution

cd