added a new example: city walking behaviour #241

Sahil-Chhoker · 2024-12-27T17:12:36Z

Add Walking Behavior Agent-Based Model

Summary

This PR introduces an Agent-Based Model (ABM) for simulating walking behavior in a hypothetical city. The model explores how socioeconomic status (SES), built environment, and social factors dynamically influence walking patterns. The following files and components have been added to the repository:

Files Added

README.md:
- Provides a detailed overview of the model architecture, agent characteristics, environmental layers, and simulation scenarios.
Model.py:
- Sets up the grid and initializes the four scenarios (RR, RS, CR, CS).
- Manages the safety and aesthetic property layers.
- Places different workplaces according to the scenario.
- Places Humans according to their SES values
- Collects metrics such as average daily walking trips, work-related trips, and leisure walks for analysis.
Agents.py:
- Demographics:
  - Gender (50/50 distribution)
  - Age (18-87 years, random distribution)
  - Family Size (1-2 members)
  - Pet Ownership (20% dog ownership rate)
- Personal Attributes:
  - Walking Ability
  - Walking Attitude
  - Employment Status
  - Social Networks
- Workplaces:
  - Grocery Store
  - Social Place
  - Non-Food Store
  - Others

Key Features Added

1. Initialization Parameters

Grid Dimensions: Width and height of the city grid.
Workplace Distribution: Configurations for Grocery Stores, Social Places, and other workplaces.
Population Demographics: SES-based household positioning, age, family size, and pet ownership distribution.

2. Environmental Layers

Safety Layer (safety_cell_layer): Dynamic safety values according to the scenarios influencing route selection.
Aesthetic Layer (aesthetic_cell_layer): Center-focused aesthetic value distribution impacting walking preferences.

3. Simulation Scenarios

RR (Random-Random): Random distribution of land use and safety values.
RS (Random-Safety): Random land use with lower safety in core areas.
CR (Centralized-Random): Centralized land use with random safety values.
CS (Centralized-Safety): Centralized land use with lower safety in core areas.

4. Agent Characteristics

Agents include attributes like walking ability, attitude, employment status, and social networks.
Agents dynamically adjust walking attitude based on feedback mechanisms like: walking attitudes of family and friends, safety and aesthetic values, pedestrian density, and total amount walked by the person during that day.
Agents decide walking routes and destinations based on proximity, safety, and purpose(basic needs, leisure and work).

5. Behavioral Feedback Mechanisms

Social Influence:
- Attitudes update based on social connections:
  - Family:
  - Friends:
Walking Experience:
- Positive walking experiences increase willingness to walk:
Density of Walkers:
- Feedback depends on the ratio of current walking density to previous density (( I_d )):
  - ( I_d > 1 ): Positive feedback.
  - ( I_d < 1 ): Negative feedback.
Total Distance Walked:
- Feedback reflects the impact of fatigue:
Daily Attitude Update:
- Combined feedback updates attitude:

6. Data Collection System

The model tracks the following metrics across five SES levels (1-5):
- Average daily walking trips
- Work-related trips
- Basic needs trips (grocery and non-food shopping)
- Leisure trips (non-purposeful neighborhood walks)

Known Shortcomings

Very slow.
Unable to simulate with recommended grid size (800x800) and human population.
Distribution of values across the safety and aesthetic property layers may not be correct.
Having a dog does not affect the walking attitude, whereas it should.
Wrong results noted:
- to be compared with
- (one day being one step)
- (attention to be paid to the SES color being different in both the graphs)

for more information, see https://pre-commit.ci

EwoutH · 2024-12-27T17:55:48Z

Looks like quite a serious model!

If you could add to the PR description:

A summary / overview of the model
Any outstanding questions / considerations

EwoutH · 2024-12-28T07:48:12Z

Thanks for the extended descriptions.

Have you profiled the model to identify the main performance bottlenecks?

EwoutH · 2024-12-28T07:52:33Z

@projectmesa/maintainers I’m a bit in doubt on the complexity of this example. On the one hand it shows you can create ABMs with detailed environments and complex behavior, on the other hand I don’t know an example this extended would really benefit our users. I would like to hear some of your stances.

Sahil-Chhoker · 2024-12-28T08:50:34Z

Have you profiled the model to identify the main performance bottlenecks?

I haven't, can you tell how can I do that?

EwoutH · 2024-12-28T09:07:33Z

Some starting point:

Most IDEs also have a profiler built-in.

Sahil-Chhoker · 2024-12-28T13:56:07Z

