|
Hello Jakob,
1) steps as follows (NETEDIT 1.2.0)
- open network
- open additionals
- save additions (dialog will appear, which seems superfluous,
since I just opened a specific file?)
- switch to TAZ mode with z
- select a TAZ
- disable the "keep" checkbox
- change a value in either the Source or Sink textboxes
- hit the Save changes button
- check the menu item
2) thanks!
3) this is not actually a zipper junction, but a junction
belonging to multiple other junctions that form an intersection
(there is a single (externally controlled) traffic light): see
below, the one on the left without traffic light lines is the
current zipper one
I set the type to zipper cause cars arriving on the edge the is
selected in the image (blue) would only use the rightmost lane.
Maybe a better solution then is to include that junction in the
complete intersection, that is, control is as well with the same
traffic light?
Thanks again,
Greets,
Menno
On 15-5-2019 21:02, Jakob Erdmann
wrote:
Hello,
1) I could not replicated the disabled menu item. Can you
give exact steps for this?
3) Zipper junctions only support lane-drop type junctions
at the moment. Real intersections with zippering are not
supported at the moment. To be more precise, zipper
connections that cross other connections before merging into
the target lane are not supported.
Since the check for this is only done when a vehicle
encounters an unsupported intersection type, it may take a
while for this error to come up in your simulation.
Does the layout in your example reflect a real intersection
where multi-lane roads merge without prioritization ? I was
not aware that such things exist.
best regards,
Jakob
Hello all,
after a while away from sumo and simulations, I have
picked this up again now. Great to see the new features!
Eg. being able to edit taz items within NETEDIT is
really helpful.
I have noticed:
- when changing 'source' and 'sink' values for edges
belonging to a TAZ, after hitting "Save changed", the
"Save additionals" menu item stay disabled. Only after
for example moving a detector can those changes then
be saved to an additionals file that had been opened
and saved before.
- NETEDIT sometime saves TAZ items like this:
<taz id="P2" shape="1183.39,406.32
1188.58,398.44 1194.54,402.09 1190.31,410.36
1183.39,406.32" color="blue">
<tazSource weight="0.00" id="gneE120"/>
<tazSink weight="1.00" id="gneE120"/>
<tazSource weight="1.00" id="gneE121"/>
<tazSink weight="0.00" id="gneE121"/>
</taz>
Important here is source-sink-source-sink: SUMO will
be unable to read this and report an error. It seems
odd that this is incorrect, because it is valid XML
and the order of the items should (in my opinion) be
irrelevant. Saving, closing, opening and saving again
of the additionals file solves the problem: then we
have source-source-sink-sink.
A question: given the junction in the picture below,
SUMO complains after a while of simulation: "Error:
Zipper junctions with more than two conflicting lanes
are not supported". I wonder: why? How to solve this?
Thanks, greets, Menno
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/sumo-user
|
