main.tex

\documentclass[a4paper,12pt]{article}
\PassOptionsToPackage{hyphens}{url}
\usepackage{makecell}
\usepackage{lastpage}
\usepackage{csquotes}

\usepackage{sidecap}    
\sidecaptionvpos{figure}{c}    

\input{biblatexTweaks}
\addbibresource{refs.bib}

\usepackage[top=4.5cm, bottom=2.9cm, left=2.1cm, right=2.1cm]{geometry}
\usepackage{xltabular}
\usepackage{enumitem}
\setlist{nosep}
\usepackage{hyperref}
\hypersetup{colorlinks=true,allcolors=blue}
\usepackage{pgfgantt}
\usepackage{hypcap}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{xcolor}
\usepackage{colortbl}
\usepackage[english]{babel}
\usepackage{lastpage}
\usepackage{slashed}
\usepackage{fontspec}
\usepackage{unicode-math}
%\usepackage{dblfnote} % multicolumn footnotes
\defaultfontfeatures{ Scale=MatchLowercase, Ligatures = TeX }
\setmainfont{Arial}
\setsansfont{Arial}
\setmonofont{Courier New Bold}[Scale=0.9]

\pagestyle{fancy}
\usepackage{ifthen}
\usepackage{titlesec}
\usepackage{wrapfig}
\usepackage{multirow}
\usepackage{caption}
\usepackage{textcomp}
\captionsetup{font=small}

\usepackage{xfp}
\usepackage{calc}

