Open rafapereirabr opened 9 months ago
Isn't this measure the same as balancing_cost()
?
In the paper, the measure is defined as:
it sounds very similar, indeed. I guess the difference is in that it considers competition, as in "greater than or equal to the *total number of individuals competing for those opportunities". If I remember correctly, the balancing_cost()
does not account for competion. But perhaps @tainabittencourt could help us clarify this
Hey,
There are fundamental differences between the two metrics.
The objective of the balancing time is to minimize the travel time of each spatial unit so that the number of opportunities reached is equal to the population living in this area. However, as the calculation is made individually for each origin, it ignores that people living in different areas compete for the same opportunities. You can see it in Figure 1 A is the isochrone of hexagon 1, so the number of opportunities inside this isochrone is equal to the number of people living in 1. B is the isochrone of hexagon 2, so the number of opportunities inside this isochrone is equal to the number of people living in 2. The opportunities inside the hatched area (intersection between A and B) are counted twice.
The objective of the optimization-based algorithm is to minimize the total travel time spent by all individuals when reaching the opportunities they need. As it is calculated by an optimization function based on the transportation problem, it assigns each individual to a single opportunity and then runs multiple combinations until the minimum total travel time is found. One opportunity cannot be accessed by two individuals at the same time. The accessibility value of hexagon 1 is then given by the average travel time of individuals living there.
We could compare the difference between the two metrics to the difference between user equilibrium and system optimization in route allocation in transportation engineering, with the difference that in user equilibrium the decision of one individual affects the decision of others, which doesn't apply to the balancing time. At least, that's what we were thinking when we came up with this...
Is it clearer now? Comparing the equations might help.
Reference:
The code is available on the repo created for the paper by @tainabittencourt.
Perhaps the name of the function could be
optimum_access()
oroptimum_access_landscape()