• 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. Difference results when re-run placedesign

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 90
  • Views 15029
  • 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

Difference results when re-run placedesign

archive
archive over 19 years ago

I've got every time a difference result when I ran placedesign (related to congestion) after I've changed some power grid even though the same placementguides have been used.
My question is how can I specify the startpoint  (sheetfactor ??? ) so that the placedesign should start at the same point.

Thanks.


Originally posted in cdnusers.org by DN
  • Cancel
Parents
  • archive
    archive over 19 years ago

    Thanks for your quickly reponses!

    I know that several factor will involve that cause diffrence in result but I'm 
    using the same options, same guides, same netlist,... from the previous run.
    And it looks like the congestion is changing every time because some modules
    are placed in an another areas.
    The result has not much impact for the timing in generally. But for a high frequent design when a little bit change of congestions can harm the timing clean on some critical paths.
    For more details what I've used:
    - cadence_fe 04.20-s315_1_USR2
    - Hierarchy netlist
    - Timingdriven
    - nopreplaceopt
    - noreordescan

    Regards,


    Originally posted in cdnusers.org by DN
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 19 years ago

    Thanks for your quickly reponses!

    I know that several factor will involve that cause diffrence in result but I'm 
    using the same options, same guides, same netlist,... from the previous run.
    And it looks like the congestion is changing every time because some modules
    are placed in an another areas.
    The result has not much impact for the timing in generally. But for a high frequent design when a little bit change of congestions can harm the timing clean on some critical paths.
    For more details what I've used:
    - cadence_fe 04.20-s315_1_USR2
    - Hierarchy netlist
    - Timingdriven
    - nopreplaceopt
    - noreordescan

    Regards,


    Originally posted in cdnusers.org by DN
    • 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