There is also a known issue where bidirectional deadlock may occur under specific circumstances (https://github.com/eclipse/sumo/issues/7078). If you can provide a small error scenario I can take a look.
Am Mi., 29. Juli 2020 um 09:27 Uhr schrieb Harald Schaefer <fechsaer@xxxxxxxxx>:
Hi Joshua,
you can start sumo with the option --railsignal-block-output
FILE.
This gives you a list showing the extend of driveways (the
railroader would say routes) starting at this signal and their
protection requirements (e.g. flank protection).
The signal goes to red, if other trains are on the required
edges/lanes.
Here is an example for signal s22 from
tests/sumo/rail/tramwayLoop/net.net.xml
Might be analyzing this file helps you to find the issue.
You can than try to add more signals or flank protection switches
in your network.
Regards Harald
Am 28.07.20 um 22:26 schrieb Harald
Schaefer:
Hi Joshua,
can you provide a small example?
In the rail signal implementation is some logic to prevent
collisions.
Regards, Harald
Am 28.07.20 um 22:01 schrieb Issa,
Joshua:
Hello,
I am wondering about how to modify rail
signal behaviour. Currently, I am running a bi-directional
rail simulation, but on occasion the rail signals will
essentially shut down and not let any trains pass.
Specifically,
in a junction like this, there will be occasion when two
out of three lanes are occupied, but the third is not an
option to travel to.