Hi Jakob and sumo-user. Thank you, now it does make sense! The responses and foes must be read from right to left. In that case I believe there is a significant mistake in the wiki documentation:
http://sourceforge.net/apps/mediawiki/sumo/index.php?title=Networks/SUMO_Road_Networks where it says: "The same order is applied in the "response" and the "foes" field, starting from left. This means: <request index="2" response="100" foes="110" cont="0"/> The a vehicle using the connection with the index "2" has to wait for vehicles that use the connection "0". Connections "0" and "1" are its foes." Anyway, my problem is solved, thank you very much for your fast and helpful replies! Pavel On Tue, Jun 10, 2014 at 7:45 AM, Jakob Erdmann <[email protected]> wrote: > Hello, > The bitstrings in attributes response and foes must be read from right to > left (response to link 0 is the rightmost entry) in contrast to tlLogic- > state strings which are read from left to right (state of link 0 is the > leftmost entry). Furthermore, you do not need to guess the link indices. > You can display them in sumo-gui by enabling 'show link junction index' in > junction-visualization settings. > regards, > Jakob > > > 2014-06-09 13:34 GMT+02:00 Pavel Janovský < > [email protected]>: > >> Hi sumo-user, >> thanks for the reply! >> >> I don't want to modify the .net.xml file at all. I am parsing it and I >> want >> to implement traffic rules in my own java project based on the data in the >> .net.xml file. When I load the sumo.cfg file into sumo, the right of way >> in >> the simulation makes sense. But I don't think it uses the data from the >> requests in the .net.xml file. >> >> I am sharing with you here >> >> https://www.dropbox.com/s/8i2zrxwduxm1m98/sumo-junction-example.zip >> >> the .net.xml file which describes one junction, also a screenshot of the >> junction in sumo and a picture of my understanding of the links and their >> responses. >> I think there are some important inconsistencies in the junction 112000667 >> data in the .net.xml - for example: how can link 1 have itself in >> response? >> How can link 4 have link 0 in foes if neither has the other one in >> response? >> >> But mainly the junction loaded to sumo has right of way which doesn't >> correspond to the requests in the .net.xml file. I am not exactly sure how >> the ordering of the links works - do I order first by angle of incoming >> edge counter-clockwise? In the picture I show different orderings, but >> none >> maps well to the junction loaded to sumo. >> >> The .net.xml file was created using the following command from an >> openstreetmap file: >> >> netconvert --osm-files <input-osm-file> -o <output-file.net.xml> >> --tls.join --remove-edges.by-vclass >> >> hov,taxi,bus,delivery,transport,lightrail,cityrail,rail_slow,rail_fast,motorcycle,bicycle,pedestrian >> --no-internal-links >> >> Could you please look at the example I am sending you and try to explain >> what I'm doing wrong? >> >> Thank you, >> Pavel Janovsky >> >> >> >> >> On Fri, Jun 6, 2014 at 11:13 AM, Jakob Erdmann < >> [email protected]> >> wrote: >> >> > Hello, >> > right of way are determined heuristically by node type, priorities of >> > edges, maximal speeds and numbers of lanes. >> > >> > >> http://sumo-sim.org/userdoc/Networks/Building_Networks_from_own_XML-descriptions.html >> > some manual overrides are possible ( >> > >> http://sumo-sim.org/wiki/Networks/Building_Networks_from_own_XML-descriptions#Setting_Connection_Priorities >> > ) >> > >> > That information is then written to the .net.xml as requests, response, >> > foes etc. Part of the information is also stored in the .net.xml at >> > <connection> elements in the state attribute >> > >> > As a general rule you should not attempt to modify .net.xml files >> directly >> > because there are many subtle inter-dependencies which may cause >> > hard-to-diagnose bugs if modified incorrectly. Instead you should modify >> > the xml-inputs to netconvert to achieve the desired right of way. So >> far we >> > have been able to represent all real-world intersections for our own >> > projects that way. >> > Please send us any counter-examples you find. >> > regards, >> > Jakob >> > >> > >> > >> > 2014-06-04 14:01 GMT+02:00 Pavel Janovský < >> > [email protected]>: >> > >> >> Hi. >> >> >> >> I want to implement the right of way on the intersections. I am >> loading a >> >> network from the .net.xml file generated by the netconvert. >> >> On the wiki page >> >> >> >> >> http://sourceforge.net/apps/mediawiki/sumo/index.php?title=Networks/SUMO_Road_Networks >> >> I found the information about requests, responses and foes stored for >> each >> >> junction. >> >> >> >> On the other hand another wiki page says the rights are chosen using >> >> priorities of edges, maximal speeds and numbers of lanes. >> >> >> >> >> http://sumo-sim.org/userdoc/Networks/Building_Networks_from_own_XML-descriptions.html >> >> >> >> Finally, when I load the .net.xml file into SUMO (0.19.0) the junction >> >> rules are again different and independent of the changes in the >> requests >> >> or >> >> priorities of edges. >> >> >> >> Could you please explain how the junction rules - the right of way is >> >> generated? >> >> >> >> Thank you, >> >> Pavel Janovsky >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Learn Graph Databases - Download FREE O'Reilly Book >> >> "Graph Databases" is the definitive new guide to graph databases and >> their >> >> applications. Written by three acclaimed leaders in the field, >> >> this first edition is now available. Download your free book today! >> >> http://p.sf.net/sfu/NeoTech >> >> _______________________________________________ >> >> sumo-user mailing list >> >> [email protected] >> >> https://lists.sourceforge.net/lists/listinfo/sumo-user >> >> >> > >> > >> >> ------------------------------------------------------------------------------ >> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions >> Find What Matters Most in Your Big Data with HPCC Systems >> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >> http://www.hpccsystems.com >> >> _______________________________________________ >> sumo-user mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/sumo-user >> > > ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
