wip: proof-of-concept for "robosim" #5
Draft
Conversation
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
A "discrete event simulator" model of our circuit(s) so we can ask questions like "which invariants are we violating?" and maybe even "what did we decide to do about the SPI clock? why?"
Attempting to connect an inverter that will delay changing its output by 6ns to my 80MHz clock, but Rust does not believe what I'm doing is safe. Maybe it even isn't?
In order to achieve the goal of 2c94850 without too much wrangling, we restrict things that are inputs into a node to only produce a single future scheduled event so we can avoid needing to possibly call downstream consumers more than once in the future. Alternatives include: * Possibly restricting consumers to being Fn (vs FnMut), and passing around lots of references with *hand wave* the correct lifetimes * Instead of taking consumers, take a FnMut that creates the consumers, (which can then all be FnOnces again), calling as many times as necessary. Also, it'd probably have to return a copy of itself for "rewiring", too But probably the most fruitful: * Stop holding Rust like it was Haskell, and make `struct Node {...}` that holds the (mutable) state of a node in the graph. (why is it always graphs?) Additionally, and more reason to do the above, the simulator engine now has to recognize the mapping between the schedule (in its entirety) and which nodes are updated at which point for saving into the history. This is probably fine (if not ideal) for a ~5 component graph, but unworkable for a general simulator.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A "discrete event simulator" model of our circuit(s) so we can ask questions like "which invariants are we violating?" and maybe even "what did we decide to do about the SPI clock? why?"