fix #422: one DCDCConverter in powertrain

See merge request vecto/vecto!171

Problem: Some powertrains had 2 DCDCConverters in them, by mistake,
when only 1 is necessary/appropriate.

Solution: use 1 DCDCConverter in a particular powertrain.

disable recuperation of EM only in case the driver wants to brake (i.e., allow...

See merge request vecto!159

Add brake action when all braking action has not succeeded

See merge request vecto/vecto!170

fix #427: correct calculation of vehicle max speed

See merge request vecto!168

fix #428: Remove speed safety margin for gearbox re-engaging

See merge request vecto/vecto!169

For the calculation of MaxVehicleSpeed, the N95 speed of the engine is
used. In some edge cases though, the speed of the vehicle may result to
exceeding the max speed of the last gear (i.e. manifested at coach
cycle on overspeed at about 102km/h). Therefore we need to use the
minimum of N95 and maxGBspeed @ last gear.

fix localization issue in battery standard values correction

See merge request vecto/vecto!164

allow 0.0 EM continuous torque in VIF

See merge request vecto/vecto!166

correcting MRF schame: make output of NgTankSystem optional for completed bus...

See merge request doumpst/vecto!1

improve searching mechanic power for a given electric power: in case the max. propulsion power is 0, the initial search interval is also 0. this leads to the same point in the map and no interpolation/extrapolation in the search algorithm can be done.
in case the max torque is 0, set the initial search interval to a small value for now.

correcting MRF schame: make output of NgTankSystem optional for completed bus (conventional and HEV)

fix(partial) #394: handled 2 null references

See merge request vecto!165

fix #289: corrected errors in VIF files

See merge request vecto!161

Problem 1: VECTO sometimes fails to find the namespace where the type
of the <Tyre><Data> element is defined, in the primary vehicle job file.

Problem 2: VECTO sometimes inserts erroneous prefix in element AirDrag
-Data of final VIF (output of Multistep: primary VIF + Completed).

implement feature to asses whether a simulation abort may be caused due to low motorization (primary bus simulation)

See merge request vecto/vecto!153

Use culture invariant conversion to lower case.

See merge request vecto/vecto!157

Bugfix/code eu 376

See merge request vecto/vecto!160

Adaptation of Bus Curb Mass in Factor Method for low weight buses

See merge request vecto/vecto!151

disable recuperation of EM only in case the driver wants to brake (i.e., allow recuperation in case the driver performs an accelerate action to overcome the drag losses in the EM)

fix #310: improved handling for invalid final VIF

See merge request vecto/vecto!156

Feat #258: VIF validation by hashing tool

See merge request vecto/vecto!154

# Conflicts:
#   VectoCore/VectoCore/OutputData/SumDataFields.cs

Use culture invariant conversion to lower case. Ohterwise 'I' may be converted to 'ı' (missing dot) depending on the culture/language settings (e.g. turkish) and thus several lookups fail. Using culture independent conversion to lower case still gives 'i'.

fix #300: proper calculation of full drive torque

See merge request !152

fix #285: don't write unavailable EM data to vsum

See merge request vecto/vecto!155

only apply mass correction in case a primary vehicle or completed generic (with mission parameters from primary mission) is simulated

adapt testcase to match call in vectorundatafactory: lookup primary segment and completed segment, use according missions in call to create vehicle data

Problem: When loading a completed final VIF where elements are missing.
(in this case HVAC) a null reference exception occurs.

Solution: added null reference checks.