Here is the table I built from the data collected by the profiler running the model 10 times.

Performance Analysis Results

Function/Method Name	NCalls	TotTime	CumTime	%Total
step(agents.py)	4,850	0.019	0.596	74.4%
simulate_daily_walks	4,850	0.033	0.426	53.2%
decide_leisure_walk	4,850	0.092	0.226	28.2%
calculate_distance	185,574	0.093	0.132	16.5%
get_feedback	1,303	0.041	0.128	16.0%
weakref.keys	185,980	0.072	0.113	14.1%
find_nearest_location	2,391	0.010	0.109	13.6%
min (built-in)	5,689	0.018	0.093	11.6%
sum (built-in)	14,770	0.012	0.068	8.5%
lambda (agents.py:135)	17,825	0.018	0.041	5.1%
sqrt (built-in)	190,260	0.039	0.039	4.9%
cell (cell_agent.py)	188,561	0.029	0.029	3.6%

EwoutH · 2024-12-28T14:17:18Z

Okay, this is quite useful already! It shows that most of the runtime is taken up in the Agent step, and specifically the decision logic.

You can try to speed that up, but if you want I can also give it a try (hopefully tomorrow or Monday).

Sahil-Chhoker · 2024-12-28T16:03:43Z

You can try to speed that up, but if you want I can also give it a try (hopefully tomorrow or Monday).

I'll do what I can, but I'm not particularly confident. Can we use caching to prevent duplicate lookups in calculate_distance? I'm also not sure what could speed up the other functions.

EwoutH · 2024-12-30T09:47:58Z

Hypothesis for model results not correlating with the paper:

Safety and aesthetics are note implemented correctly (check by adding visualisation of PropertyLayers)
Agents are not reading the correct values from the PropertyLayers
Agents are not using the read value correctly in their behavior

EwoutH · 2024-12-30T09:48:27Z

In theory this should work:

I'll help you visualize both property layers by updating the space component in app.py. We'll create a portrayal dictionary for the property layers that defines a color gradient from transparent to solid blue/green.

Here's how to modify the app.py code. First, add this portrayal dictionary right after the model_params definition:
propertylayer_portrayal = {
    "safety": {
        "color": "blue",
        "alpha": 0.5,
        "colorbar": True
    },
    "aesthetic": {
        "color": "green", 
        "alpha": 0.5,
        "colorbar": True
    }
}
Then update the space_component definition to include the property layers:
space_component = make_space_component(
    agent_portrayal, 
    draw_grid=True, 
    post_process=post_process_space,
    propertylayer_portrayal=propertylayer_portrayal
)
This will:

Draw the safety layer in blue gradient where low values are transparent and high values are solid blue

Draw the aesthetic layer in green gradient where low values are transparent and high values are solid green

Display colorbars for both layers to show the value scale

Set alpha to 0.5 so the layers blend nicely and don't completely obscure agents

The layers will be drawn before the agents, so you'll still be able to see all the agents on top of the colored background created by these layers.

EwoutH · 2024-12-30T09:52:16Z

Visualize PropertyLayers mesa#2336

Sahil-Chhoker · 2024-12-31T07:30:43Z

I have successfully visualized the property layers, and they are functioning as intended. Before moving on to the other points, I reread the paper and realized I had overlooked the concept of households. I will now implement the household concept and check the results again.

EwoutH · 2024-12-31T07:51:01Z

Awesome, that's amazing to hear! Did you figure out what the bug was or what I missed yesterday?

EwoutH · 2024-12-31T07:51:54Z

I reread the paper and realized I had overlooked the concept of households. I will now implement the household concept and check the results again.

CC @tpike3, Households sounds like Meta agents. Maybe you could assist here!

Meta agents mesa#2575

Sahil-Chhoker · 2024-12-31T08:07:05Z

@EwoutH Unfortunately no, but since they are just a bunch of numpy arrays I exported the data and made some graphs based on the values. I can confirm they are implemented as they are intended.

CC @tpike3, Households sounds like Meta agents. Maybe you could assist here!

I read a bit about MetaAgents, and from my understanding, they are groups of agents that form during the model runtime based on certain properties. While I can see their usefulness, I don’t think they are particularly relevant to this model. This is because the household system is defined during the human placement, and a household is simply the cell where they spawn. Therefore, in my opinion, this can be handled during initialization.

EwoutH · 2024-12-31T08:35:27Z

Thanks, sounds good!

Sahil-Chhoker · 2024-12-31T11:33:39Z

