Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sumo-user] Issues with Bidirectional Rail Switches and Routing in rail network
Hello,

1. Never edit the .net.xml file directly (https://sumo.dlr.de/docs/FAQ.html#i_made_changes_to_the_netxml-file_but_it_did_not_work_as_expected_why)
1b. if you wish to model a single track that is being used in both directions, you need to ensure that both edges are directly on top of each other so that only a single track is visible (rather than offset to the side).  The easiest way to fix your network is to select all edges and use inspect mode on the edge selection to change their spreadType from "right" to "center". This will fix the state of the turnaround connections so that they show up as 't'.
2. Please provide a specific example of an input file where duarouter fails to find a connection. 

Am Sa., 8. Nov. 2025 um 10:27 Uhr schrieb Reza Bahmani via sumo-user <sumo-user@xxxxxxxxxxx>:

Hello SUMO Development Team,

I am working on a rail network simulation using the attached rail_network.net.xml file. I have defined separate forward (_fwd) and reverse (_rev) edges to enable bidirectional movement on my tracks, but I am encountering two main problems related to rail switching and routing.

I would greatly appreciate your guidance on the following two points:

1. Connection Creation and Validity:

I am attempting to define rail switches (connections) between the forward and reverse edges at the nodes (junctions) by editing the .net.xml file directly. I am setting the attributes as follows: dir="t" and state="O". However, the connection often does not appear to be valid, or vehicles cannot utilize the switch in the simulation environment, even after modifying the XML.

  • Could you please advise on the precise XML syntax or the minimum required set of attributes for correctly establishing a functioning rail switch connection between a _fwd edge and its corresponding _rev edge?

2. Routing Failure with duarouter/duaiterate:

When attempting to generate routes using duarouter (or duaiterate) with a set of defined trips (e.g., from="edge_fwd" to to="edge_rev"), the tool fails to find a valid path between the given origins and destinations.

  • What are the common configuration pitfalls in a rail network that prevent duarouter from finding a route, even when the bidirectional connections are defined in the network file?

Thank you very much for your time and support. The attached file is the current network configuration I am using.

Best regards,

Reza Bahmani

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

Back to the top