.gitignore

 public/
+.cache/
+__pycache__/
+site/

.gitlab-ci.yml

 variables:
   BASE_URL: "//hcc.unl.edu/docs"
   DEPLOY_ROOT: "/var/www/html/hcc-docs"
-  HUGO_TARBALL:  "https://github.com/gohugoio/hugo/releases/download/v0.51/hugo_0.51_Linux-64bit.tar.gz"
-  GIT_SUBMODULE_STRATEGY: recursive
+  MKDOCS_PREFIX: /tmp/gitlab-${CI_JOB_ID}-${CI_COMMIT_SHORT_SHA}/mkdocs
+  MICROMAMBA_ROOT_PREFIX: /tmp/gitlab-${CI_JOB_ID}-${CI_COMMIT_SHORT_SHA}/micromamba
+
+.fetch_external_files: &fetch_external_files
+  - curl -L https://raw.githubusercontent.com/unlhcc/singularity-dockerfiles/master/IMAGELIST.md > docs/static/markdown/singularity-images.md
+  - curl -L http://swan-head.unl.edu:8192/bio/data/json > docs/static/json/biodata.json
+  - curl -L http://swan-head.unl.edu:8192/lmod/spider/json > docs/static/json/lmod.json
+  - curl -L http://swan-head.unl.edu:8192/slurm/partitions/json > docs/static/json/swan_partitions.json
 
 stages:
   - test
@@ -10,15 +16,19 @@ stages:
 
 test:
   stage: test
-  image: unlhcc/docker-glibc
+  image: python:3.11
   except:
     - master
   tags:
     - docker
   before_script:
-    - curl -L -o - ${HUGO_TARBALL} | tar -zxv -C /usr/local/bin
+    - apt-get -q update
+    - apt-get -q -y install zip pandoc
+    - pip install -q -r requirements.txt
+    - *fetch_external_files
   script:
-    - hugo --ignoreCache -v
+    - mkdocs build
+    - ./pandoc-build.sh
 
 deploy:
   stage: deploy
@@ -29,8 +39,16 @@ deploy:
     - master
   tags:
     - hcc-docs-prod
+  before_script:
+    - mkdir -p ${MICROMAMBA_ROOT_PREFIX} ${MKDOCS_PREFIX}
+    - *fetch_external_files
+    - micromamba create -y -q -p ${MKDOCS_PREFIX}/mkdocs python=3.11 pip cairo pandoc
+    - micromamba run -p ${MKDOCS_PREFIX}/mkdocs pip install -q -r requirements.txt
   script:
-    - curl -L https://raw.githubusercontent.com/unlhcc/singularity-dockerfiles/master/IMAGELIST.md > static/markdown/singularity-images.md
-    - hugo --ignoreCache -b ${BASE_URL} -v
-    - pandoc -s content/facilities.md -o public/facilities.docx
-    - rsync -avz --delete public/ $DEPLOY_ROOT
+    - micromamba run -p ${MKDOCS_PREFIX}/mkdocs mkdocs build
+    - find site/ -type f -name "*.html" -exec sed -i -e 's/src="\//src="\/docs\//g' -e 's/href="\//href="\/docs\//g' {} +
+    - micromamba run -p ${MKDOCS_PREFIX}/mkdocs ./pandoc-build.sh
+    - rsync -avz --delete site/ ${DEPLOY_ROOT}
+  after_script:
+    - rm -rf /tmp/gitlab-${CI_JOB_ID}-${CI_COMMIT_SHORT_SHA}
+

CONTRIBUTING.md