@EwoutH I have a question: is it correct to use model.random everywhere inside the agents' logic? For example, if agents need to find new locations to move to every day, wouldn’t using the same model.random result in the agents walking to the same place they walked the previous day?

quaquel · 2024-12-31T11:41:07Z

it's better to use self.random inside an Agent, so self.random.random() will draw a random number of unit interval. In either case agent.random or model.random just refer to the same seeded python stdlib random.Random instance which is a random number generator so repeated calls will return different numbers.

…alking behaviour

Sahil-Chhoker · 2024-12-31T13:38:13Z

The model has improved significantly with the following changes:

Rewriting the walking behavior to incorporate household positions.
Improving the placement of agents based on their SES.
Scaling the feedback factor by 20 due to its current size.

Tasks to be completed:

Fix the logic for leisure walks.
Review the positioning of agents.

current results for RR:

observations:

It becomes stable like in the graph from paper.
Distribution by SES is correct.

Sahil-Chhoker · 2025-01-02T09:47:30Z

I have thoroughly reviewed the model in every aspect and believe I have covered everything correctly. In my opinion, the only remaining task is to make the model efficient enough to run on an 800x800 grid or decide to keep this simpler model after applying smaller optimizations.

Current Results:

Current Profile: Running the model with 20x20 grid and 1350 humans for 10 steps.

Function	ncalls	tottime	percall	cumtime	percall
_wrapped_step	10	0.000	0.000	2.300	0.230
step	10	0.000	0.000	2.300	0.230
shuffle_do	10	0.023	0.002	2.165	0.217
step (agents)	13,500	0.055	0.000	2.119	0.000
simulate_daily_walks	13,500	0.101	0.000	1.636	0.000
decide_leisure_walk	13,500	0.024	0.000	0.920	0.000
get_leisure_cells	1,208	0.565	0.000	0.885	0.001
init (model)	1	0.000	0.000	0.761	0.761
add_initial_humans	1	0.007	0.007	0.715	0.715
init (agents)	1,350	0.011	0.000	0.687	0.001
get_workplace	1,350	0.245	0.000	0.561	0.000
keys	1,217,553	0.348	0.000	0.415	0.000
find_walkable_locations	8,851	0.038	0.000	0.404	0.000
get_feedback	3,001	0.133	0.000	0.369	0.000
check_near_point	10,022	0.126	0.000	0.254	0.000
sum	49,697	0.038	0.000	0.223	0.000
calculate_distance	368,985	0.137	0.000	0.212	0.000
collect	11	0.001	0.000	0.147	0.013
abs	864,370	0.125	0.000	0.125	0.000
mean	3,001	0.051	0.000	0.117	0.000
get_distance	87,277	0.083	0.000	0.103	0.000

examples/city_walking_behaviour/Readme.md

EwoutH · 2025-01-02T20:20:14Z

Awesome, I will do a full review this weekend.

Sahil-Chhoker · 2025-01-10T13:31:45Z

@EwoutH I would love to hear your thoughts on this.

EwoutH · 2025-01-10T16:00:20Z

examples/city_walking_behaviour/city_walking_behaviour/agents.py

+        self.cell = cell
+
+
+class WalkingBehaviorModel:


Maybe rename this to avoid confusion with the Mesa model.

EwoutH · 2025-01-10T16:04:10Z

examples/city_walking_behaviour/city_walking_behaviour/model.py

+        no_of_others: int = 475,
+        scenario: str = "random_random",
+        seed=None,
+        simulator=ABMSimulator(),


Are you actually using DEVS functionality? I can't find it in your code, so I'm curious if you use the functionality.

EwoutH · 2025-01-10T16:10:24Z

examples/city_walking_behaviour/city_walking_behaviour/model.py

