Closed behrisch closed 7 years ago
@namdre changed summary from "crash when using vTypeprobe" to "crash when using vTypeprobe, fcd-output or full-output"
@namdre changed description from:
the crash happens when attempting to retrieve the x,y-position based on the current lane. This should be fairly easy to fix with some ifdefs.
to:
the crash happens when attempting to retrieve the x,y-position based on the current lane. This should be fairly easy to fix with some ifdefs.
Most output tests are currently disabled and should be switched back on once this is fixed
@namdre changed summary from "crash when using vTypeprobe, fcd-output or full-output" to "crash when using vTypeprobe, fcd-output, full-output or emission-output"
@namdre committed 256c1d4 (aka r17378): disabling some meso tests because cause debugger-pop-ups under windows. refs #1505
@behrisch committed 8be626d (aka r17390): additional meso outputs, refs #21, #1505
@behrisch committed 8130ff7 (aka r17392): enabling meso outputs, refs #1505
there are still improvements possbile especially when calculating the position (see getPositionOnLane in MEVehicle), furthermore the E2/E3 detectors possibly need some treatment as well
the crash happens when attempting to retrieve the x,y-position based on the current lane. This should be fairly easy to fix with some ifdefs.
Most output tests are currently disabled and should be switched back on once this is fixed
Migrated from http://sumo.dlr.de/ticket/1505