Ah, I'd love to hear more about this! Getting traffic right is much tougher than we appreciated at first.
Disclaimer: Creator & lead developer of SimAirport.
I suppose we just did it "wrong" to begin with, and have since been stuck with the wrong graph / haven't put the time into fixing it yet -- but would be curious to hear high-level of how you're doing it.
Our issues are primarily that we did lanes as graph nodes instead of "node capacity" so our pathfinding prescribes precisely which lane to use; when stuck in traffic we can't intelligently find our way around it without pathfinding again, but then 'quality' ends up being correlated to how often we pathfind with node-occupancy info, which obviously is a poor (and poorly performing) solution.
Would love to hear your approach or if you'd be interested in talking shop at all, email is in profile! :)
First time I saw SimAirport, looks wonderfully antsy!
I'd love to discuss traffic with you on the Citybound subreddit, since I think there might be other people interested in such implementation details :)
Many universities in major urban areas have a school of housing and community development. They study planning, policy, design, economics, and other related disciplines.
Once trained with how to create new models in your system, academics could simulate the impact of ideas they are developing in research.
I just thought it might be nice if you did a breakdown of the physics of traffic and maybe how you coded that part.
As for teaching, I think it could be used to teach about like signal timing etc in a fun way.
Disclaimer: Creator & lead developer of SimAirport.
I suppose we just did it "wrong" to begin with, and have since been stuck with the wrong graph / haven't put the time into fixing it yet -- but would be curious to hear high-level of how you're doing it.
Our issues are primarily that we did lanes as graph nodes instead of "node capacity" so our pathfinding prescribes precisely which lane to use; when stuck in traffic we can't intelligently find our way around it without pathfinding again, but then 'quality' ends up being correlated to how often we pathfind with node-occupancy info, which obviously is a poor (and poorly performing) solution.
Would love to hear your approach or if you'd be interested in talking shop at all, email is in profile! :)