A benefit of having notifyIdle would be that it could also handle the
case of vehicles being delayed on initial insertion. But it is a
complicated thing to do because those vehicles may not have decided yet
on which lane to start so you cannot give the right MoveReminder to them
beforehand. Also
Thanks again jakob, I guess you don't sleep ;)
After sleeping on it I realised I didn't need to kludge the movereminders -
just iterate over the lane movereminders - seems fine.
I just need to cross check the computed emissions are equal across all the
outputs.
Cheers
Div
Original
Thanks for the thoughtful discussion,
- Adding MSMoveReminder::notifyIdle sounds reasonable but l'll have to
discuss this with @behrisch who designed the MoveReminder architecture and
may have further ideas about it.
- I would call the new method MSVehicle::workOnIdleReminders (I analogy to
Oops - thanks, I'll look wider!
Original Message
On 23 Feb 2020, 21:14, Jakob Erdmann wrote:
> The approach sounds reasonable. However, it won't cover all kinds of emission
> outputs:
> https://sumo.dlr.de/docs/Models/Emissions.html#outputs
>
> cheers,
> Jakob
>
> Am So., 23.
The approach sounds reasonable. However, it won't cover all kinds of
emission outputs:
https://sumo.dlr.de/docs/Models/Emissions.html#outputs
cheers,
Jakob
Am So., 23. Feb. 2020 um 20:41 Uhr schrieb The div :
> Hi,
> I'm playing with multiple aspects of vehicle behaviour associated with
>
