The biggest problem I always have with elevators is not the algorithm, it's the people seemingly being unable to grasp the concept of pressing either the up or the down request button, depending on where they want to go. Almost always I find someone will press both, because "then the elevator comes faster". Completely ignoring the fact that they end up going the wrong way first half the time, and adding an unnecessary halt for everyone already in there. How hard can it be to understand?..
My wife always randomly hits the up or down button, then gets upset if I explain why she should only pick the one she really wants. She forgets the next time. I think some people never really understand how elevators work.
See also: the keep open / close doors button. I had one building administrator explain to me we should add a delay of 10 seconds to the "quickly shut door" button because otherwise she kept getting her arm hit by the door. When I asked why we would add a delay to the button that's meant to reduce delays (why not simply wait for the door to close on its own, then?), and whether we should fix the sensor that prevents doors from closing if there's an obstacle instead, she just kept staring blankly at me. I don't think she understood me at all.
Again, some people simply don't grasp how elevators work.
Primarily this fixes the bug in the interface which is allowing the user to input data that does not match their declared destination. However, a second benefit is that you can then obtain per-user destination information, which is useful in capacity planning and currently lost in shared direction-only button pressing. Finally, you could usefully use non-floor specifications, ie. 'Ladies underwear', 'ACME Co.', etc.
This reminds me of my partner, who always sets car air conditioning to 50F (the min) or heat to 90F (the max) because she thinks it makes it get cold or hot faster.
And of course a few minutes later we’re freezing or roasting. She sees the temps setting as controlling intensity of cold/hot rather than just, you know, the temperature you want.
It doesn't; it just needs to know it was called. You make your selection once it arrives.
Look up the early history of elevators and you'll see a progression from fully manual in-car up/down controls (often with a dedicated human operator); various semi-automatic systems with minor improvements like automatic leveling and door control; and then operatorless systems that started with nondirectional calls:
It is reasonable if you either have low load say a residential building where lift is often idle. Or low number of floors where travel times in either case are short.
"2.3 Non-directional collective
Non-directive collective control provides a single pushbutton at each landing. This pushbutton is pressed by passengers to register a landing call irrespective of the desired direction of travel. Thus, a lift travelling upwards, for example, and detecting a landing call in its path stops to answer the call, although it may happen that the person waiting at the landing wishes to go down. This type of control is only acceptable for short travel lifts."
olex · · focus · HN ↗
Georgelemental · · focus · HN ↗
[deleted] · · focus · HN ↗
[deleted]
summermusic · · focus · HN ↗
esperent · · focus · HN ↗
I've never been to China but wouldn't you learn quickly after getting in an elevator going the wrong way not to do that again?
The only exception I can see if there's way more people than elevators and you just need to get spot at all costs.
the_af · · focus · HN ↗
See also: the keep open / close doors button. I had one building administrator explain to me we should add a delay of 10 seconds to the "quickly shut door" button because otherwise she kept getting her arm hit by the door. When I asked why we would add a delay to the button that's meant to reduce delays (why not simply wait for the door to close on its own, then?), and whether we should fix the sensor that prevents doors from closing if there's an obstacle instead, she just kept staring blankly at me. I don't think she understood me at all.
Again, some people simply don't grasp how elevators work.
superhuzza · · focus · HN ↗
contingencies · · focus · HN ↗
superhuzza · · focus · HN ↗
chuckadams · · focus · HN ↗
contingencies · · focus · HN ↗
brookst · · focus · HN ↗
And of course a few minutes later we’re freezing or roasting. She sees the temps setting as controlling intensity of cold/hot rather than just, you know, the temperature you want.
[deleted] · · focus · HN ↗
[deleted]
tamimio · · focus · HN ↗
what · · focus · HN ↗
allannienhuis · · focus · HN ↗
tamimio · · focus · HN ↗
what · · focus · HN ↗
cozzyd · · focus · HN ↗
userbinator · · focus · HN ↗
Look up the early history of elevators and you'll see a progression from fully manual in-car up/down controls (often with a dedicated human operator); various semi-automatic systems with minor improvements like automatic leveling and door control; and then operatorless systems that started with nondirectional calls:
<a href="https://liftescalatorlibrary.org/paper_indexing/papers/00000073.pdf" rel="nofollow">https://liftescalatorlibrary.org/paper_indexing/papers/00000...
Ekaros · · focus · HN ↗
rsanek · · focus · HN ↗
userbinator · · focus · HN ↗
userbinator · · focus · HN ↗
"2.3 Non-directional collective Non-directive collective control provides a single pushbutton at each landing. This pushbutton is pressed by passengers to register a landing call irrespective of the desired direction of travel. Thus, a lift travelling upwards, for example, and detecting a landing call in its path stops to answer the call, although it may happen that the person waiting at the landing wishes to go down. This type of control is only acceptable for short travel lifts."