• 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. Custom IC Design
  3. Short-resistor removal for LVS cleaning (Cadence Virtuoso...

Stats

  • Replies 2
  • Subscribers 130
  • Views 833
  • Members are here 0

Short-resistor removal for LVS cleaning (Cadence Virtuoso + Pegasus)

yogeshjaiswalCAD
yogeshjaiswalCAD 1 month ago

Greetings Team,

 

Thanks for always being there for help, I am working on TSMCN22 node, facing issue in Pegasus LVS cleaning as it not truncates shorted rupolym

Resistor (Plus & Minus) shorted

 

Cadence Virtuoso + Pegasus

Short-resistor removal for LVS cleaning

Best practice: device-level LVS filtering

 

Recommended (ONE-LINE SOLUTION)

 

lvs_filter_device rupolym -short_pins [PLUS MINUS]

 

What this does

  • Applies to Pegasus LVS + extraction
  • If a rupolym resistor has PLUS and MINUS on the same net:
    • X Device is removed from LVS
    • X Device is removed from spi
  • Layout geometry remains → DRC unaffected

This is the official Pegasus mechanism for shorted passives, When I am using above option to Pegasus- LVS run is taking lot of time (almost 15hour on IP) without above option is it will take on half hour to run.

Request : Please provide PVL code or any other advice or trick to remove shorted resistor rupolym in pegasus  LVS process 

Please suggest to me what option needs to be checked or selected in the Pegasus LVS option tab. 
I will be grateful for your help. Please help in !

With Warm Regards,

Yogesh Jaiswal

 

  • Cancel
  • Sign in to reply
Parents
  • pchris
    pchris 6 days ago

    Hi Yogesh,

    Two thoughts here:

    1. Your use of lvs_filter_device looks correct apart from teh syntak needing a small tweak. I quickly tried with a simple TSMC N22 example and used:

                        lvs_filter_device rupolym -short PLUS MINUS

    I see the devices filtered in the Statistics section of the <report_name>.cls file for cell in question. You can also get a summary of what has been filtered by adding lvs_report_opt -filtered_devices. This writes a report file in the run directory <report_name>.cfr.

    2. From your description though the drastic increase in run time you report should be looked at, for this please file a support case at  https://support.cadence.com/

    Best regards,

     

                   Chris

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • pchris
    pchris 6 days ago

    Hi Yogesh,

    Two thoughts here:

    1. Your use of lvs_filter_device looks correct apart from teh syntak needing a small tweak. I quickly tried with a simple TSMC N22 example and used:

                        lvs_filter_device rupolym -short PLUS MINUS

    I see the devices filtered in the Statistics section of the <report_name>.cls file for cell in question. You can also get a summary of what has been filtered by adding lvs_report_opt -filtered_devices. This writes a report file in the run directory <report_name>.cfr.

    2. From your description though the drastic increase in run time you report should be looked at, for this please file a support case at  https://support.cadence.com/

    Best regards,

     

                   Chris

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Children
  • yogeshjaiswalCAD
    yogeshjaiswalCAD 6 days ago in reply to pchris

    Greetings Chris,

    Thank you for always being there to help! It really means a lot to me that you take time out of your busy schedule to respond.

    I am able to solve my problem with the help of some of your excellent articles, which guided me in the right direction.

    Once again thanks for warm gesture

    Have a pleasant day!

    Cheers & regards,

    Yogesh Jaiswal 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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.

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

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