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.

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

unable to set bidi-edges with netedit #11397

Closed
yunpangfloetteroed opened this issue Aug 23, 2022 · 6 comments
Closed

unable to set bidi-edges with netedit #11397

yunpangfloetteroed opened this issue Aug 23, 2022 · 6 comments
Assignees
Labels
a:netedit c:bidiEdge netedit:netElements Label for netedit tickets centered in net elements worksforme
Milestone

Comments

@yunpangfloetteroed
Copy link
Contributor

Add your issue description here.
Some edges cannot be set to bidi-edges with the spread-type-setting "center", since the check-box "isBidi" is either grayed out or has not action after clicking (see the attached example files problem2 and problem).

SUMO-version:
v1_14_1+0350-48d7f2812e8
operating system:
Windows
problem2.net.xml.zip
problem_edges.zip

@yunpangfloetteroed yunpangfloetteroed added a:netedit netedit:netElements Label for netedit tickets centered in net elements labels Aug 23, 2022
@yunpangfloetteroed
Copy link
Contributor Author

The file problem2.net.xml.zip is redundant. This issue is also reported in the ticket #10445

@behrisch behrisch added this to the 1.15.0 milestone Aug 23, 2022
@yunpangfloetteroed
Copy link
Contributor Author

A extracted network is generated and attached. A reverse edge (-403054383#8) of 403054383#8 is generated. When clicking one of these two edge the attribute "isBidi" of the Mode Inspect is still grayed out. No Bidi-edges can be generated accordingly.

Where exactly should a respective test be generated under sumo\tests?

net.net.xml.zip

@namdre
Copy link
Contributor

namdre commented Aug 26, 2022

such tests would go in tests/netedit but you do not need to add it right now.

@namdre
Copy link
Contributor

namdre commented Aug 30, 2022

The geometries of both edges differs with regard to the endpoints. This is visible to the naked when looking at junction 5912628377

To enable bidi, select both edges and chose 'reset endpoints' from the context menu.

@namdre namdre added worksforme and removed bug labels Aug 30, 2022
@yunpangfloetteroed
Copy link
Contributor Author

The reversed edge is automatically generated by netedit. Don't they supposely have the same geometries regarding the end points?

Just tried the method with 'reset endpoints' the endpoints are set back to the original ones once pressing F5/saving the network. And they can still not be set to bidi-edges.

@yunpangfloetteroed
Copy link
Contributor Author

yunpangfloetteroed commented Aug 30, 2022

I also attached another case here: Edges c and -c should be set to bid-edges.

  1. No bidi can be generated after selecting these two edges and clicking the box "isBidi"
  2. unable to reset endpoints: 'reset endpoints' is grayed out after selecting both edges
    net.net.xml.zip
    sumo version: Version v1_14_1+0698-6b8d6bc7318

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:netedit c:bidiEdge netedit:netElements Label for netedit tickets centered in net elements worksforme
Projects
None yet
Development

No branches or pull requests

4 participants