This commit is contained in:
Julian M. Kunkel 2021-06-02 14:12:37 +02:00
parent db3e4a8eb0
commit 43b3cdbd6e
59 changed files with 1742 additions and 9 deletions

41
lncs-from-jhps/.gitignore vendored Normal file
View File

@ -0,0 +1,41 @@
main.pdf
*.aux
*.lof
*.log
*.lot
*.fls
*.out
*.toc
*.fmt
*.fot
*.cb
*.cb2
.*.lb
## Intermediate documents:
*.dvi
*.xdv
*-converted-to.*
# these rules might exclude image files for figures etc.
# *.ps
# *.eps
# *.pdf
## Generated if empty string is given at "Please type another file name for output:"
.pdf
## Bibliography auxiliary files (bibtex/biblatex/biber):
*.bbl
*.bcf
*.blg
*-blx.aux
*-blx.bib
*.run.xml
## Build tool auxiliary files:
*.fdb_latexmk
*.synctex
*.synctex(busy)
*.synctex.gz
*.synctex.gz(busy)
*.pdfsync

74
lncs-from-jhps/README.md Normal file
View File

@ -0,0 +1,74 @@
# JHPS LaTeX template
This LaTeX template is part of the Journal of High-Performance [description for authors](https://jhps.vi4io.org/authors/).
## Submission to the Incubator: Workflow
The workflow utilizes combination of GoogleDoc, LaTeX and Git/GitHub to ensure reliable, easy content creation, public reviews, simple merging, and flexibility.
1. Please prepare your document according to the LaTeX template (see [main.tex](main.tex)).
2. Submit the information about the repository to the journal see [for authors](https://jhps.vi4io.org/authors/).
3. Once the paper is accepted to the incubator, an ID is given. The ID will be *jhps-incubator-<month of submission>-<title-excerpt>*.
The repository it will be cloned into GitHub of the VI4IO with ID as a name, e.g., like [this paper](https://github.com/VI4IO/jhps-incubator-06-temporal). At this stage, the following documents are created:
- A Google Doc containing the manuscript ([main.tex](main.tex)) allowing for commenting by reviewers. The Google Doc will include the JHPS plugin allowing synchronization with Git and republishing of the paper.
- The initial PDF version (<ID>.pdf) of the manuscript is created and publicly shared under the URL:
https://jhps.vi4io.org/pdf/<PDF>
- The repository and Google Doc is shared with the corresponding authors.
## Workflow for Review and Feedback Phase
1. A reviewer can view the PDF and ask for "comment" permissions in Google Doc, and then make comments or suggestions directly in the LaTeX Google Doc. Typically, the author (or editorial board) will grant **review permission** for any reviewer.
2. The author shall incorporate the feedback and whenever it suits release a new version of the PDF + trigger the commit to the repository. Note that for a release, all currently pending comments must be incorporated as Google API doesn't allow to identify which text is suggested and suggested text is always included. Comments can remain and are preserved for a submission.
3. During review and feedback phase, the authors can push any update to the Git repository but shall not make an update to [main.tex](main.tex) though via Git any more as someone may add suggestions to the current Google Doc.
### Creating a new version PDF
Synchronization between Google Doc and Git/LaTeX generated PDF is an activity that is done by an author.
The author can click on "Add-ons" => "JHPS LaTeX" to open a side panel (see the figure)
![assets/jhps.jpeg](assets/jhps.jpeg))
Accept the permissions for the plugin within Google Doc, the permissions will only be active for this particular document.
With this side panel, the author can trigger the PDF creation on the JHPS server and update the Google Doc directly from the Git repository.
Note that a "pull" will remove all comments, therefore, it shall only be applied *after all suggestions/comments by reviewer has been applied*.
The side panel cannot be used by anyone except someone that has "edit" permissions to the document.
Updates of figures and other assets in the repository do not interfere with the GoogleDoc replication of main.tex and can always be made.
Whenever one of the buttons is clicked, the remote repo is pulled and merged with the current Google Doc version.
## Structure of this repository
- [main.tex](main.tex): this file shall contain all text of the full paper.
- [bibliography.bib](bibliography.bib): this file contains the BibTex of the paper.
- [meta.yaml](meta.yaml): metadata for this publication.
- [assets](assets): include all figures and material referenced by LaTeX.
- [workflow](workflow): a directory containing the workflow for the reproducible workflow.
- [line-split.py](line-split.py): this script fixes the line-breaks for LaTeX to ease merging, it is automatically invoked at the server.
- main.pdf: after you run LaTeX, it shall contain the created PDF, do not check this file into the repository!
## Preparing a JHPS submission
This step by step guide helps to prepare your paper for a submission:
1. clone this repository.
2. To test the correct behavior build the LaTeX file, e.g., using __pdflatex main.tex__ or __latexmk -pdf main.tex__. Alternatively, using Docker and Popper:
```bash
cd path/to/repo
popper run build-paper
```
For more information on Popper visit the [official documentation](https://github.com/getpopper/popper).
3. Modify the author information in meta.yaml, check the correctness of the yaml file (e.g. using yamllint)
4. Provide your main.tex, bibliography.bib
5. Before the initial submission, please format the paper calling $ ./line-split.py main.tex. Using Popper:
```bash
cd path/to/repo
popper run split-lines
```
6. Notify the board about the paper, see [for authors](https://jhps.vi4io.org/authors/)

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

After

Width:  |  Height:  |  Size: 64 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 71 KiB

Binary file not shown.

Binary file not shown.

After

Width:  |  Height:  |  Size: 252 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 292 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 89 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 51 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 271 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 51 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 48 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 42 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 240 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 63 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 42 KiB

View File

@ -0,0 +1,217 @@
@article{khotanlou2018empirical,
title={{An Empirical Comparison of Distance Measures for Multivariate Time Series Clustering}},
author={Khotanlou, Hassan and Salarpour, Amir},
journal={International Journal of Engineering},
volume={31},
number={2},
pages={250--262},
year={2018},
publisher={Materials and Energy Research Center}
}
% pages={569--580},
@inproceedings{morse2007efficient,
title={{An efficient and accurate method for evaluating time series similarity}},
author={Morse, Michael D and Patel, Jignesh M},
booktitle={{Proceedings of the 2007 ACM SIGMOD international conference on Management of data}},
year={2007}
}
@article{navarro2001guided,
title={{A guided tour to approximate string matching}},
author={Navarro, Gonzalo},
journal={ACM computing surveys (CSUR)},
volume={33},
number={1},
pages={31--88},
year={2001},
publisher={ACM New York, NY, USA}
}
% pages={67},
@article{mendez2012new,
title={{A new approach for Analyzing I/O in parallel scientific applications}},
author={M{\'e}ndez, Sandra and Panadero, Javier and Wong, Alvaro and Rexachs, Dolores and Luque, Emilio},
journal={Computer Science \& Technology Series},
year={2012}
}
@article{halawa2020unsupervised,
title={{Unsupervised KPIs-Based Clustering of Jobs in HPC Data Centers}},
author={Halawa, Mohamed S and D{\'\i}az Redondo, Rebeca P and Fern{\'a}ndez Vilas, Ana},
journal={Sensors},
volume={20},
number={15},
pages={4111},
year={2020},
publisher={Multidisciplinary Digital Publishing Institute}
}
@inproceedings{emeras2015evalix,
title={{Evalix: classification and prediction of job resource consumption on HPC platforms}},
author={Emeras, Joseph and Varrette, S{\'e}bastien and Guzek, Mateusz and Bouvry, Pascal},
booktitle={Job Scheduling Strategies for Parallel Processing},
pages={102--122},
year={2015},
organization={Springer}
}
% doi = {https://doi.org/10.1007/978-3-030-02465-9_4},
@inproceedings{TFAPIKBBCF19,
author = {Julian Kunkel and Eugen Betke and Matt Bryson and Philip Carns and Rosemary Francis and Wolfgang Frings and Roland Laifer and Sandra Mendez},
title = {{Tools for Analyzing Parallel I/O}},
year = {2019},
month = {01},
booktitle = {{High Performance Computing: ISC High Performance 2018 International Workshops, Frankfurt/Main, Germany, June 28, 2018, Revised Selected Papers}},
publisher = {Springer},
series = {Lecture Notes in Computer Science},
number = {11203},
pages = {49--70},
conference = {HPC-IODC workshop, ISC HPC},
isbn = {978-3-030-02465-9},
issn = {1611-3349},
abstract = {Parallel application I/O performance often does not meet user expectations. Additionally, slight access pattern modifications may lead to significant changes in performance due to complex interactions between hardware and software. These issues call for sophisticated tools to capture, analyze, understand, and tune application I/O. In this paper, we highlight advances in monitoring tools to help address these issues. We also describe best practices, identify issues in measure- ment and analysis, and provide practical approaches to translate parallel I/O analysis into actionable outcomes for users, facility operators, and researchers.},
}
@inproceedings{bahmani2018chameleon,
title={{Chameleon: Online clustering of mpi program traces}},
author={Bahmani, Amir and Mueller, Frank},
booktitle={{2018 IEEE International Parallel and Distributed Processing Symposium (IPDPS)}},
pages={1102--1112},
year={2018},
organization={IEEE}
}
@article{rodrigo2018towards,
title={{Towards understanding HPC users and systems: a NERSC case study}},
author={Rodrigo, Gonzalo P and {\"O}stberg, P-O and Elmroth, Erik and Antypas, Katie and Gerber, Richard and Ramakrishnan, Lavanya},
journal={{Journal of Parallel and Distributed Computing}},
volume={111},
pages={206--221},
year={2018},
publisher={Elsevier}
}
%location = {Montreal, Canada},
%url = {https://cug.org/proceedings/cug2019_proceedings/includes/files/pap118s2-file1.pdf},
@inproceedings{AOPIUOTUNS19,
author = {Andrew Turner and Dominic Sloan-Murphy and Karthee Sivalingam and Harvey Richardson and Julian Kunkel},
title = {{Analysis of parallel I/O use on the UK national supercomputing service, ARCHER using Cray's LASSi and EPCC SAFE}},
year = {2019},
month = {10},
editor = {},
conference = {CUG},
abstract = {In this paper, we describe how we have used a combination of the LASSi tool (developed by Cray) and the SAFE software (developed by EPCC) to collect and analyse Lustre I/O performance data for all jobs running on the UK national supercomputing service, ARCHER; and to provide reports on I/O usage for users in our standard reporting framework. We also present results from analysis of parallel I/O use on ARCHER and analysis on the potential impact of different applications on file system performance using metrics we have derived from the LASSi data. We show that the performance data from LASSi reveals how the same application can stress different components of the file system depending on how it is run, and how the LASSi risk metrics allow us to identify use cases that could potentially cause issues for global I/O performance and work with users to improve their I/O use. We use the IO-500 benchmark to help us understand how LASSi risk metrics correspond to observed performance on the ARCHER file systems. We also use LASSi data imported into SAFE to identify I/O use patterns associated with different research areas, understand how the research workflow gives rise to the observed patterns and project how this will affect I/O requirements in the future. Finally, we provide an overview of likely future directions for the continuation of this work.}
}
@incollection{weber2017visual,
title={{Visual Comparison of Trace Files in Vampir}},
author={Weber, Matthias and Brendel, Ronny and Wagner, Michael and Dietrich, Robert and Tsch{\"u}ter, Ronny and Brunst, Holger},
booktitle={Programming and Performance Visualization Tools},
pages={105--121},
year={2017},
publisher={Springer}
}
@inproceedings{demasi2013identifying,
title={{Identifying HPC codes via performance logs and machine learning}},
author={DeMasi, Orianna and Samak, Taghrid and Bailey, David H},
booktitle={Proceedings of the first workshop on Changing landscapes in HPC security},
pages={23--30},
year={2013}
}
@inproceedings{lu2013comprehensive,
title={{Comprehensive job level resource usage measurement and analysis for XSEDE HPC systems}},
author={Lu, Charng-Da and Browne, James and DeLeon, Robert L and Hammond, John and Barth, William and Furlani, Thomas R and Gallo, Steven M and Jones, Matthew D and Patra, Abani K},
booktitle={{Proceedings of the Conference on Extreme Science and Engineering Discovery Environment: Gateway to Discovery}},
pages={1--8},
year={2013}
}
@inproceedings{evans2014comprehensive,
title={{Comprehensive resource use monitoring for HPC systems with TACC stats}},
author={Evans, Todd and Barth, William L and Browne, James C and DeLeon, Robert L and Furlani, Thomas R and Gallo, Steven M and Jones, Matthew D and Patra, Abani K},
booktitle={{2014 First International Workshop on HPC User Support Tools}},
pages={13--21},
year={2014},
organization={IEEE}
}
@inproceedings{liu2020characterization,
title={{Characterization and identification of HPC applications at leadership computing facility}},
author={Liu, Zhengchun and Lewis, Ryan and Kettimuthu, Rajkumar and Harms, Kevin and Carns, Philip and Rao, Nageswara and Foster, Ian and Papka, Michael E},
booktitle={{Proceedings of the 34th ACM International Conference on Supercomputing}},
pages={1--12},
year={2020}
}
@inproceedings{bang2020hpc,
title={{HPC Workload Characterization Using Feature Selection and Clustering}},
author={Bang, Jiwoo and Kim, Chungyong and Wu, Kesheng and Sim, Alex and Byna, Suren and Kim, Sunggon and Eom, Hyeonsang},
booktitle={Proceedings of the 3rd International Workshop on Systems and Network Telemetry and Analytics},
pages={33--40},
year={2020}
}
@article{simakov2018workload,
title={{A Workload Analysis of NSF's Innovative HPC Resources Using XDMoD}},
author={Simakov, Nikolay A and White, Joseph P and DeLeon, Robert L and Gallo, Steven M and Jones, Matthew D and Palmer, Jeffrey T and Plessinger, Benjamin and Furlani, Thomas R},
journal={arXiv preprint arXiv:1801.04306},
year={2018}
}
@incollection{white2018automatic,
title={{Automatic Characterization of HPC Job Parallel Filesystem I/O Patterns}},
author={White, Joseph P and Kofke, Alexander D and DeLeon, Robert L and Innus, Martins and Jones, Matthew D and Furlani, Thomas R},
booktitle={{Proceedings of the Practice and Experience on Advanced Research Computing}},
pages={1--8},
year={2018}
}
@incollection{chan2019resource,
title={{A Resource Utilization Analytics Platform Using Grafana and Telegraf for the Savio Supercluster}},
author={Chan, Nicolas},
booktitle={{Proceedings of the Practice and Experience in Advanced Research Computing on Rise of the Machines (learning)}},
pages={1--6},
year={2019}
}
%doi = {https://doi.org/10.1007/978-3-030-59851-8_12},
@inproceedings{betke20,
author = {Eugen Betke and Julian Kunkel},
title = {{The Importance of Temporal Behavior when Classifying Job IO Patterns Using Machine Learning Techniques}},
year = {2020},
month = {06},
booktitle = {{High Performance Computing: ISC High Performance 2020 International Workshops, Revised Selected Papers}},
publisher = {Springer},
series = {Lecture Notes in Computer Science},
number = {12151},
pages = {191-205},
conference = {ISC HPC},
isbn = {978-3-030-59851-8},
issn = {1611-3349},
abstract = {Every day, supercomputers execute 1000s of jobs with different characteristics. Data centers monitor the behavior of jobs to support the users and improve the infrastructure, for instance, by optimizing jobs or by determining guidelines for the next procurement. The classification of jobs into groups that express similar run-time behavior aids this analysis as it reduces the number of representative jobs to look into. It is state of the practice to investigate job similarity by looking into job profiles that summarize the dynamics of job execution into one dimension of statistics and neglect the temporal behavior. In this work, we utilize machine learning techniques to cluster and classify parallel jobs based on the similarity in their temporal IO behavior to highlight the importance of temporal behavior when comparing jobs. Our contribution is the qualitative and quantitative evaluation of different IO characterizations and similarity measurements that work toward the development of a suitable clustering algorithm. We explore IO characteristics from monitoring data of one million parallel jobs and cluster them into groups of similar jobs. Therefore, the time series of various IO statistics is converted into features using different similarity metrics that customize the classification. We discuss conventional ML techniques that are applied to job profiles and contrast this with the analysis of time series data where we apply the Levenshtein distance as a distance metrics. While the employed Levenshtein algorithms arent yet optimal, the results suggest that temporal behavior is key to identify related pattern.},
}
@article{Eugen20HPS,
author = {Eugen Betke and Julian Kunkel},
title = {{Classifying Temporal Characteristics of Job I/O Using Machine Learning Techniques}},
year = {2021},
month = {01},
journal = {Journal of High Performance Computing},
series = {Issue 1},
isbn = {},
doi = {10.5281/zenodo.4478960},
url = {\url{https://jhps.vi4io.org/issues/#1-1}},
abstract = {{Every day, supercomputers execute 1000s of jobs with different characteristics. Data centers monitor the behavior of jobs to support the users and improve the infrastructure, for instance, by optimizing jobs or by determining guidelines for the next procurement. The classification of jobs into groups that express similar run-time behavior aids this analysis as it reduces the number of representative jobs to look into. This work utilizes machine learning techniques to cluster and classify parallel jobs based on the similarity in their temporal I/O behavior. Our contribution is the qualitative and quantitative evaluation of different I/O characterizations and similarity measurements and the development of a suitable clustering algorithm. <br><br> In the evaluation, we explore I/O characteristics from monitoring data of one million parallel jobs and cluster them into groups of similar jobs. Therefore, the time series of various I/O statistics is converted into features using different similarity metrics that customize the classification. <br><br> When using general-purpose clustering techniques, suboptimal results are obtained. Additionally, we extract phases of I/O activity from jobs. Finally, we simplify the grouping algorithm in favor of performance. We discuss the impact of these changes on the clustering quality.}}
}

305
lncs-from-jhps/jhps.cls Normal file
View File

@ -0,0 +1,305 @@
\ProvidesClass{jhps}[2020/07/06 v1]
\DeclareOption*{\PassOptionsToClass{\CurrentOption}{article}}
\ProcessOptions\relax
\LoadClass[a4paper,11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[usenames,dvipsnames,svgnames,table]{xcolor}
\usepackage[english]{babel}
\usepackage{geometry}
\newgeometry{left=3cm,bottom=2.5cm,right=2.5cm,top=2.5cm}
\usepackage[breakwords]{truncate}
\usepackage[cmex10]{amsmath}
\usepackage{titling}
\usepackage{hyperref}
\usepackage{graphicx}
\usepackage{cleveref}
\usepackage{fancyhdr}
\usepackage[table]{xcolor}
\usepackage{tikz}
\usepackage{floatrow}
\usepackage{colortbl}
\usepackage{listings}%utf8
\usepackage{chngcntr}
\usepackage{caption}
\usepackage{subcaption}
\usepackage{pgffor}
\usepackage{marvosym}
%%%% END packages
\newtoks\email
\newtoks\affiliation
\newtoks\JHPSissue
\newtoks\JHPSkeywords
\bibliographystyle{alpha}
\graphicspath{ {./assets/} }
\date{\today}
\definecolor{JHPSRed}{HTML}{ee2d24}
\definecolor{tblhead}{HTML}{cccccc}
\definecolor{JHPSGray}{HTML}{cccccc}
\definecolor{Blue2}{HTML}{006d9a}
\definecolor{Green1}{HTML}{9ac013}
\definecolor{Green2}{HTML}{007000}
\hypersetup{
colorlinks,
linkcolor={JHPSRed},
citecolor={JHPSRed},
filecolor={JHPSRed},
urlcolor={JHPSRed},
anchorcolor={JHPSRed}
}
\renewcommand\UrlFont{\color{JHPSRed}}
\lstset{postbreak=\raisebox{0ex}[0ex][0ex]{\ensuremath{\color{blue}\hookrightarrow\space}},
basicstyle=\fontsize{9}{8}\ttfamily, % the size of the fonts that are used for the code
breakatwhitespace=false, % sets if automatic breaks should only happen at whitespace
breaklines=true, % sets automatic line breaking
captionpos=b, % sets the caption-position to bottom
%commentstyle=\color{mygreen}, % comment style
%deletekeywords={...}, % if you want to delete keywords from the given language
escapeinside={\%*}{*)}, % if you want to add LaTeX within your code
extendedchars=false, % if true, lets you use non-ASCII characters; for 8-bits encodings only, does not work with UTF-8
frame={bt}, % adds a frame around the code frame={bt},
keepspaces=true, % keeps spaces in text, useful for keeping indentation of code (possibly needs columns=flexible)
keywordstyle=\bf\ttfamily, % keyword style
%language=C, % the language of the code
%morekeywords={*,...}, % if you want to add more keywords to the set
numbers=left, % where to put the line-numbers; possible values are (none, left, right)
xleftmargin=4ex,
numbersep=2.5ex, % how far the line-numbers are from the code
numberstyle=\tiny\color{darkgray}, % the style that is used for the line-numbers
rulecolor=\color{JHPSRed}, % if not set, the frame-color may be changed on line-breaks within not-black text (e.g. comments (green here))
showspaces=false, % show spaces everywhere adding particular underscores; it overrides 'showstringspaces'
showstringspaces=false, % underline spaces within strings only
showtabs=false, % show tabs within strings adding particular underscores
stepnumber=1, % the step between two line-numbers. If it's 1, each line will be numbered
%stringstyle=\color{mymauve}, % string literal style
tabsize=2, % sets default tabsize to 2 spaces
title=\lstname,%,
%backgroundcolor=\color{JHPSGray}
keywordstyle=\color{Green2}\ttfamily,
stringstyle=\color{JHPSRed}\ttfamily,
commentstyle=\color{Blue2}\ttfamily,
morecomment=[l][\color{magenta}]{\#}
}
\lstdefinelanguage{bibtex}{
keywords={@article,@misc},
sensitive=false,
comment=[l]{\%}
}
\lstdefinelanguage{none}{
morekeywords={},
sensitive=false
}
\crefname{lstlisting}{listing}{listing}
\Crefname{lstlisting}{Listing}{Listing}
% Figure/Table placement
\def\fps@figure{!pb}
\def\fps@table{!pb}
\newfloat{lstfloat}{!pb}{lop}
\floatname{lstfloat}{Listing}
\def\lstfloatautorefname{Listing}
\setlength\headheight{18pt}
\makeatletter
\newcount\authorcount
\def\storedata#1#2{\edef\tmp{\string#1}\storedataA#2\end\advance\authorcount by-1}
\def\storedataA#1{\advance\authorcount by1
\ifx\end#1
\else
\expandafter\def\csname data:\tmp:\the\authorcount\endcsname{#1}%
\expandafter\storedataA
\fi
}
\def\getdata[#1]#2{\csname data:\string#2:#1\endcsname}
\def\basiceval#1{\the\numexpr#1\relax}
\def\JHPSauthor#1#2#3#4{
\storedata\Jauthor{{#1}}
\storedata\Jauthor{{#2}}
\storedata\Jauthor{{#3}}
\storedata\Jauthor{{#4}}
}
\renewcommand*{\maketitle}{
\pagestyle{plain}
\thispagestyle{title}
\ifnum\the\JHPSissue>0
\else
This manuscript is in the JHPS incubator and has \textbf{not been assigned an issue}. \\[0.2cm]
%\begin{minipage}{11cm}
%\tableofcontents
%\end{minipage}
\vspace*{-2cm}
\fi
\vskip 2em%
\begin{center}%
\begin{tikzpicture}
\path [left color = JHPSRed!80, right color = JHPSRed!80]
(0,0) rectangle (\hsize,0.25ex);
\end{tikzpicture}
{\huge \@title \par}%
\begin{tikzpicture}
\path [left color = JHPSRed!80, right color = JHPSRed!80]
(0,0) rectangle (\hsize,0.25ex);
\end{tikzpicture}
\vspace*{-0.25cm}
{\hfill\tiny \hyperref[sec:reviews]{Reviews}} % \framebox[4cm]{
\vskip 1.2em%
% authors
\newcommand{\jauthorcount}{\basiceval{\the\authorcount/4}}
\foreach\index in {1,...,\jauthorcount}{
\def\val{\basiceval{12/\jauthorcount}}
\ifnum \val>3
\else \def\val{3.8}
\fi
%\fbox{ % for debuggin
\begin{minipage}[t]{\val cm}
\centering
\href{\getdata[\basiceval{\index*4-1}]\Jauthor}{\textcolor{black}{\large \getdata[\basiceval{\index*4-3}]\Jauthor}} \par
\smallskip
\getdata[\basiceval{\index*4-2}]\Jauthor \par
\def\val{\getdata[\basiceval{\index*4}]\Jauthor}
\if \val
\else \smallskip \Letter~\textit{\val}
\fi
\vspace*{1.5em}
\end{minipage}
}
%}
\end{center}%
}
\renewenvironment{abstract}{%
\vspace*{-1.1cm}
\small
\null\vfil
\begin{center}%
{\bfseries \abstractname\vspace{-.5em}\vspace{0pt}}%
\end{center}%
\quotation
}
{\par \smallskip \textbf{Keywords}: \the\JHPSkeywords \endquotation\vfil\null \vspace*{-0.75cm}}
\newcommand{\fancyRulers}{
\renewcommand\footrule{\begin{minipage}{1\textwidth}
\begin{tikzpicture}
\path [left color = JHPSGray!100, right color = JHPSRed!80]
(0,0) rectangle (\hsize,0.25ex);
\end{tikzpicture}
\end{minipage}\par}%
\renewcommand\headrule{
\vspace*{-0.5em}
\begin{tikzpicture}
\path [left color = JHPSGray!100, right color = JHPSRed!80] (0,0) rectangle (\hsize,0.25ex);
\end{tikzpicture}}%
}
\newcommand{\fancyFootRulers}{
\renewcommand\footrule{\begin{minipage}{1\textwidth}
\begin{tikzpicture}
\path [left color = JHPSGray!100, right color = JHPSRed!80]
(0,0) rectangle (\hsize,0.25ex);
\end{tikzpicture}
\end{minipage}\par}%
\renewcommand\headrule{}
}
% \makeatletter
% \global\let\tikz@ensure@dollar@catcode=\relax
% \makeatother
\fancypagestyle{plain}{
\fancyRulers
\fancyhead[L]{}
\fancyhead[R]{\@date} %\leftmark
\fancyhead[L]{\truncate{12cm}{\thetitle}}
\fancyfoot[C]{}
\fancyfoot[R]{\thepage/\pageref*{LastPage}}
\fancyfoot[L]{\includegraphics[height=0.8em]{jhps-logo} This article \ifnum\the\JHPSissue>0 appeared in the \href{https://jhps.vi4io.org/issue/\the\JHPSissue}{Journal of High-Performance Storage, \the\JHPSissue}\else is in the incubator of the \href{https://jhps.vi4io.org/incubator/}{Journal of High-Performance Storage}\fi }
}
\fancypagestyle{title}{
\fancyFootRulers
\fancyhead[L]{}
\fancyhead[R]{} %\leftmark
\fancyhead[C]{}
\fancyfoot[C]{}
\fancyfoot[R]{\thepage/\pageref*{LastPage}}
\fancyfoot[L]{\includegraphics[height=0.8em]{jhps-logo} This article \ifnum\the\JHPSissue>0 appeared in the \href{https://jhps.vi4io.org/issue/\the\JHPSissue}{Journal of High-Performance Storage, \the\JHPSissue}\else is in the incubator of the \href{https://jhps.vi4io.org/incubator/}{Journal of High-Performance Storage}\fi }
}
\fancypagestyle{reviews}{
\fancyFootRulers
\fancyhead[L]{}
\fancyhead[R]{\@date} %\leftmark
\fancyhead[L]{\truncate{12cm}{\thetitle}}
\fancyfoot[C]{Reviews}
\fancyfoot[R]{\thepage}
\fancyfoot[L]{\includegraphics[height=0.8em]{jhps-logo}}
}
\fancypagestyle{empty}{
\fancyFootRulers
\fancyhead[L]{}
\fancyhead[R]{}
\fancyfoot[C]{}
\fancyfoot[R]{}
\fancyfoot[L]{}
}
\let\oldtabular\tabular
\let\endoldtabular\endtabular
\renewenvironment{tabular}{\rowcolors{2}{white}{lightgray!20!white}\oldtabular}{\endoldtabular}
\newcommand{\tab}{\hspace{9pt}}
\newcommand{\cellHeader}[0]{\cellcolor{JHPSRed}}
\newcommand{\ra}[1]{\renewcommand{\arraystretch}{#1}}
\newcolumntype{M}[1]{>{\centering\arraybackslash}m{#1}}
%% The review bottom
\newcommand{\reviews}{
\label{LastPage}
\clearpage
\pagestyle{reviews}
\section{Reviews}
\label{sec:reviews}
\textit{This section is optional for reviewers and shows their assessment that lead to the acceptance of the original manuscript. Reviewers may or may not update their review for a major update of the paper, the exact trail is available in GitHub repository of this article. The reviews are part of the article and validate the acceptance. Please check the details on the JHPS webpage.}
\ifnum\the\JHPSissue>0
\else
Fine-grained comments and suggestions should be added directly to the manuscript in the Google Doc on the top using Suggesting mode (top right, underneath the blue share button).
\fi
}
\endinput

1079
lncs-from-jhps/main.tex Normal file

File diff suppressed because it is too large Load Diff

18
lncs-from-jhps/meta.yaml Normal file
View File

@ -0,0 +1,18 @@
---
# Metadata for this publication
- authors:
- name: Julian Kunkel
email: j.m.kunkel@reading.ac.uk # add emails for all corresponding authors
url: https://hps.vi4io.org/about/people/julian_kunkel
- name: Eugen Betke
email: betke@dkrz.de
- funding:
# Do not modify the metadata underneath, it is for internal purposes of JHPS
- publications: # Will be added every time published
- current:
pdf: https://jhps.vi4io.org/pdf/jhps-2021-03-kunkel.pdf # publication url for current revision
- v1-2021-03-16: # version + date
revision: # Git Hash that is published
doi: # Zenodo DOI
pdf: # URL for the PDF
issue: # JHPS issue

View File

@ -72,17 +72,16 @@
\crefname{codecount}{Code}{Codes}
\title{A Workflow for Identifying Jobs with Similar I/O Behavior Utilizing Time Series Analysis}
%\author{Julian Kunkel\inst{2} \and Eugen Betke\inst{1}}
\author{}
\author{Julian Kunkel\inst{2} \and Eugen Betke\inst{1}}
\institute{\vspace*{-1cm}}
%\institute{
%University of Reading--%
%\email{j.m.kunkel@reading.ac.uk}%
%\and
%DKRZ --
%\email{betke@dkrz.de}%
%}
\institute{
University of Reading--%
\email{j.m.kunkel@reading.ac.uk}%
\and
DKRZ --
\email{betke@dkrz.de}%
}
\begin{document}
\maketitle