Can KLayout open LVS result file which generated by Calibre LVS now?


KLayout can open DRC result file generated by Calibre DRC.

But when I try to open LVS result file produced by Calibre LVS using "Marker Browser" or "Netlist Browser“, I get an error.

I noticed a post several years ago said that klayout cannot open calibre LVS file .

I wonder can Klayout support opening LVS result file produced by Calibre LVS now?
Thank you in advance.

Best regards!


  • No, sorry. KLayout can't do that.

    To my knowledge the LVS format is not disclosed and can therefore not be implemented in Open Source software.


  • edited June 2022

    I don't know about "big boy" Caliber, but I have been
    provided Caliber DRC output that's near human readable
    (if you like mangled English and raw coords / arbitrary
    device & node naming) from a foundry that uses the
    "Lite" version bundled with old Tanner versions.

    Wonder if some "full retail Caliber" user could look at
    report options, maybe there remains one that does not
    need Caliber to read reports and yet provides workable
    raw info.

    Here's what "baby Caliber" can deliver for DRC:

    // L-Edit_Violation_Distance 2203
    50236 35835 52797 35104
    55000 34828 55000 40513
    e 27 2 LPNP_DonutX4 c
    // L-Edit_Violation_Distance 2203
    35104 52797 35835 50236
    40513 55000 34828 55000

    Wonder what a LVS report looks like, from "big boy
    Caliber". My chip design was small enough that I
    just went at it "80's style" with blue pencil, red pencil.
    It's clean and shipping but I have nothing to share from
    my caveman LVS that's of any value.

    I've asked a guy I've worked with to look for examples
    of human-readable Caliber LVS reports from the Tanner
    version, maybe "real Caliber" users can check into the
    report options available from their setup.

  • edited June 2022

    I'm not an expert on Calibre formats (and I should not be), but to my knowledge the LVS results are much different from the DRC results. LVS delivers a binary database as far as I know while DRC database files are plain text and easy to read.


  • By the way, if the klayout lvsdb file that results from a KLayout LVS could be read by XSCHEM to find the correspondence between schematic and layout, it would be great :smiley:


  • @Matthias

    Ok, thank you for your answer, I got it. I think the reason is I don't get the right way to access it before.

  • edited July 2022

    Thank you for your respond. I don't really know what is "baby Caliber".

    But here is a lvs report, some individual information has been replaced by xxx.

    (klayoutadmin deleted content)

  • edited July 2022


    (klayoutadmin deleted content)

  • @laurent_c,

    We can look forward to it together. :)

  • When I say "baby Caliber", that's a limited version which
    was bundled with Tanner L-Edit. Later on a more capable
    (and much, much more expensive) version became part
    of the Mentor / Synopsys tools set, proved itself more capable
    of very large digital designs and pretty much took over as the
    "Golden verification suite" at foundries. Mostly DRC, but in
    my case Tanner (and components) are -the- tool set for a
    small foundry, and until I can get a klayout extract deck
    together my only choice is to play "over-the-transom
    badminton" with the inside-foundry layout guy where he
    calls 'em and I squash 'em, and a "do-while loop" that
    takes a day per attempt.

    So my need is actually around the "baby Tanner" but the
    big picture for klayout covers a lot more foundry-engagament
    styles I am sure.

  • @dick_freebird,

    Thank you for your detailed explanation. I may understand you what you mean.

  • @Weiling_Zheng The above is just Calibre report. That's not the database. Also, I advise you to remove this as I believe that's a violation of software terms.

  • Valid point. I have deleted these documents to avoid potential conflicts. Thanks for mentioning this.

  • Calibre LVS database (svdb) is proprietary and binary.

    It can be converted to CCI (Calibre Connectivity Interface) database using Calibre Query Server.
    CCI database is an input for any standard parasitic extraction tool (StarRC, Quantum QRC, etc.).
    CCI database contains a bunch of text files (netlist, instance and net cross-reference, etc.), and an annotated GDS file - AGF file - that contains derived layers, net/connectivity info, etc. The structure of AGF file is the same as GDS file (with some useful annotations). It can be opened by Klayout or by any other GDS views/editor.

Sign In or Register to comment.