@@ -42,10 +42,10 @@ or a factual error.
 1.  Checking for outstanding [issues](https://git.unl.edu/hcc/hcc-docs/issues) is a quick way to identify contribution areas. Additionally,
     review an comments on existing merge requests are welcome.
 
-2.  All documentation content can be found within the `content` folder. Subdirectories indicate menu items,
-    with the top level document called `_index.md` within each subdirectory.
+2.  All documentation content can be found within the `docs` folder. Subdirectories indicate menu items,
+    with the top level document called `index.md` within each subdirectory.
 
-Note: please do not submit modifications to theme or CSS items, `_header` or `_footer` files unless they 
+Note: please do not submit modifications to theme or CSS items unless they 
 adhere to [UNL style guidelines](https://wdn.unl.edu/unl-web-framework-5-standards-guide).
 
 ## What to Contribute

README.md

@@ -3,8 +3,8 @@ HCC-DOCS
 
 This is the repository for HCC's user documentation.  The documentation is a
 combination of [Markdown](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)
-for the source and the [Hugo](https://gohugo.io) static site generator.  Currently, 
-the theme used is [docDock](https://themes.gohugo.io/docdock/).
+for the source and the [MkDocs](https://www.mkdocs.org/) static site generator.  Currently, 
+the theme used is [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/).
 
 The website is viewable at https://hcc.unl.edu/docs.
 
@@ -19,23 +19,16 @@ edit/create content, and preview your changes locally before creating the MR/PR.
 
 #### Clone the repo (including submodules) and create a new branch
 
-Clone the repo somewhere convenient.  The DocDock theme is provided via a git submodule,
-so after cloning, run `git submodule update --init --recursive` in the root of the repo.
-Run `git checkout -b <mybranch>` to create a new branch for your changes.
+Clone the repo somewhere convenient. 
 
-#### Download and install Hugo
+#### Download and install MkDocs
 
-Download the appropriate Hugo tarball from the Hugo [releases page](https://github.com/gohugoio/hugo/releases).
+MkDocs, the Material for MkDocs theme, and all plugins are installable with pip. 
 
-(Direct links for [Linux](https://github.com/gohugoio/hugo/releases/download/v0.51/hugo_0.51_Linux-64bit.tar.gz), [Mac](https://github.com/gohugoio/hugo/releases/download/v0.51/hugo_0.51_macOS-64bit.tar.gz), and [Windows](https://github.com/gohugoio/hugo/releases/download/v0.51/hugo_0.51_Windows-64bit.zip))
-
-The `hugo` program is a single binary with no dependencies and does not require root priviledges, 
-so just place it somewhere convenient in your `PATH` (i.e. `~/bin`).
-
-Verify it works by running the command `hugo version`:
-```
-bash-4.4# hugo version
-Hugo Static Site Generator v0.51 linux/amd64 BuildDate: 2018-11-07T10:10:13Z
+```bash
+pip install mkdocs mkdocs-material mkdocs-nav-weight \
+    mkdocs-material[imaging] mkdocs-awesome-nav mkdocs-macros-plugin \
+    mkdocs-table-reader-plugin mkdocs-include-markdown-plugin
 ```
 
 ### Previewing the site and adding content
@@ -44,89 +37,129 @@ Hugo Static Site Generator v0.51 linux/amd64 BuildDate: 2018-11-07T10:10:13Z
 
 The `hugo server` command will build the site and run a small webserver to allow you to
 preview it.  Depending whether you're working on your local machine or a VM on Anvil,
-the option you pass needs to be slightly different.  The `hugo server` command should be
-run from the root of the repository (i.e. the same directory the `config.toml` file
+the option you pass needs to be slightly different.  The `mkdocs serve` command should be
+run from the root of the repository (i.e. the same directory the `mkdocs.yml` file
 resides in).
 
-**If you're working on your local laptop/deskop:**
+This will allow you to view the webiste by going to `http://localhost:8080` in your web browser. 
 
-Run the command:
-```
-hugo server -b http://127.0.0.1
-```
+Alternatively you can build the HTML files to view in a web browser using the `mkdocs build` command 
+from the root of the repository. 
 
-You should now be able to preview the website by going to `http://localhost:1313` in your web
-browser. 
 
 **If you're working in a VM on Anvil:**
 
-You'll first need to allow port 1313.  If your VM is under the `swanson` project, there is
-already an existing "Hugo" security group.  Just add that group to your VM.  Otherwise, first
-create it and allow TCP port 1313 though.  You may also need to allow port 1313 through your
+You'll first need to allow port 8080.  If your VM is under the `swanson` project, there is
+already an existing "Port 8080" security group.  Just add that group to your VM.  Otherwise, first
+create it and allow TCP port 8080 though.  You may also need to allow port 8080 through your
 instance's firewall.
 
 Once that is done, run the command:
 ```
-hugo server -b http://<instance IP> --bind <instance IP>
+mkdocs serve
 ```
-where *\<instance IP\>* is the 10.71.x.x address of your instance.
 
-You should now be able to preview the website by going to `http://<instance IP>:1313` in your web
-browser.
 
-*Note:  The hugo server command will watch the filesystem for changes and force an update in your browswer,
+You should now be able to preview the website by going to `http://<instance IP>:8080` in your web
+browser, where *\<instance IP\>* is the 10.71.x.x address of your instance.
+
+*Note:  The mkdocs serve command will watch the filesystem for changes and force an update in your browswer,
 so you can simply leave the server running as you work.*
 
 #### Adding content
 
-The page content for the site is under the `content/` directory.  The directory structure will determine
+The page content for the site is under the `docs/` directory.  The directory structure will determine
 how the site itself is structured, so place content based on where in the site you would like it to be.
-Each level in the tree will need to have an `_index.md` file to designate it as a new section.  The content
-itself is almost all standard markdown.  However, there are a few things that are specific to Hugo that
+Each level in the tree will need to have an `index.md` file to designate it as a new section.  The content
+itself is almost all standard markdown.  However, there are a few things that are specific to MkDocs that
 are used:
 
-1.  *Front matter*  
-    [Front matter](https://gohugo.io/content-management/front-matter) is Hugo-specific metadata added
-    to the page.  The format can be TOML, YAML, or JSON.  The example here uses TOML, which is identified
-    by opening and closing `+++`.  At minimum, each page should have a title and description:  
+1.  *YAML Style Metadata*  
+    [YAML Style Metadata](https://www.mkdocs.org/user-guide/writing-your-docs/#yaml-style-meta-data) is Hugo-specific metadata added
+    to the page.  The format needs to be YAML.  The example here is for our contact-us page, and is identified
+    by opening and closing `---`  At minimum, each page should have a title and description:  
     ```
-    +++
-    title = "Contact Us"
-    description = "Contact Information for HCC"
-    +++
+    ---
+    title: "Contact Us"
+    description: "Contact Information for HCC"
+    ---
     ```  
     Another useful parameter is the `weight` option.  This will determine the order of display in the navigation tree;
     lower numbers are displayed before higher numbers.
 
-2.  *Shortcodes*  
-    [Shortcodes](https://gohugo.io/content-management/shortcodes) are "helper functions" to add content
-    that would otherwise require using raw HTML.  Hugo provides some [built-in](https://gohugo.io/content-management/shortcodes/#use-hugo-s-built-in-shortcodes)
-    shortcodes. The DocDock theme also provides its own [shortcodes](http://docdock.netlify.com/shortcodes).
-    Shortcodes are added via a `{{% shortcodename parameters %}}` declaration.  For example, to embed a YouTube
-    video with ID `-Vh7SyC-3mA`:  
-    ```
-    {{< youtube -Vh7SyC-3mA >}}
-    ```  
-    Other useful shortcodes include language-specific syntax highlighting, figures, and automatic listing
-    of page children for navgiation/summary pages.
-
-3.  *Using `relref` for link generation*  
-    The `relref` shortcode should generally be used for linking to other pages within the site.  This will
-    generate relative links that should work no matter what the base URL is.  For example, assume you're
-    editing "my\_page.md" and want to link to the page "my\_other\_page.md" in the subdirectory "mystuff".
-    To do so, add the line  
+2.  *Macros and variables*  
+    [Macros](https://mkdocs-macros-plugin.readthedocs.io/en/latest/) are "helper functions" to add content
+    that would otherwise require using raw HTML.  
+
+    Currently, a few custom ones are implemented. 
+    - `{{ youtube('Emded_URL_OR_Share_Code') }}` - Embeds a youtube video into the docs
+    - `{{ md_table('path_or_url') }}` - Embeds a markdown table as a sortable table. 
+    - `{{ json_table('path_or_url') }}` - Embeds a JSON table as a sortable table. 
+
+    Variables allow for the use of defining shorthand codes for using the same value in multiple places in the documentation.
+
+    These are all defined in the `mkdocs.yml` file in the `extra:` section. 
+    Variables are called using `{{ variable.path.to.value }}` where the path starts after the `extra:` block. 
+
+    ```yaml
+    extra:
+      hcc:  
+      # Swan Cluster Specific Information
+        swan:
+          xfer: "swan-xfer.unl.edu"
+          ood:
+            name: "Swan Open OnDemand"
+            url: "https://swan-ood.unl.edu"
+          work:
+            block: "100 TiB"
     ```
-    [My other page]({{< relref "mystuff/my_other_page" >}})
+
+    Using a section of the YAML above we can get the following exampls:
+
+    - `{{ hcc.swan.xfer }}` would yield the URL for Swan's high speed transfer node
+    - `{{ hcc.swan.ood.url }}` would yield the block quota for Swan's $WORK filesystem
+    - `{{ hcc.swan.work.block }}` would yield the Open OnDemand URL for Swan
+    - ` {{ children('path_after_docs') }} ` - List child pages and Descriptions - do not add trailing `/`
+
+    A good file for examples of the use of these variables is `docs/handling_data/index.md` where many variables 
+    are used to discuss the filesystems.
+
+3.  Code Blocks
+
+    Code blocks are able to use language specific formatting and use the standard markdown format for codeblocks. 
+    ```` markdown title="Example Code Block"
+    ``` python
+    print('Hello World!')
     ```
+    ````
+
+4.  Links 
+    MkDocs uses standard markdown links, `[Text to Display](URL or path/to/file)`
+    
     Note that you can omit the `.md` suffix from the filename.
 
-4.  *Static content*  
-    Hugo has special handling for static content (images, linked zip files, etc.).  In the root of the repo,
-    there is a `static/` directory; all static content should go there.  Subdirectories can be made to keep
-    things organized; there are existing directories for `images` and `attachments`.  Feel free to create
-    additional directories if it makes sense.  To link to static content, you can use an absolute path from
-    any page.  For example, assuming there is an image in the repo at `static/images/my_image.png`,
-    you can link to it using the `figure` shortcode as `{{< figure src="/images/my_image.png" >}}`.
+5.  *Static content*  
+    
+    1.  Images
+        Images are stored in `docs/images`. 
+
+        Images can then be embeded in one of two methods. The path starts from the `images` directory. 
+
+        Using markdown: `![Optional Image Title](/image/picture.png)`
+
+        Using HTML: `<img src="/images/picture.png">`
+        - HTML will also allow the use of standard `img` embedding and customization. 
+    
+    2.  Markdown and HTML Files
+        Sometimes there are cases where information is stored statically elsewhere. These files are organized in `docs/static`
+
+        ``` markdown
+        {% 
+            include "relative/path/to/file.html"
+        %}
+        ```
+    
+    
     -  **Special note for .png files**:  In order to keep the repo size as small as possible, all images
        should be png's if possible, and further processed using the [pngquant](https://pngquant.org) compression
        tool.  This will reduce the size by ~3-4x while keeping good quality.  For example, to process and
@@ -134,6 +167,20 @@ are used:
        prior to committing the files to the repo, otherwise git will be forced to keep multiple copies as the files
        are binary.*
 
+6. Callouts
+    These are the callouts used to highlight information and have a few customization options. 
+    
+    Callout Template:
+    
+    ``` markdown
+    !!! type "Optional Title"
+        Content goes here. It is important to make sure to have space in the markdown file above and below the callout. 
+        Content must also be indented 
+    ```
+
+    A full list of callout types and additional usage information is available in the [Material for MkDocs documentation page](https://squidfunk.github.io/mkdocs-material/reference/admonitions/#supported-types).
+
+
 #### Adding your changes
 
 Once you've got your set of changes, add and commit them to your branch.  Push the branch and

archetypes/default.md

----
-title: "{{ replace .Name "-" " " | title }}"
-date: {{ .Date }}
-draft: true
----
-

config.toml

-#baseURL = "http://hcc-docs.unl.edu/"
-languageCode = "en-us"
-title = "HCC-DOCS"
-theme = "docdock"
-contentdir    = "content"
-layoutdir     = "layouts"
-publishdir    = "public"
-baseURL = "/"
-canonifyURLs = "true"
-relativeURLs = "true"
-
-DefaultContentLanguage = "en"
-pygmentsCodeFences = true
-pygmentsStyle = "monokailight"
-
-defaultContentLanguage = "en"
-defaultContentLanguageInSubdir= false
-enableMissingTranslationPlaceholders = false
-
-[params]
-editURL = "https://git.unl.edu/hcc/hcc-docs/edit/master/content/"
-showVisitedLinks = true # default is false
-themeStyle = "original" # "original" or "flex" # default "flex"
-themeVariant = "blue" # choose theme variant "green", "gold" , "gray", "blue" (default)
-ordersectionsby = "weight" # ordersectionsby = "title"
-disableHomeIcon = false # default is false
-disableSearch = false # default is false
-disableNavChevron = false # set true to hide next/prev chevron, default is false
-highlightClientSide = false # set true to use highlight.pack.js instead of the default hugo chroma highlighter
-menushortcutsnewtab = true # set true to open shortcuts links to a new tab/window
-enableGitInfo = true
-
-[outputs]
-home = [ "HTML", "RSS", "JSON"]
-
-
-[[menu.shortcuts]]
-name = "hcc.unl.edu"
-identifier = "ds"
-url = "https://hcc.unl.edu"
-weight = 10

content/_footer.md

-+++
-  title = "Footer"
-+++
-
-{{< icon name="copyright-mark" >}} [Holland Computing Center] (https://hcc.unl.edu) | 118 Schorr Center, Lincoln NE 68588 | {{< icon name="envelope" >}}[hcc-support@unl.edu] (mailto:hcc-support@unl.edu) | {{< icon name="phone-alt" >}}402-472-5041
-
-See something wrong?  Help us fix it by [contributing](https://git.unl.edu/hcc/hcc-docs/blob/master/CONTRIBUTING.md)!

content/_header.md

-+++
-title = "Header"
-+++
-{{< figure src="/images/UNMasterwhite.gif" link="https://nebraska.edu" target="_blank" >}}
-### [Holland Computing Center](https://hcc.unl.edu)
-
-#### [HCC-DOCS]({{< relref "/" >}})

content/_index.md

-+++
-title = "HCC Documentation"
-description = "HCC Documentation Home"
-weight = "1"
-+++
-
-HCC Documentation
-============================
-
-
-The Holland Computing Center supports a diverse collection of research
-computing hardware.  Anyone in the University of Nebraska system is
-welcome to apply for an account on HCC machines.
-
-Access to these resources is by default shared with the rest of the user
-community via various job schedulers. These policies may be found on the
-pages for the various resources. Alternatively, a user may buy into an
-existing resource, acquiring 'priority access'. Finally, several
-machines are available via Condor for opportunistic use. This will allow
-users almost immediate access, but the job is subject to preemption.
-
-#### [New Users Sign Up](http://hcc.unl.edu/new-user-request)
-
-#### [Quick Start Guides](/quickstarts)
-
-Which Cluster to Use?
----------------------
-
-**Crane**: Crane is the newest and most powerful HCC resource . If you
-are new to using HCC resources, Crane is the recommended cluster to use
-initially.  Limitations: Crane has only 2 CPU/16 cores and 64GB RAM per
-node. CraneOPA has 2 CPU/36 cores with a maximum of 512GB RAM per node.
-
-**Rhino**: Rhino is intended for large memory (RAM) computing needs.
-Rhino has 4 AMD Interlagos CPUs (64 cores) per node, with either 192GB or 256GB RAM per
-node in the default partition. For extremely large RAM needs, there is also
-a 'highmem' partition with 2 x 512GB and 2 x 1TB nodes.
-
-User Login
-----------
-
-For Windows users, please refer to this link [For Windows Users]({{< relref "for_windows_users" >}}).
-For Mac or Linux users, please refer to this link [For Mac/Linux Users]({{< relref "for_maclinux_users">}}).
-
-**Logging into Crane or Rhino**
-
-{{< highlight bash >}}
-ssh <username>@crane.unl.edu
-{{< /highlight >}}
-
-or
-
-{{< highlight bash >}}
-ssh <username>@rhino.unl.edu
-{{< /highlight >}}
-
-Duo Security
-------------
-
-Duo two-factor authentication is **required** for access to HCC
-resources. Registration and usage of Duo security can be found in this
-section: [Setting up and using Duo]({{< relref "setting_up_and_using_duo">}})
-
-**Important Notes**
-
--   The Crane and Rhino clusters are separate. But, they are
-    similar enough that submission scripts on whichever one will work on
-    another, and vice versa (excluding GPU resources and some combinations of
-    RAM/core requests).
-     
--   The worker nodes cannot write to the `/home` directories. You must
-    use your `/work` directory for processing in your job. You may
-    access your work directory by using the command:
-{{< highlight bash >}}
-$ cd $WORK
-{{< /highlight >}}
-
-Resources
----------
-
-- ##### Crane - HCC's newest machine, Crane has 7232 Intel Xeon cores in 452 nodes with 64GB RAM per node.
-
-- ##### Rhino - HCC's AMD-based cluster, intended for large RAM computing needs.
-
-- ##### Red - This cluster is the resource for UNL's [USCMS](https://uscms.org/) Tier-2 site.
-
-- ##### Anvil - HCC's cloud computing cluster based on Openstack
-
-- ##### Glidein - A gateway to running jobs on the OSG, a collection of computing resources across the US.
-
-Resource Capabilities
----------------------
-
-| Cluster | Overview | Processors | RAM | Connection | Storage
-| ------- | ---------| ---------- | --- | ---------- | ------
-| **Crane**   | 548 node Production-mode LINUX cluster | 452 Intel Xeon E5-2670 2.60GHz 2 CPU/16 cores per node<br> <br>116 Intel Xeon E5-2697 v4 2.3GHz, 2 CPU/36 cores per node<br><br>("CraneOPA") | 452 nodes @ \*64GB<br><br>79 nodes @ \*\*\*256GB<br><br>37 nodes @ \*\*\*\*512GB | QDR Infiniband<br><br>EDR Omni-Path Architecture | ~1.8 TB local scratch per node<br><br>~4 TB local scratch per node<br><br>~1452 TB shared Lustre storage
-| **Rhino** | 110 node Production-mode LINUX cluster | 110 AMD Interlagos CPUs (6272 / 6376), 4 CPU/64 cores per node | 106 nodes @ 192GB\*\*/256GB\*\*\* <br><br> 2 nodes @ 512GB\*\*\*\* <br><br> 2 nodes @ 1024GB\*\*\*\*\* | QDR Infiniband | ~1.5TB local scratch per node <br><br> ~360TB shared BeeGFS storage |
-| **Red** | 344 node Production-mode LINUX cluster | Various Xeon and  Opteron processors 7,280 cores maximum, actual number of job slots depends on RAM usage | 1.5-4GB RAM per job slot | 1Gb, 10Gb, and 40Gb Ethernet | ~10.8PB of raw storage space |
-| **Anvil** | 76 Compute nodes (Partially used for cloud, the rest used for general computing), 12 Storage nodes, 2 Network nodes Openstack cloud | 76 Intel Xeon E5-2650 v3 2.30GHz 2 CPU/20 cores per node | 76 nodes @ 256GB | 10Gb Ethernet | 528 TB Ceph shared storage (349TB available now) |
-
-You may only request the following amount of RAM: <br>
-\*62.5GB <br>
-\*\*187.5GB <br>
-\*\*\*250GB <br>
-\*\*\*\*500GB <br>
-\*\*\*\*\*1000GB

content/events/2012/_index.md

-+++
-title = "2012"
-description = "Historical listing of various HCC events for the year 2012."
-weight = "70"
-+++
-
-Historical listing of HCC Events
-----------
-
-{{% children %}}

content/events/2013/HCC_Supercomputing_Symposium_2013.md

-+++
-title = "HCC Supercomputing Symposium 2013"
-description = "HCC Supercomputing Symposium 2013"
-+++
-
-<strong>Location: Wick Alumni Center, Dana Board Room</strong><br>
-The morning sessions will be interactive – attendees should bring a laptop if at all possible!  The first sessions will be primarily planned tutorial format, while the “Open Lab” will involve more individualized help of those in attendance as desired.
-
-| Time    | Title                                                 | Description                                                      |
-|---------|-------------------------------------------------------|------------------------------------------------------------------|
-| 9 - 10am| Getting started at HCC        | HCC 101 (Linux Primer, Job submission) [Quick Start Guides](https://hcc.unl.edu/docs/quickstarts/)                 |
-| 10 - 11am | Job management						  | Creating and deploying parallel jobs at HCC, OSG [Submitting Jobs](https://hcc.unl.edu/docs/guides/submitting_jobs/)  |
-| 11 - 11:45am    | HCC Open Lab                                    |      Presentations and help from HCC staff                                          |
-| 12 - 1pm     | LUNCH lecture with UNIT         | Carl Lundstedt: How Big Data Allows Us to Investigate the Smallest Things                 |
-|1:15 – 2pm   | New User Spotlight – Steve Kolbe, Theatre                           | Media Arts Film Rendering @ HCC                   |
-| 2 - 3pm     | State of HCC; Crane Announcement                 | David Swanson                           |
-
-1.  <span style="line-height: 1.4285715;">Getting Started at HCC (9-10am</span>  
-    1.  [Getting an account at HCC](https://hcc.unl.edu/new-user-request)
-    2.  Logging into HCC resources for [windows](https://hcc.unl.edu/docs/quickstarts/connecting/for_windows_users/) or [Mac/Linux Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_maclinux_users/)
-	3.	Basic Linux commands
-	4.	[Transferring files to HCC](https://hcc.unl.edu/docs/guides/handling_data/)
-2.  Job Management (10-11am)
-    1.  [End to End MPI](https://hcc.unl.edu/docs/guides/running_applications/mpi_jobs_on_hcc/) example.  Including how to transfer source code and compile an MPI application on Tusker.
-    2.  [Compiling](https://hcc.unl.edu/docs/guides/running_applications/compiling_source_code/compiling_an_openmp_application/) and [submitting](https://hcc.unl.edu/docs/guides/submitting_jobs/submitting_an_openmp_job/) multi-thread and OpenMP applications.
-    3.  Using scheduler features such as [Arrays](https://hcc.unl.edu/docs/guides/submitting_jobs/submitting_a_job_array/
-) and [Dependencies](https://hcc.unl.edu/docs/guides/submitting_jobs/job_dependencies/
-).
-    4.  Debugging on Tusker by using [interactive submission](https://hcc.unl.edu/docs/guides/submitting_jobs/submitting_an_interactive_job/). 
-        <span style="line-height: 1.4285715;">&lt;lunch&gt;</span>
-

content/events/2013/_index.md

-+++
-title = "2013"
-description = "Historical listing of various HCC events for the year 2013."
-weight = "60"
-+++
-
-Historical listing of HCC Events
-----------
-
-{{% children %}}

content/events/2013/hcc_condor_workshop_2013.md

-+++
-title = "HCC Condor Workshop 2013"
-description = "HCC Condor Workshop 2013."
-+++
-
-Condor
-============
-
-Workshop presentation slides
-<[condor\_workshop.pdf](https://unl.box.com/s/ou8tf62bqkbrh7yx0cl4me1zbp3z0j08)>
-
-| Time    | Title                   | Description                                    |
-|---------|-------------------------|------------------------------------------------|
-| 1pm-2pm | Demo/Hand-On Practice   | Executing Condor jobs on HCC supertcomputers   |
-| 2pm-3pm | Individual Consultation | Bring your research code on HCC supercomputers |
-
-Password for all demo accounts is **HCC\_condor2013**.
-Replace `<group name>` with `demo` and `<username>` with `demoXX` (e.g. `demo01`).
-
--   Get started with [For Windows Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_windows_users/)
-    or [For Mac/Linux Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_maclinux_users/).
--   Sample code for Fortran/C on HCC:
-    &lt;[serial\_dir.zip](https://unl.box.com/s/khkpt68pe3k0lu2ythn9kzjeva40itdd)&gt;
--   Sample code for Condor on HCC:
-    &lt;[condor\_dir.zip](https://unl.box.com/s/qpvgnqr9ukjcmt0d2trde4qcp5e5ez17)&gt;
--   For more details of this demonstration, see [Condor Jobs on
-    HCC](https://hcc.unl.edu/docs/guides/submitting_jobs/condor_jobs_on_hcc/).
-
-MATLAB
-============
-Workshop presentation slides
-&lt;[matlab\_workshop.pdf](https://unl.box.com/s/ou8tf62bqkbrh7yx0cl4me1zbp3z0j08)&gt;
-
-| Time    | Title                   | Description                                       |
-|---------|-------------------------|---------------------------------------------------|
-| 1pm-2pm | Demo/Hand-On Practice   | Implementing a MATLAB code on HCC supertcomputers |
-| 2pm-3pm | Individual Consultation | Bring your MATLAB code on HCC supercomputers      |
-
-Password for all demo accounts is **HCC\_matlab2013**.
-Replace `<group name>` with `demo` and `<username>` with `demoXX` (e.g. `demo01`).
-
-
--   Get started with [For Windows Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_windows_users/)
-    or [For Mac/Linux Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_maclinux_users/).
--   Hands On: [MATLAB on HCC](https://hcc.unl.edu/docs/guides/submitting_jobs/submitting_matlab_jobs/)
--   Sample code for MATLAB on HCC:
-    &lt;[matlab\_dir.zip](https://unl.box.com/s/u19fy7cjeswfl1wi7h1nkeeie8gl3z90)&gt;
--   Sample code for Parallel MATLAB Job:
-    &lt;[parallel\_matlab\_dir.zip](https://unl.box.com/s/fhl3kf6hg8dmtozkphq3u2r58yexrppe)&gt;
-

content/events/2013/hcc_matlab_workshop_2013.md

-+++
-title = "HCC Matlab Workshop 2013"
-description = "HCC Matlab Workshop 2013."
-+++
-
-Workshop presentation slides
-<[matlab\_workshop.pdf](https://unl.box.com/s/lulbnbrnr7xqwufrx5s20gxnyxpykn7j)>
-
-| Time        | Title                   | Description                                      |
-|-------------|-------------------------|--------------------------------------------------|
-| UNMC        |                         |                                                  |
-| 10am - 11am | Demo/Hand-On Practice   | Implementing a MATLAB code on HCC supercomputers |
-| 11am - 12pm | Individual Consultation | Bring your MATLAB code on HCC supercomputers     |
-| UNO         |                         |                                                  |
-| 2pm - 3pm   | Demo/Hand-On Practice   | Implementing a MATLAB code on HCC supercomputers |
-| 3pm - 4pm   | Individual Consultation | Bring your MATLAB code on HCC supercomputers     |
-
-
-Password for all demo accounts is **HCC\_matlab2013**.
-Replace `<group name>` with `demo` and `<username>` with `demoXX`
-(e.g. `demo01`).
-
--   Get started with [For Windows Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_windows_users/)
-    or [For Mac/Linux Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_maclinux_users/).
--   Hands On: [MATLAB on HCC](https://hcc.unl.edu/docs/guides/submitting_jobs/submitting_matlab_jobs/)
--   Sample code for MATLAB on HCC:
-    &lt;[matlab\_dir.zip](https://unl.box.com/s/u19fy7cjeswfl1wi7h1nkeeie8gl3z90)&gt;
--   Sample code for Parallel MATLAB Job:
-    &lt;[parallel\_matlab\_dir.zip](https://unl.box.com/s/fhl3kf6hg8dmtozkphq3u2r58yexrppe)&gt;

content/events/2013/hcc_mpi_workshop_2013.md

-+++
-title = "HCC MPI Workshop 2013"
-description = "HCC MPI Workshop 2013."
-+++
-
-Workshop presentation slides <[mpi\_workshop.pdf](https://unl.box.com/s/7rufq2a39n2vektg19ko9fjcbios4kqp)>
-
-| Time    | Title                   | Description                                    |
-|---------|-------------------------|------------------------------------------------|
-| 1pm-2pm | Demo/Hand-On Practice   | Implementing a MPI code on HCC supertcomputers |
-| 2pm-3pm | Individual Consultation | Bring your research code on HCC supercomputers |
-
-Password for all demo accounts is **HCC\_mpi2013**.
-Replace `<group name>` with `demo` and `<username>` with `demoXX` (e.g. `demo01`).
-
--   Get started with [For Windows Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_windows_users/)
-    or [For Mac/Linux Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_maclinux_users/).
--   Sample code for Fortran/C on HCC:
-    &lt;[serial\_dir.zip](https://unl.box.com/s/khkpt68pe3k0lu2ythn9kzjeva40itdd)&gt;
--   Sample code for MPI on HCC:
-    &lt;[mpi\_dir.zip](https://unl.box.com/s/fekjdxx82gxp3x75nbsrqmrri52d4zlp)&gt;
--   For more details of this demonstration, see [MPI Jobs on
-    HCC](https://hcc.unl.edu/docs/guides/submitting_jobs/submitting_an_mpi_job/).  
-
-

content/events/2014/_index.md

-+++
-title = "2014"
-description = "Historical listing of various HCC events for the year 2014."
-weight = "50"
-+++
-
-Historical listing of HCC Events
-----------
-
-{{% children %}}

content/events/2015/_index.md

-+++
-title = "2015"
-description = "Historical listing of various HCC events for the year 2015."
-weight = "40"
-+++
-
-Historical listing of HCC Events
-----------
-
-{{% children %}}

content/events/2016/_index.md

-+++
-title = "2016"
-description = "Historical listing of various HCC events for the year 2016."
-weight = "30"
-+++
-
-Historical listing of HCC Events
-----------
-
-{{% children %}}

content/events/2016/hcc_qiime_workshop_2016.md

-+++
-title = "HCC QIIME Workshop 2016"
-description = "HCC QIIME Workshop 2016."
-+++
-
-When:   October 20, 2016
-
-Where:  NIC Food Innovation Campus room 277
-
-             1901 N. 21st St., Lincoln, 68588
-
-[Details and Agenda](https://hcc.unl.edu/hcc-qiime-workshop)
-
-------------------------------------------------------------------------
-
-Materials
----------
-
-Slides for morning
-introduction: [QIIME\_2016\_intro.pdf](https://unl.box.com/s/d2o92uoar7x59a7rxl0f3y7o3ncy0swq)
-
-Software Carpentry Unix Shell
-Lessons: [http://eharstad.github.io/shell-novice/](http://eharstad.github.io/shell-novice/)
-
-Slides for HCC
-Overview: [2016\_Qiime.pdf](https://unl.box.com/s/4gryu7ny8lo95fs8clyu566k2ubbhtef)
-
-QIIME
-slides: [QIIME\_Talk\_Oct20.pdf](https://unl.box.com/s/h4zi0h27t1t16u9due3ybfrxmsdebzin)
-
-QIIME
-tutorial: [http://bioinformatics.unl.edu/qiime_tutorial.pdf](http://bioinformatics.unl.edu/qiime_tutorial.pdf)
-
-------------------------------------------------------------------------
-
-**What you need to do before Thursday October 20th**
-----------------------------------------------------
-
-*Participants will need to bring a laptop with them to the workshop.* In addition, there are a few things that are required to be completed before you arrive:
---------------------------------------------------------------------------------------------------------------------------------------------------------------
-
-1.  To participate in this workshop, you will need to
-    [sign up for an HCC account](http://hcc.unl.edu/new-user-request)
-    (if you do not already have one). Please complete the account
-    application and [DUO two-factor authentication
-    setup](https://hcc-docs.unl.edu/display/HCCDOC/Setting+up+and+using+Duo)
-    before Thursday. This process requires advisor approval (via email)
-    and a visit to the HCC offices in the Schorr Center to activate your
-    account, so it can sometimes take a day or more to complete. Please
-    plan accordingly. If you still do not have your account set up by
-    Thursday, please arrive at the workshop by 8:30AM to get help.
-2.  Once you have your HCC account and DUO set up, please make sure that
-    you are able to log into the HCC clusters (instructions for [Windows
-    Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_windows_users/)
-    and [Mac/Linux
-    Users](https://hcc.unl.edu/docs/quickstarts/connecting/for_maclinux_users/).
-    If you have any problems logging in, please email us at
-    [hcc-support@unl.edu](mailto:hcc-support@unl.edu)
-3.  On Thursday we will be demonstrating how to transfer files using
-    Globus Connect. Before arriving at the workshop, please log in to
-    the
-    [Globus Web App](https://www.globus.org/app/transfer)
-    using your My.UNL credentials (choose *University of
-    Nebraska-Lincoln* from the drop down menu).  Next, install the
-    Globus Connect Personal app on your laptop (directions for
-    [Mac OS X](https://docs.globus.org/how-to/globus-connect-personal-mac/),
-    [Linux](https://docs.globus.org/how-to/globus-connect-personal-linux/),
-    and
-    [Windows](https://docs.globus.org/how-to/globus-connect-personal-windows/)
-    so that you can begin using Globus to transfer data to and from your
-    laptop.