Check distance between obstacles for narrow bottlenecks.
Sometimes agents get stuck in front of corridors.
Reason: the global minimum (within walking distance) is in front of the corridor.
The smaller the corridor, the more likely is it that agents get stuck.
One option is to adjust the attributes of the floorfield, in particular, the parameter targetAttractionStrength.
See AttributesFloorField for details.
To make users aware of this problem I extended the scenario checker. It gives a warning if obstacles have a distance less 1.28m. If obstacles are connected, the distance is 0. If so, the scenario checker does not produce a warning, see example below.
The agent A is stuck in front of the corridor. The target T is on the right. Left: the bottleneck is identified. A user warning is produced including the distance c. Right: no warning is produced.