dick_freebird
About
- Username
- dick_freebird
- Joined
- Visits
- 1,181
- Last Active
- Roles
- Member
Comments
-
Maybe a version incompatibility, or a sub-dependency of 'xcb' that is unsatisfied? There's a jumble of Qt4. Qt5 out there as I make it out, and if you've pulled from various sources, may have some sorting out to do?
-
What if you extended your script to add (bearing in mind that my advice on scripting is not knowledge based) a 'foreach' that runs through all the "not_the_target" layers and outputs them all as-was? Maybe it needs a "null operation&q…
-
Would "print to PDF" (using one of the PDF viewers) do the job if you set the DPI option appropriately? And maybe paper size as well, if it's breaking into multiple pages? You should tell us more about why you "need to" use PDF…
-
I prefer a (well constructed) PDF manual for reasons such as a "search window" and linear document that you don't have to bounce between pages up / down to navigate, the navigation pane is handy if headings are harvested to support that…
-
I have found the move, duplicate commands' action awkward, most especially the loss of selection if you don't click exactly on the selected item(s) - then that point is taken as reslect / deselect. It would be preferable to me if the selection befo…
-
To me the "Manage Technologies" and dependents, are the PDK more or less, only "disaggregated", more of a list of pointers and settings. I could see some value to making a flat-file image from a golden technology-settings, buil…
-
In my experience (plenty, but largely trailing-edge) the layers don't change much (or at all) even when there's a lot of PDK "churn". I believe there's some facility for importing Cadence PDKs already (how completely, do not know, but be…
-
I have never seen such a rule, although it's in the category of "why wouldn't you?". In my world however the design of fat bussing proceeds from analysis of current density for reliability, and ohmic drops for parametric performance lea…
-
If you have set up a "Technology" then the name / path for the .lyp is one of the entries in the forms. Technology choice is "sticky" so should autoload until you change technologies or somehow lose the remembered settings.
-
In my opinion the answer is to insist on simplicity, let it be stupid as long as it has the functions that are needed to start, stop and scale the vertical axis (would side-diffusion be out of the question?) to build the third dimension and slice …
-
Is GDS-II even capable of dealing with circles (in form of center, radius)? I thought circles were all N-sided polygons, once you get to GDS-II data (or in some CAD universes, even in the native data structure).
-
(Quote) That looks to me like 2.5Gb (at 1 bit per pixel), which is kind of chubby for an image file. It might be overflowing some limit in a png->tiff conversion script? That's one way to get a null .tif file I reckon - just give up for files…
-
Maybe looking at the sequence of events in interactive would help? Even more so, if there were an output log that puts the commands executed, out in Ruby or Python syntax. (Layers) show only selected Select All (Layers) pick target layer (Edit>…
-
Is there no way to force a "reload"? In other tools I've seen "trigger all callbacks" or "refresh" but not always easy to find. Or maybe you have to close the script editing session and reopen it from within the exist…
-
Of course the simple example layout shown would be easier to measure, count and calculate than to code the infrastructure....
-
Tungsten plug vias can dominate net resistance. Don't know if parasitic R extract deals with vertical via resistance or only in-layer l/w*Rs. If not then you may need to make the via a "device" that will cough up the R. Breaking one net in…
-
I don't know what your desired, or your technology proper DBU may be. When I see this: (100, 333.33333333333337), (100, 166.66666666666669) I have to wonder whether you're asserting a number with precision beyond your DBU, and it's displayed at D…
-
I personally favor an all-markers approach where every device that's placed intentionally, incorporates a unique marker in its PCell which the extract deck uses to make the "recognition call" (backed up by a "recognizer" for devi…
-
Is the problem that, in a system where "contact" could stop on either P2, P1 or Active, that there is no logic that says -which-? That is, looks like contactP2, and contactP1 would both be valid as written, maybe there should be (contact…
-
It still bothers me that there is no logic to recognize the device itself. The terminals, OK. But terminals of what? I see where you assign the model name "arbitrarily". Maybe it's just that I'm used to working in bipolar technologies whe…
-
If space is exactly 0.001, and snap is 0.001, does that leave it "nothing to do"?
-
Those were my attempt to explain how I do things. If they were klayout functions, they might be useful but I also anticipated some risky behaviors (such as a 45 turning into a not-exactly-45 due to rounding errors or something like that). Or circ…
-
If they are truly so closely spaced that they would flag the generic rule (which I know can be absurdly large - I've seen 50um on a 180nm process) and truly at same potential, why not just bridge the gap with more NWell and make it all one piece?
-
Another thought - I see the extraction of connectivity, but isn't there some need to "recognize" the device as such? I don't see logic for that (what makes the NPN an NPN, to the extraction?). In more elaborate kits and tools I'm used…
-
Can you somehow display each of those logical layers that you are outputting, and see whether any of them are not giving you what you think? Maybe one is "malformed" and breaking the device extraction?
-
Your collector contact should be the stack of contact, Nplus, Nwell, buriedN. You do not have the N+ and contact in your logic. It's possible that contact to NWell could be a Schottky contact depending on surface doping unless you impose N+. Also (c…
-
Because of such behaviors I often find it better to "over-stretch" the polygon, and use an on-grid "cutter" shape with "Subtract, others from first" to shave off any off-grid "material".
-
If you want to touch only one point, I believe Partial (stretch) will move a vertex to the next grid-snap by hand. Not sure about multiple-selected vertices, you would have to play to see whether it does what you want. A "snap all vertices to …
-
Are merged polygons maintained as separate objects in some sort of "bundle", that you could do this? I thought the merged-object replaces its constituents. And if this is the case, can a merged-polygon be un-merged back to its original…
-
Punching through multiple metal layers would normally be a thing to avoid by process construction. You stop oxide etch on the first metal it hits and stop metal etch on oxide or silicon, in "normal" silicon processing. Vias normally are h…