base on Mesa is an open-source Python library for agent-based modeling, ideal for simulating complex systems and exploring emergent behaviors. # Mesa: Agent-based modeling in Python | | | | --- | --- | | CI/CD | [](https://github.com/projectmesa/mesa/actions) [](https://codecov.io/gh/projectmesa/mesa) | | Package | [](https://pypi.org/project/Mesa/) [](https://pypi.org/project/Mesa/) [](https://pypi.org/project/Mesa/) | | Meta | [](https://github.com/astral-sh/ruff) [](https://github.com/psf/black) [](https://github.com/pypa/hatch) [](https://scientific-python.org/specs/spec-0000/) | | Chat | [](https://matrix.to/#/#project-mesa:matrix.org) | Mesa allows users to quickly create agent-based models using built-in core components (such as spatial grids and agent schedulers) or customized implementations; visualize them using a browser-based interface; and analyze their results using Python's data analysis tools. Its goal is to be the Python-based alternative to NetLogo, Repast, or MASON.  *Above: A Mesa implementation of the WolfSheep model, this can be displayed in browser windows or Jupyter.* ## Features - Modular components - Browser-based visualization - Built-in tools for analysis - Example model library ## Using Mesa To install our latest stable release (3.0.x), run: ``` bash pip install -U mesa ``` To install our latest pre-release, run: ``` bash pip install -U --pre mesa ``` Starting with Mesa 3.0, we don't install all our dependencies anymore by default. ```bash # You can customize the additional dependencies you need, if you want. Available are: pip install -U --pre mesa[network,viz] # This is equivalent to our recommended dependencies: pip install -U --pre mesa[rec] # To install all, including developer, dependencies: pip install -U --pre mesa[all] ``` You can also use `pip` to install the latest GitHub version: ``` bash pip install -U -e git+https://github.com/projectmesa/mesa@main#egg=mesa ``` Or any other (development) branch on this repo or your own fork: ``` bash pip install -U -e git+https://github.com/YOUR_FORK/mesa@YOUR_BRANCH#egg=mesa ``` ## Resources For resources or help on using Mesa, check out the following: - [Intro to Mesa Tutorial](http://mesa.readthedocs.org/en/stable/tutorials/intro_tutorial.html) (An introductory model, the Boltzmann Wealth Model, for beginners or those new to Mesa.) - [Visualization Tutorial](https://mesa.readthedocs.io/stable/tutorials/visualization_tutorial.html) (An introduction into our Solara visualization) - [Complexity Explorer Tutorial](https://www.complexityexplorer.org/courses/172-agent-based-models-with-python-an-introduction-to-mesa) (An advanced-beginner model, SugarScape with Traders, with instructional videos) - [Mesa Examples](https://github.com/projectmesa/mesa-examples) (A repository of seminal ABMs using Mesa and examples of employing specific Mesa Features) - [Docs](http://mesa.readthedocs.org/) (Mesa's documentation, API and useful snippets) - [Development version docs](https://mesa.readthedocs.io/latest/) (the latest version docs if you're using a pre-release Mesa version) - [Discussions](https://github.com/projectmesa/mesa/discussions) (GitHub threaded discussions about Mesa) - [Matrix Chat](https://matrix.to/#/#project-mesa:matrix.org) (Chat Forum via Matrix to talk about Mesa) ## Running Mesa in Docker You can run Mesa in a Docker container in a few ways. If you are a Mesa developer, first [install Docker Compose](https://docs.docker.com/compose/install/) and then, in the folder containing the Mesa Git repository, you run: ``` bash $ docker compose up # If you want to make it run in the background, you instead run $ docker compose up -d ``` This runs the Schelling model, as an example. With the docker-compose.yml file in this Git repository, the `docker compose up` command does two important things: - It mounts the mesa root directory (relative to the docker-compose.yml file) into /opt/mesa and runs pip install -e on that directory so your changes to mesa should be reflected in the running container. - It binds the docker container's port 8765 to your host system's port 8765 so you can interact with the running model as usual by visiting localhost:8765 on your browser If you are a model developer that wants to run Mesa on a model, you need to: - make sure that your model folder is inside the folder containing the docker-compose.yml file - change the `MODEL_DIR` variable in docker-compose.yml to point to the path of your model - make sure that the model folder contains an app.py file Then, you just need to run `docker compose up -d` to have it accessible from `localhost:8765`. ## Contributing to Mesa Want to join the Mesa team or just curious about what is happening with Mesa? You can\... > - Join our [Matrix chat room](https://matrix.to/#/#project-mesa:matrix.org) in which questions, issues, and > ideas can be (informally) discussed. > - Come to a monthly dev session (you can find dev session times, > agendas and notes on [Mesa discussions](https://github.com/projectmesa/mesa/discussions)). > - Just check out the code on [GitHub](https://github.com/projectmesa/mesa/). If you run into an issue, please file a [ticket](https://github.com/projectmesa/mesa/issues) for us to discuss. If possible, follow up with a pull request. If you would like to add a feature, please reach out via [ticket](https://github.com/projectmesa/mesa/issues) or join a dev session (see [Mesa discussions](https://github.com/projectmesa/mesa/discussions)). A feature is most likely to be added if you build it! Don't forget to checkout the [Contributors guide](https://github.com/projectmesa/mesa/blob/main/CONTRIBUTING.md). ## Citing Mesa To cite Mesa in your publication, you can use the [CITATION.bib](https://github.com/projectmesa/mesa/blob/main/CITATION.bib). ", Assign "at most 3 tags" to the expected json: {"id":"12170","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"