You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mesa startproject does not create an agent.py, because it puts in the agent in the model.py. Should it create an agent.py? I suspect that most people would have models complex enough that they should be separating it. Thoughts?
My thought is that it might be overwhelming to have too many files as a starting point, that starting an ABM model from scratch could be perceived to be complex with lots of boilerplate code/files. But this might also be a cultural thing, because in MATLAB, every function is separated in their own file.
But splitting model.py into model.py and agent.py sounds fine to me, because the user already has a preconceived idea of what should be put there. While run.py and server.py need explanation.
mesa startproject
does not create an agent.py, because it puts in the agent in the model.py. Should it create an agent.py? I suspect that most people would have models complex enough that they should be separating it. Thoughts?For reference, this is the format of the cookiecutter project: https://github.com/projectmesa/mesa/tree/main/mesa/cookiecutter-mesa/%7B%7Bcookiecutter.snake%7D%7D
The text was updated successfully, but these errors were encountered: