Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why not try creating a customized timing function for Dynamic Signal Switching Phase? #4

Open
17110009-HICET-IT opened this issue Mar 14, 2021 · 2 comments
Open

Why not try creating a customized timing function for Dynamic Signal Switching Phase? #4

17110009-HICET-IT opened this issue Mar 14, 2021 · 2 comments
Assignees
@17110013-HICET-IT
Labels
enhancement New feature or request

Comments

@17110009-HICET-IT
Copy link
Member

17110009-HICET-IT commented Mar 14, 2021 •
edited
Loading

Like, it should be based on the average count of vehicles with consideration of lane with higher counts.

Also, we must ensure that no signal is wide open over 120 seconds because it might cause severe congestion issues. A lane must be opened within every 120 seconds to manage the free flow of traffic atleast on one lane.

What's your opinion on it?

@ashwin2125 @17110013-HICET-IT @17110014-HICET-IT

#enhancement
@17110014-HICET-IT
Copy link
Contributor

Agreed ! @17110009

@17110013-HICET-IT 17110013-HICET-IT added the enhancement New feature or request label Mar 14, 2021
@17110013-HICET-IT 17110013-HICET-IT self-assigned this Mar 14, 2021
@17110013-HICET-IT
Copy link
Member

Sure.

Working on it. 😊

ashwingopalsamy pushed a commit that referenced this issue Mar 31, 2021
enhancement
29d5b26 
Co-Authored-By: ANANDHAKUMAR P <[email protected]>
Co-Authored-By: ASHWIN G <[email protected]>

#4
#DynamicSignalSwitching
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@17110013-HICET-IT 17110013-HICET-IT

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@17110013-HICET-IT @17110009-HICET-IT @17110014-HICET-IT