|
From: Nagel K. <na...@vs...> - 2014-02-23 12:19:20
|
Dear all, As decided at the last developer meeting, I now changed the default of ActivityDurationInterpretation from minOfDurationAndEndTime to tryEndTimeThenDuration This essentially means that activities should *either have endTime *or duration . In case there are both, it will only look at endTime. (Now the recent change to max_duration is unfortunately a misnomer.) Output plans should only contain one or the other, although this behavior may not be uniformly in the code. --- In terms of simulation results: In general, your results will no longer be exactly the same as before. In terms of congestion patterns or similar, I have never seen differences once simulations are "relaxed". IMPORTANT: This will probably lead to test failures in contrib and playground. I will fix them eventually by forcing the test case to the old behavior, but I would recommend to rather more your test case to the new behavior. You will need to replace test results to achieve this. --- There is a switch to set the old behavior, in the plans section of the config file. If you had that switch previously set, in vspExperimental, it will no longer work there. Move to the plans section, or remove completely if possible. --- The idea is that "duration" is used for things such as dropping other people off, connecting an electric vehicle to a plug, getting oriented at a transit stop, and they are therefore not subject to optimization but just "mechanical" durations. Note, however, that this may not uniformly work since different pieces of matsim make different assumptions about this. Best Kai |