Closed GoogleCodeExporter closed 9 years ago
Started this and implemented a simple version, but it looks like Dynameq
doesn't understand the priorities, and I'll have to make a custom priorities
file.
Original comment by lisa.zorn@sfcta.org
on 18 Aug 2012 at 12:58
I implemented custom priorites in Revision 65f7d64f9e58, but as it turned out,
I don't think I needed to, at least for this.
When I added the TWSC flags at these nodes, the GUI did not show the priorities
being used (it didn't show the centroids yielding to the road links, and showed
that I always had "customized" the priorities there), so I initially thought I
needed to implement custom priorities.
After testing, however, I found this in the Dynameq documentation:
"If a value of follow-up time other than −1 is specified for any movement at
a node, the Customize option will be automatically set for the specified
priority template at this node and the user-defined values of follow-up time
will be used in place of those specified by the template. All movements at the
node for which −1 is specified for the follow-up time will receive the
follow-up time specified by the priority template (if applicable)."
Then I found that when Network._split is called, it sets the follow-up time as
1.0 seconds, so that was what was interfering with the priorities. I reset it
to be the default and the priorities are now not "customized", so they are
behaving as expected: the lower facility type (the connectors) yield to the
higher facility type (the street).
Original comment by lisa.zorn@sfcta.org
on 24 Aug 2012 at 1:34
Original issue reported on code.google.com by
elizab...@sfcta.org
on 14 Aug 2012 at 4:57