\newlength\myheight
\newlength\mydepth
\settototalheight\myheight{Xygp}
\settodepth\mydepth{Xygp}
\setlength\fboxsep{0pt}
\newcommand*\inlinegraphics[1]{%
  \settototalheight\myheight{Xygp}%
  \settodepth\mydepth{Xygp}%
  \raisebox{-\mydepth}{\includegraphics[height=\myheight]{#1}}%
}

\let\oldbibliography\thebibliography
\renewcommand{\thebibliography}[1]{%
  \oldbibliography{#1}%
  \setlength{\itemsep}{0pt}%
}

\setcounter{secnumdepth}{4}
\newcommand{\MSb}{\overline{\mathrm{MS}}}
\newcommand{\Dsla}{\slashed{D}}
\newcommand{\Dlr}{\buildrel \leftrightarrow \over D\raise-1pt\hbox{}}
\DeclareFieldInputHandler{title}{\def\NewValue{}}
\setlength\bibitemsep{1.5\itemsep}

\newif\ifshowinstructions
\newcommand{\instructions}[1]{\ifshowinstructions {\fontsize{10}{11}\selectfont #1} \fi}

\newcommand{\RF}[1]{\textbf{\color{magenta}RF: #1}}
\newcommand{\SB}[1]{\textbf{\color{red}SB: #1}}

\usepackage[user]{zref}

\newcounter{pageaux}
\def\currentauxref{PAGEAUX1}
\makeatletter
\newcommand{\resetpageaux}{%
  \clearpage
 \edef\@currentlabel{\thepageaux}\label{\currentauxref}%
  \xdef\currentauxref{PAGEAUX\thepage}%
  \setcounter{pageaux}{0}}
\AtEndDvi{\edef\@currentlabel{\thepageaux}\label{\currentauxref}}
\makeatother


%\showinstructionsfalse %% Suppresses template instructions
\showinstructionstrue %% Shows template instructions

\titleformat{\section}
  {\normalfont\fontsize{14}{16.8}\bfseries\selectfont}{\thesection}{1em}{}[{\color{oliv}\titlerule[1pt]}]

\titleformat{\subsection}
  {\normalfont\fontsize{14}{16.8}\selectfont}{\thesubsection}{1em}{}[{\color{oliv}\titlerule[1pt]}]
  
\titleformat{\subsubsection}
  {\normalfont\it\fontsize{14}{16.8}\selectfont}{\thesubsubsection}{0.8em}{}[{\color{orng}\titlerule}]

\titleformat{\paragraph}%[runin]
  {\normalfont\it\fontsize{14}{16.8}\selectfont}{\theparagraph}{0.5em}{}%[: \qquad]

  
\titlespacing*{\section}{0pt}{0pt}{0pt}
\titlespacing*{\subsection}{0pt}{0pt}{6pt}
\titlespacing*{\subsubsection}{0pt}{0pt}{0pt}
\titlespacing*{\paragraph}{0pt}{0pt}{0pt}
  
\definecolor{blue}{HTML}{19317B}
\definecolor{orng}{HTML}{FFC000}
\definecolor{oliv}{HTML}{FFC000}
\definecolor{lblu}{HTML}{4F81BD}
\definecolor{llbl}{HTML}{DBE5F1}

\definecolor{darkred}{HTML}{9f1313} 
\definecolor{alizarin}{rgb}{0.82, 0.1, 0.26} % red
\definecolor{bluegray}{rgb}{0.4, 0.6, 0.8} % blue
\definecolor{bittersweet}{rgb}{1.0, 0.44, 0.37}
\definecolor{forestgreen(web)}{rgb}{0.13, 0.55, 0.13}


\setlength{\belowcaptionskip}{6pt}
\setlength{\voffset}{-1in}
\setlength{\topmargin}{0pt}
\setlength{\headheight}{1.2in}
\setlength{\headsep}{0.5in}
\setlength{\footskip}{0.3in}

\newlength\mylen
\addtolength\mylen{\marginparsep}
\addtolength\mylen{\marginparwidth}
\addtolength\mylen{\hoffset}
\addtolength\mylen{1in}
\fancyheadoffset{\the\mylen}

\fancyhead[L]{}
\fancyhead[R]{}

\fancyhead[C]{
  \includegraphics[width=1\paperwidth]{head.png}
}
\fancyfoot[L]{\footnotesize\color{blue}
  \stepcounter{pageaux} Page \thepageaux\ of \ref{\currentauxref}
}
\fancyfoot[C]{\footnotesize\color{blue}\textbf{EuroHPC JU} | Application Form for Regular Access}
\fancyfoot[R]{\footnotesize\color{blue} V4: 04/04/2023}


\renewcommand{\headrulewidth}{0pt}
\renewcommand{\footrule}{\hbox to\headwidth{\color{orng}\leaders\hrule height \footrulewidth\hfill\par}}
\renewcommand{\footrulewidth}{1pt}

\DeclareBibliographyCategory{fullcited}
\newcommand{\mybibexclude}[1]{\addtocategory{fullcited}{#1}}


\usepackage{xparse} 
\NewDocumentCommand\Nf{mgg}{N\textsubscript{f}=#1\IfNoValueTF{#2}{}{+#2}\IfNoValueTF{#3}{}{+#3}}
\NewDocumentCommand\vol{mg}{#1\textsuperscript{3}\IfNoValueTF{#2}{}{×#2}}
\setlength{\parindent}{0cm}

\newcommand{\NP}{{\rm NP}}

%%% Variables related to resource estimate
\newcommand{\hrsBS}{0.8}
\newcommand{\hrsB}{0.6}
\newcommand{\hrsBL}{0.8}
\newcommand{\hrsC}{0.6}
\newcommand{\hrsCL}{0.7}
\newcommand{\hrsD}{0.8}
\newcommand{\hrsDL}{0.6}
\newcommand{\hrsE}{0.7}
\newcommand{\rABS}{0}
\newcommand{\rAB}{120*8*10}
\newcommand{\rABL}{200*32*12}
\newcommand{\rAC}{400*20*13}
\newcommand{\rACL}{410*56*5}
\newcommand{\rAD}{300*32*10}
\newcommand{\rADL}{500*128*3}
\newcommand{\rAE}{700*56*6}
\newcommand{\rBBS}{800*2*20}
\newcommand{\rBB}{800*8*20}
\newcommand{\rBC}{800*20*20}
\newcommand{\rBD}{800*32*20}


\linespread{1}
\setlength{\parskip}{6pt}

\makeatletter
\newcommand{\globalcolor}[1]{%
  \color{#1}\global\let\default@color\current@color
}
\makeatother

\AtBeginDocument{\globalcolor{blue}}

% \defbibentryset{Lubicz:2017syv-DiCarlo:2019thl-Desiderio:2020oej-Martinelli:2021onb-DiCarlo:2021dzg}{Lubicz:2017syv,DiCarlo:2019thl,Desiderio:2020oej,Martinelli:2021onb,DiCarlo:2021dzg}
% \defbibentryset{Giusti:2019xct-Giusti:2019hkz}{Giusti:2019xct,Giusti:2019hkz}
% \defbibentryset{ExtendedTwistedMass:2021rdx-Alexandrou:2021ivx}{ExtendedTwistedMass:2021rdx,Alexandrou:2021ivx}
% \nocite{}

\begin{document}



{\fontsize{20}{24} \selectfont\textbf{Project scope and plan}}
{\color{orng}\hrule height 1pt}

\vspace*{0.15in}

\begin{xltabular}{\linewidth}{|>{\columncolor{llbl}}l|>{\columncolor{llbl}}X|}
  \hline
  \textbf{Project name} & Smeared $R$-ratio and HVP contributions to $g_\mu\!\!-2$ with leading isospin-breaking effects \\
  \hline
  Research field  & Particle and Nuclear Physics\\
  \hline
\end{xltabular}

\vspace{4pt}

\textbf{Principal Investigator (PI)}
\begin{xltabular}{\linewidth}{|>{\columncolor{llbl}}l|>{\columncolor{llbl}}X|}
  \hline
  Title & Prof. \\
  \hline
  First name  & Marie  \\
  \hline
  Last name  & Sk{\l}odowksa-Curie \\
  \hline
  Organization name  &  University of Paris \\
  \hline
  Department  & Chemistry \\
  \hline
  Group  &  Institute of Radium \\
  \hline
  Country  & France \\
  \hline
\end{xltabular}

\textbf{Co-PI(s)}
\begin{xltabular}{\linewidth}{|>{\columncolor{llbl}}l|>{\columncolor{llbl}}X|}
  \hline
  Title & Prof. \\
  \hline
  First name  & Pierre  \\
  \hline
  Last name  & Curie \\
  \hline
  Organization name  & University of Paris \\
  \hline
  Department  &  Chemistry \\
  \hline
  Group  &  -- \\
  \hline
  Country  & France \\
  \hline
\end{xltabular}

\vspace{4cm}

%\newpage
\setcounter{page}{1}

\clearpage

\instructions{\it

  \textbf{IMPORTANT NOTICE}

  All of the sections and subsections below \textbf{MUST BE COMPLETED} (unless stated otherwise).
  In case you wish to leave a section empty, please provide a reason.
  The Domain Panel Chairs, appointed by the Access Resource Committee (ARC) will not be able to process proposals that neither provide the requested information nor a justification for the lack of such information for each section.

  Applicants are strongly encouraged to \textbf{base their proposal on reliable benchmark data obtained on the target machine(s)} from previous calls or access programmes.
  Such data and support to properly collect these can be obtained from the EuroHPC Benchmark Access call. In order to have the necessary data on time, please submit your Benchmark proposals \textbf{at least 1 month before the submission deadline}. 
  For additional questions, please contact the peer review office at \url{access@eurohpc-ju.europa.eu}.

  \textbf{The structure and formatting settings of this template must be preserved and respected} (change in font size or margin and spacing settings are not allowed).
  The maximum number of pages allowed is \textbf{10 pages}, including graphs, tables and references, but not counting the cover page and the appendix.
  Reviewers will be instructed not to consider any pages out of the limit.
  \textbf{Instruction paragraphs can be removed from the proposal text.}

  \textbf{Upload a single document}, based on the present template, in PDF format \textbf{without exceeding} 8 MB.

  \textbf{Proposals that do not follow the template or that are incomplete will be administratively rejected and will not be further evaluated.}

}

\clearpage

\resetpageaux

\section{Key scientific/societal/technological contribution of the proposal \instructions{(200 words max.)}}

\instructions{\it

  Outline the scientific/societal/technological importance of your project, how High Performance Computing (HPC) will help you achieve your goals and what the major expected outcomes are.
  This section would typically be the same as the abstract of the proposal in the submission form.

}

\section{Detailed proposal information \instructions{(Maximum 8 pages, graphs and tables included)}}

\instructions{\it

  The information should be suitable for expert peer review in your discipline.
  It must also have appropriate information for a broader audience as your proposal will be evaluated by a panel and in parallel with proposals in other disciplines.

}

\subsection{Justification for the importance of the scientific problem and the requested resources \instructions{(1 page)}}
\label{sec:justification}

\instructions{\it

  Describe the proposed research and the main scientific/technical advances you will achieve with the requested EuroHPC allocation.
  For industrial applications, proposals should demonstrate the innovation and industrial impact on the specific market and the broader socio-economic impact.
  For public sector applications, the proposal should demonstrate the innovative aspects of the applications, the expected societal impact, and how the application will contribute to the delivery of quality and efficient public sector services.
  The justification of the requested resources must be clearly linked to the software performance evaluation (Section 2.6).

}

\subsection{Overview of the project \instructions{(about 2 pages)}}
\label{sec:overview}
\instructions{\it

  Describe the motivation, objectives and scientific challenges of the problem.
  Describe and justify the choice of computational methods.
  State the advances that will be enabled through the requested EuroHPC Regular Access award (e.g. impact on community paradigms, valuable insights or solving a long-standing challenge, new technology/therapy, etc.).
  Provide a list of expected outcomes of your proposal and, if relevant, the interdisciplinary value of your proposal.

}

\subsection{Validation, verification, state of the art \instructions{(1 page)}}
\label{sec:methods}

\instructions{\it

  Please describe the validity of the simulations and predictions made with this proposal.
  In case you provide references to relevant publications please include here also the key relevant results.
  Please address issues of reproducibility and highlight the predictive capabilities of your simulations.

}


\subsubsection{Validation \& Verification }

\instructions{\it

  Please summarize the validation of your model against experiments or other established reference data.
  Please also provide how the numerical consistency and stability of your computational method has been verified or provide evidence of existing verifications.
  
}

\subsubsection{Comparison with state of the art}
\label{sec:stateoftheart}
\instructions{\it

  Place the project in the context of competing work.
  Explain the relative advantages AND drawbacks of your approach.

}

\subsection{Software and Attributes \instructions{(1 pages)}}

\instructions{\it

  (Please see also Examples of Performance Reporting in Section 2.6.2.1).
  Describe the software that will be used including a discussion of the state of the art in the field.
  The description should mention:

}

%<Enter your text here>

\subsubsection{Software}

\instructions{\it

  Please describe all codes you are using in the proposal.
  Justify your choices and describe alternatives (if any).

}

\subsubsection{Particular libraries}

\instructions{\it

  Describe particular libraries required by the production and analysis software, algorithms and numerical techniques employed (e.g., finite element, iterative solver), programming languages.
  Please specify requirements for compilation or build environment (build system (e.g., cmake, python version), version
  control system (e.g., git, subversion) etc.).
  
}

\subsubsection{Parallel programming}

\instructions{\it

  Model(s) used (e.g., MPI, OpenMP/Pthreads, CUDA, OpenACC, etc.).

}

\subsubsection{I/O requirements}

\instructions{\it

  I/O requirements (e.g., amount, size, bandwidth, etc.) for execution, input files, restart and other output.
  Describe I/O strategy (number of files, frequency, read/write size) and I/O behaviour of your code during the period of calculations. 
  Please specify the restart overhead, not only for I/O; (e.g., a code may have to perform a costly domain decomposition first).

}

\subsection{Data: Management Plan, Storage, Analysis and Visualization \instructions{(about 1 page)}}
\vspace{-0.2cm}
\subsubsection{Data Management Plan}

\instructions{\it

  Data Management Plan covering both short-term and long-term aspects, including needs for I/O bandwidth, number of files and input/output data volumes. 
  Specify for which system the data will be provided, how long the data must be stored at the computing centre after the termination of the project, how it will be moved from the centre, and how subsequent analysis will be performed.
  Specify the availability of both code and data to other researchers, and how this will be handled.
  EuroHPC should be given credit for all data produced through EuroHPC allocations when publishing, and described in the provenance when depositing to other infrastructures.
  
}

\subsubsection{Project workflow}

\instructions{\it

  Project workflow including the role and timeline of data analysis and visualisation identify where the analysis will be done and any potential bottlenecks in the analysis process.
  Describe any analysis and/or data reduction tools used. 

}

\subsubsection{Software workflow solution}

\instructions{\it

Software workflow solution (e.g., pre- and post-processing scripts that automate run management and analysis) to facilitate this volume of work.

}

\subsubsection{I/O requirements}

\instructions{\it

  I/O requirements (e.g., amount, size, bandwidth, etc.) for data analysis and visualisation.
  Highlight any exceptional I/O needs. Please provide data for (one or several) precise systems that will be simulated.

}

% <Enter your text here>

\subsection{Performance of Software \instructions{(Maximum 2 pages)}}
\label{sec:performance}

\subsubsection{Testing of your code on the requested machine}
\label{sec:testing}

\instructions{\it
  
  It is strongly recommended that your production code is tested in the requested machine(s) (see also the text referring to Benchmark Access in the Important Notice at the top of page 1).
  Please specify the EuroHPC Benchmark Access project (if any) or other projects (previous PRACE Calls, national calls, etc.) used to prepare the Regular Access proposal.
  If the preparatory host machine is different from the target machine, specify why you think the data is relevant.
  In the latter case, please report briefly the conversion factor (in terms of ratio of time to solution, flops or requested node hours) from the machine where the preparatory tests were performed to the requested system.
  Moreover, your proposal must account for all technical constraints and requirements of the targeted machine(s) as documented in the separate Technical Guidelines for Applicants document; failing to do so will significantly increase the risk that your project will be technically rejected.

}

\subsubsection{Quantify the HPC performance of your project}

\instructions{\it

  The presented data must be representative of the entire workflow of the project proposed and refer to the main application code you intend for the production work.
  The software scalability data (see Examples of \textbf{Performance Reporting} below) must be used to choose the most efficient job size(s) for the simulations planned in production: the corresponding software performance must be clearly linked to the justification of the computing resources requested.
  The Domain Panels will not accept estimates based on related codes and/or data related to parts of your production.
  All data must refer to the targeted systems in your production runs or a system with comparable size, software stack and with the same architecture, and network (e.g. a project can be accepted on MeluXina GPU if it was benchmarked on another GPU machine with the same NVIDIA A100 GPU).
  Please coordinate with the centres if in doubt about the portability of your code.
  Specify that performance results are reported on the basis of one of the following: whole application including I/O; whole application except I/O; kernel only; other (specify).
  More specifically you must include:

}

\paragraph{Strong and weak scalability}
\label{sec:scaling}
\instructions{\it

  Starting with the minimum size of the computer necessary to run the problem (usually 1 core or 1 node).
  Justify the minimum size for your scaling if it is larger than 1 core or 1 node (e.g. memory limitations).
  Please provide a justification in case that either the weak (e.g. study of one particular bio-molecule) or the strong (e.g. study of an ensemble) scalability metric is not considered relevant to your project.
  See \textbf{Examples of Performance Reporting} below for the requested format.

}

% <Enter your text here>

\instructions{\it

  \textbf{Examples of Performance Reporting.}
  For the weak and strong scaling please start with the minimum and finish with the maximum number of nodes that are suitable for your application.
  Please mark the number of nodes that you expect to perform the main load of your work.
  On the Y axis you may use time to solution (scaled or otherwise) or speedup with respect to the minimum number of cores.
  \textbf{\textcolor{orange}{The table with the timings is mandatory}}.

  The table should include the speedup and the parallel efficiency.
  Log/log plots are useful to span many orders of magnitude.

}

\paragraph{Precision reported}
\instructions{\it

  One of: single precision, double precision, mixed precision.
  Only the precision you use in the simulation is relevant.

}

\paragraph{Time-to-solution}

\instructions{\it

  The normalized time-to-solution averaged per iteration

  \[
  T^*_i = \frac{t_i\cdot N_c}{N_e}
  \]

  AND the normalized total time to solution

  \[
  T_f^* = \frac{t_f\cdot N_c}{N_e}
  \]

  with $t_i$ the time per iteration, $t_f$ the total time to solution, $N_c$ the number of cores and $N_e$ the number of computational
  elements (size of the problem).

  IMPORTANT: Justify the choice of your code (e.g., comparison with existing codes, methods or any other scientifically rigorous argumentation). 
  See also the text referring to Preparatory Access in the Important Notice at the top of Page 1.

}

\paragraph{System scale}

\instructions{ \it

  One of: results measured on full-scale system, projected from results of smaller system, other (specify).

}

\paragraph{Measurement mechanism}

\instructions{ \it

  One of: timers, FLOP count, static analysis tool, performance modelling, other (specify).

}

\paragraph{Memory usage}

\instructions{ \it

  Specify requirements per node or core depending on the size of the problem.

}

\paragraph{OPTIONAL: Percentage of available peak performance}

\instructions{ \it

  Please collaborate with the Centre on obtaining this information (see also the text referring to Preparatory Access in the Important Notice at the top of Page 1).
  Alternatively provide code specific metrics for the requested machine (FLOPS, etc.).

}

\section{Milestones (quarterly basis) \instructions{(Maximum 1 page)}}
\label{sec:milestones}
\instructions{\it

  Goals and milestones should articulate simulation and developmental objectives and be sufficiently detailed to assess the progress of the project for each year of any allocation granted.
  It is especially important that you provide clear connections between the project's overarching milestones, the planned production simulations, and the compute time expected to be required for these simulations.
  Please clarify any dependencies of milestones on other milestones.
  Please ensure that the node hour consumption is regular throughout the allocation or provide a requested schedule after consultation with the centres.

}

\begin{table}[h!]
    \centering
    \small
    \caption{Breakdown of the types of runs proposed and the resources requested. The number of nodes and the time per step are taken from Table~\ref{tab:timings}. We report about two types of runs, ISO and LIBE, for which we refer to Table~\ref{table:ensembles} for an overview. Comparing the two tables, the number of runs is equivalent to the number of configurations to be analyzed, and the number of steps is equivalent to the number of sources to be computed divided by one hundred since the time per step is defined as the time needed for computing one hundred sources. In the case of the ISO run type, the sources are used for computing connected light, strange and charm contributions. In the case of LIBE runs the sources are used for computing three slopes, two in the (twisted Wilson) quark mass parameters $\kappa$ and $\mu$, and one in $\alpha_{em}$, for connected and disconnected contributions and for the three quark flavors. This motivates the larger number of sources required. } 
    \begin{tabular}{|c|c|c|c|c|c|c|}
      \hline\hline
      \textbf{Run type}                & \textbf{Code}        & \textbf{\# of runs}                 & \textbf{\# of nodes} & \textbf{\# of steps} & \textbf{Time per step [h]} & \textbf{Total node hours}                                        \\\hline
      \texttt{cB64}, run ISO & PLEGMA & 120 & 8 & 10 & \hrsB{} & \fpeval{\hrsB{}*\rAB{}} \\\hline
      \texttt{cB96}, run ISO & PLEGMA & 200 & 32 & 12 & \hrsBL{} & \fpeval{\hrsBL{}*\rABL{}} \\\hline
      \texttt{cC80}, run ISO & PLEGMA & 400 & 20 & 13 & \hrsC{} & \fpeval{\hrsC{}*\rAC{}} \\\hline
      \texttt{cC112}, run ISO & PLEGMA & 410 & 56 & 5 & \hrsCL{} & \fpeval{\hrsCL{}*\rACL{}} \\\hline
      \texttt{cD96}, run ISO & PLEGMA & 300 & 32 & 10 & \hrsD{} & \fpeval{\hrsD{}*\rAD{}} \\\hline
      \texttt{cD128}, run ISO & PLEGMA & 500 & 128 & 3 & \hrsDL{} & \fpeval{\hrsDL{}*\rADL{}} \\\hline
      \texttt{cE112}, run ISO & PLEGMA & 700 & 56 & 6 & \hrsE{} & \fpeval{\hrsE{}*\rAE{}} \\\hline
      \multicolumn{5}{r|}{}            & Total run ISO & \fpeval{\hrsB{}*\rAB{}+\hrsBL{}*\rABL{}+\hrsC{}*\rAC{}+\hrsCL{}*\rACL{}+\hrsD{}*\rAD{}+\hrsDL{}*\rADL{}+\hrsE{}*\rAE{}}                                                                                                                    \\\cline{6-7}
      \multicolumn{7}{c}{}                                                                                                                                                                                                                        \\\hline
      \texttt{cB48}, run LIBE & PLEGMA, NISSA & 800 & 2 & 20 & \hrsBS{} & \fpeval{\hrsBS{}*\rBBS{}} \\\hline
      \texttt{cB64}, run LIBE & PLEGMA, NISSA & 800 & 8 & 20 & \hrsB{} & \fpeval{\hrsB{}*\rBB{}} \\\hline
      \texttt{cC80}, run LIBE & PLEGMA, NISSA & 800 & 20 & 20 & \hrsC{} & \fpeval{\hrsC{}*\rBC{}} \\\hline
      \texttt{cD96}, run LIBE & PLEGMA, NISSA & 800 & 32 & 20 & \hrsD{} & \fpeval{\hrsD{}*\rBD{}} \\\hline
      \multicolumn{5}{r|}{}            & Total run LIBE & \fpeval{\hrsBS{}*\rBBS{}+\hrsB{}*\rBB{}+\hrsC{}*\rBC{}+\hrsD{}*\rBD{}}                                                                                                                                \\\cline{6-7}
      \multicolumn{7}{c}{}                                                                                                                                                                                                                        \\\cline{6-7}
      \multicolumn{5}{r|}{}            & Total                & \fpeval{\hrsB{}*\rAB{}+\hrsBL{}*\rABL{}+\hrsC{}*\rAC{}+\hrsCL{}*\rACL{}+\hrsD{}*\rAD{}+\hrsDL{}*\rADL{}+\hrsE{}*\rAE{}+\hrsBS{}*\rBBS{}+\hrsB{}*\rBB{}+\hrsC{}*\rBC{}+\hrsD{}*\rBD{}}                                                                                                                                                                       \\\cline{6-7}
    \end{tabular}
    \label{table:costs}
\end{table}

\subsection{Gantt Chart}
\instructions{\it

  Provide a Gantt Chart of the simulation plan in production indicating job sizes and scheduling of computing tasks including a communication plan for the results and the strategy and timeline for the dissemination of the results.

} 

\begin{figure}[htb]
  \small
  \begin{ganttchart}[
      x unit=0.335cm,        
      y unit title=0.5cm,
      y unit chart=0.5cm,
      vgrid,hgrid,
      %        title label anchor/.style={below=-1.6ex},
      bar label font=\small,
      title left shift=.05,
      title right shift=-.05,
      title height=1,
      incomplete/.style={fill=white},
      progress label text={},
      bar height=0.8,
      bar top shift=+0.1,
      group right shift=0,
      group top shift=.0,
      group height=.0
    ]{1}{48}
    %labels
    \sffamily
    \gantttitle{\textbf{Allocation duration}}{48} \\
    \gantttitle{Oct.}{4} 
    \gantttitle{Nov.}{4} 
    \gantttitle{Dec.}{4} 
    \gantttitle{Jan.}{4} 
    \gantttitle{Feb.}{4} 
    \gantttitle{Mar.}{4}
    \gantttitle{Apr.}{4} 
    \gantttitle{May}{4} 
    \gantttitle{Jun.}{4} 
    \gantttitle{Jul.}{4} 
    \gantttitle{Aug.}{4} 
    \gantttitle{Sep.}{4}
    \\

    %Blocks
    \gantttitle{ISO, seven ensembles, 45\% of resources, Coord. C. Alexandrou and C. Urbach }{48}\\
    \ganttbar[inline,bar/.style={fill=bittersweet}]{ \textcolor{white}{\textbf{S/U}}}{1}{3}
    \ganttbar[inline,bar/.style={fill=bluegray}]{ \textcolor{white}{\textbf{Ensembles:} \texttt{cB64},\texttt{cB96},\texttt{cC80},\texttt{cC112},\texttt{cD96}}}{5}{28}
    \ganttbar[inline,bar/.style={fill=bluegray}]{ \textcolor{white}{\textbf{Ensemble:} \texttt{cD128}}}{30}{47}\\
    \ganttbar[inline,bar/.style={fill=bluegray}]{ \textcolor{white}{\textbf{Ensemble:} \texttt{cE112}}}{11}{38}\\
    \ganttbar[inline,bar/.style={fill=forestgreen(web)}]{\textcolor{white}{Analysis, presentations}}{29}{40}
    \ganttbar[inline,bar/.style={fill=forestgreen(web)}]{\textcolor{white}{Publications}}{42}{48}\\
    \gantttitle{LIBE, four ensembles, 55\% of resources, , Coord. V. Lubicz and U. Wenger}{48}\\
    \ganttbar[inline,bar/.style={fill=bittersweet}]{ \textcolor{white}{\textbf{S/U}}}{1}{6}
    \ganttbar[inline,bar/.style={fill=bluegray}]{ \textcolor{white}{\textbf{Ensembles:} \texttt{cB48}, \texttt{cB64}}}{8}{28}    \ganttbar[inline,bar/.style={fill=bluegray}]{ \textcolor{white}{\textbf{Ensemble:} \texttt{cD96}}}{30}{47}\\
    \ganttbar[inline,bar/.style={fill=bluegray}]{ \textcolor{white}{\textbf{Ensemble:} \texttt{cC80}}}{15}{40}\\
    \ganttbar[inline,bar/.style={fill=forestgreen(web)}]{\textcolor{white}{Analysis, presentations}}{29}{40}
    \ganttbar[inline,bar/.style={fill=forestgreen(web)}]{\textcolor{white}{Publications}}{42}{48}
    
    %Relations  
    \ganttlink{elem0}{elem1}
    \ganttlink{elem1}{elem2}
    \ganttlink{elem1}{elem4}
    \ganttlink{elem3}{elem4}
    \ganttlink{elem2}{elem5}
    \ganttlink{elem4}{elem5}
    \ganttlink{elem6}{elem7}
    \ganttlink{elem7}{elem8}
    \ganttlink{elem7}{elem10}
    \ganttlink{elem9}{elem10}
    \ganttlink{elem8}{elem11}
    \ganttlink{elem10}{elem11}


    %Milestones
    \ganttvrule[vrule/.style={dashed,line width=0.00001pt}]{MS2}{6}      
    \ganttvrule[vrule/.style={dashed,line width=0.00001pt}]{MS2}{14}
    \ganttvrule[vrule/.style={dashed,line width=0.00001pt}]{MS3}{28}
    \ganttvrule[vrule/.style={dashed,line width=0.00001pt}]{MS4}{40}
    \ganttvrule[vrule/.style={dashed,line width=0.00001pt}]{MS5}{48}

  \end{ganttchart}
  \caption{Gantt chart describing the scheduling of the steps involved
    in our calculation. Results will be presented at the international Lattice conference and at least one publication is targeted by the end of the project. The production for the ISO run type will be performed by the Cyprus and Bonn groups. The production for the LIBE run type will be performed by the Rome and Bern groups.}
  \label{fig:gantt}
  \vspace*{-0.6cm}
\end{figure}

\section{Personnel and Management Plan \instructions{(0.5 page)}}


\instructions{\it

  What personnel are already in place and what are their roles on the project? 
  If applicable, describe (i) personnel that will be hired for the project in the future and their responsibilities and (ii) potential personnel turnover that may occur during the project and a strategy for replacing them.
  The EuroHPC Regular Access calls welcome proposals from individual PIs or teams of collaborators.
  Outline the focus of each individual or subgroup and their interrelationships.

  {\color{orange}\textbf{It is mandatory to include all team members on the online form.}}

}

{\it Graduate students:} 

{\it Postdoctoral fellows:} 

{\it Senior researchers:} 

\section{References \instructions{(Maximum 30)}}

\begingroup
\small
\printbibliography[heading=none]
\endgroup

\section{Confidentiality (0.5 page)}
\begin{itemize}
\item Is any part of the project covered by confidentiality? \textbf{yes/no}
\end{itemize}
If \textbf{YES}, specify which aspect is confidential and justify (Maximum 500 words):

\begin{itemize}
\item Does your project involve handling of personal data? \textbf{yes/no}
\end{itemize}
If \textbf{YES}, please confirm to take care of the data controller’s responsibilities as described in applicable data protection legislation – and note that you will need to make a data processing agreement with the production site.

\end{document}