-
Notifications
You must be signed in to change notification settings - Fork 940
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move experimental DEVS examples to mesa-examples #2191
Comments
Please assign this issue to me @EwoutH I will work on this |
Awesome! Also check out this issue, for some more resources: |
@EwoutH hey can you explain me this issue ,it is confusing |
We have two repo’s: Mesa for our core project and Mesa-examples for examples using that project. The examples linked above are now in our main Mesa repo (and are a bit outdated), and need to be moved to Mesa-examples. Also, since our Discrete Event Scheduling functionality is quite new, we like more examples using it in general. Does this help? |
Yeah, That's Great Information and I will complete this soon. |
Hi @EwoutH, I would like to work on this issue. Could you please assign it to me? |
@RaisunLakra thanks for the interest! With the discussion about the monorepo kicking in, I like to put this on hold for a while: If you want to work on Mesa, we could use a lof of help with updating our examples! See these issues and this part of our contribution guide. |
The examples in https://github.com/projectmesa/mesa/tree/main/mesa/experimental/devs/examples should be moved to mesa-examples, and tested in CI there.
Or at least tested in CI.
Like all our examples, the code should be exemplary and clearly documented. The code part is already good, but a visualisation (
app.py
) using Solara and Readme should be added.So for each model:
_experimental_devs
suffix.agent.py
andmodel.py
app.py
file in which SolaraViz is used(see Remove or update outdated visualisation from examples mesa-examples#154)
(including DEVS, see Use new Discrete Event Scheduling in examples mesa-examples#124)
The text was updated successfully, but these errors were encountered: