• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. detailRoute vs trialRoute

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 90
  • Views 14241
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

detailRoute vs trialRoute

Rajesh Vembu
Rajesh Vembu over 15 years ago

Is there a way to report the differences/ratio of detail route vs trialroute net wirelengths?

Currently reportWire command reports the ratio of detailRoute vs half-perimeter net wirelengths. However, if trialRoute statistics were also included in this, it would be great.

 Are the net lengths stored as part of the net object in encounter? 

  • Cancel
Parents
  • Rajesh Vembu
    Rajesh Vembu over 15 years ago

     Bob,

    Thanks for the script.The only limitation in the script is that trialRoute and detailRoute wirelengths have to be computed in a different databases.If the netlength information is stored as part of net object, we can query it easily.

    Here are some reasons, i feel, why we should have a trialRoute vs detailRoute comparison

    1. In case of multi-fanout nets half-perimeter lengths are way-off compared to the detail route. Trial route might be a good indicator as it is based on steiner route.

    2. Since all the optimizations are based on trialRoute information, it would make sense to have a correlation between trialRoute and detailRoute readily available.

    3. Does layer assignment happen while calculating half-perimeter net lengths?

    If net lengths are not stored as part of net object, does it mean reportWire calculates the wirelength (both detail and half-perimeter) everytime it is invoked. For a larger design with millions of nets this could have a big runtime hit.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Rajesh Vembu
    Rajesh Vembu over 15 years ago

     Bob,

    Thanks for the script.The only limitation in the script is that trialRoute and detailRoute wirelengths have to be computed in a different databases.If the netlength information is stored as part of net object, we can query it easily.

    Here are some reasons, i feel, why we should have a trialRoute vs detailRoute comparison

    1. In case of multi-fanout nets half-perimeter lengths are way-off compared to the detail route. Trial route might be a good indicator as it is based on steiner route.

    2. Since all the optimizations are based on trialRoute information, it would make sense to have a correlation between trialRoute and detailRoute readily available.

    3. Does layer assignment happen while calculating half-perimeter net lengths?

    If net lengths are not stored as part of net object, does it mean reportWire calculates the wirelength (both detail and half-perimeter) everytime it is invoked. For a larger design with millions of nets this could have a big runtime hit.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information