When PATHSAMPLE finds a connected path, but using DIJKSTRA 0 fails to find the connected path

If your PATHSAMPLE runs has finished with a connected path found, running DIJKSTRA 0 to calculate the rates of this path can sometimes fail by outputing that there is no connection between the A and B regions. How intriguing right? This can happen for long paths and/or high barriers, and some rate constants have been rounded to zero. (ref. David :) )

One way to circumvent this is raising the TEMPERATURE keyword in the pathdata file to increase all the rates.

Hopefully this will help solving the issue, and a suggestion afterwards is to use SHORTCUT to get rid of these high barriers!