> Destination Dispatch [...] are in general worse
I wonder if this is an artifact of how the author used random destinations. I worked in a building that used Destination Dispatch, and the common travel pattern seemed to be:
- Everyone who is not on the ground floor generally want to go to the ground floor.
- People who are on the ground floor generally travel in large groups to the same destination.
This happens because people who worked on the same floor often leave for lunch at the same time, and return at the same time to the same floor. Destination Dispatch helps in this case because it's batching large groups of people with the same destination.
Is it because the criteria is wait time not travel time? Destination dispatch would avoid some extra stops on the trip.
I just visited a new building with destination dispatch, so it seems to be still around.
My EE roommate in college had to build an elevator circuit as a final problem. It was on a bread board and had a bunch of call buttons and had a motor and a clear disk with black squares so it could figure out where it was…. I think it was the simple algorithm…
It very well could be the case that people get more upset about waiting for the car than total travel time when they are already in the car. Ie, pick them up sooner even if travel time is longer. In fact, I would bet that this is the case.
Having chatted with friends who have gotten stuck in elevators, you definitely should care about total travel time.
In one case, the building was still being commissioned and it took a while for anyone to even realize they were stuck (could spawn a whole discussion about launch processes in itself).
It should be both, I think. Same goes for queuing in the restaurant. Waiting for the table for 5 minutes, then 5 minutes for the waiter, then 10 minutes for the drink, then 25 for the food is better than waiting for the table for 25 and then getting your full order in another 5.
Basically you have an irrational sense of progress even if things get delayed
omoikane · · focus · HN ↗
I wonder if this is an artifact of how the author used random destinations. I worked in a building that used Destination Dispatch, and the common travel pattern seemed to be:
- Everyone who is not on the ground floor generally want to go to the ground floor.
- People who are on the ground floor generally travel in large groups to the same destination.
This happens because people who worked on the same floor often leave for lunch at the same time, and return at the same time to the same floor. Destination Dispatch helps in this case because it's batching large groups of people with the same destination.
acomjean · · focus · HN ↗
I just visited a new building with destination dispatch, so it seems to be still around.
My EE roommate in college had to build an elevator circuit as a final problem. It was on a bread board and had a bunch of call buttons and had a motor and a clear disk with black squares so it could figure out where it was…. I think it was the simple algorithm…
vova_hn2 · · focus · HN ↗
Yeah, it doesn't make any sense to optimize wait time instead of total time from pressing the button to reaching destination.
esikich · · focus · HN ↗
donalhunt · · focus · HN ↗
In one case, the building was still being commissioned and it took a while for anyone to even realize they were stuck (could spawn a whole discussion about launch processes in itself).
esikich · · focus · HN ↗
Gabrys1 · · focus · HN ↗
Basically you have an irrational sense of progress even if things get delayed