You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #7. When comparing the performance of the matching algorithms we've implemented (currently just one), we need to have one or more metrics to rate the output. One option is to take the number of buses paired together in the matching, and divide it by the average distance of all buses paired together. The higher the value, the better the quality of the matching.
The text was updated successfully, but these errors were encountered:
this one is a bit different as while it is a graph theory algorithm we care more about the geography here - essentially what you need to do is to go through the matching of the buses (at the moment this is a pairing) returned by the matching algorithm, and see how far apart (in geographical distance) the pairs of buses are. Then take an average of these distances.
Related to #7. When comparing the performance of the matching algorithms we've implemented (currently just one), we need to have one or more metrics to rate the output. One option is to take the number of buses paired together in the matching, and divide it by the average distance of all buses paired together. The higher the value, the better the quality of the matching.
The text was updated successfully, but these errors were encountered: