coriolis/crlcore/etc/symbolic/vsc200
Jean-Paul Chaput 1a338f620c Corrections in the Dijkstra global routing (ripup) mechanism.
* Bug: In Anabatic::Dijkstra, the degree of a vertex (the number of neighbors
    belonging to the same net) was miscalculated. This was leading, in the
    materialize step to some feed-through vertexes not being broken.
    Leading in turn to incomplete transformation of the detailed routing.
      Also in _trackback(), the degree of the first vertex we were backtracking
    from was not incremented.
* Bug: In Anabatic::Dijkstra::materialize(), systematically use
    GCell::breakGoThrough() on both source and target. This is needed when
    we are in the ripup phase as both source and target can be go-through.
      This was also leading to incomplete detailed routing transformation.
* Change: In Anabatic::Edge::ripup(), ripup one third of the segments instead
    of thoses exeeding the global length threshold. This way we are sure to
    desaturate an edge. Needs to be further calibrated.
* Change: In Aanabatic::GCell::breakGoThrough(), no longer return NULL.
    Return existing gcontact if any. Break if it is a go-through and create
    a new gcontact in last resort. Maybe rename this function.
* New: In Anabatic::Configuration, new parameters:
    - anabatic.edgeHScaling, to adjust the length of the horizontal edges
        relative to the vertical ones (this is a ratio).
    - anabatic.globalIterations, set the maximum number of ripup passes
        of the global router.
* New: In CRL/etc/*/kite.conf, added new parameters anabatic.edgeHScaling
    and anabatic.globalIterations.
* New: In Katana::GlobalRoute::DigitalDistance, take into account the new
    edgeHScaling factor. Must be used when the capacity of V-edges differs
    greatly for H-edges (case of AMS 350nm c35b4 for instance).
* Bug: In Katana::GlobalRoute::DigitalDistance, the historic cost is
    computed for an edge length of "1". Must be multiplicated by the
    current edge length to have any measurable effect.
      This bug is finally explaining why the ripup was producing the
    same solutions over and over, the historical cost was negligible!
2018-04-16 12:10:48 +02:00
..
alliance.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
display.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
etesian.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
hMetis.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
kite.conf Corrections in the Dijkstra global routing (ripup) mechanism. 2018-04-16 12:10:48 +02:00
mauka.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
misc.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
nimbus.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
patterns.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
plugins.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
stratus1.conf New DataBase::getCell() and bug in Technology::getNthMetal(). 2017-11-17 10:54:19 +01:00
technology.conf Cleaner support for real technologies (Hurricane, CRL Core configuration). 2017-12-27 13:13:29 +01:00