Live data from Hacker News

Show HN: Elevators

john.fun

131–140 of 427 posts

Re: Show HN: Elevators

#131
> This counterintuitive result is all thanks to the rebalancing step where every 5 seconds, the system re-optimizes each elevator's path. The kiosk enforces rigidity, you must get in the assigned elevator.

Sounds like destination dispatch would work better if it didn't tell you which elevator to get into until the elevator arrived.

EDIT: already being discussed in the thread at https://news.ycombinator.com/item?id=49125423

Re: Show HN: Elevators

#132
Having gone to many large furry cons(notoriously brutal on the elevators due to how much floor-to-floor traffic there is compared to other usage) I’ve seen these algos basically completely fail to adapt to unusual patterns. I once spent over half an hour on checkout day, in a hotel with 8 banks, to even have a car stop on our floor at all. Can’t really blame the algo for such a unique situation and at the end of the day a saturated system is a saturated system and nothing can be done to make it fast, but it’s always interesting to witness when a system is completely unable to accommodate a demand like that.

(In the example above we gave up and decided it was cardio time, five laps up and down 14 flights to escape with all our luggage.)

Re: Show HN: Elevators

#134

Makes me want to play Sim Tower again. There’s something so satisfying about watching a machine just dutifully work through queued tasks like this.

A fun tidbit about Sim Tower: > After my lecture, a Maxis employee who shall remain nameless buttonholed me. "You guessed right," she said. "Sim Tower was built around a real elevator simulation program we bought from a Japanese guy." https://web.archive.org/web/20090916193335/http://www.gamasu...

Would that be Yoot Saito? I remember his name on the box.

Re: Show HN: Elevators

#135

Earlier quoted context omitted.

That sounds like two separate things then. Could you not have people select a destination without locking in an elevator? (I've never encountered destination dispatch myself, so I'm not really sure how it works in practice)

The way I've seen it work is that there's a touch screen in the elevator lobby. You tap a floor, and then screen will say "Car C" (along with an audible message). The problem is that then the system can't reassign you to a different car after that. You'll typically have a bunch of different people going to a bunch of different floors, and there would be no reliable way to communicate to each individual their new assi…

Display a set of floors on a big overhead screen (in floor order so they're easy to find), have the "elevator" column blank until the elevator is assigned, and let them watch the column that's going to show them which elevator to use.

But yes, this seems like a case of "unfortunately, people".

Re: Show HN: Elevators

#136
Level 1: Elevators, load balancing (1D arrays)

Level 2: Traffic lights, graphics (2D arrays)

Level 3: Flight control, simulations (3D arrays)

Level 4: Satellite tracking, virtual worlds (4D arrays)

...

So many problems can be cast to arrays to be solved with various linear algebra.

Considering LLMs are "Level 1000+" puzzles in this analogy, I wonder if every problem could be represented by an n-dimensional vector and solvable with algebra.

They at least make great interview questions - Tic-Tac-Toe is commonly given, but is obvious. The board already "looks" like arrays. The less obvious ones, like elevators (or load balancing), are always interesting.

Re: Show HN: Elevators

#139
User experience is not always correlated with metrics targeted by engineers.

I visit a building sometimes with destination dispatch elevators, and with low exposure across multiple years I'm confused every time the elevator I need to take is open behind me.

I once used the paternoster lift in Germany, beats any elevator algorithm efficiency because it's a non-stop "conveyor" with no doors. I still get nightmares about that elevator.

Re: Show HN: Elevators

#140

> 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 bec…

Surely there's a dataset out there with elevator calls for an office building you could test on, instead of the poor random destination case.

Surprisingly, claude failed to find a good one.

Also, part of destination dispatch (I'm guessing based on experience) removes the 'stopping on every floor problem', so the real test would be total time including wait at that point I think.

Post reply on HN