Home > Community > Forums > Digital Implementation > Choice of default extraction mode and detailed extraction mode

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 Choice of default extraction mode and detailed extraction mode 

Last post Tue, Jan 2 2007 10:33 AM by archive. 1 replies.
Started by archive 02 Jan 2007 10:33 AM. Topic has 1 replies and 1196 views
Page 1 of 1 (2 items)
Sort Posts:
  • Tue, Jan 2 2007 10:33 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    Choice of default extraction mode and detailed extraction mode Reply

    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
    • Post Points: 0
  • Tue, Jan 2 2007 11:00 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Choice of default extraction mode and detailed extraction mode Reply

    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
    • Post Points: 0
Page 1 of 1 (2 items)
Sort Posts:
Started by archive at 02 Jan 2007 10:33 AM. Topic has 1 replies.