deploy: de23f88

_sources/about.md

@@ -23,12 +23,12 @@ their work.
 | Total GPU Cores      | 0                  | 132,608      | 275,968      | 1,392,640    | 122,880      |
 | Total Memory         | 29.2 TB            | 116.5 TB     | 120 TB       | 52.5 TB      | 103 TB       |
 | Network Bandwidth    | 20 Gb/s            | 100 Gb/s     | 100 Gb/s     | 200 Gb/s     | 200 Gb/s     |
-| Work Storage         | None               | None         | 768 TB       | 3.5 PB*      | 3.5 PB*      |
+| Project Storage         | None               | None         | 768 TB       | 3.5 PB*      | 3.5 PB*      |
 | Scratch Space        | 1.4 PB             | 1.4 PB       | 2.8 PB       | 750 TB       | 3.5 PB       |
 | Archive Capabilities | No                 | Yes          | Yes          | No           | No           |
 | Operating System     | Scientific Linux 6 | CentOS 7     | CentOS 7     | Ubuntu 22.04 | Ubuntu 22.04 |
 
-\* The 3.5 PB `Work Storage` is shared on M3 and the SuperPOD.
+\* The 3.5 PB `Project Storage` is shared on M3 and the SuperPOD. It was formerly referred to as `Work Storage`, which has been deprecated and will be phased out beginning on January 15, 2025.
 
 ## ManeFrame III (M3)
 
@@ -62,7 +62,7 @@ their work.
 | GPU Accelerator Cores  | 1,392,640                                   |
 | Total Memory           | 52.5 TB                                     |
 | Interconnect Bandwidth | 10x200 Gb/s Infiniband Connections Per Node |
-| Work Storage           | 3.5 PB (Shared with M3)                     |
+| Project Storage           | 3.5 PB (Shared with M3)                     |
 | Scratch Storage        | 750 TB (Raw)                                |
 | Operating System       | Ubuntu 22.04                                |
 

_sources/examples/conda/README.md

@@ -19,7 +19,7 @@ module load conda
 
 ### User Installation
 
-You can also install your own versions of Conda in your `$WORK` or `$HOME` directory.
+You can also install your own versions of Conda in your `$HOME` directory.
 We recommend 
 
 - Micromamba: <https://mamba.readthedocs.io/en/latest/user_guide/micromamba.html>
@@ -37,24 +37,24 @@ In most cases, you can source your shell profile to avoid having to log out.
 For most users, this is `source ~/.bashrc`.
 
 We additionally recommend that you disable Conda's auto-activate base
-functionallity. By default, Conda will load a base environment, which can cause
+functionality. By default, Conda will load a base environment, which can cause
 issues with system dependencies. In particular, applications on
-<https://hpc.m3.smu.edu> often behave in unexpected ways becuase it tries to
+<https://hpc.m3.smu.edu> often behave in unexpected ways because it tries to
 use a Conda package instead of the correct system package.
 The next two commands tell Conda to prefer to save packages and environments
-in your `$WORK` directory so they don't take up space in your `$HOME`.
+in your `$HOME` directory (you can specify other locations you have access to,
+but performance is generally better in `$HOME`).
 
 ```bash
 conda config --set auto_activate_base false
-conda config --prepend envs_dirs $WORK/.conda/envs
-conda config --prepend pkgs_dirs $WORK/.conda/pkgs
+conda config --prepend envs_dirs $HOME/.conda/envs
+conda config --prepend pkgs_dirs $HOME/.conda/pkgs
 ```
 
 ## Creating Virtual Environments from the Command Line
 
 For simple environments with a small number of packages, you can create an
-environment named `conda_env` (or any name of your choosing) in your `$WORK`
-directory with
+environment named `conda_env` (or any name of your choosing)
 
 ```bash
 conda create -n conda_env python=3.9 package1 package2 package3
@@ -63,7 +63,7 @@ conda create -n conda_env python=3.9 package1 package2 package3
 The `-n` tells Conda what to name the environment. Here, we request Python
 version 3.9 and the packages `package1 package2 package3` which are the
 packages you'd like to install (e.g. `numpy`, `tensorflow`, `pandas`, etc.). In
-general, it is a good idea install all the packages at the same time becasue
+general, it is a good idea install all the packages at the same time because
 Conda will do a better job of resolving dependencies.
 
 ## Creating Virtual Environments From environment.yml File
@@ -103,7 +103,7 @@ The next section is `dependencies` and this is where you should list all of the
 packages you would like to install. If you have packages that need to be
 installed with `pip`, you should include `pip` in the dependencies as above and
 you can list the specific packages like the above as `pip_package1`, etc.
-and/or you can have all the `pip` packages in a `requirments.txt` file.
+and/or you can have all the `pip` packages in a `requirements.txt` file.
 
 Once you have made the `environment.yml` file, you can create the environment
 with:

_sources/policies/policies.md

@@ -18,8 +18,14 @@ Data older than 60 days will be purged (deleted) without warning.
 `$SCRATCH` is intended as high performance, temporary storage for jobs.
 
 If data is needed for a longer period of time, it should be stored in
-`$WORK` (8 TB limit) or `$HOME` directories (200 GB). If those are also
-insuffiencient, please contact us to discuss options.
+ColdFront storage allocations (limits vary and require justification) or `$HOME` directories (200 GB). If those are also
+insufficient, please contact us to discuss options.
+
+:::{important} SMU does not currently have facilities for archival storage of large datasets.
+Most of our HPC storage is redundant, but it is not (and cannot) be backed up.
+Storage space is also limited and current and active usage is prioritized.
+Please contact us to discuss needs and potential options [contact us](about/contact.md)
+:::
 
 ## Account and Account Password Sharing Policy
 
@@ -30,6 +36,6 @@ one.
 
 ## Data Transfer Nodes
 
-Access to data tranfer nodes is available by request and legitimate need. 
-These nodes are meant only for transferring large amounts data to/from HPC resources. 
+Access to data transfer nodes is available by request and legitimate need.
+These nodes are meant only for transferring large amounts data to/from HPC resources.
 They should not be used for computational jobs.

about.html

@@ -503,7 +503,7 @@ <h1>About<a class="headerlink" href="#about" title="Permalink to this heading">#
 <td><p>200 Gb/s</p></td>
 <td><p>200 Gb/s</p></td>
 </tr>
-<tr class="row-odd"><td><p>Work Storage</p></td>
+<tr class="row-odd"><td><p>Project Storage</p></td>
 <td><p>None</p></td>
 <td><p>None</p></td>
 <td><p>768 TB</p></td>
@@ -533,7 +533,7 @@ <h1>About<a class="headerlink" href="#about" title="Permalink to this heading">#
 </tr>
 </tbody>
 </table>
-<p>* The 3.5 PB <code class="docutils literal notranslate"><span class="pre">Work</span> <span class="pre">Storage</span></code> is shared on M3 and the SuperPOD.</p>
+<p>* The 3.5 PB <code class="docutils literal notranslate"><span class="pre">Project</span> <span class="pre">Storage</span></code> is shared on M3 and the SuperPOD. It was formerly referred to as <code class="docutils literal notranslate"><span class="pre">Work</span> <span class="pre">Storage</span></code>, which has been deprecated and will be phased out beginning on January 15, 2025.</p>
 <section id="maneframe-iii-m3">
 <h2>ManeFrame III (M3)<a class="headerlink" href="#maneframe-iii-m3" title="Permalink to this heading">#</a></h2>
 <section id="configuration">
@@ -627,7 +627,7 @@ <h3>Configuration<a class="headerlink" href="#id1" title="Permalink to this head
 <tr class="row-odd"><td><p>Interconnect Bandwidth</p></td>
 <td><p>10x200 Gb/s Infiniband Connections Per Node</p></td>
 </tr>
-<tr class="row-even"><td><p>Work Storage</p></td>
+<tr class="row-even"><td><p>Project Storage</p></td>
 <td><p>3.5 PB (Shared with M3)</p></td>
 </tr>
 <tr class="row-odd"><td><p>Scratch Storage</p></td>

examples/conda/README.html

@@ -449,7 +449,7 @@ <h3>System Installation<a class="headerlink" href="#system-installation" title="
 </section>
 <section id="user-installation">
 <h3>User Installation<a class="headerlink" href="#user-installation" title="Permalink to this heading">#</a></h3>
-<p>You can also install your own versions of Conda in your <code class="docutils literal notranslate"><span class="pre">$WORK</span></code> or <code class="docutils literal notranslate"><span class="pre">$HOME</span></code> directory.
+<p>You can also install your own versions of Conda in your <code class="docutils literal notranslate"><span class="pre">$HOME</span></code> directory.
 We recommend</p>
 <ul class="simple">
 <li><p>Micromamba: <a class="reference external" href="https://mamba.readthedocs.io/en/latest/user_guide/micromamba.html">https://mamba.readthedocs.io/en/latest/user_guide/micromamba.html</a></p></li>
@@ -464,31 +464,31 @@ <h3>User Installation<a class="headerlink" href="#user-installation" title="Perm
 In most cases, you can source your shell profile to avoid having to log out.
 For most users, this is <code class="docutils literal notranslate"><span class="pre">source</span> <span class="pre">~/.bashrc</span></code>.</p>
 <p>We additionally recommend that you disable Conda’s auto-activate base
-functionallity. By default, Conda will load a base environment, which can cause
+functionality. By default, Conda will load a base environment, which can cause
 issues with system dependencies. In particular, applications on
-<a class="reference external" href="https://hpc.m3.smu.edu">https://hpc.m3.smu.edu</a> often behave in unexpected ways becuase it tries to
+<a class="reference external" href="https://hpc.m3.smu.edu">https://hpc.m3.smu.edu</a> often behave in unexpected ways because it tries to
 use a Conda package instead of the correct system package.
 The next two commands tell Conda to prefer to save packages and environments
-in your <code class="docutils literal notranslate"><span class="pre">$WORK</span></code> directory so they don’t take up space in your <code class="docutils literal notranslate"><span class="pre">$HOME</span></code>.</p>
+in your <code class="docutils literal notranslate"><span class="pre">$HOME</span></code> directory (you can specify other locations you have access to,
+but performance is generally better in <code class="docutils literal notranslate"><span class="pre">$HOME</span></code>).</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>conda<span class="w"> </span>config<span class="w"> </span>--set<span class="w"> </span>auto_activate_base<span class="w"> </span><span class="nb">false</span>
-conda<span class="w"> </span>config<span class="w"> </span>--prepend<span class="w"> </span>envs_dirs<span class="w"> </span><span class="nv">$WORK</span>/.conda/envs
-conda<span class="w"> </span>config<span class="w"> </span>--prepend<span class="w"> </span>pkgs_dirs<span class="w"> </span><span class="nv">$WORK</span>/.conda/pkgs
+conda<span class="w"> </span>config<span class="w"> </span>--prepend<span class="w"> </span>envs_dirs<span class="w"> </span><span class="nv">$HOME</span>/.conda/envs
+conda<span class="w"> </span>config<span class="w"> </span>--prepend<span class="w"> </span>pkgs_dirs<span class="w"> </span><span class="nv">$HOME</span>/.conda/pkgs
 </pre></div>
 </div>
 </section>
 </section>
 <section id="creating-virtual-environments-from-the-command-line">
 <h2>Creating Virtual Environments from the Command Line<a class="headerlink" href="#creating-virtual-environments-from-the-command-line" title="Permalink to this heading">#</a></h2>
 <p>For simple environments with a small number of packages, you can create an
-environment named <code class="docutils literal notranslate"><span class="pre">conda_env</span></code> (or any name of your choosing) in your <code class="docutils literal notranslate"><span class="pre">$WORK</span></code>
-directory with</p>
+environment named <code class="docutils literal notranslate"><span class="pre">conda_env</span></code> (or any name of your choosing)</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>conda<span class="w"> </span>create<span class="w"> </span>-n<span class="w"> </span>conda_env<span class="w"> </span><span class="nv">python</span><span class="o">=</span><span class="m">3</span>.9<span class="w"> </span>package1<span class="w"> </span>package2<span class="w"> </span>package3
 </pre></div>
 </div>
 <p>The <code class="docutils literal notranslate"><span class="pre">-n</span></code> tells Conda what to name the environment. Here, we request Python
 version 3.9 and the packages <code class="docutils literal notranslate"><span class="pre">package1</span> <span class="pre">package2</span> <span class="pre">package3</span></code> which are the
 packages you’d like to install (e.g. <code class="docutils literal notranslate"><span class="pre">numpy</span></code>, <code class="docutils literal notranslate"><span class="pre">tensorflow</span></code>, <code class="docutils literal notranslate"><span class="pre">pandas</span></code>, etc.). In
-general, it is a good idea install all the packages at the same time becasue
+general, it is a good idea install all the packages at the same time because
 Conda will do a better job of resolving dependencies.</p>
 </section>
 <section id="creating-virtual-environments-from-environment-yml-file">
@@ -523,7 +523,7 @@ <h2>Creating Virtual Environments From environment.yml File<a class="headerlink"
 packages you would like to install. If you have packages that need to be
 installed with <code class="docutils literal notranslate"><span class="pre">pip</span></code>, you should include <code class="docutils literal notranslate"><span class="pre">pip</span></code> in the dependencies as above and
 you can list the specific packages like the above as <code class="docutils literal notranslate"><span class="pre">pip_package1</span></code>, etc.
-and/or you can have all the <code class="docutils literal notranslate"><span class="pre">pip</span></code> packages in a <code class="docutils literal notranslate"><span class="pre">requirments.txt</span></code> file.</p>
+and/or you can have all the <code class="docutils literal notranslate"><span class="pre">pip</span></code> packages in a <code class="docutils literal notranslate"><span class="pre">requirements.txt</span></code> file.</p>
 <p>Once you have made the <code class="docutils literal notranslate"><span class="pre">environment.yml</span></code> file, you can create the environment
 with:</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>conda<span class="w"> </span>env<span class="w"> </span>create<span class="w"> </span>-f<span class="w"> </span>environment.yml<span class="w"> </span>-n<span class="w"> </span>conda_env

policies/policies.html

@@ -437,8 +437,15 @@ <h2>Purge Policy<a class="headerlink" href="#purge-policy" title="Permalink to t
 Data older than 60 days will be purged (deleted) without warning.
 <code class="docutils literal notranslate"><span class="pre">$SCRATCH</span></code> is intended as high performance, temporary storage for jobs.</p>
 <p>If data is needed for a longer period of time, it should be stored in
-<code class="docutils literal notranslate"><span class="pre">$WORK</span></code> (8 TB limit) or <code class="docutils literal notranslate"><span class="pre">$HOME</span></code> directories (200 GB). If those are also
-insuffiencient, please contact us to discuss options.</p>
+ColdFront storage allocations (limits vary and require justification) or <code class="docutils literal notranslate"><span class="pre">$HOME</span></code> directories (200 GB). If those are also
+insufficient, please contact us to discuss options.</p>
+<div class="admonition important">
+<p class="admonition-title">Important</p>
+<p>SMU does not currently have facilities for archival storage of large datasets.
+Most of our HPC storage is redundant, but it is not (and cannot) be backed up.
+Storage space is also limited and current and active usage is prioritized.
+Please contact us to discuss needs and potential options <span class="xref myst">contact us</span></p>
+</div>
 </section>
 <section id="account-and-account-password-sharing-policy">
 <h2>Account and Account Password Sharing Policy<a class="headerlink" href="#account-and-account-password-sharing-policy" title="Permalink to this heading">#</a></h2>
@@ -449,7 +456,7 @@ <h2>Account and Account Password Sharing Policy<a class="headerlink" href="#acco
 </section>
 <section id="data-transfer-nodes">
 <h2>Data Transfer Nodes<a class="headerlink" href="#data-transfer-nodes" title="Permalink to this heading">#</a></h2>
-<p>Access to data tranfer nodes is available by request and legitimate need.
+<p>Access to data transfer nodes is available by request and legitimate need.
 These nodes are meant only for transferring large amounts data to/from HPC resources.
 They should not be used for computational jobs.</p>
 </section>