I think I know why it happens: I am also passing the attribute --tls.group-signals. If I remove that, then the ring and barierPhases are also defined. Not sure if this is a bug or limited feature that has not been implemented yet.
Thanks, Sasan On Thu, Feb 29, 2024 at 11:06 AM Jakob Erdmann via sumo-user <[email protected]> wrote: > > 1 We do have tests where ring and barrier params are created automatically > (see > https://sumo.dlr.de/extractTest.php?path=netconvert/import/XML/tl_types/NEMA). > Please provide example input where an invalid NEMA controller is written to > the network. > 2. This is the fallback if the existing guess-a-NEMA-controller code fails. > If you can provide an example input along with a definition of the expected > NEMA controller I can try to improve the code. > > regards, > Jakob > > Am Mi., 28. Feb. 2024 um 14:11 Uhr schrieb Sasan Amini via sumo-user > <[email protected]>: >> >> Dear all, >> >> I am trying to define all my traffic signals as a NEMA type but I am >> facing two issues: >> 1- Rings and barrierPhases are not automatically defined so I get an >> error in SUMO complainging bout it. >> 2- Some junctions seem to be "actuated" type even when I set >> tls.default-type NEMA in netconvert (see attached screenshot) >> Any suggestions how I could fix this? >> >> Thanks, >> Sasan >> _______________________________________________ >> sumo-user mailing list >> [email protected] >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/sumo-user > > _______________________________________________ > sumo-user mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user _______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
