• 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. Via count details

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 14358
  • 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

Via count details

archive
archive over 17 years ago

    Hi,
       I am trying to get the via count details by using some of the scripts (userRptViaStats.tcl)  provided by cadence in gift directory ( installation area), but i am getting a different  count when i use the script when compared to the count that i have in the log file.
    If any one has some information of how to get the details of via count using any command or using any script, please let me know.


thanks
deepak.


Originally posted in cdnusers.org by deepak
  • Cancel
Parents
  • archive
    archive over 17 years ago

    For the benefit of others that might happen upon this thread, I thought to mention a couple of other public commands that are available to query via statistics on a routed design.

    First is "reportRoute". It reports via statistics like this:

    Total length: 6.990e+04um, number of vias: 14605
    M1(H) length: 2.278e+03um, number of vias: 6394
    M2(V) length: 2.323e+04um, number of vias: 5930
    M3(H) length: 2.430e+04um, number of vias: 1768
    M4(V) length: 1.271e+04um, number of vias: 433
    M5(H) length: 5.234e+03um, number of vias: 80
    M6(V) length: 2.153e+03um

    Note that as of 7.1, reportRoute and userRptViaStats.tcl do *not* break out multi-cut vias in their reporting.

    Another command to consider, especially if you're interested in multi-cut via usage is the "reportYield" command. reportYield generates information about yield (ie, Design For Manufacturing) and includes information about multi-cut via usage:

    Via
    ===
    Layer | Number of Vias | Cost | Total
    | 1-cut 2-cut Array | 1-cut 2-cut Array | Cost
    via12 | 1.6100e+03 4.7840e+03 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    via23 | 1.4300e+02 5.7870e+03 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    via34 | 3.0000e+00 1.7650e+03 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    via45 | 0.0000e+00 4.3300e+02 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    via56 | 0.0000e+00 8.0000e+01 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    -------|----------------------------------|----------------------------------|-----------
    total | 1.7560e+03 1.2849e+04 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00

    Be aware that reportYield requires a yield technology file. If you're primarily interested in using reportYield to obtain multi-cut via information, you can create a quick/default yield technology file like this:

    reportYield -createYieldFile myYield.file
    reportYield -yld myYield.file
    ->write .dfm.rpt to your current directory which contains the via statistics

    Be aware that reportYield requires a GXL license.

    Thanks,
    Bob


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

    For the benefit of others that might happen upon this thread, I thought to mention a couple of other public commands that are available to query via statistics on a routed design.

    First is "reportRoute". It reports via statistics like this:

    Total length: 6.990e+04um, number of vias: 14605
    M1(H) length: 2.278e+03um, number of vias: 6394
    M2(V) length: 2.323e+04um, number of vias: 5930
    M3(H) length: 2.430e+04um, number of vias: 1768
    M4(V) length: 1.271e+04um, number of vias: 433
    M5(H) length: 5.234e+03um, number of vias: 80
    M6(V) length: 2.153e+03um

    Note that as of 7.1, reportRoute and userRptViaStats.tcl do *not* break out multi-cut vias in their reporting.

    Another command to consider, especially if you're interested in multi-cut via usage is the "reportYield" command. reportYield generates information about yield (ie, Design For Manufacturing) and includes information about multi-cut via usage:

    Via
    ===
    Layer | Number of Vias | Cost | Total
    | 1-cut 2-cut Array | 1-cut 2-cut Array | Cost
    via12 | 1.6100e+03 4.7840e+03 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    via23 | 1.4300e+02 5.7870e+03 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    via34 | 3.0000e+00 1.7650e+03 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    via45 | 0.0000e+00 4.3300e+02 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    via56 | 0.0000e+00 8.0000e+01 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00
    -------|----------------------------------|----------------------------------|-----------
    total | 1.7560e+03 1.2849e+04 0.0000e+00 | 0.0000e+00 0.0000e+00 0.0000e+00 | 0.0000e+00

    Be aware that reportYield requires a yield technology file. If you're primarily interested in using reportYield to obtain multi-cut via information, you can create a quick/default yield technology file like this:

    reportYield -createYieldFile myYield.file
    reportYield -yld myYield.file
    ->write .dfm.rpt to your current directory which contains the via statistics

    Be aware that reportYield requires a GXL license.

    Thanks,
    Bob


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