Closed colinhanrahan closed 2 months ago
Sorry to do this to you, but do this the other way around. Our implementation of Sugarscape adds new functionality by splitting vision and movement. We shouldn't handicap our features out-of-the-box to what the book has. Instead, we should adjust our examples to match the more limited scope of the book.
Also set it to 1000 rather than 9999. The latter case could be misinterpreted as our logical max in the code being 9999 rather than the max size of an integer in the system. They're both equally comic in size.
@nkremerh Done. Where should we add the note about why we're using a comically large value (if we are adding a note)? Adding it to every single example might be a bit much.
No need for additional comment. At most, we may put a note in the wiki or a second README inside the examples directory. A second README sounds more appealing since it's self-contained in the repo on download, but we don't need that right now.
Current repo:
Changes:
README
, "true default" settings insugarscape.py
, andconfig.json
to use single-variable range by default. Movement is set to 9999 and vision is used as the deciding variable.