• 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. Quantus (Calibre) Interface

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 15272
  • 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

Quantus (Calibre) Interface

paulinho
paulinho over 3 years ago

I've done DRC and LVS in Calibre and want to use Quantus for extraction. I went to the menu Quantus->Run Calibre-Quantus and the below menu pops up. Is there any user manual which explains how this interface works and how to fill up the below shown form ?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    Yes, it's in the Quantus Extraction User Manual (which you can find by running <QUANTUSinstDir>/bin/cdnshelp and searching for "calibre"). There's also these two relevant sections on Cadence Online Support (the same manual):

    • Pegasus_and_Calibre_Inputs
    • Quantus UI and Calibre LVS Input

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • MaximX
    MaximX over 3 years ago

    Calibre LVS generates SVRF (binary) database.
    You need to run Calibre Query on SVRF to generate CCI (Calibre Connectivity Interface) or QCI (Quantus Connectivity Interface?) database - which is a bunch of files (agf - annotated GDS file, and several text files), equivalent to SVRF, but interoperable with downstream tools (parasitic extraction - QRC, StarRC, etc.), and located in "query output directory". This directory name / path is programmable (in Calibre Query script), and usually named "query_output", or/and can be located within SVRF directory.
    Calibre Query script is run right after / during LVS.
    CCI / QCI database is the input for parasitic extraction tools.

    Cadence LVS (Pegasus / PVS) generates a very similar database, called PVS, that is absolutely equivalent to CCI (same files, file extensions, content).

    This simple step / flow is absolutely fundamental for understanding of the custom IC design flow, but I have not seen a simple, clear, and concise explanation of this step anywhere (maybe Andrew's links provide such an explanation).

    • 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