Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
N
NGS-intro-course
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
courses
NGS-intro-course
Commits
f67f342c
Commit
f67f342c
authored
11 years ago
by
Laros
Browse files
Options
Downloads
Patches
Plain Diff
Using pframes in connecting lecture.
parent
40622af6
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
connecting/connecting.tex
+50
-81
50 additions, 81 deletions
connecting/connecting.tex
with
50 additions
and
81 deletions
connecting/connecting.tex
+
50
−
81
View file @
f67f342c
...
...
@@ -30,9 +30,8 @@
% First page of the presentation.
\section
{
Introdution
}
\begin{frame}
\frametitle
{
Servers
}
\subsection
{
Servers
}
\begin{pframe}
Remote machines can be very convenient:
\begin{itemize}
\item
One central machine for calculation.
...
...
@@ -42,23 +41,22 @@
\item
Multiple users can use it at the same time.
\item
\ldots
\end{itemize}
\end{frame}
\end{
p
frame}
\section
{
Using servers
}
\begin{frame}
\frametitle
{
Logging in
}
\subsection
{
Logging in
}
\begin{pframe}
There are lots of ways to connect to a server.
\begin{itemize}
\item
HTTP -- When visiting websites.
\item
IMAP -- When fetching mail.
\item
\ldots
\end{itemize}
\
big
skip
\
med
skip
\pause
In order to execute commands, we need to
\emph
{
log in
}
.
\
big
skip
\
med
skip
We use a
\emph
{
secure
}
protocol to log in.
\begin{itemize}
...
...
@@ -66,15 +64,13 @@
\item
When working with patient data, we don't want eavesdropping.
\item
The connection from your machine to the server is
\emph
{
encrypted
}
.
\end{itemize}
\end{frame}
\begin{frame}
[fragile]
\frametitle
{
Secure Shell
}
\end{pframe}
\subsection
{
Secure Shell
}
\begin{pframe}
\begin{lstlisting}
[language=none, caption=Using Secure Shell (ssh)..]
$
ssh user@host
\end
{
lstlisting
}
\bigskip
\begin
{
table
}
[]
\begin
{
center
}
...
...
@@ -93,12 +89,11 @@
\begin
{
lstlisting
}
[
language
=
none, caption
=
Example.
]
$
ssh course@shark
\end{lstlisting}
\end{frame}
\end{
p
frame}
\section
{
File transfer
}
\begin{frame}
\frametitle
{
Copying data
}
\subsection
{
Copying data
}
\begin{pframe}
We frequently need to transfer data before and after we do an analysis.
\begin{itemize}
\item
The input needs to be on the server.
...
...
@@ -116,15 +111,13 @@
\item
Copy data from the server to your machine (downloading).
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}
[fragile]
\frametitle
{
Secure Copy
}
\end{pframe}
\subsection
{
Secure Copy
}
\begin{pframe}
\begin{lstlisting}
[language=none, caption=Copying something to the server.]
$
scp localfile user@host:
/
path
/
to
/
remotefile
\end
{
lstlisting
}
\bigskip
\begin
{
table
}
[]
\begin
{
center
}
...
...
@@ -139,18 +132,17 @@
\bt
{
remotefile
}
&
Name of the file on the
\emph
{
server
}
.
\end
{
tabular
}
\end
{
center
}
\caption
{}
\caption
{
Description of the parameters.
}
\label
{}
\end
{
table
}
\end
{
frame
}
\begin
{
frame
}
[
fragile
]
\frametitle
{
Secure Copy
}
\end
{
pframe
}
\begin
{
pframe
}
\begin
{
lstlisting
}
[
language
=
none, caption
=
Example.
]
$
scp localfile host:
$
scp host:remotefile .
\end
{
lstlisting
}
\vspace
{
-
0
.
5
cm
}
\begin
{
table
}
[]
\begin
{
center
}
...
...
@@ -168,12 +160,11 @@
\caption
{
Some defaults
(
when left empty
)
.
}
\label
{}
\end
{
table
}
\end
{
frame
}
\end
{
p
frame
}
\section
{
Connecting from an other OS
}
\begin
{
fframe
}
\frametitle
{
Windows
}
\subsection
{
Windows
}
\begin
{
pframe
}
Windows does not have the
\bt
{
ssh
}
command, but there are programs that
give the same functionality.
\bigskip
...
...
@@ -189,12 +180,10 @@
\end
{
itemize
}
\vfill
\bs
{
http:
//
www.chiark.greenend.org.uk
/
~sgtatham
/
putty
}
\end
{
fframe
}
\begin
{
frame
}
\frametitle
{
Windows
}
\permfoot
{
http:
//
www.chiark.greenend.org.uk
/
~sgtatham
/
putty
}
\end
{
pframe
}
\begin
{
pframe
}
\begin
{
figure
}
[]
\begin
{
center
}
\includegraphics
[
height
=
0
.
8
\textheight
]
{
PuTTY
_
login
}
...
...
@@ -202,11 +191,9 @@
\caption
{
Connecting to a server using PuTTY.
}
\label
{}
\end
{
figure
}
\end
{
frame
}
\begin
{
frame
}
\frametitle
{
Windows
}
\end
{
pframe
}
\begin
{
pframe
}
\begin
{
figure
}
[]
\begin
{
center
}
\includegraphics
[
height
=
0
.
8
\textheight
]
{
PuTTY
_
terminal
}
...
...
@@ -214,12 +201,11 @@
\caption
{
A terminal when connected to a server.
}
\label
{}
\end
{
figure
}
\end
{
frame
}
\end
{
p
frame
}
\section
{
Examples
}
\begin
{
frame
}
\frametitle
{
Typical workflow
}
\subsection
{
Typical workflow
}
\begin
{
pframe
}
When doing an analysis, the general workflow looks like this:
\begin
{
itemize
}
\item
First copy the input data to the server.
...
...
@@ -229,16 +215,14 @@
\item
Clean up the input data and the results on the server.
\item
Log out.
\end
{
itemize
}
\end
{
frame
}
\begin
{
frame
}
[
fragile
]
\frametitle
{
Typical workflow: an example
}
\end
{
pframe
}
\subsection
{
Typical workflow: an example
}
\begin
{
pframe
}
Step one: preparing the input.
\bigskip
On your machine, copy the raw data to the server, then log in on the server.
\bigskip
\begin
{
lstlisting
}
[
language
=
none, caption
=
Copy data to the server and log
in.
]
...
...
@@ -248,16 +232,13 @@
\bigskip
Now the file
\bt
{
reads.fq
}
is available on the server.
\end
{
frame
}
\begin
{
frame
}
[
fragile
]
\frametitle
{
Typical workflow: an example
}
\end
{
pframe
}
\begin
{
pframe
}
Step two: The analysis.
\bigskip
On the server, you can do an analysis.
\bigskip
\begin
{
lstlisting
}
[
language
=
none, caption
=
Example pipeline.
]
$
bwa aln ./indexes/chr17.fa reads.fq > reads.sai
...
...
@@ -269,40 +250,34 @@
$
samtools pileup -vcf ./indexes/chr17.fa
\
reads.bam.sorted.bam > reads.pileup
\end{lstlisting}
\end{frame}
\begin{frame}
[fragile]
\frametitle
{
Typical workflow: an example
}
\end{pframe}
\begin{pframe}
Step three: Retrieving the output.
\bigskip
Copy the output from the server back to your own machine.
\bigskip
\begin{lstlisting}
[language=none, caption=Copy data from the server.]
$
scp course@shark:reads.pileup .
\end
{
lstlisting
}
\bigskip
\pause
Step four: Cleaning up.
\bigskip
Clean up on the server and leave.
\bigskip
\begin
{
lstlisting
}
[
language
=
none, caption
=
Delete temporary files and log
out.
]
$
rm reads.*
$
logout
\end
{
lstlisting
}
\end
{
frame
}
\end
{
p
frame
}
\section
{
Why remote servers?
}
\begin
{
fframe
}
\frametitle
{
Clusters
}
\subsection
{
Clusters
}
\begin
{
pframe
}
\begin
{
figure
}
[]
\begin
{
center
}
\includegraphics
[
height
=
0
.
8
\textheight
]
{
supercomputer
}
...
...
@@ -313,11 +288,9 @@
\vfill
\permfoot
{
http:
//
en.wikipedia.org
/
wiki
/
IBM
\_
Roadrunner
}
\end
{
fframe
}
\begin
{
frame
}
\frametitle
{
Clusters
}
\end
{
pframe
}
\begin
{
pframe
}
Massive parallel computing.
\begin
{
itemize
}
\item
A large number of computers working together.
...
...
@@ -337,11 +310,9 @@
\item
Chop the problem op in parts
/
combine the results.
\end
{
itemize
}
\end
{
itemize
}
\end
{
frame
}
\begin
{
frame
}
\frametitle
{
Clusters
}
\end
{
pframe
}
\begin
{
pframe
}
\begin
{
figure
}
[]
\begin
{
center
}
\includegraphics
[
height
=
0
.
8
\textheight
]
{
cluster
-
schematic
}
...
...
@@ -349,11 +320,9 @@
\caption
{
Schematic overview of a cluster.
}
\label
{}
\end
{
figure
}
\end
{
frame
}
\begin
{
frame
}
\frametitle
{
Clusters
}
\end
{
pframe
}
\begin
{
pframe
}
General characteristics of a cluster.
\begin
{
itemize
}
\item
Jobs are submitted to a
\emph
{
control node
}
.
...
...
@@ -368,11 +337,11 @@
\item
Jobs can be prioritised.
\item
\ldots
\end
{
itemize
}
\end
{
frame
}
\end
{
p
frame
}
\section
{
Questions?
}
\lastpagetemplate
\begin
{
f
frame
}
\begin
{
p
frame
}
\begin
{
center
}
\bigskip
\bigskip
...
...
@@ -386,5 +355,5 @@
\vfill
\permfoot
{
https:
//
humgenprojects.lumc.nl
/
trac
/
humgenprojects
/
wiki
/
NGS
-
intro
}
\end
{
f
frame
}
\end
{
p
frame
}
\end
{
document
}
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment