# Dijkstra algorithm

# Almost Shortest Path - weighted

Finding the shortest path that goes from a starting point to a destination point given a set of points and route lengths connecting them is an already well known problem, and it's even part of our daily lives, as shortest path programs are widely available nowadays.

Most people usually like very much these applications as they make their lives easier. Well, maybe not that much easier.

Now that almost everyone can have access to GPS navigation devices able to calculate shortest paths, most routes that form the shortest path are getting slower because of heavy traffic. As most people try to follow the same path, it's not worth it anymore to follow these directions.

With this in his mind, your boss asks you to develop a new application that only he will have access to, thus saving him time whenever he has a meeting or any urgent event. He asks you that the program must answer not the shortest path, but the almost shortest path. He defines the almost shortest path as the shortest path that goes from a starting point to a destination point such that no route between two consecutive points belongs to any shortest path from the starting point to the destination.

For example, suppose the figure below represents the map given, with circles representing location points, and lines representing direct, one-way routes with lengths indicated. The starting point is marked as **s** and the destination point is marked as **d**. The bold lines belong to a shortest path (in this case there are two shortest paths, each with total length **4**). Thus, the almost shortest path would be the one indicated by dashed lines (total length **5**), as no route between two consecutive points belongs to any shortest path. Notice that there could exist more than one possible answer, for instance if the route with length **3** had length **1**. There could exist no possible answer as well.

#### Input

Contains several test cases. The first line of a test case contains two integers **n** (**2** ≤ **n** ≤ **500**) and **m** (**1** ≤ **m** ≤ `10`

), indicating respectively the number of points in the map and the number of existing one-way routes connecting two points directly. Each point is identified by an integer between ^{4}**0** and **n** – **1**. The second line contains two integers **s** and **d**, indicating respectively the starting and the destination points (**s** ≠ **d**; **0** ≤ **s**, **d** < **n**).

Each one of the following **m** lines contains three integers **u**, **v** and **p** (**u** ≠ **v**, **0** ≤ **u**, **v** < **n**, **1** ≤ **p** ≤ `10`

), indicating the existence of a one-way route from ^{3}**u** to **v** with distance **p**. There is at most one route from a given point **u** to a given point **v**, but notice that the existence of a route from **u** to **v** does not imply there is a route from **v** to **u**, and, if such road exists, it can have a different length. The last line contains two zeros and will not be processed.

#### Output

For each test case print a single line, containing **-1** if it is not possible to match the requirements, or an integer representing the length of the almost shortest path found.

7 9 0 6 0 1 1 0 2 1 0 3 2 0 4 3 1 5 2 2 6 4 3 6 2 4 6 4 5 6 1 4 6 0 2 0 1 1 1 2 1 1 3 1 3 2 1 2 0 3 3 0 2 6 8 0 1 0 1 1 0 2 2 0 3 3 2 5 3 3 4 2 4 1 1 5 1 1 3 0 1 0 0

5 -1 6