lab00 : lab00 on basics, by Phill
|lab00||true||lab00 on basics, by Phill||Mon 08/01 09:30AM||Tue 08/02 05:00PM|
If you find typos or problems with the lab instructions, please report them on Piazza
Your first lab in SPIS
For your first lab, you’ll be using the computers in B230, a lab in the basement of the CSE building.
These computer run the Linux operating system, and you’ll log into them with your SPIS ACMS account.
Administrative one-time tasks for lab00
During this lab you will acheive the following administrative one-time steps
- Learn what your ACMS username/password for SPIS is
- Access your UCSD email account to get your invitation to Piazza
- Create an account on github.com using your UCSD email address
- Fill out a Google Form so that we know your github id
- Accept an invitation to the ucsb-cse-spis-2016 github organization
- Activate your Piazza account
After completing this lab, you should be able to
- Login to your SPIS ACMS account on the Linux Systems in B230 of the CSE Building
- Bring up a web browser on those machines
- Bring up a terminal window to access the “bash shell prompt”
- Bring up IDLE, the programming environment for Python
- Create a short Python program and run it
- Create a Github repository under the UCSD-CSE-SPIS-2016 organization
- Use the github web interface to upload files and edit text in a README.md file
Step 0: Obtain your ACMS username and password.
Before you can even sit down and begin using a workstation in B230, even to surf the web, you need to know your ACMS username and password.
And to obtain those, you’ll need to be able to access a web browser. Catch-22!
But if someone else (a mentor or instructor) has a web browser, then the information at this page can be used to lookup your ACMS username, and reset your password:
Once you know your username and password, please sit down at a workstation with your pair partner.
Step 1: Choose initial “driver” and “navigator”
During SPIS, we’ll be using Pair Programming, a system where two people collaborate on a single solution to a problem.
You will share a single workstation with your pair partner, and alternate being the “driver” and the “navigator”.
The “driver” is the one typing, and the “navigator” provides guidance to the driver as to what to do.
Please take a moment to visit this link and learn more about Pair Programming.
To “learn the do’s and don’ts” of pair programming and to see pairs in action, you may also want to check out this entertaining (if a bit corny/cheesey) video about pair programming from North Carolina State University: An Introduction to Pair Programming for Students.
Step 2: Log in and bring up web browser and a terminal
This step should be straightforward, but if you need assistance, ask a mentor or instructor for help.
Step 3: Visit github.com to create or update your account
Each pair partner should take a turn completing this step separately.
Open a web browser, and navigate to github.com.
At the github.com page, if you don’t already have a github.com account, using your UCSD email address, create one on the “free plan”.
Or, if you already have a github.com account, log in to it, and add your ucsd.edu email address to the list of email addresses associated with the account.
Then, fill out the following form to let us know what your github id is: https://goo.gl/forms/sgehc2hlH8pSkUEp1
Step 4: Bringing up IDLE
IDLE is the program we’ll use to do Python programming during SPIS.
In IDLE, you you create, edit, and run Python code.
To bring up idle, type
idle at the bash shell prompt.
For this step, there is one goal: write a Python 2.7 program that prints the string
Hello, World! as its output.
In this sense, we are following a long tradition: for more than 40 years it has been a tradition to make printing
Hello, World! be the first thing you do when learning a new programming language.
In Python, this program is very short. It looks like this:
print 'Hello, World!'
That’s it! Now, you can also add, on the first line, a comment with your name, your pair partner’s name, and the reason you wrote the program.
# Alex Triton and Chris La Jolla for CSE SPIS 2016 print 'Hello, World!'
You are encouraged to do that, because it helps someone looking at your code know that you wrote it. But, other than that, it isn’t necessary. In general, in computer programming, a comment is something that is intended only for human readers of the code, and is otherwise “ignored by the system”. Nearly every programming language has some way to express comments, though the exact rules for formatting of comments–that is, the syntax of comments–differs from one language to another.
In Python, a
# starts a comment. Everything from the
# to the end of that line is part of the comment.
As far as how to create, save and run this program in IDLE, it’s easier to just watch someone do it than to try to read an explanation. So, we’ll demonstrate this in Lecture. But if you need a refresher, this Youtube video explains Hello World in IDLE
Once you’ve run your “Hello World!” program, you are ready to move on to the next step.
Step 5: Accept invitation to UCSD-CSE-SPIS-2016 github organization
By now, the mentors/instructors should have inivited you to the UCSD-CSE-SPIS-2016 github organization.
You should find an place where you can accept this invitation if you click on this link and look near the top of the page:
Click on the invitation so that you are part of the ucsd-cse-spis-2016 organization.
Step 6: Create your first github repo, a practice repo.
Each pair partner should take a turn at this step.
Your next step will be to create a github repository or repo for short.
Your first repository will have a name that corresponds to your first name and last initial such as:
To create this repo:
In your web browser, navigate to https://github.com
Login to your github.com account, and
Then and find the button at upper right to create a repository.
- That button looks like a + sign with a triangle next to it.
- When you click that button, there are three choices. Select “New Repository”
On the next screen:
- Be sure that you select to create your repository with the owner being
ucsd-cse-spis-2016, NOT your own github id.
practice-alex-tas the name (BUT PUT YOUR OWN NAME AND FIRST INITIAL, not literally
- Click the box to create a
README.mdfile in the repo
- Select a
.gitignorefile for Python
- You don’t need to select a license file.
Then, once you’ve entered all of this information, click to create the repository.
After you’ve done that, logout of github.com, and let your pair partner take a turn doing the same thing.
Step 6: Add a message and a photo to your
For this step, please ask one of the mentors to take a photo of you, with your face and your name tag visible, and then email the photo to you.
- If you, your pair partner, or a fellow SPISer happen to have a phone with a camera and email capability, you can also just take the photo yourself.
Once you have the photo in your email, access your email from the web browser of the ACMS linux machine at which you are
seated. Save the photo (i.e. the .png, .jpg, or whatever) to a file. Depending on the browser you are using, this
file may end up in your “home directory”, or in some other directory (e.g.
Once you’ve located it, your next job will be to upload it to your github practice repository. We’ll discuss how in the next step.
Step 7: Upload your photo to your
Navigate to the web page for your repo. It will be something like:
except it will be your name instead of
On the right hand side, there is a great big green button labelled “Clone or Download”. Eventually, we’ll be using that button a lot. But for now, look just a few buttons to the left, and you’ll find a button that says “Upload files”.
Click that button, and upload your photo from the place where you saved it out of your email.
Once you’ve uploaded it, you should be able to change the name to
alex-t.png or whatever. You need to keep the .jpg or .png exactly as it is, but change the first part of the filename to match your first name and last initial, in lowercase, separated by a hyphen (
-). The naming convention is important, because the SPIS staff is going to access all of these images to create a SPIS photo album so that we can all learn your names more quickly.
Step 8: Edit your README.md file to add some information about you, and a link to your photo
Navigate again to the main page for your repo, e.g.
You’ll see a file called README.md. Click on the filename. This should take you a page for just that file, where you’ll see, among other things, a pencil icon that allows you to make changes to the file.
In that file, add a few lines of text that introduces yourself to the SPIS 2016 instructional staff. Tell us where you are from, some of things you are hoping to learn during SPIS, and perhaps some outside interests and activities you might like to participate in during our non-academic sessions (e.g. sports, musical instruments you play, board games, etc.)
Then, add the following, on a line by itself, with a blank line before it and after it.
Copying it exactly, except for changing the
alex-t.jpg part to whatever the name
of your image file is:
Save it, and take a look at your README.md file. You should see your photo embedded in the README.md text.
If so, you are finished with lab00!
Step 8: Piazza Invitation
Each pair partner should take a turn doing this step.
In your UCSD email you should find an invitation to Piazza. Please accept the invitation.
Then visit https://piazza.com to log in to Piazza
Find the UCSD CSE SPIS 2016 course and familiarize yourself with the Piazza site.
A note about assignment deadlines
SPIS will use a series of deadlines to help you stay on track with your work as well as to allow us to keep track of your progress.
Those deadlines are listed on the Calendar which is linked to from the navigation links at the top of the SPIS FOCS website (
Before each of these deadlines, please submit whatever you have completed on that assignment, following the instructions given. Sometimes this means submission via Gradescope. Other times, it may mean simply having your latest changes pushed to the appropriate repo on github.com.
You can also submit earlier if you like.
However, please know that while we want to encouage you to try to complete assignments by the given deadlines, if you find that you are working at a slower pace, just keep working. Because SPIS is not graded, it’s OK if you don’t get everything done, but we’d like you to do as much as you can. If you aren’t finished, submit what you have, but then keep working on the assignment as long as it is helping you learn the material.
Periodically, you’ll get feedback from your mentors and instructors about your progress on the assignments. Trying to stay ahead of the deadlines is good practice for the regular quarter, and it will help you get the most out of SPIS. But the most important thing is to work at the pace at which you will learn the material best.