calculate correct propulsion power for looking up weighting group

See merge request vecto/vecto!68

Changes to VTP for the 2nd amendment for version 4 (transfer from version 3)

See merge request vecto/vecto!56

Release 2023_08_28-VECTO-4.0.0.3161-RC

See merge request vecto/vecto!67

Amdm2/develop

See merge request vecto/vecto!66

Merge branch 'amdm2/develop' of https://code.europa.eu/vecto/tug-itna/mq_vecto-sim into amdm2/develop

Test all generic vehicles

See merge request vecto/vecto!42

updated generic vehicle testfiles, to pass new checks (duplicate entries in powermaps, efficiency > 1)

Merge branch 'amdm2/develop' of https://code.europa.eu/vecto/tug-itna/mq_vecto-sim into amdm2/develop

adding sanity checks for electric components: efficiency must not be greater...

See merge request vecto/vecto!65

ICE: if stationary full load gets negative (extrapolation) return 0W - too high engine speed is handled by Hybrid strategy or shift strategy later on

EM: GetTorqueForElectricPower: handle the case that the maxdrive torque may be null because the REESS is almost empty

adding sanity checks for electric components: efficiency must not be greater than 1, drag torque must be negative

IEPC: handle the case that power map contains only a single entry with 0 Nm...

See merge request vecto/vecto!64

Amdm2/develop

See merge request vecto/vecto!63

Merge branch 'amdm2/develop' of https://code.europa.eu/vecto/tug-itna/mq_vecto-sim into amdm2/develop

IEPC: handle the case that power map contains only a single entry with 0 Nm when extending the power map

fix HEV CS iterative runs: limit equivalence factor in 2nd run

See merge request vecto/vecto!62

Implement high voltage auxiliaries (Padd_hv) for PEVs and hybrids read from cycle

See merge request vecto/vecto!58

Fix issue 119: replace Jira links in GUI and manual with codeu

See merge request vecto/vecto!57

bugfix: IEPC max outshaft speed is provided in RPM!

See merge request vecto/vecto!60

bugfix: reading the voltage level at the completed stage results in a...

See merge request vecto/vecto!59

bugfix: reading the voltage level at the completed stage results in a null-reference error because the voltage level is not defined. use same wrapper class to use same voltage level data for two voltage levels

calculate ignore reasons: use power demand instead of torque and apply search tolerance

driver strategy: additional condition to switch to braking action in case the next actions braking distance is in the current simulation interval while the current action still demands coasting

extend drag data to higher speed ratios (required for eco-roll preprocessing in case of APTReleaseLockupClutch)

3rd run: in case the deltaSoc is the same for both runs, set equivalence factor to min/max accordingly