Code development platform for open source projects from the European Union institutions

Skip to content
Snippets Groups Projects
Select Git revision
  • HEV-timeruns-dev
  • IEPC-experiments
  • XSD-v26-jobs
  • amdm2/develop
  • amdm2/main
  • amdm3/develop
  • amdm3/main
  • aptngearbox-not-auto
  • backup-powertrain-refactor
  • david-xsd
  • issue-493
  • issue-751
  • issue-templates
  • official/develop
  • official/main
  • pdf-reports
  • playground
  • powertrains-multiple-axles
  • prepare-4.3.4
  • stable default
  • Release/4.3.4-DEV
  • Release/4.3.3
  • Release/4.3.2-RC
  • Release/v4.3.0-DEV
  • Release/4.2.7
  • XMLConverterTool/4.2.6.0
  • Release/4.2.6-RC
  • Release/v4.2.5
  • Release/v4.2.3
  • Release/v4.2.2.3539-RC
  • Release/v4.2.1.3469
  • Release/v0.11.2.3456-DEV
  • Release/v4.2.0.3448-RC
  • Release/v4.1.3.3415
  • Release/v4.1.1.3413
  • Release/v4.1.0.3392-RC
  • Release/v4.0.3.3330
  • Release/v4.0.2.3275
  • Release/v4.0.2.3273
  • Release/v0.11.1.3228-DEV
40 results
You can move around the graph by using the arrow keys.
Created with Raphaël 2.2.02Mar129Feb2625242322191817161512111095432129Jan28262521201918141312118717Dec161514111087432130Nov26252417161211better validation error messagesfixed error in validation (validation attributes on interfaces)Merge remote-tracking branch 'vecto/develop' into feature/VECTO-172-suggestion-visible-message-if-torqueerrors and warnings in gui and consoleMerge pull request #124 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:feature/VECTO-107-check-valid-range-of-input-parameters to developMerge branch 'bugfix/VECTO-202-improve-defaultdriverstrategy' into feature/VECTO-107-check-valid-range-of-input-parametersupdate repoadding validation ranges as stated in the current parameter list (xls)Merge pull request #123 in VECTO/vecto-sim from ~EMKRISPMI/vecto-sim:feature/VECTO-200-automatically-detect-execution to developcreated test files for small loss maprenamed tests, removed not needed testupdated engine only tests with variable time stepsupdated cycles due to stricter cycle format checkdisplay detected cycles in output window of GUIupdated licence header to display more informationupdated assembly infos to copyright 2016added console output of detected driving cyclesMerge remote-tracking branch 'vecto/develop' into feature/VECTO-200-automatically-detect-executionadded test cases for automatic cycle detection and readingMerge pull request #122 in VECTO/vecto-sim from ~EMQUARIMA/vecto-sim:bugfix/VECTO-202-improve-defaultdriverstrategy to developMerge branch 'Private/InvestigateLongrunningTests' of git+ssh://129.27.107.191:2211/vecto-sim into bugfix/VECTO-202-improve-defaultdriverstrategyupdate repoinvestigate in ignored testcases, many of them run agein. STATUS: 4 Failed, 1 Inconclusive, 346 Green!removed time-based cycle, replaced by measured speed, pwheel and engine-onlyMerge branch 'develop' of https://webgate.ec.europa.eu/CITnet/stash/scm/~emquarima/vecto-sim into Private/InvestigateLongrunningTestsMerge pull request #121 in VECTO/vecto-sim from ~EMKRISPMI/vecto-sim:feature/VECTO-181-measured-speed-mode to developdriver strategy: if the vehicle already stopped and has to perform a roll action issue a time-interval request so that the gearbox finishes the gearshiftcorrection: if remaining distance is 0, try again with half of the simulation distance (assumption: acceleration is approx. the same as deceleration)fix: compute road gradient if distance is 0 (use entry from cycle)update reference files due to changed column headersfix: check if gearbox has a full-load curvefixed warningdummy retarder has to be before gearboxadded additional tests for measured speed with cross wind correction (front, back, no wind)Merge branch 'Private/InvestigateLongrunningTests' of git+ssh://129.27.107.191:2211/vecto-sim into Private/InvestigateLongrunningTestsif for some reason (e.g., the target velocity changes when already braking) the vehicle is faster than the target speed, allow the current vehicle's speed for roll/coastadded correct factors for FC-WHTC and FC-AUXcuse the same braking safety margin when estimating if the current distance exceeds the next actionfix in driver strategy: if the estimated new simulation interval becomes zero or negative (i.e. the driver has to brake _now_ instead of accelerating) switch to brake-mode and re-start the current simulation interval with the original dscorrected typo in comment

For further information about the platform and support, please see https://code.europa.eu/info/about