• 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. Choice of default extraction mode and detailed extraction...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 90
  • Views 13164
  • 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

Choice of default extraction mode and detailed extraction mode

archive
archive over 18 years ago

Hi,

I wish to hear from you your choice of default extraction mode and detailed extraction mode from placement to post-cts optimization.

The default Encounter flow is:
Start to pre-CTS : default extraction
CTS to pre-detailed routing : clock nets detailed extraction.  The  other use defualt extraction.

Do you see advantages in switching to detailed extraction during placemet and CTS, and run optDesign with detailed extraction ? (Just in case you are not aware, there is an undocumented swith to make optdesign use detailed extraction (setOptMode -useExtractRCModeSetting).

I am assuming that both RC factor for default extraction and detailed extraction are properly obtained from running Ostrich. I was told that it is okay to follow the default flow for 0.13um or larger process, but should use detailed extraction for nanometer process. I am not sure about this.

Regards,
Eng Han


Originally posted in cdnusers.org by EngHan
  • Cancel
  • archive
    archive over 18 years ago

    my comments

    It depends how long do you are willing to wait for the run to finish. Regardless of default or detail mode, SOCE extraction only co-related less than 70-80% of nets (worst for default mode) as compared to signoff tool (StarRC or QRC). For setup check you could try to increase the multiplier to compensate for it, but for Hold time you are out of luck. SOCE (both default & detail) extraction is very inaccurate in small cap (parallel & xtalk cap) thus created a lot of problem in post route xalk hold check.

    for PreCts opt, the routing is not done yet, so default is as good as detail mode. You will save some run time using default mode. For postCts since the clk nets are routed, detail mode for clk nets make sense. For postRoute, you really want to use a signoff extraction flow so as to reduce the margin you put on SOCE to fix both setup & hold time.

    li siang


    Originally posted in cdnusers.org by lisiang
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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