+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 1
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+            "avg_basic_ses2": lambda x: (  # average basic-needs trips for SES=2
+                sum(
+                    agent.basic_needs_trips
+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 2
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+            "avg_basic_ses3": lambda x: (  # average basic-needs trips for SES=3
+                sum(
+                    agent.basic_needs_trips
+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 3
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+            "avg_basic_ses4": lambda x: (  # average basic-needs trips for SES=4
+                sum(
+                    agent.basic_needs_trips
+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 4
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+            "avg_basic_ses5": lambda x: (  # average basic-needs trips for SES=5
+                sum(
+                    agent.basic_needs_trips
+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 5
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+            "avg_leisure_ses1": lambda x: (  # average leisure trips for SES=1
+                sum(
+                    agent.leisure_trips
+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 1
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+            "avg_leisure_ses2": lambda x: (  # average leisure trips for SES=2
+                sum(
+                    agent.leisure_trips
+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 2
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+            "avg_leisure_ses3": lambda x: (  # average leisure trips for SES=3
+                sum(
+                    agent.leisure_trips
+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 3
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+            "avg_leisure_ses4": lambda x: (  # average leisure trips for SES=4
+                sum(
+                    agent.leisure_trips
+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 4
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+            "avg_leisure_ses5": lambda x: (  # average leisure trips for SES=5
+                sum(
+                    agent.leisure_trips
+                    for agent in x.agents_by_type[Human]
+                    if agent.SES == 5
+                )
+                / len(x.agents_by_type[Human])
+                if x.agents_by_type[Human]
+                else 0
+            ),
+        }
+
+        self.datacollector = DataCollector(model_reporters)


Maybe we can generate these a bit more elegantly, can you check if something like this works?

Suggested change

model_reporters = {

"avg_walk_ses1": lambda x: ( # average daily walking trips for SES=1

sum(

agent.daily_walking_trips

for agent in x.agents_by_type[Human]

if agent.SES == 1

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_walk_ses2": lambda x: ( # average daily walking trips for SES=2

sum(

agent.daily_walking_trips

for agent in x.agents_by_type[Human]

if agent.SES == 2

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_walk_ses3": lambda x: ( # average daily walking trips for SES=3

sum(

agent.daily_walking_trips

for agent in x.agents_by_type[Human]

if agent.SES == 3

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_walk_ses4": lambda x: ( # average daily walking trips for SES=4

sum(

agent.daily_walking_trips

for agent in x.agents_by_type[Human]

if agent.SES == 4

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_walk_ses5": lambda x: ( # average daily walking trips for SES=5

sum(

agent.daily_walking_trips

for agent in x.agents_by_type[Human]

if agent.SES == 5

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_work_ses1": lambda x: ( # average work trips for SES=1

sum(

agent.work_trips

for agent in x.agents_by_type[Human]

if agent.SES == 1

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_work_ses2": lambda x: ( # average work trips for SES=2

sum(

agent.work_trips

for agent in x.agents_by_type[Human]

if agent.SES == 2

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_work_ses3": lambda x: ( # average work trips for SES=3

sum(

agent.work_trips

for agent in x.agents_by_type[Human]

if agent.SES == 3

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_work_ses4": lambda x: ( # average work trips for SES=4

sum(

agent.work_trips

for agent in x.agents_by_type[Human]

if agent.SES == 4

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_work_ses5": lambda x: ( # average work trips for SES=5

sum(

agent.work_trips

for agent in x.agents_by_type[Human]

if agent.SES == 5

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_basic_ses1": lambda x: ( # average basic-needs trips for SES=1

sum(

agent.basic_needs_trips

for agent in x.agents_by_type[Human]

if agent.SES == 1

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_basic_ses2": lambda x: ( # average basic-needs trips for SES=2

sum(

agent.basic_needs_trips

for agent in x.agents_by_type[Human]

if agent.SES == 2

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_basic_ses3": lambda x: ( # average basic-needs trips for SES=3

sum(

agent.basic_needs_trips

for agent in x.agents_by_type[Human]

if agent.SES == 3

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_basic_ses4": lambda x: ( # average basic-needs trips for SES=4

sum(

agent.basic_needs_trips

for agent in x.agents_by_type[Human]

if agent.SES == 4

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_basic_ses5": lambda x: ( # average basic-needs trips for SES=5

sum(

agent.basic_needs_trips

for agent in x.agents_by_type[Human]

if agent.SES == 5

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_leisure_ses1": lambda x: ( # average leisure trips for SES=1

sum(

agent.leisure_trips

for agent in x.agents_by_type[Human]

if agent.SES == 1

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_leisure_ses2": lambda x: ( # average leisure trips for SES=2

sum(

agent.leisure_trips

for agent in x.agents_by_type[Human]

if agent.SES == 2

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_leisure_ses3": lambda x: ( # average leisure trips for SES=3

sum(

agent.leisure_trips

for agent in x.agents_by_type[Human]

if agent.SES == 3

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_leisure_ses4": lambda x: ( # average leisure trips for SES=4

sum(

agent.leisure_trips

for agent in x.agents_by_type[Human]

if agent.SES == 4

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

"avg_leisure_ses5": lambda x: ( # average leisure trips for SES=5

sum(

agent.leisure_trips

for agent in x.agents_by_type[Human]

if agent.SES == 5

)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

),

}

self.datacollector = DataCollector(model_reporters)

def create_model_reporters():

"""Create a dictionary of model reporters with minimal boilerplate"""

reporters = {}

metrics = ['daily_walking_trips', 'work_trips', 'basic_needs_trips', 'leisure_trips']

for metric in metrics:

for ses in range(1, 6):

name = f"avg_{metric.split('_')[0]}_ses{ses}" # e.g. "avg_walk_ses1"

# Create the reporter function

reporters[name] = lambda x, m=metric, s=ses: (

sum(getattr(agent, m) for agent in x.agents_by_type[Human] if agent.SES == s)

/ len(x.agents_by_type[Human])

if x.agents_by_type[Human]

else 0

)

return reporters

# Generate the model_reporters dict

model_reporters = create_model_reporters()

self.datacollector = DataCollector(model_reporters)

EwoutH · 2025-01-10T16:13:27Z

examples/city_walking_behaviour/city_walking_behaviour/model.py

+
+    def step(self):
+        """Advance the model by one step."""
+        self.agents_by_type[Human].shuffle_do("step")


Are there humans added or removed after initialisation? Otherwise you could generate the humans AgentSet once, and then simply use that.

EwoutH · 2025-01-10T16:14:28Z

examples/city_walking_behaviour/city_walking_behaviour/model.py

+        self.agents_by_type[Human].daily_walking_trips = 0
+        self.agents_by_type[Human].work_trips = 0
+        self.agents_by_type[Human].basic_needs_trips = 0
+        self.agents_by_type[Human].leisure_trips = 0


Maybe give Human a method reset_daily_walking_trips and call that one here.

EwoutH · 2025-01-10T16:17:24Z

examples/city_walking_behaviour/city_walking_behaviour/agents.py

+class GroceryStore(Workplace, FixedAgent):
+    def __init__(self, model: Model, cell=None):
+        Workplace.__init__(self, store_type="Grocery Store")
+        FixedAgent.__init__(self, model)
+        self.cell = cell
+
+
+class NonFoodShop(Workplace, FixedAgent):
+    def __init__(self, model: Model, cell=None):
+        Workplace.__init__(self, store_type="Non-Food Shop")
+        FixedAgent.__init__(self, model)
+        self.cell = cell
+
+
+class SocialPlace(Workplace, FixedAgent):
+    def __init__(self, model: Model, cell=None):
+        Workplace.__init__(self, store_type="Social Place")
+        FixedAgent.__init__(self, model)
+        self.cell = cell
+
+
+class Other(Workplace, FixedAgent):
+    def __init__(self, model: Model, cell=None):
+        Workplace.__init__(self, store_type="Other")
+        FixedAgent.__init__(self, model)
+        self.cell = cell


I'm curious why these are classes, and not just a Place with a place_type variable.

It might be that there's a very good reason, just curious.

EwoutH · 2025-01-10T16:20:00Z

examples/city_walking_behaviour/city_walking_behaviour/agents.py

+    @lru_cache(maxsize=1024)  # noqa
+    def get_max_walking_distance(self, ability: float, activity: ActivityType) -> float:
+        """Cached calculation of max walking distance based on ability."""
+        return self.BASE_MAX_DISTANCES[activity] * ability
+
+    @staticmethod
+    @lru_cache(maxsize=4096)
+    def calculate_distance(x1: int, y1: int, x2: int, y2: int) -> float:
+        """Cached distance calculation between two points."""
+        dx = x2 - x1
+        dy = y2 - y1
+        return math.sqrt(dx * dx + dy * dy)
+
+    def get_distance(self, cell1, cell2) -> float:
+        """Get distance between cells using cache."""
+        key = (cell1, cell2)
+        if key not in self._distance_cache:
+            x1, y1 = cell1.coordinate
+            x2, y2 = cell2.coordinate
+            self._distance_cache[key] = self.calculate_distance(x1, y1, x2, y2)
+        return self._distance_cache[key]


@quaquel this example model uses the cell space. Since it's one of the first user models using it, could you check if:

everything is used according to best practices

there are inconsistencies, missing function or opportunities to improve the cell space

Sahil-Chhoker and others added 3 commits December 27, 2024 11:15

added a new example: city walking behaviour

0142b18

[pre-commit.ci] auto fixes from pre-commit.com hooks

c850d5f

for more information, see https://pre-commit.ci

added pre-commit suggestions

058453d

Sahil-Chhoker added 2 commits December 28, 2024 11:23

added model description

91abe57

updated readme

f405721

improved the model with faster lookups, better placement and better w…

7de1a16

…alking behaviour

Sahil-Chhoker added 2 commits January 2, 2025 15:01

fixed leisure walks, improved household logic and placement for Humans.

32207b2

fixed imports in model.py

9159ee1

EwoutH reviewed Jan 2, 2025

View reviewed changes

examples/city_walking_behaviour/Readme.md Show resolved Hide resolved

Sahil-Chhoker added 4 commits January 3, 2025 10:13

fix: model can pass tests

7fd5559

updated readme

f32b04e

added pictures

d6b1e0f

Update Readme.md

859c9f0

EwoutH reviewed Jan 10, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

added a new example: city walking behaviour #241

added a new example: city walking behaviour #241

Sahil-Chhoker commented Dec 27, 2024 •

edited

Loading

EwoutH commented Dec 27, 2024

EwoutH commented Dec 28, 2024

EwoutH commented Dec 28, 2024

Sahil-Chhoker commented Dec 28, 2024

EwoutH commented Dec 28, 2024

Sahil-Chhoker commented Dec 28, 2024 •

edited

Loading

EwoutH commented Dec 28, 2024

Sahil-Chhoker commented Dec 28, 2024

EwoutH commented Dec 30, 2024

EwoutH commented Dec 30, 2024

EwoutH commented Dec 30, 2024

Sahil-Chhoker commented Dec 31, 2024

EwoutH commented Dec 31, 2024

EwoutH commented Dec 31, 2024

Sahil-Chhoker commented Dec 31, 2024

EwoutH commented Dec 31, 2024

Sahil-Chhoker commented Dec 31, 2024

quaquel commented Dec 31, 2024

Sahil-Chhoker commented Dec 31, 2024

Sahil-Chhoker commented Jan 2, 2025

EwoutH commented Jan 2, 2025

Sahil-Chhoker commented Jan 10, 2025

EwoutH Jan 10, 2025

EwoutH Jan 10, 2025

EwoutH Jan 10, 2025

EwoutH Jan 10, 2025

EwoutH Jan 10, 2025

EwoutH Jan 10, 2025

EwoutH Jan 10, 2025

added a new example: city walking behaviour #241

Are you sure you want to change the base?

added a new example: city walking behaviour #241

Conversation

Sahil-Chhoker commented Dec 27, 2024 • edited Loading

Add Walking Behavior Agent-Based Model

Summary

Files Added

Key Features Added

1. Initialization Parameters

2. Environmental Layers

3. Simulation Scenarios

4. Agent Characteristics

5. Behavioral Feedback Mechanisms

6. Data Collection System

Known Shortcomings

EwoutH commented Dec 27, 2024

EwoutH commented Dec 28, 2024

EwoutH commented Dec 28, 2024

Sahil-Chhoker commented Dec 28, 2024

EwoutH commented Dec 28, 2024

Sahil-Chhoker commented Dec 28, 2024 • edited Loading

Performance Analysis Results

EwoutH commented Dec 28, 2024

Sahil-Chhoker commented Dec 28, 2024

EwoutH commented Dec 30, 2024

EwoutH commented Dec 30, 2024

EwoutH commented Dec 30, 2024

Sahil-Chhoker commented Dec 31, 2024

EwoutH commented Dec 31, 2024

EwoutH commented Dec 31, 2024

Sahil-Chhoker commented Dec 31, 2024

EwoutH commented Dec 31, 2024

Sahil-Chhoker commented Dec 31, 2024

quaquel commented Dec 31, 2024

Sahil-Chhoker commented Dec 31, 2024

Sahil-Chhoker commented Jan 2, 2025

EwoutH commented Jan 2, 2025

Sahil-Chhoker commented Jan 10, 2025

EwoutH Jan 10, 2025

Choose a reason for hiding this comment

EwoutH Jan 10, 2025

Choose a reason for hiding this comment

EwoutH Jan 10, 2025

Choose a reason for hiding this comment

EwoutH Jan 10, 2025

Choose a reason for hiding this comment

EwoutH Jan 10, 2025

Choose a reason for hiding this comment

EwoutH Jan 10, 2025

Choose a reason for hiding this comment

EwoutH Jan 10, 2025

Choose a reason for hiding this comment

Sahil-Chhoker commented Dec 27, 2024 •

edited

Loading

Sahil-Chhoker commented Dec 28, 2024 •

edited

Loading