You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead, it would be great if the DRC script could be separated from the wrapper and simply included with # %include. This would make it possible to run the DRC scripts from within a Ruby or Python script. It is actually possible to run the .lydrc macro directly.
An example of how this works can be found in sky130.
There is one sky130A_mr.drc DRC script that is included in several .lydrc files:
I agree that a single DRC script would be better because it avoids code duplication. However, due to the way we generate the scripts, some major changes are required. Therefore, it is not a priority for us at the moment.
In the end, it is not so different than for sky130: We have two .lydrc files, they have three. Besides, you can already run the .lydrc scripts from Ruby and Python:
Currently, the DRC scripts are implemented using a
.lydrc
file, which is an XML wrapper around the DRC script: https://github.com/IHP-GmbH/IHP-Open-PDK/tree/dev/ihp-sg13g2/libs.tech/klayout/tech/drcInstead, it would be great if the DRC script could be separated from the wrapper and simply included with
# %include
.This would make it possible to run the DRC scripts from within a Ruby or Python script.It is actually possible to run the .lydrc macro directly.An example of how this works can be found in sky130.
There is one sky130A_mr.drc DRC script that is included in several
.lydrc
files:By setting the values of global variables, different DRC runsets can be enabled/disabled.
The same approach could be used to combine the
sg13g2_maximal
andsg13g2_minimal
DRC scripts into a single file.The text was updated successfully, but these errors were encountered: