Merge pull request #840 in VECTO/vecto-sim from VECTO/mq_vecto-sim:feature/VECTO-1360-make-unit-tests-execute-in-parallel to develop

* commit 'de7acc51':
  adding annotations to allow parallel execution of nunig tests where possible

* commit 'e91b1817':
  adding release report for VECTO 3.3.8.2052
  compile VECTO release 3.3.8.2052
  compiling new VECTO Release: 3.3.8.2024-RC

* commit '6569e1b7':
  adding release report for VECTO 3.3.8.2052
  compile VECTO release 3.3.8.2052

* commit 'f43875d9':
  compiling new VECTO Release: 3.3.8.2024-RC
  slighlty increas tolerance for detecting vehicle stop (<2mm/s)
  driver strategy: handle the case that an underload may happen and the clutch is already re-engaged -> use engaged action
  in case the simulation interval is short (<0.05s) due to other conditions (driving cycle speed change, driving action distance reached, ...) allow extending the traction interruption to avoid high inertia torque and thus extrapolation of loss-maps
  bugfix causes slight change in fuel consumption - adapt testcase
  cause of the error: a short simulation interval occurs because braking to the next but one target speed (stop) starts slightly before the next target speed change. thus the simulation first goes to the distance where braking has to start and then simulates the short distance to the next target speed (as we do not cross target speed changes) solution: allow simulating over a target speed change if the distance to the next target speed change is short and the vehicle is already below the next target speed.
  only avoid short braking intervals if action distance is within current simulation interval
  driver startegy: prolong min. braking intreval to 0.125s, handle AT transmisions as well

Merge pull request #836 in VECTO/vecto-sim from VECTO/mq_vecto-sim:bugfix/VECTO-1327-simulation-abort-construction-refload-unexpected-response-responseoverload to develop

* commit 'dab11726':
  slighlty increas tolerance for detecting vehicle stop (<2mm/s)

Merge pull request #834 in VECTO/vecto-sim from VECTO/mq_vecto-sim:VECTO-1288-simulation-abort-ud-rl to develop

* commit 'f3828927':
  driver strategy: handle the case that an underload may happen and the clutch is already re-engaged -> use engaged action
  in case the simulation interval is short (<0.05s) due to other conditions (driving cycle speed change, driving action distance reached, ...) allow extending the traction interruption to avoid high inertia torque and thus extrapolation of loss-maps

driver strategy: handle the case that an underload may happen and the clutch is already re-engaged -> use engaged action

in case the simulation interval is short (<0.05s) due to other conditions (driving cycle speed change, driving action distance reached, ...) allow extending the traction interruption to avoid high inertia torque and thus extrapolation of loss-maps

Merge pull request #833 in VECTO/vecto-sim from VECTO/mq_vecto-sim:bugfix/VECTO-1280-simulation-abort-ud-refload to develop

* commit '33a8c964':
  bugfix causes slight change in fuel consumption - adapt testcase
  cause of the error: a short simulation interval occurs because braking to the next but one target speed (stop) starts slightly before the next target speed change. thus the simulation first goes to the distance where braking has to start and then simulates the short distance to the next target speed (as we do not cross target speed changes) solution: allow simulating over a target speed change if the distance to the next target speed change is short and the vehicle is already below the next target speed.

cause of the error: a short simulation interval occurs because braking to the next but one target speed (stop) starts slightly before the next target speed change. thus the simulation first goes to the distance where braking has to start and then simulates the short distance to the next target speed (as we do not cross target speed changes)
solution: allow simulating over a target speed change if the distance to the next target speed change is short and the vehicle is already below the next target speed.

Merge pull request #832 in VECTO/vecto-sim from VECTO/mq_vecto-sim:bugfix/VECTO-1266-gear-4-loss-map-was-extrapolated to develop

* commit 'a9e8f12e':
  only avoid short braking intervals if action distance is within current simulation interval
  driver startegy: prolong min. braking intreval to 0.125s, handle AT transmisions as well

* commit '656be7d6':
  Compiling new VECTO Release (3.3.7.1964)
  adapt expected values in testcase
  adapt testcase so that all runs are created
  fix typo

* commit 'f38fda7a':
  Compiling new VECTO Release (3.3.7.1964)
  adapt expected values in testcase
  adapt testcase so that all runs are created
  fix typo

* commit '888d644f':
  update mission profile weighting factors for vehicles of group 16
  adding additional check that the weighting factors of all simulated cycles have to sum up to 1!
  adapting xslt transformation applied before hashing to ignore xsi:type attribute
  adding testcase to show how xsi:type attribute invalidates existing hashes

Merge pull request #828 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-1259-mission-profile-weightinf-factors-for-vehicles-of-group-16-are-not-correct to develop

* commit 'd8f54cc2':
  update mission profile weighting factors for vehicles of group 16
  adding additional check that the weighting factors of all simulated cycles have to sum up to 1!

Merge pull request #827 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-1254-hashing-method-does-not-ignore-certain-xml-attributes to develop

* commit '4df823f9':
  adapting xslt transformation applied before hashing to ignore xsi:type attribute
  adding testcase to show how xsi:type attribute invalidates existing hashes

* commit '3d3ecdbe':
  creating new official VECTO version
  fix bug in creating new gearbox file for AT-S from scratch. GUI tries to use vehicle category in order to decide whether TC is used in 1st or 1st and 2nd gear. use 'not truck' as default

* commit 'f6554888':
  creating new official VECTO version

Merge pull request #824 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:ReleaseCandidates/v3.3.6.1898 to master

* commit '9f55d21e':
  fix bug in creating new gearbox file for AT-S from scratch. GUI tries to use vehicle category in order to decide whether TC is used in 1st or 1st and 2nd gear. use 'not truck' as default

Merge pull request #823 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-1250-error-creating-new-gearbox-file-from-scratch to ReleaseCandidates/v3.3.6.1898

* commit 'd62839da':
  fix bug in creating new gearbox file for AT-S from scratch. GUI tries to use vehicle category in order to decide whether TC is used in 1st or 1st and 2nd gear. use 'not truck' as default

fix bug in creating new gearbox file for AT-S from scratch. GUI tries to use vehicle category in order to decide whether TC is used in 1st or 1st and 2nd gear. use 'not truck' as default

* commit '7fb76516':
  compiling release, adding release report and results
  updating version number, adding release notes
  adapt equality method for pto activation
  fix: activate only pto mode 3 at drive-off
  fix testcase: set simulation type so that distance is reported via databus
  fix: activate only pto mode 3 at drive-off
  fix some testcases

* commit '727d93ad': (42 commits)
  compiling release, adding release report and results
  updating version number, adding release notes
  adapt equality method for pto activation
  fix: activate only pto mode 3 at drive-off
  fix testcase: set simulation type so that distance is reported via databus
  fix: activate only pto mode 3 at drive-off
  fix some testcases
  Updating user manual for PTO activations mode 2 and 3
  fix: 'reverse apply' fuel correction factor in vtp evaluation
  adding testcase illustrating vtp bug: vtp factor for same vehicle is different although the same model data is used (only the fuel type was changed to CNG)
  adding testcase: CNG vehicle vtp
  allow pto activity already at drive-off, interpolate pto power between entries in cycle
  torque converter: use same engine speed during dryrun in case no operating point can be found.
  update mission profile weights in declaration data
  extending testcases to lookup weighting class for vehicle groups 1, 2, 3, 11, 12, 16
  putting mission profiles in typical order: LH, RD, D, MU, CO; LL/RL
  adapt testcase to new expected values for mission profile weighting
  udating project file
  fix: writing pto consumer only if not already set by idel controller
  moving things around in gui
  ...