Code Monkey home page Code Monkey logo

warg-report-2022's Introduction

LaTeX style files for HYPERRIDE deliverables.

Basic usage:

The basic structure of a deliverable formatted according with these styles should be (minimally):

\documentclass[11pt]{report}
\usepackage{hyperride}  

\begin{document}

%% a Changelog. Each call to \istChange adds an entry to the
%% changelog. After LaTeX is run, it will generate a table on page 2
%% containing all changes. N.B.: I could not find a way to generate
%% this table directly, so the whiledo{} loop in istprog.sty writes
%% the changelog table to a temp file (more or less the way tables of
%% content are generated), so you have to run LaTeX twice to update
%% this table (as you would to update the TOC).
\istChange{dd/mm/yyyy}{v1.o}{Name (Partner short name)}{Draft report template}
\istChange{...}{}{...}{}
\istChange{}{}{}{}

%% Deliverable information
\ProjectAcronym{HYPERRIDE}
\ProjectFullTitle{Hybrid Provision of Energy based on Reliability and Resiliency by Integration of Dc Equipment}
\ProjectRefNo{957788}
\delivNumber{Dx.y}
\delivName{[Title as appears in the DoA]}
\delivShortTile{Short Title}
%% Lead partner
\delivResponsible{[Responsible partner]} 
\delivVersion{vn.n}
\ActualDate{dd/mm/yyyy}
\delivDissLevel{CO}
\delivType{[Report, Prototype, Other]}
\delivWP{WPx} % Workpackage x; not used at the moment
\delivAuthor{Names of co-authors  (partners short names)}
\delivFPAuthor{Names of co-authors  (partners short names)}
\delivStatus{Draft}
\delivKeywords{[List of free keywords relevant to the deliverable]}
\delivTask{Tn.n}
\delivStatus{[Draft, v1.0, v2.0, Final version]}
\delivExecSummary{This is a summary of the deliverable; a paragraph or
so to go on the cover page} 

\makecover
% page 3: table of contents
\newpage
\fancypagestyle{plain}{}

\settableofcontents
\tableofcontents

\vfill
\section*{List of abbreviations}

\begin{tabular}[h]{ll}
 EC	        &	European Commission \\
 DoA	&	Description of Action\\
\end{tabular}


\newpage
\section{Your first section}

\subsection{A subsection of your first section}

etc

\bibliography{your-bib-file}
\bibliographystyle{apacite} %% recommended 
\{document}

Further details

See template.tex/template.pdf in this directory.

If you have any thoughts on how to improve this style, feel free to implement them and share your results. The same goes for bug fixes.

Just clone the project and 'Have fun!'

warg-report-2022's People

Contributors

hhhapz avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.