rht

I think this PR is too big, and will take a while to be merged. It is better to make a separate PR that does only the Python part.

Check out the reserved fields of hash.ai's hengine for inspiration for the names: https://hash.ai/docs/simulation/creating-simulations/anatomy-of-an-agent/state#Reserved-Fields. ```javascript // Can be used for custom movement logic. Will affect the agent's visualization // Suggested...

For context, hash.ai's hEngine is a performant ABM library written in Rust, with interfaces to Javascript, Python, and other languages.

The experiment was a great success! I was able to reduce the `pip install` step from 24 s to 4 s (+3 s for the virtualenv initialization, which could be...

No, hasn't been implemented.

This seems to be a more recent solution: https://stackoverflow.com/questions/37905690/tornado-setting-headers-for-caching. @aiwhoo if you are up for it, a pull request would be great.

Just wondering if it is simpler to convert the canvas grid visualization code to use D3 and its animation, instead of implementing this from scratch. D3 might already been performance-optimized...

> Disagree. For me it was always clear that neighbors => Agents, neighborhood => Coordinates Is it just me or that the dictionary definition of "neighborhood" refers to people, not...

If `iter_neighborhood` is find, then the problematic wording is the `neighbor_iter` and `iter_neighbors`. They should be called `iter_neighborhood_content` for clarity.

Since a good method name pattern is something along the line of "verb_object", `iter_neighbors` sounds better for me than `neighbor_iter`. But `iter_neighbors` is never used in the examples.