-
Notifications
You must be signed in to change notification settings - Fork 63
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
NW.b violation when two ebufn_2 abutt themselves #246
Comments
And as a side note, that rule isn't checked by the DRC deck. |
@b10346 additional hint Other cells: |
yes, the rule |
I added this locally, which does report those errors, but given it's mostly just a cut&paste of similar rules in --- sg13g2_maximal.lydrc 2024-10-30 10:51:23.044619042 +0000
+++ sg13g2_maximal_nwb.lydrc 2024-10-30 10:51:09.123354890 +0000
@@ -1613,6 +1613,9 @@
NWell_NW_a.dup
end.().output("NW.a", "Min. NWell width = 0.62")
-> do
+ NWell.ext_fast_space(0.62.um, consider_intersecting_edges: false, ignore_non_axis_aligned_edges: true)
+end.().output("NW.b", "Min. NWell space or notch = 0.62")
+-> do
NWell.ext_fast_separation(NActHV_ana, 0.62.um)
end.().output("NW.d1", "Min. NWell space to external N+Activ inside ThickGateOx = 0.62")
-> (;x, y) do |
Yes, as a temporary fix, you can implement the rule like this. However, the rule should only look at connected polygons – that's why we haven't implemented it, yet. |
FYI, #247 |
See attached image.
The rule is 0.62 min, but with two ebufn_2 cells next to each other you get 0.42. And actually if one of them is in the other orientation it can get down to 0.345.
The text was updated successfully, but these errors were encountered: