New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need some help figuring out what's wrong with this marker database #1550
Comments
Hi @donn, thanks for the nicely prepared test case. I could see the effect you describe, but it looks consistent to me: But for me it works nicely .. it jumps to the box marker. For reproduction here is my configuration: Another question is how you generated it. I guess it has been made from edges that got expanded, while the other database features edge pairs. Can you describe the script that generated this marker? Matthias |
The script is public: https://github.com/efabless/openlane2/blob/main/openlane/common/drc.py For example, this Magic DRC report, which lists rules and bounding boxes:
Would become this KLayout Marker Database: <report-database>
<cells>
<cell>
<name>RAM8</name>
</cell>
</cells>
<categories>
<category>
<name>LU.3</name>
<description>P-diff distance to N-tap must be < 15.0um (LU.3)</description>
</category>
</categories>
<items>
<item>
<cell>RAM8</cell>
<category>'LU.3'</category>
<visited>false</visited>
<multiplicity>1</multiplicity>
<values>
<value>box: (17.990,21.995;18.265,22.995)</value>
</values>
</item>
<item>
<cell>RAM8</cell>
<category>'LU.3'</category>
<visited>false</visited>
<multiplicity>1</multiplicity>
<values>
<value>box: (20.905,22.935;21.575,22.995)</value>
</values>
</item>
<item>
<cell>RAM8</cell>
<category>'LU.3'</category>
<visited>false</visited>
<multiplicity>1</multiplicity>
<values>
<value>box: (18.535,21.995;18.795,22.635)</value>
</values>
</item>
</items>
</report-database> (You will notice the multiplicity is wrong- I fixed it in another branch but it doesn't appear to have any bearing on this functionality) |
Thanks for pointing to the script ... however, I still don't see the issue on my installation (0.28.13, Ubuntu 22). To further debug the issue, you could try to export the markers ("File" menu in the marker browser). If you export them to a Layout and they do not show up as shapes, something is wrong with the way they are read and not with the way they are handled in the browser. Matthias |
I have two marker databases- one generated by KLayout (for another design) and provided by a colleague, and one that is manually converted from Magic using a script.
The one from my colleague works fine:
…but the one I generated simply refuses to show a bounding box for the markers when clicked:
Not really sure what's going on there.
I've attached a reproducible for convenience: to get this design and both marker databases, unpack it and run:
repro.tgz
The text was updated successfully, but these errors were encountered: