https://open-source-silicon.dev
Join Slack
Hello, I'm checking my design with Klayout DRC. Magic was printing `drc.rpt` file for DRC errors. Ho...
# openlane
y
Hello, I'm checking my design with Klayout DRC. Magic was printing 
drc.rpt
file for DRC errors. However, I could not find a similar report for Klayout DRC. My design completes the flow successfully, does that mean I don't have any design rule errors? Thank you.
m
yes
✅ 1
y
I've run both Klayout and Magic DRC, and runtime of Klayout was shorter than Magic. Why Klayout runs faster than Magic?
m
good question
my guess is that magic is doing more checks than klayout
as klayout DRC is done with python, so it would probably be slower if it was doing the same depth of checks
y
Now, I've run SKY130 DRC runset in standalone Klayout with the same GDS and it takes longer from the one in OpenLane flow but it is near to Magic flow. For comparsion, standalone Klayout > Magic DRC > OpenLane Klayout. Are the omitted checks unimportant or something else?
m
maybe @Tim Edwards can answer when he gets back from DATE / OSDA
t
@Matt Venn: I'm already back.
👋 2
y
I think there's wrong about Klayout flow, it prints nothing meaningful about design rule violations. I have GDS which could not pass Magic DRC but the same one does not produce any output in Klayout DRC. Only "DRC section Writing report database:" section is printed in terminal.
This is the printed database file, I think it does not produce any meaningful data about DRC. It looks empty. 
<?xml version="1.0" encoding="utf-8"?>
<report-database>
<description>SKY130 DRC runset</description>
<original-file/>
<generator>drc: script='/openlane/sky130A/libs.tech/klayout/drc/sky130A_mr.drc'</generator>
<top-cell>top</top-cell>
<tags>
</tags>
<categories>
</categories>
<cells>
<cell>
<name>top</name>
<variant/>
<references>
</references>
</cell>
</cells>
<items>
</items>
</report-database>
24 Views
Open in Slack
PreviousNext
Powered by

What is Linen?

Linen is a search-engine friendly community platform. We offer integrations with existing Slack/Discord communities and make those conversations Google-searchable.

Powered by