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.
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
Netedit cannot load joined TLS via menu #4622
Comments
so to rephrase this: Your issue is that netedit does not handle WAUT. correct? |
Not exactly. The matching of waut's junctionID attribute works in sumo and sumo-gui, but not at all in netedit. The TL name information is stored in the connection definitions as reference to tlLogic tag's id attribute, not on the level of junction definition where only the type is set to 'traffic_light'. It would be more accurate, if the wautJunction tag would reference the tlLogic tag instead of the junction |
Despite the attribute name 'junctionID' the attribute actually references a tlLogic id so the implementation works as intended, only the attribute name is crap. Netedit doesn't know anything about WAUT and doesn't even try to parse them. |
That is what does not work, because netedit drops an error entry: 'ERROR, Junction doesn't exist', and the programs in traffic light editor remain the original. |
please send the input files directly to me so I can take a look. |
The initial error message does not originate with the WAUT. Rather, netedit cannot load joined traffic lights via menu. Then the programs are loaded and work (as long as they have the correct state length). When saving the tls definitions, all of them are written to a file but the WAUT are lost. (#4631) |
Thanks, till there is a bugfix I'll do so. |
Hello Jakob |
@ZoltanBaksa Have you tried this with the latest development version? |
No, I used SUMO version: 1.0.1 + 0019-83bdcaf4ad |
Technical explanation:
The text was updated successfully, but these errors were encountered: