Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Getting Started

Your COMP 521 computational workspace

This module gets one complete scientific-computing loop working on your own computer: navigate to a project, activate its Python environment, run a notebook, and save the result with Git.

Your first 10-minute success

Before installing anything, establish one small success in the terminal. Open the course terminal described in Chapter 1 and run:

pwd
cd ~
mkdir -p comp521_cli_practice/terminal-practice
cd comp521_cli_practice/terminal-practice
pwd

Success means the final command prints a path ending in comp521_cli_practice/terminal-practice. You have not installed software or changed a course repository; you have simply proved that you can navigate a workspace. Chapter 1 explains each command and gives you a longer practice task.

What to read, and when

Complete before class Thursday

Set aside about two hours for this route. Allow up to three hours if you are installing software from scratch or encounter a network delay. Start early enough to ask for help before you need Python and Jupyter in class.

Complete by Friday night

3. Git and GitHub

Accept and clone your assigned Project 1 repository, then push the required README setup commit. About 35–50 minutes after setup.

Use while writing Project 1

Keep beside you from Project 2 onward

Scientific software workflow checklist

A phase-aware pre-coding, debugging, and submission checklist. It is a working aid, not a grading rubric.

The Project 1 Repository Check

Due Fri Aug 28 at 11:59 pm PT. This completion-only check verifies that you can push to the Project 1 repository you will submit through Canvas. It does not assess Project 1 progress or Python skill.

  1. Use the Project 1 repository assigned through Classroom50, or create/use the individual repository you will link in the Canvas Project 1 assignment.

  2. Clone that repository and change into its directory.

  3. In README.md, change the repository-check box from [ ] to [x].

  4. Stage that README change, inspect it, commit, and push:

    git status
    git add README.md
    git diff --staged
    git commit -m "Complete Project 1 repository check"
    git push
  5. Open your P1 repository on GitHub and confirm that the commit is visible.

The complete repository-check contract and due date live on the Project 1 brief.

When an error appears

An error message is evidence, not a verdict on your ability. Preserve the exact text before trying fixes.

SymptomFirst checks
command not foundCheck spelling, whether the program is installed, and whether this shell can find it.
ModuleNotFoundErrorRun conda activate comp521, then confirm which Python is active.
No such file or directoryRun pwd and ls; verify the path one component at a time.
git push failsRead the exact reason; check git status, git remote -v, and whether you made a commit. Do not pull or force-push blindly.
A notebook uses the wrong kernelIn VS Code, select the comp521 kernel, restart, and run the cell again.

If the first checks do not resolve it, ask for help with:

Use the Canvas discussion board when the answer may help the class, Canvas Inbox for a private course matter, or bring the evidence to class or office hours. Follow the AI Use & Growth Mindset Policy if you use an AI tool for tutoring or error interpretation.

Ready means observable

Your laptop is ready for Thursday when you can demonstrate all of these:

Your repository check is complete Friday when your locally created README commit is visible in the Project 1 repository you will link through Canvas.