> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/archive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/archive/bootcamp-2021/schedule/tuesday-4-may.md).

# Tuesday, 4 May

Using Oscar: Beyond the Basics

## Version Control with Git | 9:30 - 11:00 EDT

A practical introduction to version control for software management using Git. Topics covered include: creating a repository, checking the status of a repository, committing changes, viewing changes, reverting to older versions of files, and setting up a remote repository.

[Repository](https://github.com/dscov-tutorials/gitintro) | [nbviewer](https://nbviewer.jupyter.org/github/dscov-tutorials/gitintro/blob/master/gitintro.ipynb)

## Building Software on Oscar | 11:00 - 12:30 EDT

Learn how to build and install software packages on Oscar. Topics covered include: make, cmake, compiler options on Oscar, pip, building python packages from source, and python virtual environments.

[Slides](https://docs.google.com/presentation/d/1Rtd3mjHPhI8CUsTLOn8lRA6X7dGQAlMeqoImszAqqFI/edit?usp=sharing) | [Exercises](https://docs.google.com/presentation/d/1RDP3Hi1CMWAi0uPsqQVfcWu1ig7hV78Jr3WSPP4niFU/edit?usp=sharing)

## Slurm for Beginners | 1:30 - 3:00 EDT

A primer on submitting jobs to the job scheduler on Oscar. Some basic familiarity with Unix/Linux systems is assumed. Topics covered include: an overview of the use of Slurm for resource allocation, submitting jobs to Slurm, and using Bash scripts to configure and submit jobs to Slurm.

[Slides](https://docs.google.com/presentation/d/1XumM5oXrfO4mMjPiXSsWNAm0A8zyzCfqynDohblveXI/edit?usp=sharing) | [Exercises](https://docs.google.com/presentation/d/1njUjfnrxL4hmk6yTHUGwgGCLhggqhVK6B2dVdlizQjI/edit?usp=sharing)

## Advanced Slurm | 3:00 - 4:30 EDT

This workshop is for people who are already familiar with Slurm, but would like to use Slurm's more powerful features. Topics covered include: dependencies for conditional execution of jobs, job arrays for parameter sweeps, dealing with hundreds or thousands of small tasks, how to limit the number of jobs running at once, and how to cancel multiple jobs.

[Slides](https://docs.google.com/presentation/d/1Dhte5lTCdiHCNkj4f0-RzcGOSehWpAuk6f9XAR1XiUk/edit?usp=sharing) | [Exercises](https://docs.google.com/presentation/d/1-UGU6XWibh5wMWaX2AIW35Kw3xEsrOQzQvcwpDH00kI/edit?usp=sharing)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ccv.brown.edu/archive/bootcamp-2021/schedule/tuesday-4-may.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
