My requeusts:
Synchro
1. Synchro roundabout still does not give delay. I would want delay from synchro. just for roundabouts i do not want to use SIDRA or RODEL.
2. I hate the help file format for version 7. A PDF of the whole thing may be helpful for printing the guide but not for seraching. I am aware someone asked for it before the version 7 cam in. Can It go back to the format of version 6?
3. To have the option of having a scope where we can have the whole link to edit (for name or speed limit). Say after creating a huge network, we found that the speed limit is changed, we do not want to slect each intersection, we want an option where we can select the network to make the change.

Simtraffic
4. If you do not make any change in Synchro, just save it, Simtraffic starts to run. It is sometimes very frustrating. can it be changed?
5. Sometimes a vehicles show unrealistic behavior in simtraffic. (for instance, i have seen it several time, a car is trying to merh from ramp, now the car travelling along the road and car on the ramp, both seem to stop and both stay there minutes after minutes; is it realistic? in rela life someone would move) can it be changed?
6. When we put pedestrians it changes the vehicular delay to some extent (as it should be), but the pedestrians cannot be seen in simtraffic? can it be done?


I think you guys are aware, that another version of HCM is coming in 2010. it is planned to add lot of new things (for instance, turn bay length in delay/queue calculation). Is the coming version incorporating the new HCM.
It probably would be good idea to include that. Many jurisdictions wants HCM

I anticipate a number of public agencies will not yet be prepared to adopt HCM 2010 right away...depending on the amount of overhauling the HCM committees do I wonder how ambitious it is to look for a future Synchro Build or option that might allow active "switching" between 2000/2010 methods for analyzing intersections and roadway segments?

Simtraffic
5. I agree that it's annoying that cars get stuck. Though sometimes it's just an error in coding intersection control, which your example seems to be, and then it's probably good that the stuck cars point that out.
6. I'm pretty sure there are already little purple peds with gray heads walking across the intersection when ped volumes are entered. They gather at the corner and then wait for their signal to cross.

quote:

Originally posted by Gregory:
I anticipate a number of public agencies will not yet be prepared to adopt HCM 2010 right away...depending on the amount of overhauling the HCM committees do I wonder how ambitious it is to look for a future Synchro Build or option that might allow active "switching" between 2000/2010 methods for analyzing intersections and roadway segments?

I agree. Keeping HCM 2000 support for a little while after the 2010 introduction would be a huge plus. Since we probably all have projects that get revisited months and even years into a review, I'd appreciate having to avoid explaining why the LOS potentially changed everywhere when it was only "one last thing" getting tweaked. It would probably be safe to drop the 2000 compatibility after a few years.

Besides, maintaining compatibility might get a little bit of a quicker adoption rate for a new Synchro version.