rht
> I think for many users having to go to a terminal is counterintuitive, and I want to directly trigger run the Solara visualisation from the Python script. So doing...
> Could you elaborate on "They are soon going to be part of one umbrella of measures" https://github.com/projectmesa/mesa/discussions/2236, and in https://github.com/projectmesa/mesa/pull/2263, where measures and space are merged into "components" (what...
`steps` is bread and butter: used in the batch runner and the visualization (to detect if user has reset the simulation), so it can't be fixed to 1 by default.
> Also, and separately, is this use case so common that it should be supported in a core class of MESA? If you looked at the PR's timeline, the time...
> I choose to increment the time before the user step, in the spirit of "a new step" (or a new day) has begun. Then the model does things during...
> > There is no action happening at steps 0. > > The whole `__init__` is happening at step 0. If you have N steps, step 0 is the init...
What if there is an arbitrary `kwargs` that you can pass to `nx.draw`, `ax.plot`, and so on, to expose their full API?
Oh, the layout has to be initialized separately from `nx.draw`, so this needs a separate kwarg.
The logging to an SQLite DB is probably overkill when done by default for a simple initialization, and should be disabled
The tests used to pass, but the library hasn't been maintained for years, and the `dataset` requirement is pinned to be too outdated. I tried a fix at #222, but...