Overview / Reminder

• Work in small groups (we’re in a different room and space is different; you may need to adjust groups)
• Studios are a time to explore the material and refine your understanding.
  • You should NOT “divide and conquer” to complete all of the studio. The time is meant for improving your understanding.
• You should ensure that everyone in your group contributes to and benefits from the work.

Artifacts for this studio

Complete the code.

Studio Setup

1. Everyone should log in to GitHub using the ID you want to use for the course.
2. Designate one member of your group to “create a team”.
3. The designated “group creator” should:
   1. Navigate to link
   2. Select their WUSTL Key from the list
      
   3. They should create a team name that starts with the studio name (s4b) followed by the last name of each member of your team separated by dashes, like s4b-hu-perez-smith if the last names of your group members are Hu, Perez, and Smith.
      
   4. They should “Accept the assignment”.
      
   5. The “group creator” should follow the link to the new repository for the group:
      
4. Other members of your group should now:
   1. Navigate to link
   2. Select their WUSTL Key from the list.
   3. Select and join the group that was created in the last step.
5. We’ll be using a Codespace for today’s studio. You should work from a single computer. (Perhaps the “Group creator”)
6. Create a code space from the repository:
   

Overview of Window

The primary areas of interest in the Codespace are:

1. The editor area, where we will enter our Verilog code.
2. The File Explorer, where we will select files and tasks. (Be sure it’s selected from the Activity Bar on the left by clicking on the icon that shows a stack of papers)
3. The “Problems” panel. Be sure it’s selected.
4. The Task Explorer panel within the File Explorer.

Submission / End-of-class

Discuss your work/findings with TAs/instructors.