We should be able to easily pair many (but not all) corridors with their reverse, if drawn, because it's just a swap of the node_ids, as in A/B is the reverse of the corridor B/A.
Corridors in the factor list are unsorted at present.
Outputs are currently sorted by the URI which doesn't tend to group paired corridors. Effectively, it just sorts by the start node ID which is pretty arbitrary.
@A-DUYVESTYN had suggested that having reversed corridor pairs grouped in the output would be helpful when looking at the results.
Related to #150
We should be able to easily pair many (but not all) corridors with their reverse, if drawn, because it's just a swap of the node_ids, as in
A/Bis the reverse of the corridorB/A.Corridors in the factor list are unsorted at present.
Outputs are currently sorted by the URI which doesn't tend to group paired corridors. Effectively, it just sorts by the start node ID which is pretty arbitrary.
@A-DUYVESTYN had suggested that having reversed corridor pairs grouped in the output would be helpful when looking at the results.
Related to #150