From 1c9b43a5f1c4e8c5af87fd486359163009e0afe2 Mon Sep 17 00:00:00 2001
From: Markus Quaritsch <markus.quaritsch@tugraz.at>
Date: Wed, 11 Nov 2015 17:34:31 +0100
Subject: [PATCH] draft version of release notes and release report
---
Documentation/ReleaseNotes/ReleaseNotes.tex | 2 +-
Documentation/ReleaseNotes/ReleaseReport.tex | 21 +
.../Vecto_3.0.1.312/Comparison.tex | 475 ++++++++++++++++++
.../Vecto_3.0.1.312/ReleaseNotes.tex | 362 +++++++------
Documentation/ReleaseNotes/content.tex | 33 +-
Documentation/ReleaseNotes/header.tex | 15 +-
.../ReleaseNotes/preamble_handout.tex | 48 +-
7 files changed, 722 insertions(+), 234 deletions(-)
create mode 100644 Documentation/ReleaseNotes/ReleaseReport.tex
create mode 100644 Documentation/ReleaseNotes/Vecto_3.0.1.312/Comparison.tex
diff --git a/Documentation/ReleaseNotes/ReleaseNotes.tex b/Documentation/ReleaseNotes/ReleaseNotes.tex
index 7c08efef72..2d464e2e1a 100644
--- a/Documentation/ReleaseNotes/ReleaseNotes.tex
+++ b/Documentation/ReleaseNotes/ReleaseNotes.tex
@@ -1,7 +1,7 @@
\input{preamble_handout}
-\includeonlylecture{lecture_0}
+% \includeonlylecture{lecture_0}
\input{content}
diff --git a/Documentation/ReleaseNotes/ReleaseReport.tex b/Documentation/ReleaseNotes/ReleaseReport.tex
new file mode 100644
index 0000000000..cac578e12d
--- /dev/null
+++ b/Documentation/ReleaseNotes/ReleaseReport.tex
@@ -0,0 +1,21 @@
+\input{preamble_handout}
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\begin{document}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+% \titleframe
+\title{Vecto 3.0.1 Release Report} % Kurztitel in []
+
+\maketitle
+
+%====================
+
+\input{Vecto_3.0.1.312/ReleaseNotes.tex}
+
+\input{Vecto_3.0.1.312/Comparison.tex}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\end{document}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Documentation/ReleaseNotes/Vecto_3.0.1.312/Comparison.tex b/Documentation/ReleaseNotes/Vecto_3.0.1.312/Comparison.tex
new file mode 100644
index 0000000000..abb05df26d
--- /dev/null
+++ b/Documentation/ReleaseNotes/Vecto_3.0.1.312/Comparison.tex
@@ -0,0 +1,475 @@
+%!TEX root = ../ReleaseReport.tex
+
+%=========================================================================
+\section{Comparison of Vecto 2.2 and Vecto 3.0.1} % (fold)
+\label{sec:comparison_of_vecto_2_2_and_vecto_3_0_1}
+%=========================================================================
+
+To compare the Driving behavior of Vecto~2.2 and Vecto~3.0.1 a number of simple driving cycles (about 2 -- 5\,km) have been used to visually compare the most important parameters such as
+\begin{itemize}
+ \item Vehicle speed
+ \item Acceleration
+ \item Engine speed
+ \item Gear
+ \item Engine power and torque
+ \item Fuel consumption
+\end{itemize}
+for two different vehicles: (i) 40t truck, and (ii) coach. The driving cycles tested are listed in \Cref{sec:driving_cycles_comparison}. \Cref{sec:comparison_vecto_2_2_and_vecto_3_0_1_on_the_basic_driving_cycles} contains graphs comparing the parameters listed above for Vecto~2.2 and Vecto~3.0.1 for the basic driving cycles.
+
+\Cref{sec:comparison_of_vecto_2_2_and_vecto_3_0_1_on_the_declaration_cycle} shows a comparison of Vecto~2.2 and Vecto~3.0.1 for selected Declaration-Mode driving cycles (long-haul, regional delivery, and urban delivery) for different loadings and two different vehicles.
+
+\Cref{sec:declaration_results_report_for_vecto_2_2_and_vecto_3_0_1} contains Declaration Reports for different Vecto jobs, generated with version~2.2 and version~3.0.1
+
+
+
+%=========================================================================
+\section{ACEA Requirements} % (fold)
+\label{sec:subsection_name}
+%=========================================================================
+
+
+%-------------------------------------------------------------------------
+\subsection{General Requirements} % (fold)
+\label{sub:general_requirements}
+
+
+\begin{tabular}{L{\IdColWidth}|L{\ReqColWidth}|M{\StatusColWidth}}
+ID & Requirement & Status Vecto 3.0.1 \\ \hline\hline
+Req 101 & The tool shall calculate fuel usage, CO2 emissions, indicators to enable verification tests and performance indicators for any admissible vehicle configuration, driver behaviour and mission profile. &
+ \Vcheck \\ \hline
+Req 102 & All tools which will be needed for delcaring CO2 values shall be free of charge for anyone who is obliged to use these tools. &
+ \Vcheck \\ \hline
+Req 103 & The tool shall have a functional user interface which addresses all simulation functionalities so that the tool can be used for the tool testing and testing non-declared variants. &
+ --- \\ \hline
+Req 104 & The simulation tool shall be able to run without any GUI. &
+ \Vcheck \\ \hline
+Req 105 & The English language shall be used for naming configuration parameters and internal interfaces. &
+ \Vcheck \\ \hline
+Req 106 & The English language shall be used for naming configuration parameters and internal interfaces. &
+ \Vcheck \\ \hline
+Req 107 & SI Units shall be used as the basis for modelling and configuration. &
+ \Vcheck \\ \hline
+Req 108 & The inaccuracy due to the numerical functions shall not be larger then 0.01\% while the discriminating factor between different variants or OEM's is in the order of 0.1\%. &
+ ?? \\ \hline
+Req 110 & The application shall not store measurement and input data internally. &
+ \Vcheck \\ \hline
+Req 111 & A direct connection to the simulation core shall be requested via API &
+ \Vtodo \\ \hline
+\end{tabular}
+
+%-------------------------------------------------------------------------
+\subsection{Models} % (fold)
+\label{sub:models}
+
+\begin{tabular}{L{\IdColWidth}|L{\ReqColWidth}|M{\StatusColWidth}}
+ID & Requirement & Status Vecto 3.0.1 \\ \hline\hline
+Req 201 & The simulation model shall be modular in the sense that each module may be configured and validated as a separate entity. In order to simplify validation, configuration and data management. &
+ \Vcheck \newline (not most recent whitebook version) \\ \hline
+Req 202 & There shall be modules for specification of at least: vehicle combination, chassis, weight, auxiliaries, rolling resistance, air resistance, engine map, gear box, additional (Eco) equipment, mission profile, load factor, driver, climate and fuel. &
+ \Vcheck \newline (not most recent whitebook version) \\ \hline
+Req 203 & It shall be possible to configure conventional drivelines. &
+ \Vcheck \\ \hline
+Req 204 & It shall be possible to add user defined component modules to the standard vehicle models. Models may be extended for experimental purposes or as a certified way to handle proprietary features. &
+ supported by the architecture, no configuration interface yet \\ \hline
+Req 205 & It shall be possible to add user defined OEM independent control strategies to the standard vehicle models. &
+ supported by the architecture, no configuration interface yet \\ \hline
+Req 206 & It shall be possible to add user defined OEM dependent control strategies to the standard vehicle models. &
+ supported by the architecture, no configuration interface yet \\ \hline
+Req 209 & It shall be possible to configure hybrid drivelines. &
+ supported by architecture, no hybrid models available atm. \\ \hline
+\end{tabular}
+
+%-------------------------------------------------------------------------
+\subsection{Openess} % (fold)
+\label{sub:openess}
+
+\begin{tabular}{L{\IdColWidth}|L{\ReqColWidth}|M{\StatusColWidth}}
+ID & Requirement & Status Vecto 3.0.1 \\ \hline\hline
+Req 301 & The model equations shall be open for inspection or documented in such detail that each calculation can be verified in another tool. Quality assurance by peer review. &
+ \Vcheck \\ \hline
+Req 302 & It shall be possible to monitor intermediate results and quantities in the interfaces between system modules in the "engineering mode" only. Quality assurance by peer review. &
+ \Vcheck \newline (mod-data) \\ \hline
+\end{tabular}
+
+%-------------------------------------------------------------------------
+\subsection{Configuration} % (fold)
+\label{sub:configuration}
+
+\begin{tabular}{L{\IdColWidth}|L{\ReqColWidth}|M{\StatusColWidth}}
+ID & Requirement & Status Vecto 3.0.1 \\ \hline\hline
+Req 401 & It shall be possible to define an arbitrary drive cycle with speed (or speed limit) and altitude (or inclination) as a function of travelled distance for evaluating the simulation tool &
+ \Vcheck \\ \hline
+Req 403 & It shall be possible to limit configuration options for regulatory usage. &
+ \Vcheck \\ \hline
+\end{tabular}
+
+%-------------------------------------------------------------------------
+\subsection{Tool Operation} % (fold)
+\label{sub:tool_operation}
+
+\begin{tabular}{L{\IdColWidth}|L{\ReqColWidth}|M{\StatusColWidth}}
+ID & Requirement & Status Vecto 3.0.1 \\ \hline\hline
+Req 501 & The simulation tool should consist of a library that can be linked to a OEM specific environment and a standalone application which uses this library. &
+ \Vcheck \\ \hline
+Req 502 & The API should be platform independent &
+ \Vcheck \newline (.Net 4.5) \\ \hline
+Req 503 & It shall be possible to configure and run simulations programmatically by means of API. &
+ \Vcheck \newline (file-based atm.) \\ \hline
+Req 504 & It shall be possible to export simulation results in an open structured format. &
+ \Vcheck \\ \hline
+Req 505 & It shall be possible to generate simulation results with unique identifiers per simulation &
+ \Vtodo \\ \hline
+Req 506 & The core application shall provide descriptive errors and warnings reporting according to common used norms for OEM internal specific handling &
+ modular logging is implemented, potentially needs some refactoring \\ \hline
+Req 508 & The european comission should be responsible for the functionality of the tool. &
+ \\ \hline
+\end{tabular}
+
+%-------------------------------------------------------------------------
+\subsection{Maintenance} % (fold)
+\label{sub:maintenance}
+
+\begin{tabular}{L{\IdColWidth}|L{\ReqColWidth}|M{\StatusColWidth}}
+ID & Requirement & Status Vecto 3.0.1 \\ \hline\hline
+Req 601 & There shall be a process for maintenance of the tool. &
+ not applicable \\ \hline
+Req 602 & There shall be a process for validation of the tool. &
+ not applicable \\ \hline
+Req 603 & There shall be a process for distribution of the tool. &
+ not applicable \\ \hline
+Req 604 & There shall be a support organisation that provides quick solution of any type, permanent or non-permanent, within 48 hours to bug reports of critical nature. A bug is considered critical if the application can’t provide a correct calculation when given correct input. &
+ not applicable \\ \hline
+Req 606 & There shall be a support organisation that provides a response to bugs of non-critical nature, with the next release. &
+ not applicable \\ \hline
+Req 607 & There shall be a support organisation that provides bug acknowledgement of any kind within 24 hours. &
+ not applicable \\ \hline
+Req 608 & In order to support a broad target audience, the simulation tool's user and support documentation shall be available in English &
+ \Vcheck \\ \hline
+Req 609 & Simulation tool versions shall be backward compatible so rework at the OEM with regard to processing simulation tool input and output data shall be reduced to the minimum &
+ \Vcheck \\ \hline
+Req 610 & The simulation tool will be developed under version control, so stakeholders are able to trace simulation tool changes over time. &
+ \Vcheck \\ \hline
+Req 611 & The provided interfaces shall be well documented so the OEM's are able to connect their own tools. &
+ not applicable \\ \hline
+Req 612 & Technical support in English shall be available at least from 8 to 18 CET Monday to Friday (except for common European public holidays) by telephone and email. &
+ not applicable \\ \hline
+Req 613 & All documentation affected by the new release of the software must be updated. &
+ \\ \hline
+Req 614 & There shall be a platform by which all OEM's shall be able to view or get actively notified on all OEM bug reports and the solving proces for these bug reports. &
+ \Vcheck \\ \hline
+\end{tabular}
+
+%-------------------------------------------------------------------------
+\subsection{Input Data} % (fold)
+\label{sub:input_data}
+
+\begin{tabular}{L{\IdColWidth}|L{\ReqColWidth}|M{\StatusColWidth}}
+ID & Requirement & Status Vecto 3.0.1 \\ \hline\hline
+Req 701 & The simulation tool shall be able to accept input data through an agreed open document format so OEM's are able to check their own input data is compatible with the input data format. &
+ \\ \hline
+Req 702 & There shall be a module for determination of driving resistances out of standardized measuring methods &
+ \\ \hline
+Req 703 & It shall be possible to select from predefined vehicle classes (defined in the legislative procedure) in order to get standard values for vehicle data. &
+ \Vcheck \\ \hline
+Req 704 & Predefined driving cycles (defined in the legislative procedure) shall be included in the simulation program &
+ \Vcheck \\ \hline
+Req 705 & The set of input data (number of parameters) shall be minimized but sufficient to reach the desired accuracy. &
+ \\ \hline
+Req 706 & The input data should be 1 file per truck which contains all information in case of file based data input/output. &
+ \\ \hline
+Req 707 & The input files/ API should only contain certified input data for the CO2 declarations &
+ \\ \hline
+\end{tabular}
+
+%-------------------------------------------------------------------------
+\subsection{Output Data} % (fold)
+\label{sub:output_data}
+
+\begin{tabular}{L{\IdColWidth}|L{\ReqColWidth}|M{\StatusColWidth}}
+ID & Requirement & Status Vecto 3.0.1 \\ \hline\hline
+Req 801 & "The simulation tool should give the output data according to given API. (The OEM will handle the results internally) &
+ \\ \hline
+Req 802 & Only the values required by the legislative procedure should be communicated with the legislative authorities. &
+ \\ \hline
+Req 803 & In order to support the repeatability of simulation results, the simulation output should contain the simulation tool version and the date-time describing when the simulation has been performed. &
+ \\ \hline
+Req 804 & The output of the simulation tool shall ensure the authenticity of simulation results so that simulation results cannot be changed. &
+ \\ \hline
+Req 805 & The simulation tool shall be able to provide output data via an open format so that data can be accessed and processed separately from the simulation tool. &
+ \\ \hline
+\end{tabular}
+
+%-------------------------------------------------------------------------
+\subsection{Quality} % (fold)
+\label{sub:quality}
+
+\begin{tabular}{L{\IdColWidth}|L{\ReqColWidth}|M{\StatusColWidth}}
+ID & Requirement & Status Vecto 3.0.1 \\ \hline\hline
+Req 902 & The turnaround time of the core application for a single vehicle evaluation should be less than 1 second so that it can be used with current customer information process. &
+ impossible \\ \hline
+Req 903 & The library and the simulation tool shall not have unhandled exceptions so that any exceptions can be understood by the user &
+ \Vcheck \\ \hline
+Req 904 & The simulation tool shall be able to handle concurrent usage so that several simulations should be possible at the same time without interfering with each other. &
+ \Vcheck \\ \hline
+\end{tabular}
+
+
+
+%===========================
+\newpage
+
+% [ ] erfuellte ACEA requirements (x von y erfuellt/obsolet/uebrig)
+
+% [~] Architektur: simulationsarchitektur
+% [x] komponenten, ports mit def. physikalischen typen
+% [x] variable zeitschritte
+% [x] runtime typechecking, SI einheiten
+% [x] multithreading
+% [x] liste der komponenten
+% [x] driver strategy
+% [x] gear-shift strategy
+% [ ] unit tests, code coverage
+% [x] complexitaetsmetrik
+% [x] list of use-cases + comparison
+% [x] distanzgenauig: < 1um
+% [x] vb -> c\#, .net 4.5, new libraries
+% [x] logging framework
+% [x] nur neueste Version der Input Files unterstuetzt
+% [x] zugkraftunterbrechung <1s moeglich, exakt (+/- 5\%) eingehalten
+% [x] Idle Controller während zugkraftunterbrechung
+% [x] SearchOperatingPoint: Lastpunkte < 0,5W genauigkeit zu Vollastkurven
+% [x] exakte analytische loesungen (wo moeglich) anstelle von suchen
+% [x] compressed cycle format supported
+% [x] CSV-Files: reihenfolge der spalten beliebig (wenn header passt)
+% [x] Overspeed: energieeffizienter da beschleunigung nur durch gefaelle (schleppkurve)
+
+% new and improved
+% pdf report
+% mod data: simulation interval
+
+\appendix
+
+% section section_name (end)
+\section{Basic Driving Cycles for comparing Vecto 2.2 and Vecto 3.0.1}
+\label{sec:driving_cycles_comparison}
+
+\begin{itemize}
+\item Accelerate 0\,km/h to 40\,km/h slope: downhill 1\,\% with overspeed
+\item Accelerate 0\,km/h to 40\,km/h slope: downhill 3\,\% with overspeed
+\item Accelerate 0\,km/h to 40\,km/h slope: downhill 5\,\% with overspeed
+\item Accelerate 0\,km/h to 60\,km/h slope: downhill 1\,\% with overspeed
+\item Accelerate 0\,km/h to 60\,km/h slope: downhill 3\,\% with overspeed
+\item Accelerate 0\,km/h to 60\,km/h slope: downhill 5\,\% with overspeed
+\item Accelerate 0\,km/h to 85\,km/h slope: downhill 1\,\% with overspeed
+\item Accelerate 0\,km/h to 85\,km/h slope: downhill 15\,\%
+\item Accelerate 0\,km/h to 85\,km/h slope: downhill 25\,\%
+\item Accelerate 0\,km/h to 85\,km/h slope: downhill 3\,\% with overspeed
+\item Accelerate 0\,km/h to 85\,km/h slope: downhill 5\,\%
+\item Accelerate 0\,km/h to 85\,km/h slope: downhill 5\,\% with overspeed
+\item Accelerate 0\,km/h to 85\,km/h slope: 0\,\%
+\item Accelerate 0\,km/h to 85\,km/h slope: uphill 1\,\%
+\item Accelerate 0\,km/h to 85\,km/h slope: uphill 10\,\%
+\item Accelerate 0\,km/h to 85\,km/h slope: uphill 2\,\%
+\item Accelerate 0\,km/h to 85\,km/h slope: uphill 25\,\%
+\item Accelerate 0\,km/h to 85\,km/h slope: uphill 5\,\%
+\item Accelerate 20\,km/h to 22\,km/h slope: uphill 5\,\%
+\item Accelerate 20\,km/h to 60\,km/h slope: downhill 15\,\%
+\item Accelerate 20\,km/h to 60\,km/h slope: downhill 25\,\%
+\item Accelerate 20\,km/h to 60\,km/h slope: downhill 5\,\%
+\item Accelerate 20\,km/h to 60\,km/h slope: 0\,\%
+\item Accelerate 20\,km/h to 60\,km/h slope: uphill 15\,\%
+\item Accelerate 20\,km/h to 60\,km/h slope: uphill 25\,\%
+\item Accelerate 20\,km/h to 60\,km/h slope: uphill 5\,\%
+\item Accelerate stop 0\,km/h to 85\,km/h slope: 0\,\%
+\item AccelerateAtBrake 80\,km/h to 0\,km/h slope: 0\,\%
+\item AccelerateBeforeBrake 80\,km/h to 0\,km/h slope: 0\,\%
+\item AccelerateWhileBrake 80\,km/h to 0\,km/h slope: 0\,\%
+\item Decelerate 22\,km/h to 20\,km/h slope: downhill 5\,\%
+\item Decelerate 45\,km/h to 0\,km/h slope: downhill 5\,\%
+\item Decelerate 45\,km/h to 0\,km/h slope: 0\,\%\,\%
+\item Decelerate 45\,km/h to 0\,km/h slope: uphill 5\,\%
+\item Decelerate 60\,km/h to 20\,km/h slope: downhill 15\,\%
+\item Decelerate 60\,km/h to 20\,km/h slope: downhill 25\,\%
+\item Decelerate 60\,km/h to 20\,km/h slope: downhill 5\,\%
+\item Decelerate 60\,km/h to 20\,km/h slope: 0\,\%\,\%
+\item Decelerate 60\,km/h to 20\,km/h slope: uphill 5\,\%
+\item Decelerate 80\,km/h to 0\,km/h slope: downhill 15\,\%
+\item Decelerate 80\,km/h to 0\,km/h slope: downhill 25\,\%
+\item Decelerate 80\,km/h to 0\,km/h slope: downhill 5\,\%
+\item Decelerate 80\,km/h to 0\,km/h slope: 0\,\%\,\%
+\item Decelerate 80\,km/h to 0\,km/h slope: uphill 5\,\%
+\item DecelerateWhileBrake 80\,km/h to 0\,km/h slope: 0\,\%
+\item Drive 10\,km/h slope: downhill 15\,\%
+\item Drive 10\,km/h slope: downhill 25\,\%
+\item Drive 10\,km/h slope: downhill 5\,\%
+\item Drive 10\,km/h slope: 0\,\%\,\%
+\item Drive 10\,km/h slope: uphill 15\,\%
+\item Drive 10\,km/h slope: uphill 25\,\%
+\item Drive 10\,km/h slope: uphill 5\,\%
+\item Drive 20\,km/h slope: downhill 15\,\%
+\item Drive 30\,km/h slope: Decreasing - Increasing Slope
+\item Drive 30\,km/h slope: Decreasing Slope
+\item Drive 30\,km/h slope: downhill 15\,\%
+\item Drive 30\,km/h slope: Increasing Slope
+\item Drive 50\,km/h slope: Decreasing - Increasing Slope
+\item Drive 50\,km/h slope: Decreasing Slope
+\item Drive 50\,km/h slope: downhill 15\,\%
+\item Drive 50\,km/h slope: Increasing Slope
+\item Drive 80\,km/h slope: Decreasing Increasing Slope
+\item Drive 80\,km/h slope: Decreasing Slope
+\item Drive 80\,km/h slope: downhill 15\,\%
+\item Drive 80\,km/h slope: downhill 5\,\%
+\item Drive 80\,km/h slope: Increasing Slope
+\item Drive 80\,km/h slope: 0\,\%\,\%
+\item Drive 80\,km/h slope: uphill 15\,\%
+\item Drive 80\,km/h slope: uphill 25\,\%
+\item Drive 80\,km/h slope: uphill 3\,\%
+\item Drive 80\,km/h slope: uphill 5\,\%
+\item Drive stop 85\,km/h stop 85\,km/h slope: 0\,\%
+\end{itemize}
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\section{Comparison Vecto 2.2 and Vecto 3.0.1 on the Basic Driving Cycles} % (fold)
+\label{sec:comparison_vecto_2_2_and_vecto_3_0_1_on_the_basic_driving_cycles}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+%=========================================================================
+% \subsection{40t Long Haul Truck} % (fold)
+% \label{sub:40t_long_haul_truck}
+%=========================================================================
+\includepdf[page=1,scale=0.8,pagecommand=\subsection{40t Long Haul Truck}]{img/Truck_DriverStrategy}
+\includepdf[page=2-,scale=0.8,pagecommand={}]{img/Truck_DriverStrategy}
+% subsection 40t_long_haul_truck (end)
+
+%=========================================================================
+% \subsection{Coach} % (fold)
+% \label{sub:coach}
+%=========================================================================
+% subsection coach (end)
+\includepdf[page=1,scale=0.8,pagecommand=\subsection{Coach}]{img/Coach_DriverStrategy}
+\includepdf[page=2-,scale=0.8,pagecommand={}]{img/Coach_DriverStrategy}
+% section results_of_comparing_vecto_2_2_and_vecto_3_0_1_on_the_basic_driving_cycles (end)
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\section{Comparison of Vecto 2.2 and Vecto 3.0.1 on the Declaration Cycle} % (fold)
+\label{sec:comparison_of_vecto_2_2_and_vecto_3_0_1_on_the_declaration_cycle}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+%=========================================================================
+\subsection{40t Long Haul Truck} % (fold)
+\label{sub:40t_long_haul_truck}
+%=========================================================================
+
+%-------------------------------------------------------------------------
+% \subsubsection{Long Haul Cycle, Full Loading} % (fold)
+% \label{ssub:long_haul_cycle_full_loading}
+%-------------------------------------------------------------------------
+\includepdf[pages=1,scale=0.8,pagecommand=\subsubsection{Long Haul Cycle, Full Loading}]{img/40t_Long_Haul_Truck_LongHaulFullLoading_time}
+\includepdf[pages=-,scale=0.8,pagecommand={}]{img/40t_Long_Haul_Truck_LongHaulFullLoading_dist}
+
+% subsubsection long_haul_cycle_full_loading (end)
+
+%-------------------------------------------------------------------------
+% \subsubsection{Regional Delivery Cycle, Reference Loading} % (fold)
+% \label{ssub:regional_delivery_cycle_reference_loading}
+%-------------------------------------------------------------------------
+\includepdf[pages=1,scale=0.8,pagecommand=\subsubsection{Regional Delivery Cycle, Reference Loading}]{img/40t_Long_Haul_Truck_RegionalDeliveryReferenceLoad_time}
+\includepdf[pages=-,scale=0.8,pagecommand={}]{img/40t_Long_Haul_Truck_RegionalDeliveryReferenceLoad_dist}
+% subsubsection regional_delivery_cycle_reference_loading (end)
+
+% subsection 40t_long_haul_truck (end)
+
+
+%=========================================================================
+\subsection{12t Delivery Truck} % (fold)
+\label{sub:12t_delivery_truck}
+%=========================================================================
+
+%-------------------------------------------------------------------------
+% \subsubsection{Regional Delivery Cycle, Reference Loading} % (fold)
+% \label{ssub:regional_delivery_cycle_reference_loading}
+%-------------------------------------------------------------------------
+\includepdf[pages=1,scale=0.8,pagecommand=\subsubsection{Regional Delivery Cycle, Reference Loading}]{img/12t_Delivery_Truck_RegionalDeliveryReferenceLoad_time}
+\includepdf[pages=-,scale=0.8,pagecommand={}]{img/12t_Delivery_Truck_RegionalDeliveryReferenceLoad_dist}
+% subsubsection regional_delivery_cycle_reference_loading (end)
+
+%-------------------------------------------------------------------------
+% \subsubsection{Urban Delivery Cycle, Reference Loading} % (fold)
+% \label{ssub:urban_delivery_cycle_reference_loading}
+%-------------------------------------------------------------------------
+\includepdf[pages=1,scale=0.8,pagecommand=\subsubsection{Urban Delivery Cycle, Reference Loading}]{img/12t_Delivery_Truck_UrbanDeliveryReferenceLoad_time}
+\includepdf[pages=-,scale=0.8,pagecommand={}]{img/12t_Delivery_Truck_UrbanDeliveryReferenceLoad_dist}
+% subsubsection urban_delivery_cycle_reference_loading (end)
+
+% subsection 12t_delivery_truck (end)
+
+
+
+% section comparison_of_vecto_2_2_and_vecto_3_0_1_on_the_declaration_cycle (end)
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\section{Declaration Results Report for Vecto 2.2 and Vecto 3.0.1} % (fold)
+\label{sec:declaration_results_report_for_vecto_2_2_and_vecto_3_0_1}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+%=========================================================================
+\subsection{Vecto 2.2: 40t Long Haul Truck} % (fold)
+\label{sub:vecto_2_2_40t_long_haul_truck}
+%=========================================================================
+
+% \includepdf[pages=-,scale=0.25,pagecommand=\subsection{Vecto 2.2: 40t Long Haul Truck}\label{sub:vecto_2_2_40t_long_haul_truck}]{img/40t_Long_Haul_Truck_v2}
+
+\fbox{\includegraphics[page=1,scale=0.5]{img/40t_Long_Haul_Truck_v2}}\\[1cm]
+\fbox{\includegraphics[page=2,scale=0.5]{img/40t_Long_Haul_Truck_v2}}\\[1cm]
+\fbox{\includegraphics[page=3,scale=0.5]{img/40t_Long_Haul_Truck_v2}}
+
+% subsection vecto_2_2_40t_long_haul_truck (end)
+
+%=========================================================================
+\subsection{Vecto 3.0.1: 40t Long Haul Truck} % (fold)
+\label{sub:vecto_3_0_1_40t_long_haul_truck}
+%=========================================================================
+
+\fbox{\includegraphics[page=1,scale=0.5]{img/40t_Long_Haul_Truck_v3}}\\[1cm]
+\fbox{\includegraphics[page=2,scale=0.5]{img/40t_Long_Haul_Truck_v3}}\\[1cm]
+\fbox{\includegraphics[page=3,scale=0.5]{img/40t_Long_Haul_Truck_v3}}
+
+% subsection vecto_3_0_1_40t_long_haul_truck (end)
+
+%=========================================================================
+\subsection{Vecto 2.2: 12t Delivery Truck} % (fold)
+\label{sub:vecto_2_2_12t_delivery_truck}
+%=========================================================================
+
+\fbox{\includegraphics[page=1,scale=0.5]{img/12t_Delivery_Truck_v2}}\\[1cm]
+\fbox{\includegraphics[page=2,scale=0.5]{img/12t_Delivery_Truck_v2}}\\[1cm]
+\fbox{\includegraphics[page=3,scale=0.5]{img/12t_Delivery_Truck_v2}}
+
+% subsection vecto_2_2_12t_delivery_truck (end)
+
+%=========================================================================
+\subsection{Vecto 3.0.1: 12t Delivery Truck} % (fold)
+\label{sub:vecto_2_2_12t_delivery_truck}
+%=========================================================================
+
+\fbox{\includegraphics[page=1,scale=0.5]{img/12t_Delivery_Truck_v3}}\\[1cm]
+\fbox{\includegraphics[page=2,scale=0.5]{img/12t_Delivery_Truck_v3}}\\[1cm]
+\fbox{\includegraphics[page=3,scale=0.5]{img/12t_Delivery_Truck_v3}}
+
+% subsection vecto_2_2_12t_delivery_truck (end)
+
+
+% section declaration_results_report_for_vecto_2_2_and_vecto_3_0_1 (end)
+
+
+%----------------------------
+
+% \begin{frame}[t,allowframebreaks]\frametitle{Known Issues}
+% \begin{itemize}
+% \item
+% \end{itemize}
+
+% \end{frame}
\ No newline at end of file
diff --git a/Documentation/ReleaseNotes/Vecto_3.0.1.312/ReleaseNotes.tex b/Documentation/ReleaseNotes/Vecto_3.0.1.312/ReleaseNotes.tex
index 6ab6693119..f4ca92d7e4 100644
--- a/Documentation/ReleaseNotes/Vecto_3.0.1.312/ReleaseNotes.tex
+++ b/Documentation/ReleaseNotes/Vecto_3.0.1.312/ReleaseNotes.tex
@@ -1,191 +1,185 @@
-%!TEX root = lecture.presentation.tex
-
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\begin{document}
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-\titleframe
-
-%###########################################################################
-%###########################################################################
-%###########################################################################
-
-\mode
-<all>
-\lecture{Preparatory Meeting}{lecture_0}
-
-\part{Part 0: Preparatory Notes}
-% \lecture{Part 0: Preparatory Notes}{Part_0}
-
-\input{../0_Preparatory/content.tex}
-
-%###########################################################################
-%###########################################################################
-%###########################################################################
-
-\mode
-<all>
-\lecture{Lecture 1}{lecture_1}
-
-\sectionslidenote{
-\emph{Processor basics:} nur grundlegende Modelle vermitteln, nicht auf die Details eingehen. Verschiedene Modelle für unterschiedliche Prozessorarchitekturen.
-}
-% \lecture{Part 1: Recap Microprocessors}{Part_1}
-\part{Part 1: Microprocessor Fundamentals}
-
-%====================
-
-\begin{frame}[t]{Agenda}
-\vskip-1em
- % \tableofcontents
- \tableofcontents[subsectionstyle=hide,subsubsectionstyle=hide]
- % \begin{itemize}
- % \item Processor \& Programming Models
- % \item Performance Criteria
- % \item Data Path Implementation
- % \item Memory System
- % \item DMA
- % \end{itemize}
- \note{
- Goals: \begin{itemize}
- \item Understand internas of CPU (Fetch/Decode/Execute/Writeback), Instruction set, Addressing
- \item Get an idea of different realizations of a CPU (data path)
- \item Speed up execution
- \begin{itemize}
- \item Understand pipelining, what are the issues?
- \item Branch prediction
- \item Out-of-Order execution
- \end{itemize}
- \item Memory system
+%!TEX root = ../ReleaseNotes.tex
+
+
+% %----------------------------
+
+% \begin{frame}[t]\frametitle{Usage -- GUI}
+% \tskipl
+% \begin{itemize}
+% \item Vecto 3 has been integrated in the GUI of Vecto 2.2
+% \item Separate ``Start'' Button for Vecto 3
+% \end{itemize}
+% \begin{center}
+% \includegraphics[width=\textwidth]{Vecto3_0_1_UI.png}
+% \end{center}
+% \end{frame}
+
+% \begin{frame}[t]\frametitle{Usage -- Command Line}
+% \tskipl
+% \begin{itemize}
+% \item Vecto 3 can also be started from the command line
+% \item Type ``vectocmd.exe -h'' for usage instructions
+% \end{itemize}
+% \begin{center}
+% \includegraphics[width=\textwidth]{Vecto3_0_1_cmd.png}
+% \end{center}
+
+% \end{frame}
+
+% %----------------------------
+
+% \begin{frame}[t,allowframebreaks]{Changes in Vecto 3.0.1}
+% \tskipl
+% \begin{itemize}
+% \item Vecto 3.0 is written from scratch
+% \begin{itemize}
+% \item Windows DLL written in C\#
+% \item Modular software architecture
+% \item Distance-based simulation
+% \end{itemize}
+% \end{itemize}
+
+% \end{frame}
+
+
+\section{Vecto 3.0.1 Release Notes}
+
+%-------------------------------------------------------------------------
+\subsection{General Notes} % (fold)
+\label{ssub:general_notes}
+%-------------------------------------------------------------------------
+
+Vecto 3.0 has been rewritten from scratch. It is now a dynamic program library that contains the core simulation and can be embedded in other applications.
+
+
+Vecto 3.0.1 has been integrated in the graphical user interface of Vecto 2.2 via an additional ``Start'' button on the main screen (cf.~\Cref{fig:Vecto3_GUI}). Additionally, a command-line program is provided to run multiple Vecto jobs (cf.~\Cref{fig:Vecto3_CMD}). For more information how to use the command-line program please see ``vectocmd.exe - h''.\\[-0.3em]
+
+In case you find a bug or Vecto 3.0 does not behave as expected \textbf{please follow the instructions} given in \Cref{sec:how_to_submit_a_bug_report}.
+
+\begin{figure}
+ \centering
+ \includegraphics[width=0.6\textwidth]{img/Vecto3_0_1_UI.png}
+ \caption{Vecto 3.0.1 Graphical User Interface}
+ \label{fig:Vecto3_GUI}
+\end{figure}
+
+\begin{figure}
+ \centering
+ \includegraphics[width=0.6\textwidth]{img/Vecto3_0_1_cmd.png}
+ \caption{Vecto 3.0.1 Command Line Program}
+ \label{fig:Vecto3_CMD}
+\end{figure}
+
+%-------------------------------------------------------------------------
+\subsection{Changes in Vecto 3.0.1} % (fold)
+\label{ssub:changes_in_vecto_3_0_1}
+%-------------------------------------------------------------------------
+
+\begin{itemize}
+ \item New distance-based simulation model
+ \item Simulation with variable steps. The simulation distance is adapted such that the respective time is about 0.5\,s (parameter \textsc{TargetTimeInterval})
+ \item Accuracy of simulated distance vs. driving cycle distance $< 1\,\mu\textrm{m}$
+ \item New componend-based software architecture
+ \begin{itemize}
+ \item Separate software component for every part of the power-train:
+ Combustion Engine,
+ Clutch,
+ Gearbox,
+ Retarder,
+ Axle Gear
+ Vehicle,
+ Wheels,
+ Driver,
+ Driving Cycle
+
+ The models of every component are taken from Vecto 2.2
+ \item Interfaces for components reflecting physical quantities:
+ force/velocity, angular speed/torque, \ldots
+ \item Power-train components modularly usable, custom power-train configurations possible
\end{itemize}
- }
-\end{frame}
-
-\input{../1_Microprocessor_Fundamentals/content.tex}
-
-%###########################################################################
-%###########################################################################
-%###########################################################################
-
-\mode
-<all>
-\lecture{Lecture 2}{lecture_2}
-
-\part{Part 2: Processor Examples}
-% \lecture{Part 2: Processor Examples}{Part_2}
-
-%====================
-
-\begin{frame}[c]\frametitle{Agenda}
- \tableofcontents[subsectionstyle=hide,subsubsectionstyle=hide]
- \note{
- Goals: \begin{itemize}
- \item Get an idea of different processor types and families
- \item Approaches built into CPUs to speed up execution (or spend transistors)
- \item Get an idea which processor can/may be used for what purpose
+ \item \textsc{DriverStrategy} as separate component with well-defined interface
+ \item \textsc{GearshiftStrategy} as separate component with well-defined interface
+ \item All computations are done in SI units; datatypes reflect concrete SI units (i.e., kg, m, s, Nm, \ldots)
+ \item Run-time conformity check of SI units on all computations and SI conversions
+ \item Traction interruption of arbitrary time possible (also $<$ 1\,s), accurate simulation of traction interruption time
+ \item New \textsc{Idle-Controller} to simulate engine speed during traction interruption periods
+ \item Intelligent search of operating point during coasting, braking, and in engine-overload situations, deviation from FLD $<$ 0.5\,W (parameter \textsc{EnginePowerSearchTolerance}).
+ \item Exact analytical solutions instead of exhaustive search where possible, e.g., computing engine's preferred speed, computing time interval required for driving a certain distance, compute distance required to decelerate to a given target speed depending on the driver's deceleration curve, computation of distance to drive when accelerating before braking, \ldots
+ \item Support sparse representation of driving cycles. Instead of specifying the driving cycle on a per-meter basis only distance entries with speed or slope changes need to be specified. Reduction of 96\,\% in disk space
+ \item Multithreaded execution when multiple driving cycles resp. multiple Vecto jobs are executed
+ \item Vecto 3.0.1 only supports the latest version of the input file formats (JSON), i.e., .vecto: v\,2; .vveh: v\,7; .vgbx: v\,5; .veng: v\,3
+ \item Support for arbitrary order of columns in CSV files if the header is given as specified in the Manual. If the header is not recognized: fall-back to column-based parsing
+ \item more energy-efficient implementation of \textit{Overspeed}: vehicle acceleration only due to road's slope, engine is on drag-curve
+ \item Use of well-known logging framework (NLog) allows to configure logging output based on severity and namespace. Supports different logging targets
+ \item Implemented in C\#, requires .net Framework version 4.5
+ \item Use of latest libraries for logging, parsing JSON files, and processing of PDF files
+ \item Software Tests: 258 successful unit- and integration tests
+ \begin{itemize}
+ \item Code coverage: 84\,\% \\
+ The main parts of the code are covered by tests, the main parts with low coverage are tests of auto-generated equality methods and parsing of input data
\end{itemize}
- }
-\end{frame}
-
-\input{../2_Processor_Examples/content.microcontrollers.tex}
-
-\input{../2_Processor_Examples/content.cpus.tex}
-
-\input{../2_Processor_Examples/content.specialpurpose.tex}
-
-\input{../2_Processor_Examples/content.multicomputer.tex}
-
-\input{../2_Processor_Examples/content.summary.tex}
-
-% % \input{../3_System_Peripheral_Connect/content.tex}
-
-
-%###########################################################################
-%###########################################################################
-%###########################################################################
-
-\mode
-<all>
-\lecture{Part 3: Connecting Peripherals}{lecture_3}
-
-
-\part{Part 3: Connecting Peripherals}
-
-%====================
-
-\begin{frame}[c]\frametitle{Agenda}
- \tskips
- \tableofcontents[subsectionstyle=hide,subsubsectionstyle=hide]
- \note{
- Buses are used to connect peripherals, i.e., often sensors, actuators. \\
- Goals: \begin{itemize}
- \item Get an overview of typically/often used buses
- \item Get an idea how the different buses work
- \item What are (distinct) features of a bus
- \begin{itemize}
- \item throughput, hardware effort, topology (multiple masters, arbitration)
- \end{itemize}
- \item Get an idea about the protocols
- \item Get an idea how buses evolve(d) over time
+ \item Code complexity\footnote{According to \textit{SourceMonitor}}: currently the max. complexity is 20 (single method) and 10 methods have a complexity $>$10. The most complex methods are in the ShiftStrategy, the DriverStrategy, and the Powertrain builder
+\end{itemize}
+
+%=========================================================================
+\subsection{Open Issues} % (fold)
+\label{sub:open_issues}
+%=========================================================================
+
+\begin{itemize}
+ \item Sanity checks on input data
+ \item Refactoring of DefaultDriverStrategy to handle certain situations when braking is required during coasting to meet small target-speed changes during coasting.
+ \item Status output to GUI/Console during simulation
+ \item Advanced Driver Assist Systems
+ \item Adaptation of component models to most recent ACEA Whitebook
+\end{itemize}
+
+% subsection open_issues (end)
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\section{How to Submit a Bug Report} % (fold)
+\label{sec:how_to_submit_a_bug_report}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+In case you encounter a bug or Vecto~3 is not behaving as you would expect it is of utmost importance that the developers can reproduce your results\footnote{\url{http://www.chiark.greenend.org.uk/~sgtatham/bugs.html}}. All bugs should be submitted as Jira Issue (either \textit{Bug} or \textit{Feature}/\textit{Task}) to maintain tracability. \\[0.5em]
+
+Every bug-report should contain a detailed description containing:
+\begin{itemize}
+ \item What did you do
+ \item What is your expected outcome
+ \item What is the actual outcome
+ \item Which Vecto version did you use? (Version number and Build number) \\
+ The version number is printed when you start vectocmd in verbose mode
+ \item Screenshots if necessary
+\end{itemize}
+
+In addition a detailed log of your simulation is necessary. Please follow these instruction to create a log-file and the mod-files:
+
+\begin{itemize}
+ \item \textbf{Start a command-line}\\
+ Press \textit{Windows-r} and type \texttt{cmd}, change to the directory where you extracted Vecto 3.0
+ \item Delete old log-files:\\
+ \texttt{del logs\textbackslash*}
+ \item Start the simulation using Vecto-Commandline: \\
+ \texttt{vectocmd.exe -t -vvvv -mod $<$jobfile.vecto$>$} \\
+ it is important to use the option \texttt{-vvvv} and \texttt{-mod} which enable verbose logging and output of the mod-data file (\texttt{.vmod}. \\[0.5em]
+ If logging is enabled, the simulation runs are executed sequentially. If the error occurs only in some simulation runs (i.e., driving cycle and loading) you can cancel the other simulation runs by pressing \textit{Ctrl-c}. (Note: if verbose logging is enabled the simulation takes much longer)
+ \item File a new Jira issue with a detailed description (see above)
+ \item Attach all data necessary to reproduce your results to the Jira issue, or if the data is confidential you can directly send it to the developers.
+ \begin{itemize}
+ \item All input files
+ \item All Log-files in the directory \texttt{logs} (compressed)
+ \item Mod-files (stored in the directory of the Vecto job)
\end{itemize}
- }
-\end{frame}
-
-
-\input{../3_System_Peripheral_Connect/content_memory.tex}
-
-\input{../3_System_Peripheral_Connect/content_bus-arbitration.tex}
-
-\input{../3_System_Peripheral_Connect/content_bus-pipelining_p4.tex}
-
-\input{../3_System_Peripheral_Connect/content_amba}
-
-\input{../3_System_Peripheral_Connect/content_SPI.tex}
-
-\input{../3_System_Peripheral_Connect/content_I2C.tex}
-
-\input{../3_System_Peripheral_Connect/content_onewire.tex}
-
-\input{../3_System_Peripheral_Connect/content_PCI.tex}
-
-\input{../3_System_Peripheral_Connect/content_USB.tex}
-
-%###########################################################################
-%###########################################################################
-%###########################################################################
-
-\mode
-<all>
-\lecture{Part 4: Computer Networks}{lecture_4}
-
-
-\part{Part 4: Computer Networks}
-
-%====================
-
-\begin{frame}[t]\frametitle{Agenda}
- \tableofcontents[subsubsectionstyle=hide]
-\end{frame}
-%--- Next Frame ---%
-
-\input{../4_Networking/content_motivation.tex}
-
-\input{../4_Networking/content_lan_datalink_layer.tex}
-
-\input{../4_Networking/content_ip_layer.tex}
-
-\input{../4_Networking/content_transport_layer.tex}
-
-\input{../4_Networking/content_physical_layer.tex}
+\end{itemize}
-% \input{../4_Networking/content_application_dns_diagnostics.tex}
+% - use jira
+% - cmdline, ctrl-c
+% - enable verbose logging (Debug)
+% - clean logs
+% - send input data (all), mod-files, logs, exact version number, expected behavior vs. actual output/result
+% section how_to_submit_a_bug_report (end)
-\begin{frame}[t]\frametitle{}
-
-\end{frame}
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\end{document}
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Documentation/ReleaseNotes/content.tex b/Documentation/ReleaseNotes/content.tex
index ac3d60444a..bf21984763 100644
--- a/Documentation/ReleaseNotes/content.tex
+++ b/Documentation/ReleaseNotes/content.tex
@@ -1,42 +1,17 @@
-%!TEX root = lecture.presentation.tex
+%!TEX root = ReleaseNotes.tex
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{document}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\titleframe
+% \titleframe
-%###########################################################################
-%###########################################################################
-%###########################################################################
-
-% \mode
-% <all>
-% \lecture{Preparatory Meeting}{lecture_0}
-
-% \part{Part 0: Preparatory Notes}
-% % \lecture{Part 0: Preparatory Notes}{Part_0}
-
-% \input{../0_Preparatory/content.tex}
-
-%###########################################################################
-%###########################################################################
-%###########################################################################
-
-% \mode
-% <all>
-% \lecture{Lecture 1}{lecture_1}
-
-% \sectionslidenote{
-
-% }
-% % \lecture{Part 1: Recap Microprocessors}{Part_1}
-% \part{Part 1: Microprocessor Fundamentals}
+\maketitle
%====================
-\input{Vecto 3.0.1.312/ReleaseNotes.tex}
+\input{Vecto_3.0.1.312/ReleaseNotes.tex}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\end{document}
diff --git a/Documentation/ReleaseNotes/header.tex b/Documentation/ReleaseNotes/header.tex
index 3ffbf29e76..df063951b9 100644
--- a/Documentation/ReleaseNotes/header.tex
+++ b/Documentation/ReleaseNotes/header.tex
@@ -1,12 +1,12 @@
-%!TEX root = lecture.presentation.tex
+%!TEX root = ReleaseNotes.tex
%%%
%%% Common Settings
%%%
\institute{Institute for Technical Informatics, TU Graz}
-\title{ICT Computer Architectures} % Kurztitel in []
+\title{Vecto 3.x Release Notes} % Kurztitel in []
\author{DI Dr. Markus Quaritsch}
-\date{WS 2015/16} % \today für heutiges Datum verwenden
+\date{\today} % \today für heutiges Datum verwenden
\setcounter{tocdepth}{4}
\usepackage{listings}
@@ -221,11 +221,6 @@
\renewcommand{\arraystretch}{1.17}
\graphicspath{ %
- {../beamer_theme/} %
- {../Everything/img/} %
- {../0_Preparatory/img/} %
- {../1_Microprocessor_Fundamentals/img/} %
- {../2_Processor_Examples/img/} %
- {../3_System_Peripheral_Connect/img/} %
- {../4_Networking/img/} %
+ {beamer_theme/} %
+ {img/} %
}
diff --git a/Documentation/ReleaseNotes/preamble_handout.tex b/Documentation/ReleaseNotes/preamble_handout.tex
index b5d5f19d62..ef5154f643 100644
--- a/Documentation/ReleaseNotes/preamble_handout.tex
+++ b/Documentation/ReleaseNotes/preamble_handout.tex
@@ -1,21 +1,49 @@
% \pdfminorversion=5
% \pdfminorversion=4
\pdfobjcompresslevel=1
-\documentclass[14pt,handout]{beamer}
+% \documentclass[14pt,handout]{beamer}
+\documentclass[11pt,a4paper]{scrartcl}
% \documentclass[14pt,aspectratio=169]{beamer}
-\usepackage{../beamer_theme/pgfmorepages}
-% \usetheme[notes]{tugraz2013}
-\usepackage[institute]{../beamer_theme/beamerthemetugraz2013}
+% \usepackage{beamer_theme/pgfmorepages}
+% \usepackage[institute]{beamer_theme/beamerthemetugraz2013}
+\usepackage{graphicx}
\usepackage{bookmark}
-\makeatletter
-\apptocmd{\beamer@@frametitle}{\only<1>{\bookmark[page=\the\c@page,level=5]{#1}}}%
-{\message{** patching of \string\beamer@@frametitle succeeded **}}%
-{\message{** patching of \string\beamer@@frametitle failed **}}%
-\makeatother
+\usepackage{geometry}
+\geometry{verbose,paperwidth=21cm,paperheight=29.7cm}
+ \geometry{tmargin=25mm,bmargin=25mm,lmargin=25mm,rmargin=25mm}
+
+% \makeatletter
+% \apptocmd{\beamer@@frametitle}{\only<1>{\bookmark[page=\the\c@page,level=5]{#1}}}%
+% {\message{** patching of \string\beamer@@frametitle succeeded **}}%
+% {\message{** patching of \string\beamer@@frametitle failed **}}%
+% \makeatother
+
+% \institute{Institute for Technical Informatics, TU Graz}
+\title{Vecto 3.x Release Notes} % Kurztitel in []
+\author{DI Dr. Markus Quaritsch}
+\date{\today} % \today für heutiges Datum verwenden
+
+\usepackage{pdfpages}
+\usepackage{pifont}
+
+\usepackage{array}
+\newcolumntype{L}[1]{>{\raggedright\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
+\newcolumntype{C}[1]{>{\centering\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
+\newcolumntype{R}[1]{>{\raggedleft\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
+\newcolumntype{M}[1]{>{\centering\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
+
+\newlength{\IdColWidth}\setlength{\IdColWidth}{0.1\textwidth}
+\newlength{\ReqColWidth}\setlength{\ReqColWidth}{0.62\textwidth}
+\newlength{\StatusColWidth}\setlength{\StatusColWidth}{0.22\textwidth}
+
+\usepackage{cleveref}
+
+\newcommand{\Vcheck}{\ding{52}}
+\newcommand{\Vtodo}{ToDo}
% \input{lecture_builder.tex}
-\input{header.tex}
+% \input{header.tex}
--
GitLab