<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="4.3.3">Jekyll</generator><link href="https://dyammons.github.io/csu-general-coding/feed.xml" rel="self" type="application/atom+xml"/><link href="https://dyammons.github.io/csu-general-coding/" rel="alternate" type="text/html" hreflang="en"/><updated>2024-01-09T12:22:44+00:00</updated><id>https://dyammons.github.io/csu-general-coding/feed.xml</id><title type="html">FACC bioinformatics</title><subtitle>homepage for all general coding workshop resources </subtitle><entry><title type="html">lesson 1 - Alpine overview and customization</title><link href="https://dyammons.github.io/csu-general-coding/lessons/2023/lesson1/" rel="alternate" type="text/html" title="lesson 1 - Alpine overview and customization"/><published>2023-12-15T13:00:00+00:00</published><updated>2023-12-15T13:00:00+00:00</updated><id>https://dyammons.github.io/csu-general-coding/lessons/2023/lesson1</id><content type="html" xml:base="https://dyammons.github.io/csu-general-coding/lessons/2023/lesson1/"><![CDATA[<h2 data-toc-text="Apline overview" id="an-overview-of-alpine">An overview of Alpine</h2> <p>All information pertaining to Alpine use obtained from the <a href="https://curc.readthedocs.io/en/latest/index.html">CURC read the docs page</a>. The goal of the overview is to introduce key concepts and provide a basis from which Users can better navigate the documentation.</p> <h3 id="general-use-and-purpose">General use and purpose</h3> <blockquote> <p><em>“Alpine is a heterogeneous supercomputing cluster based primarily on the AMD EPYC “Milan” CPUs with Nvidia A100 GPUs; AMD MI100 GPUs; HDR InfiniBand; and 25 Gb Ethernet. Alpine is jointly funded by the University of Colorado Boulder, the University of Colorado Anschutz, Colorado State University, and the National Science Foundation (award 2201538).”</em></p> </blockquote> <p><br/></p> <p>UC Boulder RC Mission:</p> <blockquote> <p><em>“CU Boulder Research Computing (RC) supports fair and equitable access for a diverse set of stakeholders to innovative large-scale computing and data resources emphasizing open, stable, and secure access to data while maintaining required measures of compliance for our sponsors. “</em></p> </blockquote> <h3 id="accessing-the-computer">Accessing the computer</h3> <p>There are a few different ways to access the supercomputer. No approach is inherently better than another, so the choice is up to the User to decide what works best for them.</p> <p><br/></p> <h4 id="1-terminal">1. Terminal</h4> <p>To access the server via a terminal you will need a linux terminal (Mac) or a third party application to launch a terminal through a subprocess (Windows; typically Ubuntu, git bash, putty).</p> <p>Once a terminal is installed access is fairly straight forward. Simply launch a terminal then <code class="language-plaintext highlighter-rouge">ssh</code> onto the server.</p> <p><br/></p> <blockquote> <p><strong><em>NOTE:</em></strong> <code class="language-plaintext highlighter-rouge">ssh</code> stand for Secure Shell protocol and is a secure method to connect your personal laptop (or desktop) to the remote server.</p> </blockquote> <p><br/></p> <p>The command to <code class="language-plaintext highlighter-rouge">ssh</code> onto the server looks like:</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>ssh username@login.rc.colorado.edu
</code></pre></div></div> <p>where “username” will be whatever UC Boulder has on record. For CSU Users this is typical your NetID followed by “@colostate.edu”.</p> <p>For example mine would look like:</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>ssh dyammons<span class="se">\@</span>colostate.edu@login.rc.colorado.edu
</code></pre></div></div> <p><br/></p> <blockquote> <p><strong><em>NOTE:</em></strong> Because CSU Users have a special character in their usernames (<code class="language-plaintext highlighter-rouge">@</code>) the addition of a backslash (<code class="language-plaintext highlighter-rouge">\</code>) is required to cancel out the special effect of the <code class="language-plaintext highlighter-rouge">@</code> and allow the computer to read it as part of the username.</p> </blockquote> <p><br/></p> <p>Once the above command is run you will initiate an interaction with the computer and be prompted with:</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="o">(</span>NetID@colostate.edu@login.rc.colorado.edu<span class="o">)</span> Password:
</code></pre></div></div> <p>You will now need to enter in your CSU login password and verify the login using 2-factor authentication. There are two options to accomplish this…</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c">#option 1:</span>
<span class="o">(</span>NetID@colostate.edu@login.rc.colorado.edu<span class="o">)</span> Password: password,push
</code></pre></div></div> <p>This will send a push to duo that you can then accept.</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c">#option 2:</span>
<span class="o">(</span>NetID@colostate.edu@login.rc.colorado.edu<span class="o">)</span> Password: password
</code></pre></div></div> <p>If you only enter in you password you will be prompted with:</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="o">(</span>NetID@colostate.edu@login.rc.colorado.edu<span class="o">)</span> Enter passcode:
</code></pre></div></div> <p>The computer is asking for your 6 digit authentication key that can be retrieved from the duo app</p> <p><br/></p> <blockquote> <p><strong><em>NOTE:</em></strong> When entering in a password in a terminal you will typically not be able to see what you are typing, this is for security purposes.</p> </blockquote> <p><br/></p> <p>Once the connection is established a welcome message will appear, with some useful information and state that you are on a login node (more on this later).</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Last login: Sat Nov 11 11:42:17 2023 from 129.82.95.71
Welcome to CU-Boulder Research Computing.

  <span class="k">*</span> Website http://colorado.edu/rc
  <span class="k">*</span> Questions? rc-help@colorado.edu
  <span class="k">*</span> Subscribe to system announcements: https://curc.statuspage.io/
  <span class="k">*</span> Please <span class="nb">type </span>rc-help <span class="k">for </span>the Acceptable Use Policy and a short <span class="nb">help </span>page.

