Possible fix for error in detecting m2.5 DRC rule #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @laurentc2 ,
First of all, thanks a ton for your cool script!!
I happen to notice that there is a bug in detecting m2.5 DRC error. In first scenario, the error won't go even after providing proper enclosures to the via as argument to .width() is 0.14. Since minimum width of via is 0.15um, polygons would never be created and always .not_interacting would highlight the via as a DRC violation.
Even after changing this argument from 0.14 to 0.15, I noticed that there were some cases where the code wouldn't highlight the via during an actual DRC violation. Please have a look at the attached excel file for more details on this. Hence I suggest a small fix for this issue.
Looking forward to hear your thoughts on same :)
Thanking you,
Vishal
Before correcting 0.14um
After correcting 0.14um
DRC script fix explanation.xlsx