Pull request #172: Feature/VECTO-1560 update toolchain for generating usermanual

Merge in VECTO/vecto-dev from VECTO/mq_vecto-dev:feature/VECTO-1560-update-toolchain-for-generating-usermanual to develop

* commit '099a8d06':
  upload compiled help
  update readme
  update javascript for HTML5 elements
  update convert script for new pandoc version
  update markdown files to have space after headings-marker

Documentation/User Manual/1-user-interface/0_start.md

@@ -10,7 +10,7 @@ Software Requirements
 
    + Microsoft .NET Framework 4.5
 
-##Installation Options
+## Installation Options
 
 VECTO is distributed as a portable application. This means you can simply unzip the archive and directly start VECTO.exe. This, however, requires write and execute permissions for the VECTO application directory.
 

Documentation/User Manual/1-user-interface/B_mainform.md

-##Main Form
+## Main Form
 
 
 
 ![](pics/mainform.svg)
 
 
-###Description
+### Description
 
 
 The Main Form is loaded when starting VECTO. Closing this form will close VECTO even if other dialogs are still open. In this form all global settings can be controlled and all other application dialogs can be opened.
@@ -18,10 +18,10 @@ The Main Form includes two tabs as described below:
 * Options Tab
 
 
-###Job Files Tab
+### Job Files Tab
 
 
-####Job Files List#
+#### Job Files List#
 
 Job files (.vecto) listed here will be used for calculation. Unchecked files will be ignored!
 Doubleclick entries to edit job files with the [VECTO Editor](#job-editor).
@@ -35,7 +35,7 @@ Doubleclick entries to edit job files with the [VECTO Editor](#job-editor).
 
 ![up](pics/Actions-arrow-up-icon.png)![down](pics/Actions-arrow-down-icon.png) ***Move selected files up or down in list***
 
-#####List Options#
+##### List Options#
 
 - **Save/Load List**
     - Save or load Job List to text file
@@ -50,13 +50,13 @@ Doubleclick entries to edit job files with the [VECTO Editor](#job-editor).
 
 
 
-####![START](pics/Play-icon.png) ***START Button***
+#### ![START](pics/Play-icon.png) ***START Button***
 
 Start VECTO in the selected mode (see [Options](#options-tab)).
 
 
 
-###Options Tab
+### Options Tab
 
 ![](pics/VECTO_OptionsTab.png)
 
@@ -89,7 +89,7 @@ Output values in vmod at beginning and end of simulation iterval
 ![Regular VECTO .vmod output (top) vs. beginning and end of simulation interval (bottom)](pics/VECTO_vmod_vgl.png)
 
 
-###Controls
+### Controls
 
 ![new](pics/blue-document-icon.png) New Job File
 : Create a new .vecto file using the [VECTO Editor](#job-editor)

Documentation/User Manual/1-user-interface/C_settings.md

-##Settings
+## Settings
 
 
 ![](pics/Settings.PNG)
 
 
-###Description
+### Description
 
 In the Settings dialog controls general application settings. The settings are saved in the [settings.json](#application-files) file.
 
-###Interface Settings
+### Interface Settings
 
 File Open Command
 :	This command will be used to open CSV Input Files like Driving Cycles (.vdri). See: [Run command![](pics/external-icon%2012x12.png)](http://en.wikipedia.org/wiki/Run_command)\
@@ -18,7 +18,7 @@ File Open Command
 :	***Example*** *: If the command is* ***excel*** *and the file is* ***C:\\VECTO\\cycle1.vdri*** *then VECTO will run:* ***excel "C:\\VECTO\\cycle1.vdri"***
 
 
-###Calculation Settings
+### Calculation Settings
 
 <div class="engineering">
 Air Density \[kg/m³\]
@@ -27,7 +27,7 @@ Air Density \[kg/m³\]
 This  setting is only used in Engineering mode. In Declaration mode the default value of 1.188 \[kg/m³\] is used.
 </div>
 
-###Controls
+### Controls
 
 
 Reset All Settings

Documentation/User Manual/1-user-interface/D1_VECTO-Job-Editor.md

-##Job Editor
+## Job Editor
 
 
 ![](pics/VECTO_JobEditor_ParHyb_General.png)
 
 
-###Description
+### Description
 
 The [job file (.vecto)](#job-file) includes all informations to run a VECTO calculation. It defines the vehicle and the driving cycle(s) to be used for calculation. In summary it defines:
 
@@ -17,14 +17,14 @@ The [job file (.vecto)](#job-file) includes all informations to run a VECTO calc
 -   Driving Cycles (only in Engineering Mode)
 
 
-###Relative File Paths
+### Relative File Paths
 
 It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. Example: "Vehicles\\Vehicle1.vveh" points to the "Vehicles" subdirectory of the Job File's directoy.
 
 VECTO automatically uses relative paths if the input file (e.g. Vehicle File) is in the same directory as the Job File. (*Note:* The Job File must be saved before browsing for input files.)
 
 
-###General Settings
+### General Settings
 
 ![](pics/checkbox.png) Engine Only Mode
 
@@ -49,7 +49,7 @@ Filepath ot the Hybrid Strategy Parameters File(.vhctl)
 :	Files can be created and edited using the [Hybrid Strategy Parameters Editor](#hybrid-strategy-parameters-editor).
 
 
-###Auxiliaries Tab
+### Auxiliaries Tab
 
 ![](pics/VECTO_JobEditor_ParHyb_Aux.png)
 
@@ -76,7 +76,7 @@ The third option is to use the bus-auxiliaries model. For details see the [Bus A
 See [Auxiliaries](#auxiliaries) for details.
 
 
-###Cycles Tab
+### Cycles Tab
 
 ![](pics/VECTO_JobEditor_Cycles.png)
 
@@ -98,7 +98,7 @@ In Engineering Mode the cycles can be freely selected. All declaration cycles ar
 : ![remcycle](pics/minus-circle-icon.png) Remove the selected cycle from the list
 
 
-###Driver Assist Tab
+### Driver Assist Tab
 
 ![](pics/JobForm_DriverModel.png)
 
@@ -115,7 +115,7 @@ Acceleration Limiting
 :	See [Acceleration Limiting](#driver-acceleration-limiting) for details.
 
 
-###ADAS Parameters
+### ADAS Parameters
 
 ![](pics/JobForm_ADASParams.png)
 
@@ -123,11 +123,11 @@ In this tab certain general parameters for the advanced driver assistant system
 
 For details on the individual parameters see the corresponding section [Engine Stop/Start](#advanced-driver-assistant-systems-engine-stopstart), [Eco-Roll](#advanced-driver-assistant-systems-eco-roll), [Predictive Cruise Control](#advanced-driver-assistant-systems-predictive-cruise-control)
 
-###Chart Area
+### Chart Area
 
 The chart area on the right shows the main vehicle parameters like HDV group and axle configuration if a valid [Vehicle File](#vehicle-editor-general-tab), [Engine File](#engine-file-.veng) and [Gearbox File](#gearbox-file-.vgbx) is loaded into the Editor. The plot shows the full load curve(s) and sampling points of the fuel consumption map. 
 
-###Controls
+### Controls
 
 ![new](pics/blue-document-icon.png) New Job File
 :	Create a new empty .vecto file

Documentation/User Manual/1-user-interface/D2_VTP-Job-Editor.md

-##VTP-Job Editor
+## VTP-Job Editor
 
 
 ![](pics/VTP-Job.png)
 
 
-###Description
+### Description
 
 A VTP-Job is intended to verify the declared data of a vehicle through an on-road test. VTP-Jobs can be either simulated in engineering mode or declaration mode. For a VTP simulation the measured driving cycle along with the VECTO job-file is required. The driving cycle has to contain the vehicle's velocity, rotational speed of the driven wheels, torque of the driven wheels, and fuel consumption in a temporal resolution of 2Hz.
 
@@ -27,7 +27,7 @@ In declaration mode only the first given driving cycle is simulated as the resul
 In declaration mode the manufacturer's record file needs to be provided. Furthermore, declaration mode simulations consider correction factors for the net calorific value of the used fuel and the vehicle's mileage. In engineering mode the according input fields are not shown.
 </div>
 
-###Relative File Paths
+### Relative File Paths
 
 It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. Example: "Vehicles\\Vehicle1.xml" points to the "Vehicles" subdirectory of the Job File's directoy.
 
@@ -45,11 +45,11 @@ Cycles
 
 
 
-###Chart Area
+### Chart Area
 
 The chart area on the right shows the main vehicle parameters like HDV group and axle configuration if a valid Vehicle File is loaded into the Editor. The plot shows the full load curve(s) and sampling points of the fuel consumption map. 
 
-###Controls
+### Controls
 
 ![new](pics/blue-document-icon.png) New Job File
 :	Create a new empty .vecto file

Documentation/User Manual/1-user-interface/E_VECTO-Editor_Aux.md

-##Auxiliary Dialog
+## Auxiliary Dialog
 
 
 <div class="declaration">
 ![Auxiliary Dialog (Declaration Mode)](pics/VECTO-Editor_Aux_DECL.jpg)
 
-###Description
+### Description
 
 
 The Auxiliary Dialog is used to configure auxiliaries. In [Declaration Mode](#declaration-mode) the set of auxiliaries and their power demand is pre-defined. For every auxiliary the user has to select the technology from a given list. 
 
-###Settings
+### Settings
 
 Technology
 :   List of available technology for the auxiliary type
 For the  steering pump multiple technologies can be defined, one for each steered axle.
 
-###Controls
+### Controls
 
 ![ok](pics/OK.png) ***Save and close***
 
@@ -28,7 +28,7 @@ In Engineering Mode the auxiliary power demand can either be specified in the dr
 </div>
 
 
-##BusAuxiliary Dialog
+## BusAuxiliary Dialog
 
 <div class="engineering">
 
@@ -36,7 +36,7 @@ In Engineering Mode the auxiliary power demand can either be specified in the dr
 
 In Engineering Mode the electrical and mechanical power demand for the electric system, the pneumatic system and the HVAC can be provided.
 
-####Electric System
+#### Electric System
 
 Current Demand Engine On
 :   Demand of the electric system when the ICE is on. The current is multiplied with the nominal voltage of 28.3V.
@@ -65,7 +65,7 @@ Electric Storage Efficiency
 ESS supply from HEV REESS
 :   If selected, the low-voltage electric auxiliaries can be supplied from the high voltage REESS via the DC/DC converter. Needs to be selected in case "no alternator" is chosen as alternator technology. In case of a smart alternator, the low-voltage battery is used first and if empty the energy is drawn from the high voltage system.
 
-####Pneumatic System
+#### Pneumatic System
 
 Compressor Map
 :   [Compressor map file](#advanced-compressor-map-.acmp) defining the mechanical power demand and the air flow depending on the compressor speed.
@@ -79,7 +79,7 @@ Compressor Ratio
 Smart Air Compressor
 :    If enabled, the air compressor may generate excessive air during braking events. The air consumed and generated are [corrected in post processing](#engine-fuel-consumption-correction).
 
-####HVAC System
+#### HVAC System
 
 Mechanical Power Demand
 :   Power demand of the HVAC system directly applied at the crank shaft

Documentation/User Manual/1-user-interface/F_VEH-Editor.md

-##Vehicle Editor -- General Tab
+## Vehicle Editor -- General Tab
 
 ![](pics/VEH-Editor.PNG)
 
-###Description
+### Description
 
 The [Vehicle File (.vveh)](#vehicle-file-.vveh) defines the main vehicle/chassis parameters like axles including [RRC](#vehicle-rolling-resistance-coefficient)s, air resistance and masses.
 
 The Vehicle Editor contains up to 6 tabs, depending on the powertrain architecture and simulation mode, to edit all vehicle-related parameters. The 'General' tab allows to input mass, loading, air resistance, vehicle axles, etc. The 'Powertrain' tab allows to define the retarder, an optional angle drive. The third tab is dedicated to all electric components in case of hybrid electric and battery electric vehicles. In the fourth tab the torque limitations for the combustion engine, the electric motor and the whole vehicle can be specified. The fifth tab allows to enable or disable certain advanced driver assistant systems to be considered in the vehicle. The last tab is dedicated to PTOs, either as a basic component or to simulate municipal vehicles such as refuse trucks or road sweepers with dedicated PTO activation either during driving or during standstill. 
 
-###Relative File Paths
+### Relative File Paths
 
 It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths.
 Example: "Demo\\RT1.vrlm" points to the "Demo" subdirectory of the Vehicle File's directoy.
 
 VECTO automatically uses relative paths if the input file (e.g. Retarder Losses File) is in the same directory as the Vehicle File. (*Note:* The Vehicle File must be saved before browsing for input files.)
 
-###General vehicle parameters
+### General vehicle parameters
 
 Vehicle Category
 : Needed for [Declaration Mode](#declaration-mode) to identify the HDV Group.
@@ -29,7 +29,7 @@ Technically Permissible Maximum Laden Mass [t] (TPMLM)
 HDV Group
 : Displays the automatically selected HDV Group depending on the settings above.
 
-###Masses/Loading
+### Masses/Loading
 
 Corrected Actual Curb Mass Vehicle
 : Specifies the vehicle's mass without loading
@@ -50,7 +50,7 @@ Loading
 In Declaration Mode only the vehicle itself needs to be specified. Depending on the vehicle category and mission the simulation adds a standard trailer for certain missions.
 </div>
 
-###Air Resistance and Corss Wind Correction Options
+### Air Resistance and Corss Wind Correction Options
 
 The product of Drag Coefficient [-] and Cross Sectional Area [m²] (**c~d~ x A**) and **Air Density** [kg/m³] (see [Settings](#settings)) together with the vehicle speed defines the Air Resistance. Vecto uses the combined value **c~d x A** as input. 
 **Note that the Air Drag depends on the chosen [**Cross Wind Correction**](#vehicle-cross-wind-correction).**
@@ -71,12 +71,12 @@ In delcaration mode the 'Speed dependent (Declaration Mode)' cross-wind correcti
 
 Depending on the chosen mode either a [Speed Dependent Cross Wind Correction Input File (.vcdv)](#speed-dependent-cross-wind-correction-input-file-.vcdv) or a [Vair & Beta Cross Wind Correction Input File (.vcdb)](#speed-dependent-cross-wind-correction-input-file-.vcdv) must be defined. For details see [Cross Wind Correction](#vehicle-cross-wind-correction).
 
-###Dynamic Tyre Radius
+### Dynamic Tyre Radius
 
 In [Engineering Mode](#engineering-mode) this defines the effective (dynamic) wheel radius (in [mm]) used to calculate engine speed. In [Declaration Mode](#declaration-mode) the radius calculated automatically using tyres of the powered axle.
 
 
-###Axles/Wheels
+### Axles/Wheels
 
 For each axle the parameters **Relative axle load, RRC~ISO~** and **F~zISO~** have to be given in order to calculate the total [Rolling Resistance Coefficient](#vehicle-rolling-resistance-coefficient).
 
@@ -98,7 +98,7 @@ Doubleclick entries to edit existing axle configurations.
 
 
 
-###Controls
+### Controls
 
 
 ![](pics/blue-document-icon.png) New file
@@ -121,15 +121,15 @@ Doubleclick entries to edit existing axle configurations.
 
 
 
-##Vehicle Editor -- Powertrain Tab
+## Vehicle Editor -- Powertrain Tab
 
 ![](pics/VehicleForm_Powertrain.png)
 
-###Vehicle Idling Speed
+### Vehicle Idling Speed
 
 The idling speed of the combustion engine can be increased in the vehicle settings. This may be necessary due to certain auxiliaries or for other technical reasons. This value is only considered if it is higher than the idling speed defined in the combustion engine.
 
-###Retarder Losses
+### Retarder Losses
 
 If a separate retarder is used in the vehicle a **Retarder Torque Loss Map** can be defined here to consider idling losses caused by the retarder.
 
@@ -143,7 +143,7 @@ Both, primary and secondary retarders, require an [Retarder Torque Loss Input Fi
 
 The Retarder Ratio defines the ratio between the engine speed/cardan shaft speed and the retarder.
 
-###Angledrive
+### Angledrive
 
 If an angledrive is used in the vehicle, it can be defined here.
 Three options are available:
@@ -154,7 +154,7 @@ Three options are available:
 
 
 
-##Vehicle Editor -- Electric Components Tab
+## Vehicle Editor -- Electric Components Tab
 
 ![](pics/VECTO_VehicleEditor_ParHyb_El.png)
 
@@ -182,7 +182,7 @@ In the REESS Dialog the battery file itself and how it is connected to the elect
 ![](pics/BatteryPackDialog.png)
 
 
-##Vehicle Editor -- Torque Limits Tab
+## Vehicle Editor -- Torque Limits Tab
 
 ![](pics/VehicleForm_TorqueLimits.png)
 
@@ -195,7 +195,7 @@ Next, the maximum available torque for the electric machine can be reduced at th
 
 Last, the overall propulsion of the vehicle (i.e., HEV Px, electric motor plus combustion engine) can be limited. The "Propulsion Torque Limit" curve limits the maximum effective torque at the gearbox input shaft over the input speed. This curve is added to the combustion engine's maximum torque curve (only positive values are allowed!). For details on the file format see [Vehicle Boosting Limits](#vehcle-boosing-limits-.vemp). The propulsion torque limit has to be provided from 0 rpm to the maximum speed of the combustion engine. In case of P3 or P4 configuration, the torque at the gearbox input shaft is calculated assuming that the electric motor does not contribute to propelling the vehicle, considering the increased losses in the transmission components inbetween. For P2.5 powertrain configurations no special calculations are necessary as this architecture is internally anyhow modelled as P2 architecture.
 
-##Vehicle Editor -- ADAS Tab
+## Vehicle Editor -- ADAS Tab
 
 ![](pics/VehicleForm_ADAS.png)
 
@@ -217,11 +217,11 @@ The following table describes which ADAS technology can be used and is supported
 * Inputs for EcoRoll possible in GUI, but no effect in simulation
 
 
-##Vehicle Editor -- PTO Tab
+## Vehicle Editor -- PTO Tab
 
 ![](pics/Vehicleform_PTO.png)
 
-###PTO Transmission
+### PTO Transmission
 
 If the vehicle has an PTO consumer, a pto transmission and consumer can be defined here. (Only in [Engineering Mode](#engineering-mode))
 
@@ -235,12 +235,12 @@ Three settings can be set:
 In engineering mode additional PTO activations are available to simulate different types of municipal vehicles. It is possible to add a certain PTO load during driving while the engine speed and gear is fixed (to simulate for example roadsweepers), or to add PTO activation while driving (to simulate side loader refuse trucks for example). In both cases the PTO activation is indicated in the [driving cycle](#driving-cycles-.vdri) (column "PTO").
 
 
-###Roadsweeper operation
+### Roadsweeper operation
 
 PTO activation mode 2 simulates PTO activation while driving at a fixed engine speed and gear. The minimum engine speed and working gear is entered in the PTO tab. For details see [PTO](#pto).
 
 
-###Sideloader operation
+### Sideloader operation
 
 PTO activation mode 3 simulates a time-based PTO activation while driving. Therefore, a separate PTO cycle ([.vptor]()) containing the PTO power over time has to be provided. The start of PTO activation is indicated with a '3' in the 'PTO' column of the [driving cycle](#driving-cycles-.vdri). For details see [PTO](#pto).
 

Documentation/User Manual/1-user-interface/G_ENG-Editor.md

-##Engine Editor
+## Engine Editor
 
 ![](pics/EngineForm.png)
 
-###Description
+### Description
 
 The [Engine File (.veng)](#engine-file-.veng) defines all engine-related parameters and input files like Fuel Consumption Map and Full Load Curve.
 
-###Relative File Paths
+### Relative File Paths
 
 It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths.
 Example: "Demo\\FLD1.vfld" points to the "Demo" subdirectory of the Engine File's directory.
 
 VECTO automatically uses relative paths if the input file (e.g. FC Map) is in the same directory as the Engine File. *Note:* The Engine File must be saved before browsing for input files.)
 
-###Main Engine Parameters
+### Main Engine Parameters
 
 Make and Model \[text]\
 :   Free text defining the engine model, type, etc.
@@ -39,7 +39,7 @@ Max Torque \[rpm\]
 Dual Fuel
 : If enabled, a secondary fuel can be specified. 
 
-###Primary/Secondary Fuel
+### Primary/Secondary Fuel
 
 Fuel Type
 :   Used to compute derived results such as fuel consumption in liters and CO2 values. This parameter influences the CO2-to-fuel ratio and fuel density. The actual values can be looked up in [FuelTypes.csv](../Declaration/FuelTypes.csv).
@@ -64,11 +64,11 @@ The Cold/Hot Emission Balancing Factor is an additional correction factor that i
 In engineering a single correction factor for correcting WHTC, Cold/Hot Balancing, ... can be specified. 
 </div>
 
-###Dual Fuel Engines
+### Dual Fuel Engines
 
 If the engine is operated in dual-fuel mode, enabling the checkbox "Dual Fuel Engine" shows an additional tab for providing the fuel type, fuel consumption map, and fuelconsumption correction factors for the second fuel. For dual-fuel engines the result files (.vmod, .vsum, XML reports) contain the fuel consumption for each fuel separately and the total CO2 emissions.
 
-###Waste Heat Recovery
+### Waste Heat Recovery
 
 ![](pics/EngineForm_WHR.png)
 
@@ -81,12 +81,12 @@ For WHR systems with mechanical power output to the drivetrain the generated mec
 The final fuel consumption is at the end corrected for the electric and mechanical energy generated by the WHR system (see [fuel consumption correction](#engine-fuel-consumption-correction))
 Similar correction factors as applied for the fuel consumption (WHR Correction factors) have to be provided for the WHR system. The weighting of these correction factors is the same as for the WHTC correction factors.
 
-###Chart Area
+### Chart Area
 
 
 The Chart Area shows the fuel consumption map and the selected full load curve. The fuel consumption map of the primary fuel is plotted in red and if provided the secondary fuel is plotted in green.
 
-###Controls
+### Controls
 
 
 ![new](pics/blue-document-icon.png)New file

Documentation/User Manual/1-user-interface/H1_HybridStrategyParams-Editor.md

-##Hybrid Strategy Parameters Editor
+## Hybrid Strategy Parameters Editor
 
 
 ![](pics/HybridStrategyParams.png)
 
-###Description
+### Description
 
 
 The [Hybrid Strategy Parameters File (.vhctl)](#hybrid-strategy-parameters-file-.vhctl) defines all parameters used by the [Hybrid Control Strategy](#hybrid-control-strategy) to evaluate the best option for splitting the demanded torque between electric motor and combustion engine.
 
-###Strategy Parameters
+### Strategy Parameters
 
 The hybrid control strategy evaluates different allocations of torque to the electric motor and different gears and calculates the following cost function:
 

Documentation/User Manual/1-user-interface/H_GBX-Editor.md

-##Gearbox Editor
+## Gearbox Editor
 
 ![](pics/GearboxForm.png)
 
-###Description
+### Description
 
 The [Gearbox File (.vgbx)](#gearbox-file-.vgbx) defines all gearbox-related input parameters like gear ratios and transmission loss maps. 
 Furthermore, certain parameters for the gearshift strategy such as the gearshift lines can be provided (see [Gear Shift Model](#gear-shift-model) for details).
 
 
-###Relative File Paths
+### Relative File Paths
 
 It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. \
 Example: "Gears\\Gear1.vtlm" points to the "Gears" subdirectory of the Gearbox File's directoy.
@@ -16,7 +16,7 @@ Example: "Gears\\Gear1.vtlm" points to the "Gears" subdirectory of the Gearbox F
 VECTO automatically uses relative paths if the input file (e.g. Shift Polygons File) is in the same directory as the Gearbox File. (The Gearbox File must be saved before browsing for input files.)
 
 
-###Main Gearbox Parameters
+### Main Gearbox Parameters
 
 Make and Model
 :   Free text defining the gearbox model, type, etc.
@@ -40,7 +40,7 @@ Traction Interruption \[s\]
 :   Interruption during gear shift event. (Engineering mode only)
 
 
-###Gears
+### Gears
 
 Use the ![add](pics/plus-circle-icon.png) and ![remove](pics/minus-circle-icon.png) buttons to add or remove gears from the vehicle. Doubleclick entries to edit existing gears.
 
@@ -51,7 +51,7 @@ Use the ![add](pics/plus-circle-icon.png) and ![remove](pics/minus-circle-icon.p
 -	 **"Max Torque"** defines the maximum allowed torque (if applicable) for a gear. It is used for limiting the engine's torque in certain gears. Note: in Declaration mode the [generic shift polygons](#gear-shift-model) are computed from the engine's full-load curve. If the maximum torque is limited by the gearbox, the minimum of the gearbox and engine maximum torque will be used to compute the [generic shift polygons](#gear-shift-model)!
 
 
-###Gear shift strategy parameters
+### Gear shift strategy parameters
 
 ![](pics/Vecto_ShiftStrategyParameters.svg)
 
@@ -84,7 +84,7 @@ Automatic Transmission (APT-N) - Pure Electric vehicle
 
 <div class="engineering">
 
-####Gearshift Parameters
+#### Gearshift Parameters
 
 Torque reserve
 :   The minimal torque reserve which has to be provided after a gearshift. Only used for MT transmissions.
@@ -92,14 +92,14 @@ Torque reserve
 Minimum time between gearshifts
 :   Defines the time interval between two consecutive gearshifts. Has to be greater than 0. This time interval is ignored if the engine speed gets too high or too low.
 
-####Shift Strategy Parameters
+#### Shift Strategy Parameters
 
 The user interface contains input fields for the following parameters:
 : - **Downshift after upshift delay**: to prevent frequent (oscilating) up-/down shifts this parameter blocks downshifts for a certain period after an upshift
 - **Upshift after downshift delay**: to prevent frequent (oscilating) up-/down shifts this parameter blocks upshifts for a certain period after a downshift
 - **Min acceleration after upshift**: after an upshift the vehicle must be able to accelerate with at least the given acceleration. The achievable acceleration after an upshift is estimated on the current driving condition and powertrain state.
 
-####Start Gear
+#### Start Gear
 
 In order to calculate an appropriate gear for vehicle start (first gear after vehicle standstill) a fictional load case is calculated using a specified **reference vehicle speed** and **reference acceleration** together with the actual road gradient, transmission losses and auxiliary power demand. This way the start gear is independent from the target speed. VECTO uses the highest possible gear which provides the defined **torque reserve**.
 
@@ -112,7 +112,7 @@ Reference acceleration at clutch-in
 
 </div>
 
-###Torque Converter
+### Torque Converter
 
 Torque converter characteristics file
 :   Defines the [Torque converter characteristics file](#torque-converter-characteristics-.vtcc) containing the torque ratio and reference torque over the speed ratio.
@@ -131,7 +131,7 @@ Torque converter shift polygon
 :   Defines the [Shift Polygons InputFile (.vgbs)](#shift-polygons-input-file-.vgbs) separately for the torque converter. For details on shifting from/to the torque converter gear please see [AT Gear Shift Strategy](#shift-strategy-apt-gearshift-rules).
 
 
-###Torque Converter: Minimal acceleration after upshift
+### Torque Converter: Minimal acceleration after upshift
 
 Here the minimal achievable accelerations before upshifts can be defined.
 
@@ -142,17 +142,17 @@ Acc. for C->C \[m/s²\]
 :   The minimal achievable acceleration for shifts from first torque converter gear to second torque converter gear (1C->2C)
 
 
-###Power shift losses
+### Power shift losses
 
 Shift time \[s\]
 :   The shift time for powershift losses.
 
-###Chart Area
+### Chart Area
 
 The Chart Area displays the [Shift Polygons Input File(.vgbs)](#shift-polygons-input-file-.vgbs) as well as the declaration mode shift polygons (dashed lines) for the selected gear together with the engine's full-load curve.
 
 
-###Controls
+### Controls
 
 
 

Documentation/User Manual/1-user-interface/I_Graph.md

-##Graph Window
+## Graph Window
 
 
 ![](pics/Graph.svg)
 
 
-###Description
+### Description
 
 
 The Graph Window allows to visualise [modal results files (.vmod)](#modal-results-.vmod). Multiple windows can be open at the same time to display different files.
@@ -12,7 +12,7 @@ The Graph Window allows to visualise [modal results files (.vmod)](#modal-result
 Note that the graph does **not** update automatically if the results file has changed.
 
 
-###Channels
+### Channels
 
 
 Use the ![add](pics/plus-circle-icon.png) and ![remove](pics/minus-circle-icon.png) buttons to add or remove channels. Doubleclick entries to edit existing channels.
@@ -20,7 +20,7 @@ Use the ![add](pics/plus-circle-icon.png) and ![remove](pics/minus-circle-icon.p
 Each channel can be plotted either on the left or on the right Y Axis. Use the checkbox to disable channels in the graph.
 
 
-###X Axis Controls
+### X Axis Controls
 
 
 The X Axis can either show distance or time.
@@ -38,7 +38,7 @@ Reset button
 :   Move the x axis range left/right.
 
 
-###Controls
+### Controls
 
 ![open](pics/Open-icon.png) ***Open a .vmod file***
 

Documentation/User Manual/1-user-interface/L_ElectricMotor.md

-##Electric Motor Editor
+## Electric Motor Editor
 
 ![](pics/VECTO_ElectricMotor.png)
 
 
-###Description
+### Description
 
 The electric motor file defines all parameters relevant for the electric machine. These are the motor's maximum drive and recuperation torque, the drag torque as well as the electric power map.
 
-###Relative File Paths
+### Relative File Paths
 
 It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. 
 
 VECTO automatically uses relative paths if the input file (e.g. elctric power map) is in the same directory as the Electric Motor File. (The Electric Motor File must be saved before browsing for input files.)
 
 
-###Main Parameters
+### Main Parameters
 
 Make and Model
 :   Free text defining the gearbox model, type, etc.
@@ -54,12 +54,12 @@ Voltage Level Low/High
 
 
 
-###Chart Area
+### Chart Area
 
 The Chart Area displays the electric machine's max. drive curve and max. generation curve (blue), the drag curve (green) and the entries provided in the electric power consumption map (red).
 
 
-###Controls
+### Controls
 
 
 

Documentation/User Manual/1-user-interface/M_BatteryPackEditor.md

 
-##Rechargeable Electric Energy Storage Editor
+## Rechargeable Electric Energy Storage Editor
 
 Two types of rechargeable electric energy storage can be configured in VECTO: either a battery pack or a super capacitor.
 
-###Battery Pack
+### Battery Pack
 
 ![](pics/VECTO_Battery.png)
 
-####Description
+#### Description
 
 The electric energy storage editor allows to edit all model parameters relevant for the electric energy storage.
 
-####Relative File Paths
+#### Relative File Paths
 
 It is recommended to use relative filepaths. This way the Job File and all input files can be moved without having to update the paths. 
 
 VECTO automatically uses relative paths if the input file (e.g. SoC) is in the same directory as the Battery file. (The Battery File must be saved before browsing for input files.)
 
 
-####Main Parameters
+#### Main Parameters
 
 Make and Model
 :   Free text defining the model, type, etc.
@@ -42,16 +42,16 @@ Internal Resistance Curve
 :   Defines the battery's internal resistance depending on its state of charge. The file must cover the SOC range from 0 to 100%! (see [Battery Internal Resistance File (.vbatr)](#battery-internal-resistance-file-.vbatr))
 
 
-####Chart Area
+#### Chart Area
 
 The Chart Area displays the battery's internal voltage (blue) and the internal resistance (red) over its state of charge.
 
 
-###SuperCap
+### SuperCap
 
 ![](pics/VECTO_SuperCap.png)
 
-####Main Parameters
+#### Main Parameters
 
 Make and Model
 :   Free text defining the model, type, etc.
@@ -69,7 +69,7 @@ Internal Resistance
 :   Defines the capacitor's internal resistance 
 
 
-###Controls
+### Controls
 
 
 

Documentation/User Manual/2-calculation-modes/calculation-modes.md

-#Calculation Modes
+# Calculation Modes
 
 VECTO supports different calculation modes for declaring a vehicle, validation of test-results, or experimenting with different parameters and components. These modes are described here.
 

Documentation/User Manual/2-calculation-modes/declaration.md

-##Declaration Mode
+## Declaration Mode
 
 In Declaration Mode many input parameters are predefined for the official certification. They are locked in the user interface and will automatically be set by VECTO during calculation. Calculations will be performed for each mission profile (of the corresponding HDV class) with two different loadings: low loading and reference loading. 
 
 Declaration Mode can be activated in the [Options Tab](#main-form).
 
 
-###Requirements
+### Requirements
 
 -   One or more checked job files in the Job List
 -   The job files don't need to include driving cycles. These are automatically assigned.
 
-###Results
+### Results
 
 -   Modal results (.vmod). One file for each vehicle/cycle/loading combination. Modal results are only written if the modal output is enabled in the 'Options' tab on the [Main Window](#main-form)
 -   Sum results (.vsum). One file for each invocation of VECTO.

Documentation/User Manual/2-calculation-modes/engine-only.md

-##Engine-Only Mode
+## Engine-Only Mode
 
 When this mode is enabled in the Job File then VECTO only calculates the fuel consumption based on a load cycle (engine speed and torque). In the [Job File](#job-file) only the following parameters are needed:
 

Documentation/User Manual/2-calculation-modes/engineering.md

-##Engineering Mode
+## Engineering Mode
 
 The Engineering Mode lets the user define every aspect in the component models of the vehicle and the driving cycle. This is for experimenting and validation purposes.
 
 In this mode the given list of job files is simulated with the respective driving cycles. Each job file defines a separate vehicle.
 
 
-###Requirements
+### Requirements
 
 -   One or more checked job files in the Job List
 -   Each job file must include at least one driving cycle
 
-###Results
+### Results
 
 -   Modal results (.vmod). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the 'Options' tab on the [Main Window](#main-form)
 -   Sum results (.vsum). One file for each invocation of VECTO.
 
 
-###Options
+### Options
 The Driving Cycle determines the simulation method in engineering mode. The option depends directly on the driving cycle input and cannot be set explicitely. For more information about the formats see [Driving Cycles](#driving-cycles-.vdri).
 
 * [Target speed, distance-based](#engineering-mode-target-speed-distance-based-cycle)

Documentation/User Manual/2-calculation-modes/verification-test.md

-##Verification Test Mode
+## Verification Test Mode
 
 The purpose of the verification test is to simulate a vehicle defined in declaration mode on a measured real-driving cycle. This simulation mode uses its own [cycle format](#verification-test-cycle), requiring mainly vehicle speed, wheel speed, wheel torque, engine-fan speed, and engine speed. VECTO then calculates the appropriate gear and simulates the cycle. Auxiliary power is according to the technologies defined in the vehicle. However, the engine fan auxiliary is ignored and the power demand for the engine fan is calcuated based on the engine-fan speed. The power demand for the other auxiliaries depends on the vehicle's actual speed. The fuel consumption is calculated using the engine speed from the driving cycle and the torque demand as given in the cycle, adding the losses of all powertrain components.
 
 <div class="engineering">
-###Requirements
+### Requirements
 
 -   One or more checked job files in the Job List
 -   Each job must include a vehicle in declaration mode (XML)
 -   Each job file must include at least one driving cycle
 
-###Results
+### Results
 
 -   Modal results (.vmod). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the 'Options' tab on the [Main Window](#main-form)
 -   Sum results (.vsum). One file for each invocation of VECTO.
@@ -17,21 +17,21 @@ The purpose of the verification test is to simulate a vehicle defined in declara
 
 
 <div class="declaration">
-###Requirements
+### Requirements
 
 -   One or more checked job files in the Job List
 -   Each job must include a vehicle in declaration mode (XML)
 -   Each job must include the manufacturer report (XML) of the vehicle as generated for the vehicle declaration
 -   Each job file must include exactly one driving cycle (in case multiple driving cycles are provided, only the first cycle is simulated!)
 
-###Results
+### Results
 
 -   VTP Report (.xml). Contains a description of the vehicle and its components, the verification test analysis according to the draft legislation, and a validation of the input data digest values
 -   Modal results (.vmod). One file for each vehicle/cycle combination. Modal results are only written if the modal output is enabled in the 'Options' tab on the [Main Window](#main-form)
 -   Sum results (.vsum). One file for each invocation of VECTO.
 
 
-###Validations
+### Validations
 
 -   Before the simulation of the measured VTP cycle starts, the provided cycle data is passed through some sanity checks:
    * The cycle is provided in 2Hz

Documentation/User Manual/3-simulation-models/ADAS_EcoRoll.md

-##Driver: Overspeed
+## Driver: Overspeed
 
 Overspeed controls the vehicle's behaviour on uneven road sections (slope ≠ 0) and can be configured in the [Job File](#job-file)'s Driver Assist Tab. Overspeed is designed to model an average driver's behaviour without the aid of driver assistance systems. Eco-Roll  represents an optional driver assistance feature. For this reason vehicles without Eco-Roll should always have the Overspeed function enabled.
 
@@ -15,13 +15,13 @@ Parameters in [Job File](#job-file):
 -   **Max. Overspeed \[km/h\]** (relative to target speed)
 
 
-##Advanced Driver Assistant Systems: Engine Stop/Start
+## Advanced Driver Assistant Systems: Engine Stop/Start
 
-###Description
+### Description
 
 If engine stop/start is enabled in the Vehicle, the engine is turned off during vehicle stops to reduce the fuel consumption. During vehicle stops the energy demand for certain auxiliaires and for starting the engine is accumulated. In a post-processing step the final [fuel consumption is corrected](#engine-fuel-consumption-correction) to consider the energy demand for the auxiliaries and engine start.
 
-###Model Parameters
+### Model Parameters
 
    - **Delay engine-off:** if the vehicle stops, the engine is switched off after this timespan
    - **Max engine-off timespan:** if the enine is switched off at a vehicle stand, the engine is turned on again after this timespan. This basically limits the max. time the engine is switched off at a single engine-off event.
@@ -33,7 +33,7 @@ If engine stop/start is enabled in the Vehicle, the engine is turned off during
    - Engine stop/start utility factor: 0.8
 </div>
 
-###Engine Start-Up Energy Demand
+### Engine Start-Up Energy Demand
 
 The energy demand to ramp-up the engine depends on the engine's inertia and the engine's drag torque and is computed according to the following equation:
 
@@ -44,7 +44,7 @@ $E_{ICE,start} = E_{ICE,rampUp} / \eta_{alternator}^2$
 
 $E_{ICE,start}$ is the amount of energy the combustion engine needs to provide to compensate the start up is the ramp-up energy multiplied by the efficiency of the alternator.  $t_{ICE,start}$ is assumed to be 1 second and $\eta_{alternator}$ is 0.7.
 
-###Auxiliaries and Utility Factor
+### Auxiliaries and Utility Factor
 
 During ICE-off phases the ICE is fully shut of in the simulation (.vmod data). However, in reality the ICE is not always switched off due to certain
 boundary conditions (e.g. power demand from an auxiliary, temperature, etc.). This is considered in the [post-processing](#engine-fuel-consumption-correction). 
@@ -70,9 +70,9 @@ In Engineering Mode the energy demand of the auxiliaries can be specified for th
 </div>
 
 
-##Advanced Driver Assistant Systems: Eco-Roll
+## Advanced Driver Assistant Systems: Eco-Roll
 
-###Description
+### Description
 
 Eco-roll is a driver assistant system that automatically decouples the internal combustion engine from the power train during specific downhill driving conditions with low negative slopes. The aim is to save fuel during such phases. VECTO supports eco-roll without engine stop/start and eco-roll with engine stop/start. In the former case, the combustion engine is idling during eco-roll phases while in the latter case the combustion engine is turned off during eco-roll events. For vehicles having eco-roll with engine stop/start the fuel consumption is corrected for the engine stop/start events and the auxiliary power demand during engine-off phases.
 
@@ -96,7 +96,7 @@ can be specified. When the ICE is on, the auxiliary energy demand is directly ap
 </div>
 
 
-###Model Parameters
+### Model Parameters
 
   - **Minimum speed:** minimum vehicle speed to allow eco-roll to be activated
   - **Activation delay:** delay between the point in time when all conditions for an eco-roll event are fulfilled until eco-roll is activated
@@ -109,7 +109,7 @@ can be specified. When the ICE is on, the auxiliary energy demand is directly ap
   - Underspeed threshold: 0 km/h
 </div>
 
-###Eco-Roll Model
+### Eco-Roll Model
 
 **Calulations during simulation**
 
@@ -121,9 +121,9 @@ The following state diagram depicts when eco-roll is activated during the simula
 
 ![](pics/EcoRollActivation.svg)
 
-##Advanced Driver Assistant Systems: Predictive Cruise Control
+## Advanced Driver Assistant Systems: Predictive Cruise Control
 
-###Description
+### Description
 
 Predictive cruise control (PCC): systems which optimise the usage of potential energy during a driving cycle based on an available preview of road gradient data and the use of a GPS system. A PCC system declared in the input to the simulation tool shall have a gradient preview distance longer than 1000 meters and cover all following use cases:
 
@@ -147,7 +147,7 @@ Predictive cruise control is only considered on highway sections of the simulate
 In declaration mode, the whole long-haul cycle is considered as highway. Moreover, the section from 29760m to 96753m of the regional delivery cycle is considered as highway.
 </div>
 
-###Model Parameters
+### Model Parameters
 
    - **Allowed underspeed:** Threshold below the target speed the vehicle's velocity may be reduced to during a PCC event (use-case 1 & 2, $v_{neg}$)
    - **Allowed overspeed:** Threshold above the target speed the vehicle's velocity may reach during a PCC event (use-cae 3)
@@ -165,7 +165,7 @@ In declaration mode, the whole long-haul cycle is considered as highway. Moreove
    - Preview distance use case 2: 1000 m
 </div>
 
-###Predictive Cruise Control Model Use-cases 1 and 2
+### Predictive Cruise Control Model Use-cases 1 and 2
 
 **Pre-Processing**
 
@@ -208,6 +208,6 @@ The following state diagram depicts the activation of a PCC event during the sim
 
 The fuel consumption of vehicles equipped with PCC option 1 & 2 and eco-roll with engine stop/start will be corrected for engine stop/start as described in [engine stop/start correction](#engine-fuel-consumption-correction).
 
-###Predictive Cruise Control Model Use-case 3
+### Predictive Cruise Control Model Use-case 3
 
 To consider predictive cruise control use-case 3, the driver model's allowed overspeed is set to the model parameter *allowed overspeed* in highway sections if the vehicle supports PCC use-case 3.

Documentation/User Manual/3-simulation-models/Auxiliaries.md

-##Auxiliaries
+## Auxiliaries
 
 <div class="declaration">
 In Declaration mode the auxiliaries are pre-defined and the power demand is defined based on the vehicle category and mission. For every type of auxiliary (fan, steering pump, HVAC, electrig system, pneumatic system) the user can select a technology from a given list.