Summary

This PR migrates Mesa's tutorials, examples, and benchmarks to use the new Model.run_for() method. It replaces manual for _ in range(N): model.step() loops with a single, unified call to model.run_for(N).

Motive

With the introduction of event-based scheduling, running a model for a specific duration should be handled by the model's internal time-advancement mechanism rather than external loops. Manual loops calling .step() can lead to inconsistencies when models use discrete-event simulators. model.run_for() provides a declarative, robust, and unified way to advance a simulation regardless of the underlying scheduling mechanism.

Implementation

1. Tutorials: Updated all Jupyter notebooks in docs/tutorials/ to use run_for() which was introduced in Add public event scheduling and time advancement methods #3266 . This involved updating both the code cells and the surrounding markdown explanation to reflect the recommended usage.
2. Benchmarks: Refactored benchmarks/global_benchmark.py to use model.run_for(). This significantly simplified the code by removing the need to check if a model was using a Simulator or a standard loop.
3. Tests:

• Refactored tests/examples/test_examples.py to replace repetitive test loops with concise run_for() calls.
• Added a dedicated unit test in tests/test_model.py to verify that run_for() correctly increments both model steps and simulation time.

Usage Examples

Legacy Pattern:

model = MoneyModel(10)
for _ in range(30):
    model.step()

New Pattern:

model = MoneyModel(10)
model.run_for(30)

Additional Notes

• Related Issue: Mesa 4 development tracking issue #3132