diff options
Diffstat (limited to 'slides-intro.tex')
| -rw-r--r-- | slides-intro.tex | 389 |
1 files changed, 216 insertions, 173 deletions
diff --git a/slides-intro.tex b/slides-intro.tex index 3ffedf9..c395cdc 100644 --- a/slides-intro.tex +++ b/slides-intro.tex @@ -35,31 +35,32 @@ %% Set the title \title{\huge\textbf{BIG} Data, \textbf{BIG} responsibility - \\ {\normalsize Introducing \emph{Maneage}: customizable framework for \emph{man}aging data lin\emph{eage}}} + \\\vspace{2mm} \large Maneage: \emph{Man}aging data lin\emph{eage} for long-term and archivable reproducibility \\\vspace{1mm} \footnotesize (Published in CiSE 23 (3), pp 82-91: \textcolor{blue}{\href{https://doi.org/10.1109/MCSE.2021.3072860}{DOI:10.1109/MCSE.2021.3072860}}, \textcolor{blue}{\href{https://arxiv.org/abs/2006.03018}{arXiv:2006.03018}})} %% Set the author -\author{\vspace{1cm}\\ +\author{\\ \href{https://akhlaghi.org}{Mohammad Akhlaghi}\\\vspace{0.5mm} \footnotesize - Instituto de Astrof\'isica de Canarias ({\scriptsize IAC}), Tenerife, Spain + Centro de Estudios de F\'isica del Cosmos de Arag\'on ({\scriptsize CEFCA}), Teruel, Spain\vspace{8mm} } %% Set the date and insitutional logos. -\date{\footnotesize\vspace{0cm}\\ - \textcolor{white}{PLACE HOLDER}\\\textcolor{white}{MONTH DAY, YEAR} \\ - \tiny\vspace{3mm} +\date{\footnotesize\vspace{-5mm}\\ + \textcolor{black}{Royal Observatory Coffee talk; Edinburgh}\\ + \textcolor{black}{23rd of May 2023} \\ + \tiny\vspace{9mm} Most recent slides available in link below (this PDF is built from \href{http://git.maneage.org/slides-intro.git}{Git commit} \gitcommit):\\ \footnotesize\textcolor{blue}{\url{https://maneage.org/pdf/slides-intro.pdf}}\\ - \vspace{2mm}\hspace{-0.25cm} - \raisebox{+0.4\height}{\includegraphics[width=2.5cm]{img/ministerio-ciencia.png}} - \raisebox{+0.3\height}{\includegraphics[width=1.3cm]{img/sundial.png}} + \vspace{2mm} + \raisebox{+0.4\height}{\includegraphics[width=3cm]{img/jcava.jpg}} + \includegraphics[width=1cm]{img/cefca.png} \includegraphics[width=1.2cm]{img/iac.png} \includegraphics[width=1cm]{img/eu-sundial.png} \raisebox{0.13\height}{\includegraphics[width=1cm]{img/eu-regional.png}} \raisebox{0.05\height}{\includegraphics[width=1cm]{img/eu-rdaeu4.png}} \raisebox{+0.1\height}{\includegraphics[width=1.4cm]{img/rda-europe.png}} - \raisebox{+1.3\height}{\includegraphics[width=1.4cm]{img/ull.png}} - { }\raisebox{+0.5\height}{\includegraphics[width=2cm]{img/gobierno-canarias.png}}\\ + \raisebox{+1\height}{\includegraphics[width=1.5cm]{img/aragon.png}} + \raisebox{+0.8\height}{\includegraphics[width=1.6cm]{img/gobierno-canarias.png}}\\ \vspace{1cm} } @@ -88,10 +89,6 @@ \titlepage \end{frame} - - - - \begin{frame}{Let's start with this nice image of the Wirlpool galaxy (M51): \small{\url{https://i.redd.it/jfqgpqg0hfk11.jpg}}} \begin{center} \includegraphics[width=0.8\linewidth]{img/m51-amateur.jpg} @@ -231,9 +228,88 @@ for computational reproducibility] \end{frame} - \begin{frame}{``Reproducibility crisis'' in the sciences? (Baker 2016, Nature 533, 452)} - \centering - \includegraphics[width=0.85\linewidth]{img/reproducibility-crisis.jpg} + + + + \begin{frame}{``Reproducibility crisis'' in the sciences? (Baker 2016, Nature 533, 452, \textcolor{blue}{\href{https://doi.org/10.1038/533452a}{DOI:10.1038/533452a}})} + \Large + 1576 researchers participated in a survey by Nature, \alert{$90\%$} believed in a crisis! + + \vspace{7mm} + \begin{center} + \begin{tabular}{ |l|r| } + \hline + Status & $\%$ agreed \\ + \hline + \alert{Yes}, a significant crisis & \textcolor{red}{$52$} \\ + \alert{Yes}, a slight crisis & \textcolor{red}{$38$} \\ + Don't know & $7$ \\ + No, there is no crisis & $3$ \\ + \hline + \end{tabular} + \end{center} + + \vspace{7mm} + Full PDF available at \textcolor{blue}{\url{https://www.nature.com/articles/533452a.pdf}} + \end{frame} + + + + + + \begin{frame}{Our solution: CiSE 23 (3), pp 82-91: \textcolor{blue}{\href{https://doi.org/10.1109/MCSE.2021.3072860}{DOI:10.1109/MCSE.2021.3072860}}, \textcolor{blue}{\href{https://arxiv.org/abs/2006.03018}{arXiv:2006.03018}}} + \begin{columns} + \column{0.4\linewidth} + \includegraphics[width=\linewidth]{img/maneage-paper.png} + \column{0.6\linewidth} + \includegraphics[width=\linewidth]{img/maneage-webpage.png} + \begin{center} + \huge{https://maneage.org} + \end{center} + \end{columns} + \end{frame} + + + + \begin{frame}{Recognition 1: RDA adoption grant (2019) to IAC for Maneage} + \begin{center} + \includegraphics[width=3cm]{img/rda.png}\hspace{1cm} + \includegraphics[width=1.8cm]{img/iac.png} + \includegraphics[width=\linewidth]{img/h2020.jpg} + \end{center} + + \vspace{1cm} For Maneage, the \alert{IAC} is selected as + a \alert{Top European organization} funded to adopt RDA + Recommendations and Outputs. + + \vspace{1cm} + \scriptsize + \begin{itemize} + \item Research Data Alliance was launched by the \alert{European + Commission}, NSF, National Institute of Standards and + Technology, and the Australian Government’s Department of + Innovation. + \item RDA Outputs are the technical and social infrastructure + solutions developed by RDA Working Groups or Interest + Groups that enable data sharing, exchange, and + interoperability. + \end{itemize} + + \vspace{0.2cm} + \end{frame} + + + + + + \begin{frame}{Recognition 2: ``News and Views'' in Nature Astronomy (\textcolor{blue}{\href{https://ui.adsabs.harvard.edu/abs/2021NatAs...5..986K}{2021NatAs...5..986K}})} + \begin{center} + \includegraphics[width=\linewidth]{img/nature-astronomy.png} + \end{center} + + \vspace{1cm} + Free-to-read link: \textcolor{blue}{\url{https://rdcu.be/cmYVx}}\\ + DOI: \textcolor{blue}{\href{https://doi.org/10.1038/s41550-021-01402-3}{10.1038/s41550-021-01402-3}} \end{frame} @@ -290,7 +366,7 @@ for computational reproducibility] \vspace{-5mm} \includegraphics[width=0.7\linewidth]{img/hale-prime-focus-marked.jpg}\\ \vspace{-0.6mm} - \tiny \href{http://slittlefair.staff.shef.ac.uk/teaching/phy217/lectures/telescopes/L07/index.html}{http://slittlefair.staff.shef.ac.uk} + \tiny \href{https://slittlefair.staff.shef.ac.uk/teaching/phy217/lectures/telescopes/l07}{http://slittlefair.staff.shef.ac.uk} \end{center} \column{0.5\linewidth} @@ -318,7 +394,7 @@ for computational reproducibility] \vspace{-5mm} \includegraphics[width=0.7\linewidth]{img/hale-prime-focus.jpg}\\ \vspace{-0.6mm} - \tiny \href{http://slittlefair.staff.shef.ac.uk/teaching/phy217/lectures/telescopes/L07/index.html}{http://slittlefair.staff.shef.ac.uk} + \tiny \href{https://slittlefair.staff.shef.ac.uk/teaching/phy217/lectures/telescopes/l07}{http://slittlefair.staff.shef.ac.uk} \end{center} \column{0.5\linewidth} @@ -336,9 +412,9 @@ for computational reproducibility] \centering \vspace{3mm} - \includegraphics[width=0.8\linewidth]{img/digital-tunnel.jpg}\\ + \includegraphics[width=0.88\linewidth]{img/binary-blue.jpg}\\ \vspace{-0.6mm} - \tiny \href{https://tsongas.com/newsletter_articles/the-new-electronic-version-of-the-advantage/digital-tunnel-wallpaper/}{https://tsongas.com} + \tiny \href{https://commons.wikimedia.org/wiki/File:Binary_blue.jpg}{Wikimedia Commons} \end{columns} \end{frame} @@ -354,14 +430,15 @@ for computational reproducibility] \begin{frame}{General outline of a project (after data collection)} \include{tex/project-graph} \end{frame} \newcommand{\sver}{} \begin{frame}{General outline of a project (after data collection)} \include{tex/project-graph} \end{frame} - \begin{frame}{Different package managers have different versions of software (repology.org, 2019/11/20)} + \begin{frame}[t]{Different package managers have different versions of software (repology.org, 2021/12/02)} \begin{columns} \column{7cm} \center Astropy\\ - \includegraphics[width=2.2cm]{img/distros-astropy.pdf} + \includegraphics[width=2.8cm]{img/distros-astropy.pdf} \column{7cm} \center GNU Astronomy Utilities (Gnuastro)\\ - \includegraphics[width=2.7cm]{img/distros-gnuastro.pdf} + \includegraphics[trim={0 8cm 0 0}, clip, width=2.9cm]{img/distros-gnuastro.pdf} + \includegraphics[trim={0 0 0 16cm}, clip, width=2.9cm]{img/distros-gnuastro.pdf} \end{columns} \end{frame} \newcommand{\srep}{} @@ -386,13 +463,13 @@ for computational reproducibility] al. 2020, CiSE, DOI:\textcolor{blue}{\href{https://doi.org/10.1109/MCSE.2019.2949413}{10.1109/MCSE.2019.2949413}}). } \end{frame} - \begin{frame}{Impact of ``Dependency hell'' on native building in various hardware (CPU architectures)} + \begin{frame}{Impact of ``Dependency hell'' on native building in various hardware (CPU architectures), retrieved from Debian on 2021/12/02} \begin{columns} \column{7cm} - \includegraphics[width=0.9\linewidth]{img/cpu-arch-astropy.png} + \includegraphics[width=\linewidth]{img/cpu-arch-astropy.png} Astropy depends on Matplotlib \column{6cm} - \includegraphics[width=0.9\linewidth]{img/cpu-arch-gnuastro.png} + \includegraphics[width=1.05\linewidth]{img/cpu-arch-gnuastro.png} GNU Astronomy Utilities doesn't. \end{columns} \end{frame} @@ -444,23 +521,16 @@ for computational reproducibility] \begin{frame}{Science is a tricky business} - \begin{center} - \includegraphics[width=0.9\linewidth]{img/nature-cartoon.jpg} - \end{center} - - \vspace{-0.3cm}\hfill - {\tiny Image from nature.com - (``\href{https://www.nature.com/articles/d41586-017-07522-z}{Five - ways to fix statistics}'', Nov 2017)}\hspace{7mm} - \vspace{-1mm} \begin{tcolorbox}[boxsep=0pt,left=1mm,right=1mm,top=1mm,bottom=1mm] - \small Data analysis [...] is a \alert{human + \large Data analysis [...] is a \alert{human behavior}. Researchers who hunt hard enough will turn up a result that fits statistical criteria, but their \alert{discovery} will probably be a \alert{false positive}. - \hfill Five ways to fix statistics, Nature, 551, Nov 2017. + \vspace{3mm} + \small + \hfill Five ways to fix statistics (Nature, 551, Nov 2017; DOI:\textcolor{blue}{\href{https://doi.org/10.1038/d41586-017-07522-z}{10.1038/d41586-017-07522-z}}). \end{tcolorbox} \end{frame} @@ -1185,7 +1255,10 @@ for computational reproducibility] - + \begin{frame}{New projects branch from Maneage} \include{tex/git-branch} \end{frame} + \newcommand{\tomorrow}{1} + \begin{frame}{New projects branch from Maneage} \include{tex/git-branch} \end{frame} + \newcommand{\abstractify}{1} \begin{frame}{New projects branch from Maneage} \include{tex/git-branch} \end{frame} \newcommand{\projinit}{} \begin{frame}{New projects branch from Maneage} \include{tex/git-branch} \end{frame} @@ -1226,6 +1299,12 @@ for computational reproducibility] + \begin{frame}{Any Git-based workflow is possible.} + \centering + \includegraphics[width=1.2\linewidth]{img/figure-branching.pdf} + \end{frame} + + \begin{frame}{Publication of the project} @@ -1242,17 +1321,25 @@ for computational reproducibility] \alert{negligible} compared to a single figure in a paper (usually $\sim100$ kilo-bytes). - \vspace{1cm} The project's pipeline (customized Maneage) can be + \pause + + \vspace{7mm} The project's pipeline (customized Maneage) can be \alert{published} in \begin{itemize} \item \alert{arXiv}: uploaded with the \LaTeX{} source to always stay with the paper \\(for example - \textcolor{blue}{\small\href{https://arxiv.org/abs/1505.01664}{arXiv:1505.01664}}). The - file containing all macros must also be uploaded so arXiv's - server can easily build the \LaTeX{} source. + \textcolor{blue}{\small\href{https://arxiv.org/abs/1505.01664}{arXiv:1505.01664}} or \textcolor{blue}{\href{https://arxiv.org/abs/2006.03018}{arXiv:2006.03018}}). \item \alert{Zenodo}: Along with all the input datasets (many Gigabytes) and software \\(for example - \textcolor{blue}{\small\href{https://doi.org/10.5281/zenodo.3408481}{zenodo.3408481}}) and given a unique DOI. + \textcolor{blue}{\small\href{https://doi.org/10.5281/zenodo.3872247}{zenodo.3872247}}) and given a unique DOI. + \begin{itemize} + \item ... and put links to data in paper! See ending of caption of Figure 1 in the \textcolor{blue}{\href{https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=9403875}{Maneage paper}}. + \end{itemize} + \item \alert{Software Heritage}: to archive the full version-controlled history of the project.\\(for example + {\small \textcolor{blue}{\href{https://archive.softwareheritage.org/swh:1:dir:33fea87068c1612daf011f161b97787b9a0df39f;origin=http://git.maneage.org/paper-concept.git/;visit=swh:1:snp:89af43c4b076a17d9298299f224247038af355ea;anchor=swh:1:rev:313db0b04bd3499f83d9e79fd7e92578cd367c2b}{swh:1:dir:33fea87068c1612daf011f161b97787b9a0df39fk}}}) + \begin{itemize} + \item ... and put links to exact parts of the code! See caption of Listing 1 in the \textcolor{blue}{\href{https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=9403875}{Maneage paper}}. + \end{itemize} \end{itemize} \end{frame} @@ -1260,6 +1347,19 @@ for computational reproducibility] + \begin{frame}{Software Heritage IDs (SWHID); persistent identifier for source code (or any text!)} + + \vspace{5mm} + \includegraphics[width=\linewidth]{img/SWHIDs.png} + \vspace{5mm} + + {\hfill\small For more details, see SoftwareHeritage FAQ (at \textcolor{blue}{\url{https://www.softwareheritage.org/faq}}}) + \end{frame} + + + + + \begin{frame}{Project source and its execution} \begin{tcolorbox} Programs \textcolor{gray}{[here: Scientific projects]} must be @@ -1333,58 +1433,45 @@ for computational reproducibility] - \begin{frame}{RDA adoption grant (2019) to IAC for Maneage} - \begin{center} - \includegraphics[width=3cm]{img/rda.png}\hspace{1cm} - \includegraphics[width=1.8cm]{img/iac.png} - \includegraphics[width=\linewidth]{img/h2020.jpg} - \end{center} - - \vspace{1cm} For Maneage, the \alert{IAC} is selected as - a \alert{Top European organization} funded to adopt RDA - Recommendations and Outputs. - - \vspace{1cm} - \scriptsize - \begin{itemize} - \item Research Data Alliance was launched by the \alert{European - Commission}, NSF, National Institute of Standards and - Technology, and the Australian Government’s Department of - Innovation. - \item RDA Outputs are the technical and social infrastructure - solutions developed by RDA Working Groups or Interest - Groups that enable data sharing, exchange, and - interoperability. - \end{itemize} - - \vspace{0.2cm} - \end{frame} - - + \begin{frame}{Summary:} + Maneage is introduced as a customizable template that will do the + following steps/instructions (all in simple plain text files). + \begin{itemize} + \item \alert{Automatically downloads} the necessary + \emph{software} and \emph{data}. + \item \alert{Builds} the software in a \alert{closed + environment}. + \item Runs the software on data to \alert{generate} the final + \alert{research results}. + \item Only parts affected by a modifcation are re-done. + \item Using LaTeX macros, paper's figures, tables and numbers + will be \alert{Automatically updated}. + \item The whole project is under \alert{version control} (Git) + \alert{encouraging tests/experimentation}. + \item The \alert{Git commit hash} of the project source, is + \alert{printed} in the paper and \alert{on output} data + products. + \item \colorbox{green!30!white}{These slides are available at + \textcolor{blue}{\url{https://maneage.org/pdf/slides-intro.pdf}}.} + \end{itemize} - \begin{frame}{Workshop on Maneage at IAC: \alert{first week of April} (March 30th to April 3rd)} + \begin{tcolorbox}[width=\linewidth, boxsep=1pt, left=1pt, right=1pt, + top=1pt, bottom=1pt] + For a technical description of Maneage's implementation, as well + as a checklist to customize it, and tips on good practices, + please see this page: - We are organizing a workshop to help interested \alert{early career researchers} adopt Maneage. + \textcolor{blue}{\url{https://gitlab.com/maneage/project/-/blob/maneage/README-hacking.md}} - \vspace{5mm} - \begin{columns} - \column{0.25\linewidth} - \centering - \includegraphics[width=\linewidth]{img/rda-europe.png} - \column{0.5\linewidth} - \centering - \includegraphics[width=\linewidth]{img/workshop-shutterstock.png}\\ - {\tiny Image from \href{https://www.shutterstock.com/es/image-vector/managers-workshop-training-manager-skills-brainstorming-1334996078}{shutterstock.com}} + \vspace{3mm} + \hfill \colorbox{green!30!white}{Feel free to contact me: \textcolor{blue}{\large{\url{mohammad@akhlaghi.org}}}} + \end{tcolorbox} + \end{frame} +\end{document} - \column{0.25\linewidth} - \includegraphics[width=0.7\linewidth]{img/iac.png} - \end{columns} - \vspace{7mm} - Please contact \alert{akhlaghi@iac.es} to join (Space is very limited: it is hands-on). - \end{frame} @@ -1419,93 +1506,49 @@ In summary, they only \alert{store a built} environment (they are outputs, not g -\begin{frame}{Existing technologies (Package managers)} - - \begin{itemize} - \item \textbf{Operating system package managers:} - \begin{itemize} - \setlength\itemsep{2mm} - \item For example \texttt{apt} or \texttt{yum} for Debian-based and RedHat-based GNU/Linux operating systems\\(the most common way to install software). - \item Tightly intertwined with the operating system's components\\(arbitrary control of software versions is not easily possible). - \item Older software (for example +5 years) is usually removed. - \end{itemize} - \item \textbf{Conda/Anaconda:} - \begin{itemize} - \setlength\itemsep{2mm} - \item Conda has build instructions for software and their dependencies. - \item But it doesn't go down to the C library or the lower-level components of operating system. - \item It is written in Python (can't be used later when current Python is depreciated). - \item Authors of Uhse+2019\footnote{\url{http://dx.doi.org/10.1002/cppb.20097}} report\footnote{\url{https://github.com/conda-forge/conda-forge.github.io/issues/787}} that their Conda environment breaks roughly every 3 months\\(Conda environments need to be updated to be used later! Breaking reproducibility). - \end{itemize} - \item \textbf{Nix, or GNU Guix:} - \begin{itemize} - \setlength\itemsep{2mm} - \item Deliver perfectly reproducible builds (bit-wise reproducibility of software), needs root access. - \item Doesn't \emph{require} documentation of dependencies. - \end{itemize} - \item \textbf{Spack:} Similar to Nix/Guix but written in Python. - \end{itemize} -\end{frame} - -\begin{frame}{Existing technologies (workflow tools)} - \begin{itemize} - \setlength\itemsep{4mm} - \item \textbf{Binder:} (\url{https://mybinder.org}) Docker+Conda. - \item \textbf{Galaxy:} (\url{https://galaxyproject.org}) A web-based user interface, primarily designed for genomics. The GUI make it hard to automate, and has too many dependencies. Very similar to GenePattern (2008 to 2017): with +40,000 users and $\sim4000$ jobs running per week, but cut due to funding. - \item \textbf{Sciunit:} (\url{https://sciunit.run}) Parses program binaries to try to infer their dependencies and copy them. - \item \textbf{Popper:} (\url{https://falsifiable.us}), HCL (previously used by GitHub Actions) + Conda + Docker. - \item \textbf{WholeTale:} (\url{https://wholetale.org}) Jupyter + Conda + Docker. - \item \textbf{Image Processing On Line (IPOL) journal:} The best example of publishing algorithms/methods I have seen, only useful for very basic/low-level software. - \end{itemize} - \alert{Summary}: except for IPOL, most solutions surveyed have far too many dependencies to be usable \alert{beyond the immediate future}. +%\begin{frame}{Existing technologies (Package managers)} +% +% \begin{itemize} +% \item \textbf{Operating system package managers:} +% \begin{itemize} +% \setlength\itemsep{2mm} +% \item For example \texttt{apt} or \texttt{yum} for Debian-based and RedHat-based GNU/Linux operating systems\\(the most common way to install software). +% \item Tightly intertwined with the operating system's components\\(arbitrary control of software versions is not easily possible). +% \item Older software (for example +5 years) is usually removed. +% \end{itemize} +% \item \textbf{Conda/Anaconda:} +% \begin{itemize} +% \setlength\itemsep{2mm} +% \item Conda has build instructions for software and their dependencies. +% \item But it doesn't go down to the C library or the lower-level components of operating system. +% \item It is written in Python (can't be used later when current Python is depreciated). +% \item Authors of Uhse+2019\footnote{\url{http://dx.doi.org/10.1002/cppb.20097}} report\footnote{\url{https://github.com/conda-forge/conda-forge.github.io/issues/787}} that their Conda environment breaks roughly every 3 months\\(Conda environments need to be updated to be used later! Breaking reproducibility). +% \end{itemize} +% \item \textbf{Nix, or GNU Guix:} +% \begin{itemize} +% \setlength\itemsep{2mm} +% \item Deliver perfectly reproducible builds (bit-wise reproducibility of software), needs root access. +% \item Doesn't \emph{require} documentation of dependencies. +% \end{itemize} +% \item \textbf{Spack:} Similar to Nix/Guix but written in Python. +% \end{itemize} +%\end{frame} +% +%\begin{frame}{Existing technologies (workflow tools)} +% \begin{itemize} +% \setlength\itemsep{4mm} +% \item \textbf{Binder:} (\url{https://mybinder.org}) Docker+Conda. +% \item \textbf{Galaxy:} (\url{https://galaxyproject.org}) A web-based user interface, primarily designed for genomics. The GUI make it hard to automate, and has too many dependencies. Very similar to GenePattern (2008 to 2017): with +40,000 users and $\sim4000$ jobs running per week, but cut due to funding. +% \item \textbf{Sciunit:} (\url{https://sciunit.run}) Parses program binaries to try to infer their dependencies and copy them. +% \item \textbf{Popper:} (\url{https://falsifiable.us}), HCL (previously used by GitHub Actions) + Conda + Docker. +% \item \textbf{WholeTale:} (\url{https://wholetale.org}) Jupyter + Conda + Docker. +% \item \textbf{Image Processing On Line (IPOL) journal:} The best example of publishing algorithms/methods I have seen, only useful for very basic/low-level software. +% \end{itemize} +% \alert{Summary}: except for IPOL, most solutions surveyed have far too many dependencies to be usable \alert{beyond the immediate future}. \end{frame} - - \begin{frame}{Summary:} - - Maneage is introduced as a customizable template that will do the - following steps/instructions (all in simple plain text files). - \begin{itemize} - \item \alert{Automatically downloads} the necessary - \emph{software} and \emph{data}. - \item \alert{Builds} the software in a \alert{closed - environment}. - \item Runs the software on data to \alert{generate} the final - \alert{research results}. - \item A modification in one part of the analysis will only - result in re-doing that part, not the whole project. - \item Using LaTeX macros, paper's figures, tables and numbers - will be \alert{Automatically updated} after a change in - analysis. Allowing the scientist to focus on the scientific - interpretation. - \item The whole project is under \alert{version control} (Git) - to allow easy reversion to a previous state. This - \alert{encourages tests/experimentation} in the analysis. - \item The \alert{Git commit hash} of the project source, is - \alert{printed} in the published paper and \alert{saved on - output} data products. Ensuring the - integrity/reproducibility of the result. - \item \colorbox{green!30!white}{These slides are available at - \textcolor{blue}{\url{https://maneage.org/pdf/slides-intro.pdf}}.} - \end{itemize} - - \begin{tcolorbox}[width=\linewidth, boxsep=1pt, left=1pt, right=1pt, - top=1pt, bottom=1pt] - For a technical description of Maneage's implementation, as well - as a checklist to customize it, and tips on good practices, - please see this page: - - \textcolor{blue}{\footnotesize\url{https://gitlab.com/maneage/project/-/blob/maneage/README-hacking.md}} - \end{tcolorbox} - \end{frame} -\end{document} - - - - - % \begin{frame}{Funding to help adoption of template} % \begin{itemize} % \setlength\itemsep{5mm} |