From 22537671031094e29fc596fb7039972d2cd24372 Mon Sep 17 00:00:00 2001
From: nicolas <nfontrodona@orange.fr>
Date: Tue, 14 Jun 2022 18:26:31 +0200
Subject: [PATCH] Change first slide

---
 presentation_gblk.tex | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/presentation_gblk.tex b/presentation_gblk.tex
index 96bea12..8fbb6a5 100644
--- a/presentation_gblk.tex
+++ b/presentation_gblk.tex
@@ -117,14 +117,21 @@
 
 \begin{frame}{Data versioning}{}
 
-During a bioinformatic project we often need to develop some code that will produce results. Sometimes, we might want to keep and associate results to a specific version of our code to get back to them in the future. \\
+In a bioinformatic project:
+
+\begin{itemize}
+\item Code
+\item Results produced by this code
+\item Save those results
+\begin{itemize}
+\item Compare results between code versions
+\item Have an overview of results produced by the project code
+\end{itemize}
+\end{itemize}
 
 \alert{Data versioning tools} can help us to achieve this. \\
 
 
-\begin{center}
-\alert{Data Versioning} is the storage of different version of data that evolve over time
-\end{center}
 \begin{block}{Controlling your data version with a tool may help you to}
 \begin{itemize}
 \item Save you some time to manage and track your data version
-- 
GitLab