Test branch

docs/requirements.txt

@@ -1,3 +1,6 @@
-sphinxemoji
+sphinx
+sphinx-autobuild
 sphinx-rtd-theme
+sphinx-fontawesome
+sphinxemoji
 sphinx-togglebutton

docs/section1/overview.rst

@@ -6,3 +6,48 @@ and tools, as well as the primary Python libraries used for data processing and
 
 .. toctree::
    :maxdepth: 1
+
+
+
+**Test 17 February 2025**
+
+
+Introduction to High Performance Computing
+==========================================
+
+Basic High Performance Computing (HPC) System Architecture
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+As you prepare to use TACC systems for this workshop, it is important to understand
+the basic architecture. Think of an HPC resource as a very large and complicated lab
+instrument. Users need to learn how to:
+
+* Interface with it / push the right buttons (Linux)
+* Load samples (data)
+* Run experiments (jobs)
+* Interpret the results (data analysis / vis)
+
+.. image:: ./images/hpc_schematic.png
+   :target: ./images/hpc_schematic.png
+   :alt: HPC System Architecture
+
+**Login vs. Compute Nodes**
+
+As we've discussed, an HPC system has login nodes and compute nodes. We cannot run
+applications on the login nodes because they require too many resources and will 
+interrupt the work of others. Instead, we must submit a job to a queue to run on compute nodes.
+
+Tips for Success
+^^^^^^^^^^^^^^^^
+
+Read the `documentation <https://docs.tacc.utexas.edu/>`_.
+
+* Learn node schematics, limitations, file systems, rules
+* Learn about the scheduler, queues, policies
+* Determine the right resource for the job
+
+User Responsibility on Shared Resources
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+HPC systems are shared resources. Your jobs and activity on a cluster, if mismanaged,
+can affect others. TACC staff are always `available to help <https://www.tacc.utexas.edu/about/help/>`_.