Merge branch 'main' into review_tutorial_intro_hpc

Author: RobJY

.github/workflows/spellcheck.yaml

@@ -17,6 +17,6 @@ jobs:
       uses: actions/checkout@v5
 
     - name: Spell Check Repo
-      uses: crate-ci/typos@v1.36.2
+      uses: crate-ci/typos@v1.37.2
       with:
         files: docs/**/**/*.md docs/**/**/*.mdx

.github/workflows/update-lockfiles.yml

@@ -15,7 +15,7 @@ jobs:
     steps:
       - uses: actions/checkout@v5
       - name: Set up pixi
-        uses: prefix-dev/setup-pixi@v0.9.0
+        uses: prefix-dev/setup-pixi@v0.9.1
         with:
           run-install: false
 

.helix/config.toml

@@ -0,0 +1,2 @@
+[editor]
+soft-wrap.enable = true

docs/cloud/04_dataproc/03_computation.md

@@ -120,7 +120,7 @@ trino --catalog=hive
 
 ## Using Conda
 
-NYU Dataproc comes with `miniconda3` by default. This can be used to manage Python packages within your filesystem home directory. See [here](https://docs.conda.io/projects/conda/en/latest/user-guide/getting-started.html) or [here](../../hpc/06_tools_and_software/04_conda_environments.mdx) for more information on the conda command.
+NYU Dataproc comes with `miniconda3` by default. This can be used to manage Python packages within your filesystem home directory. See [here](https://docs.conda.io/projects/conda/en/latest/user-guide/getting-started.html) or [here](../../hpc/06_tools_and_software/06_conda_environments.mdx) for more information on the conda command.
 
 ## Using Jupyter Notebooks
 

docs/hpc/01_getting_started/01_intro.md

@@ -0,0 +1,9 @@
+# Start here!
+
+Welcome to the Torch HPC documentation! If you do not have an HPC account, please proceed to the next section that explains how you may be able to get one.
+
+If you are an active user, you can proceed to one of the categories on the left.
+
+## Announcements
+
+<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vR8sCeFahadhOL_PRaMl8_dBT6dXEVkLqWznRvEEzNbF3-aUH7AQT1KiZEiwznsy8cMYrvzZoTHORVx/pubembed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>

docs/hpc/01_getting_started/01_intro.mdx

@@ -7,7 +7,7 @@ import TabItem from '@theme/TabItem';
 This section is only applicable to the Torch cluster!
 :::
 
-Coldfront is the HPC project and allocation management portal for Torch at NYU. You can access it by navigating to [coldfront.hpc.nyu.edu](https://coldfront.hpc.nyu.edu). With it you can:
+Coldfront is the HPC project and allocation management portal for Torch at NYU. You can access it by navigating to [projects.hpc.nyu.edu](https://projects.hpc.nyu.edu). With it you can:
 <Tabs>
   <TabItem value="PIs" label="PIs" default>
     -   Create a project
@@ -29,13 +29,13 @@ Coldfront is the HPC project and allocation management portal for Torch at NYU.
 <br/>
 
 :::info[VPN Needed]
-You need to be connected to the NYU VPN or be present on campus to access the Coldfront HPC project management portal.
+You need to be connected to the NYU VPN to access the Coldfront HPC project management portal.
 :::
 
 How do I:
--   Create a project: refer to [creating a project](08_coldfront_creating_a_project.mdx)
--   Request an allocation: refer to [submitting an allocation request](09_coldfront_requesting_an_allocation_request.mdx)
--   Approve an allocation request: refer to [approving an allocation request](10_approving_an_allocation_request.md)
--   View resources that are available to me: refer to [current allocations sub-section here](09_coldfront_requesting_an_allocation_request.mdx)
+-   [Create a project?](08_coldfront_creating_a_project.mdx)
+-   [Request an allocation?](09_coldfront_requesting_an_allocation_request.mdx)
+-   [Approve an allocation request?](10_approving_an_allocation_request.md)
+-   [View resources that are available to me?](09_coldfront_requesting_an_allocation_request.mdx)
 
 A coldfront allocation is needed to perform any work on Torch. The next sections describe the project and allocation request process in detail.

docs/hpc/01_getting_started/07_what_is_coldfront.mdx

@@ -21,14 +21,20 @@ After clicking "+Request Resource Allocation", you'll see a list of resources yo
 :::info Available resource for each school:
 <Tabs>
   <TabItem value="tandon" label="Tandon" default>
-    -   **tandon_advanced**: includes both A100 and H100 GPUs
-    -   **tandon_priority**: includes A100 GPUs only
+    -   **tandon_advanced**: includes both A100, H100 and H200 GPUs
+    -   **tandon_priority**: includes A100 and H100 GPUs
   </TabItem>
   <TabItem value="arts-sciences" label="Arts & Sciences">
     -   **cilvr**: A100 GPUs
-    -   **cds**: rtx8000 and A100
+    -   **cds**: rtx8000, A100 and H200 GPUs
     -   **chemistry**: A100 GPUs
   </TabItem>
+  <TabItem value="courant" label="Courant Institute of Mathematical Sciences">
+    -   **courant**: L40s and H200 GPUs 
+    -   **lpinto**: stakeholder L40s GPUs
+    -   **mren**: stakeholder L40s GPUs    
+    -   **bpeher**: stakeholder H200 GPUs
+  </TabItem>
 </Tabs>
 :::
 

docs/hpc/01_getting_started/09_coldfront_requesting_an_allocation_request.mdx

@@ -105,7 +105,7 @@ The HPC team makes available a number of public datasets that are commonly used
 
 For some of the datasets users must provide a signed usage agreement before accessing.
 
-Public datasets available on the HPC clusters can be viewed on the [Datasets page](../01_getting_started/01_intro.md).
+Public datasets available on the HPC clusters can be viewed on the [Datasets page](../04_datasets/01_intro.md).
 
 #### HPC Archive
 Once the Analysis stage of the research data lifecycle has completed, <ins>_HPC users should **tar** their data and code into a single tar.gz file and then copy the  file to their archive directory (**`/archive/$USER`**_).</ins> The HPC Archive file system is not accessible by running jobs; it is suitable for long-term data storage. Each user has access to a default disk quota of **2TB** and ***20,000 inode (files) limit***. The rather low limit on the number of inodes per user is intentional.  The archive file system is available only ***on login nodes*** of Greene. The archive file system is backed up daily.

docs/hpc/03_storage/01_intro_and_data_management.mdx

@@ -5,7 +5,7 @@ Globus is the recommended tool to use for large-volume data transfers due to the
 :::
 
 ## Data-Transfer nodes
-Attached to the NYU HPC cluster Greene, the Greene Data Transfer Node (gDTN) are  nodes optimized for transferring data between cluster file systems (e.g. scratch)  and other endpoints outside the NYU HPC clusters, including user laptops and desktops. The gDTNs have 100-Gb/s Ethernet connections to the High Speed Research Network (HSRN) and are connected to the HDR Infiniband fabric of the HPC clusters. More information on the hardware characteristics is available at [Greene spec sheet](../10_spec_sheet.mdx).
+Attached to the NYU HPC cluster Greene, the Greene Data Transfer Node (gDTN) are  nodes optimized for transferring data between cluster file systems (e.g. scratch)  and other endpoints outside the NYU HPC clusters, including user laptops and desktops. The gDTNs have 100-Gb/s Ethernet connections to the High Speed Research Network (HSRN) and are connected to the HDR Infiniband fabric of the HPC clusters. More information on the hardware characteristics is available at [Greene spec sheet](../10_spec_sheet.md).
 
 ### Data Transfer Node Access
 The HPC cluster filesystems include `/home`, `/scratch`, `/archive` and the [HPC Research Project Space](./05_research_project_space.mdx) are available on the gDTN. The Data-Transfer Node (DTN) can be accessed in a variety of ways