Repository navigation
Add an elevator simulation driven by a terminal UI - #76
Merged
Merged
Conversation
Floors, a dispatcher, and two cabs each with a motor and a door; button presses go into the mesh as signals and the building's state comes back out as one, one run per simulated second. Closes #25 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WbQCnCrtf3EqpxJD24koiW
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by ovsep · project thread
Before: no example had a building's worth of interacting stateful parts driven from a UI.
After:
simulation/elevatoris two cabs in a six-floor building, 14 components: six floor call panels, a dispatcher, a display, and per cab a controller, a motor and a door. In the terminal you type a floor to call a cab ora5/b2to ride one; presses go into the mesh as signals and the building's state comes back out as aViewsignal the UI draws as a shaft view.-demo(or non-terminal stdin) plays a scripted rush hour.How: every
Runis one simulated second; components keep their state between runs. Each cab has two feedback loops (motor, door) plus the loop through the dispatcher, which assigns calls by cost and turns a cab's arrival into a lamp going off. Controllers record feedback in any cycle but decide once per tick, keeping direction while stops lie ahead. Tests play the demo to a quiet building, check how the dispatcher split the calls, and cover pressing a call where a cab already stands with open doors.Closes #25
🤖 Generated with Claude Code
https://claude.ai/code/session_01WbQCnCrtf3EqpxJD24koiW
Generated by Claude Code