-
Notifications
You must be signed in to change notification settings - Fork 385
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
Klayout DRC integration #1702
Comments
I am more interested in the long term solution, as OL isn't the only tool facing this issue. I think we should put requirements in open_pdks for the interfaces with the DRC deck. This will involve fixes in both decks we have now (sky130 and gf180mcu), and precheck. For sky130, the only actual interface with the deck is in precheck, which is a python script that calls the deck, but it is very specific for precheck. we should probably start by listing the difference in interfaces we have now, then come up with requirements for the current and future decks. |
FYI - @proppy |
@proppy are you doing similar work ? |
Fixed by #2059 |
Description
Processes/PDKs have varying methods for defining their klayout deck(s) and different ways to invoke them.
Proposal
Just some ideas:
A long term solution would be requesting a specific interface from a PDK.
A short term solution would be having an OL wrapper per PDK.
The text was updated successfully, but these errors were encountered: