reading config file if VECTO should run in 'installed' mode and change path to %APPDATA% and %LOCALAPPDATA% if so
change all access to config files and use path .combine for creating file and directory paths

Merge pull request #732 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-883-traction-interruption-may-be-too-long to develop

* commit '0b0b06a9':
  adapt testcase: allow few traction interruptions to be longer than specified in model data (i.e. due to gearshift right before a speed change (simulation interval can't be changed))
  allow reduction of traction interruption interval by 10%
  correct testdata
  updated testcases with expected fuel consumption (slight changes due to shorter effective traction interruption)
  allow tolerance of 0.1*tractioninterruption for engaging geear
  adding testcase for traction interruption

adapt testcase: allow few traction interruptions to be longer than specified in model data (i.e. due to gearshift right before a speed change (simulation interval can't be changed))

updated testcases with expected fuel consumption (slight changes due to shorter effective traction interruption)

Merge pull request #731 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-879-simulation-run-aborted-distancerun-got-an-unexpected-response to develop

* commit '7a5641cd':
  default driver strategy: repeat handling of overspeed/gearshift as this may occur in different combinations

default driver strategy: repeat handling of overspeed/gearshift as this may occur in different combinations

Merge pull request #730 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:feature/VECTO-873-add-digest-value-to-sumdata to develop

* commit 'f687d2ad':
  modify writing sum data to contain digest value
  adding testcase for digest value in sum-file

Merge pull request #729 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:feature/VECTO-865-extend-sum-data to develop

* commit '19310bd5':
  updating expected vsum files - new columns
  update testcase due to changed colum indizes
  sum data: for new columns handle case no data for efficiency calculation is available
  add new fields to sum file

Merge pull request #728 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-872-mrf-cif-torque-converter-certification-method-missing to develop

* commit 'f8746a9b':
  set certification number and certification method of torque converter in vectorundata

Merge pull request #727 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:feature/VECTO-864-prevent-vecto-loss-map-extension-to-result-in-negative-torque-loss to develop

* commit 'd31c8aaf':
  removed testcases for VTP cycle validation (no longer used)
  loss-map extension: in case of negative slope for regression line exten loss-map with torque loss of last entry in loss-map
  adding testcase where linear regression leads to negative torque when extrapolating

loss-map extension: in case of negative slope for regression line exten loss-map with torque loss of last entry in loss-map

Merge pull request #726 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:feature/VECTO-847-simulation-abort-due-to-error-in-nlog to develop

* commit '87742470':
  updating used libraries: nlog 4.5.11 nunit 3.11 nunit test adapter 3.12

nlog 4.5.11
nunit 3.11
nunit test adapter 3.12

Merge pull request #725 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:feature/VECTO-768-vtp-mode to develop

* commit '8b821030':
  remove checks in vtp mode

Merge pull request #724 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-789-apt-responseunderload to develop

* commit '19cf6d13':
  adding missing file
  handle null-response also in the case no max-power operating point can be found
  TC: output speed may already be too high so that no drag operating point is found (during acceleration) - use high constant value
  TC: cleaning up code, refactoring, moving some parts to separate method
  TC: in case no solution for an operating point fulfilling a certain power demand is found, and first guess is also not suitable, perform search....
  corrected error in comment
  AT gearbox: correction: requestAfterGearshift most not be set immediately but after shift losses are applied
  TC: in case the operating point for the TC is below idle speed use the same as in case no operating point is found at all
  reset braking power in case of gear switch for AT vehicles
  TC: for drag operating point search decrease engine speed to allow for negative torque (at least not keep high output power)
  Torque converter: use previous engine speed in case no operating point for certain power demand was found (more stable, reduces torque due to engien inertia)
  code formatting
  DriverStrategy BrakingMode CoastingPhase: DoCoast may return null in case a gearshift occurs - re-iterate
  in case no operating point could be found use last engine speed to avoid high inertia losses
  increase returned delta-value due to high tolerance of line search algorithm (may lead to slight over-/underload in non-dry-run request)
  Driver: in case of overload or Underload response and gear changed abort braking action
  fix for testcase: set engine inertia
  AT Gearbox: correctly handle response gearshifts from TC to consider shift losses
  extend message in case of negative brake power
  AT Shift Strategy: add shift losses for estimation of acceleration after gearshift, add engine inertia for consideration of acceleration after gearshift

TC: output speed may already be too high so that no drag operating point is found (during acceleration) - use high constant value

TC: in case no solution for an operating point fulfilling a certain power demand is found, and first guess is also not suitable, perform search....

AT gearbox: correction: requestAfterGearshift most not be set immediately but after shift losses are applied