julian.kunkel
/
mistral-io-datasets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
mistral-io-datasets/lncs-from-jhps
History
Eugen Betke ced1384734 Mit Grammarly geprueft 2021-06-03 19:02:24 +02:00
..
assets Spacve ^-^ 2021-06-02 15:22:56 +02:00
.gitignore Nai 2021-06-02 14:12:37 +02:00
README.md Nai 2021-06-02 14:12:37 +02:00
bibliography.bib Kürzen auf 12 Seiten - Completed. 2021-06-02 15:36:29 +02:00
llncs.cls jhps -> llncs 2021-06-03 19:02:04 +02:00
main.tex Mit Grammarly geprueft 2021-06-03 19:02:24 +02:00
meta.yaml Nai 2021-06-02 14:12:37 +02:00

README.md

JHPS LaTeX template

This LaTeX template is part of the Journal of High-Performance description for 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).

  2. Submit the information about the repository to the journal see for 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. At this stage, the following documents are created:

    • A Google Doc containing the manuscript (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 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) 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: this file shall contain all text of the full paper.
  • bibliography.bib: this file contains the BibTex of the paper.
  • meta.yaml: metadata for this publication.
  • assets: include all figures and material referenced by LaTeX.
  • workflow: a directory containing the workflow for the reproducible workflow.
  • 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:

    cd path/to/repo

popper run build-paper

    For more information on Popper visit the official documentation.

  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:

    cd path/to/repo

popper run split-lines

  6. Notify the board about the paper, see for authors