Index: TRBS/trbs.html =================================================================== --- TRBS/trbs.html (revision 536) +++ TRBS/trbs.html (revision 537) @@ -35,7 +35,13 @@ coordinates of the 2nets are not considered, only the order of 2nets crossing triangulation edges.

-TODO: img tri.lht +

+


 
  +

trianglulation +

Figure 1: triangulation; grey lines are triangle edges; yellow lines + are three 2nets to route +


 
  +

Furthermore each 2net has a required geometry (wire thickness and clearance), and edges have physical lengths. Local congestion is avoided by @@ -49,7 +55,13 @@ to physical geometry, introducing new edges (spokes) and moving the 2net-edge crossing points on the edge without changing the order of them.

-TODO: img 3net.lht +

+


 
  +

three nets routed +

Figure 2: three networks routed; first the two horizontal ones then + the vertical one +


 
  +

This document focuses on the TRBS step. @@ -119,7 +131,13 @@ endpoint are the same. Main input is the enter point or vertex. Other input is a target edge or target vertex within the same triangle.

-TODO: passthru1 +

+


 
  +

in-triangle visibility algorithm +

Figure 3: edge-to-edge visibility in a triangle; annotations are + drawn with red, existing paths with blue +


 
  +

In case of target edge, the output is a point on that edge (which topologically means the index on the edge's crossing list, where the new crossing is to be @@ -128,8 +146,6 @@

The algorithm for determining visibility is:

-TODO: image passthru1 -