You are using login node: login11
<span class="o">(</span>base<span class="o">)</span> login11 ~ <span class="err">$</span>
</code></pre></div></div> <p>For anyone following along, we will now close our connection to the server and switch to connecting via OnDemand. To do this all you need to do is type <code class="language-plaintext highlighter-rouge">exit</code> and you will be be prompted with:</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="o">(</span>base<span class="o">)</span> login11 ~ <span class="nv">$ </span><span class="nb">exit
logout
</span>Connection to login.rc.colorado.edu closed.
</code></pre></div></div> <p>While I typically prefer to use OnDemand (introduced below) to interact with Alpine, it is important to understand this more “primitive” approach (especially if OnDemand is down) and to better understand how User-computer interactions work (which will come in play with data transfer).</p> <h4 id="2-ondemand">2. OnDemand</h4> <p>This is personally my favorite method of connecting to the server. It is versatile web browser based application that allows for interaction via a variety of approaches.</p> <p>OnDemand can be accessed at: https://ondemand-rmacc.rc.colorado.edu/</p> <p>For first time login you will have to select your institution, but if you select remember my selection you will not have to do this step again.</p> <p>IMG IMG</p> <h3 id="file-systems">File systems</h3> <p>The file system consists of four major systems: <code class="language-plaintext highlighter-rouge">/home</code>, <code class="language-plaintext highlighter-rouge">/scratch</code>, <code class="language-plaintext highlighter-rouge">/projects</code>, and <code class="language-plaintext highlighter-rouge">/pl</code>. Each file system has a designated purpose and we will be exploring each space.</p> <h3 id="resources">Resources</h3> <h3 id="jobs">Jobs</h3> <h2 data-toc-text="Personalization" id="terminal-personalization">Terminal personalization</h2> <h3 id="aliases">Aliases</h3> <h3 id="ps1">PS1</h3> <h2 data-toc-text="Global executables" id="setting-up-global-executables">Setting up global executables</h2>]]></content><author><name></name></author><category term="lessons"/><category term="overview"/><category term="bash"/><summary type="html"><![CDATA[Alpine orientation, alias creation, and global executables]]></summary></entry></feed>