> For the complete documentation index, see [llms.txt](https://workshop.dukeieee.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://workshop.dukeieee.org/workshops/quickstart.md).

# ACCESS INTRO: NSF Computing Resources Overview

{% hint style="warning" %}
Requires a Duke NetID 
{% endhint %}

Slides: 

{% embed url="<https://prodduke-my.sharepoint.com/:p:/g/personal/sc814_duke_edu/ES-3n1iqkdhLoDzym1KgkU0BHaskHYAYUXwQtLQsVxgA5Q?e=BZaiMD>" %}

{% embed url="<https://allocations.access-ci.org/>" %}

ACCESS (Advanced Cyberinfrastructure Coordination Ecosystem: Services & Support) is a program funded by the National Science Foundation (NSF) that provides researchers and educators with access to advanced computing, data analysis, and storage resources. It offers a variety of computing systems, such as GPUs, large-memory nodes, and storage, to support a wide range of research and educational needs. Users can apply for an allocation, which grants them project-specific resource units to utilize these resources for their research or classroom projects, without needing an NSF award.

## Available Compute

{% embed url="<https://allocations.access-ci.org/resources>" %}

ACCESS provides various HPC resources, including:

* **SLURM based HPC**: A workload manager for scheduling and managing compute jobs.
* **Virtual Machines**: Flexible environments for custom configurations.
* **GPU Compute**: High-performance graphics processing units for parallel computing tasks.
* **Large Memory Nodes**: Systems designed for memory-intensive applications.
* **Cloud Computing**: Virtual resources for scalable computing.
* **Tape Storage**: Long-term archival storage for large datasets.
* **Specialized Hardware**: Unique architectures like the Cerebras Wafer Scale Engine (largest chip ever built) for AI acceleration.

## Who is Elgible

{% embed url="<https://allocations.access-ci.org/allocations-policy#eligibility>" %}

### Recommended Resources

#### Jetstream 2 GPU:

Jetstream2 GPU is a hybrid-cloud platform that provides flexible, on-demand, virtual machines with preloaded software and root admin access.  This particular portion of the resource is allocated separately from the primary resource and contains 360 NVIDIA A100 GPUs -- 4 GPUs per node, 128 AMD Milan cores, and 512gb RAM connected by 100gbps ethernet to the spine. (ACCESS Website)

## How to login

1. Go to the login portal - <https://allocations.access-ci.org/login>
2. Select Duke as login provider and login with NetID

<figure><img src="/files/4l9aA1ejrdYotUU335P1" alt=""><figcaption></figcaption></figure>

## Review project types: <https://allocations.access-ci.org/project-types>

<figure><img src="/files/lgxyLafOYz958oyBAlWT" alt=""><figcaption></figcaption></figure>

## Request Resources

User can either request access to Duke's Campus Champion allocation or request an individual project.&#x20;

#### Duke Campus Champion allocation&#x20;

The Campus Champion allocation is designed to provide instant access to compute for the Duke community. To request access email <tom.milledge@duke.edu> and cc <sanjeev.chauhan@duke.edu>

#### Requesting a project

Once logged in, head to the my project page and request a new project.

<figure><img src="/files/xoeigmGXfrm6oO59zeD7" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/1vAuMwKYI1dZylvs06Tk" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://workshop.dukeieee.org/workshops/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.