-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add more Cnt rules #256
Add more Cnt rules #256
Conversation
@akrinke I figured out Cnt.g1 generates no violation. Can you take a look why it doesn't? |
Add three new DRC rules for Cont. Cnt.g1 currently doesn't work! Signed-off-by: Daniel Schultz <[email protected]>
Add test GDS file with violations to verify DRCs are actually working. This GDS file contains wrong Cont placements to trigger Cnt. rules. Additionally, add pytest tests to run klayout and verify the result. Signed-off-by: Daniel Schultz <[email protected]>
Add Tox as infrastructure to run various Python checks. For now, add pytest to run all DRC verification tests. Signed-off-by: Daniel Schultz <[email protected]>
6f2d296
to
b93ac74
Compare
@dnltz this |
Hi @dnltz, thank you for contribution! |
We have implemented new DRC rules in PR #259, including |
@sergeiandreyev ah, perfect they already exists. Thanks for pointing them out. @akrinke Yes I can do that :) |
More Cnt rules and a test GDS file to trigger violations. The file only contains Cont violations but can be extended in the future!
layout is drawn after the layout rules with each rule violating the requirements.