This is about the "Cells" window (alongside Layers et al) that
displays the layout hierarchy / cells list. While object copy /
paste affects the X-Y viewport (if enabled), the "Cells" copy /
paste affects the "Z dimension&qu…
IME the DBU comes from what your mask shop (or other lithography)
can deliver. I'm used to older nodes and 0.001um (1nm) has never
been close to a problem. But you might find that 20nm circles are a
little raggedy (ortho structures, less so).
Usu…
If I had a good "Make" setup I would do
the compile but I depend on spoon feeding
for that, I do not comprehend all the low
level setup stuff I see.
My interests include long term archival of
design tools alongside chip designs and
I am…
Right, the "package managers" seem to want -their-
style (though I don't rightly know whether (say) Red Hat
"rpm" would do the right thing if you pointed it at a Debian
.deb - I just try to pull the ones they say is "their …
Wonder whether this has to do with "Partial (move/stretch) being
"two for one" (select, and follow cursor) and maybe that selection
does not pay attention to modal setting (it's acting differently, on
different features).
Curious whe…
As a practical and business-protection matter, you should have
published a set of layout groundrules which your RDL process
can manufacture, and insist that a customer DB run clean to
some agreed-upon design rules check.
If you did your part and th…
Thanks Matthias. I will try out the import table.
My goal here is, like every PDK, to get a complete
and stable layer set and behaviors (not layers
that change with every layout I open, even in
the same Technology, because of content detail).
I …
Maybe a closer look at the differences in parameter value / style,
between the failing and succeeding PCell instantiations? The
error seems to complain about missing args / values?
Have you tried forcing the file extension so the browse "filter"
can "see" it?
Some Linux file browse popups seem to leave out the "All
Files (.*) option.
You have Round, Square, Flush and Variable extension
options in the Path popup. Square will make you a clean
end, but past where you click. Flush is what gives non-
ortho straight angles, where you click. No idea what is
Variable trying to do or …
Just a thought, but to me looks like there are too many vertices
and some make for kooky path generation.
Is it practical to use Partial to select one "don't need" vertex and
delete it? This seems to work for me, deleting a vertex leaves…
For reasons such as this, I use a pretty dark gray for a "black"
background which can still show "true black" features.
I think it's either #40 or #41 that I settled on.I also do the same
with the Linux desktop, Ubuntu's defau…
The only way I fix these is by overlaying a "filler" or "cutter"
polygon and doing a merge or subtract as appropriate.
I imagine that Partial could drag the path straight too.
You have some other, uglier ones to fix around the r…
Is there anything in all this, that depends on the "end type" setting
in the path creation? Obviously not "round", but maybe "square" vs
"flush"?
And then of course the whole Python-script vs menu-pick quest…
I tried "Clean Up Layer Entries" and it gave almost the
opposite of what I wanted. Rather than letting me combine
duplicates, it blows away all unused (though valid for masks)
layers, and leaves the duplicates untouched / unremarked.
Th…
I see this behind the Import panel
(Image)
Which perhaps defaults to importing -all- the layers -even if-
in the mapping table? I would like behavior to be "use existing, if"
and "create if not". But I can't say for sure what…
I'm having a different issue now (on the same project).
That is, I have an old process development wafer DB which
I am trying to harvest transistors off of, to modify. I have a
.lyp which has worked for me fine (created from scratch by
menu han…
I encountered the same thing again today (whilst not trying, and not-saved :( ). Over-enthusiastic mouse-wheel behavior, provoked by some unexpected lag in rendering.
It may just be a Windows thing, but it's still hiding in the woodwork of 0.28.7 …
Worth noting that, in most modern production, the "stepped object"
is the reticle field, and that is what's architected out of the "die
payload". Then you step -that-. The foundry usually (and always,
when multiproject) create…
I haven't seen much from Tracy since he got a "straight
job" quite a while back. I think he may pop in sparsely.
Sending him a message here might percolate at least
a notification to his "home" email.
My involvement with this …
I do notice that on my layouts, a text will "drive" the display
extent (so probably all computed extents) but will only do
so as far as the origin sits. Not the displayed width of the text.
Everything outboard of the origin (subject to dis…
Another suggestion which might work, is that I've seen that
the "Shapes Library" has a TEXT primitive PCell. I have not
really dug into that, but since it's probably all Python-y in
its guts perhaps it plays nice with scripting and could b…
Just on the off chance that you haven't jumped up to humor
me just yet, here is another stab at "masked selection" (sorta)
which might solve the "stuff gets moved for being selected by
mistake".
That is, in the instance propert…
Not sure about DRC, but there is "a thing" about the default text
font not scaling (the others all do). You might want to look at
asserting one of the other fonts, as a start?
I made my own layertables from paper sources, to
save as .lyp - this is essential in any case, if you mean
to keep working in a consistent environment. There you
can add the human readable names if you like.
I use the Technology just to make them e…
OK, that's understandable I guess.
Let me suggest some things.
Seems to me that whatever sits there looking at
keyboard & mouse, could be told to yip something
out to a logfile every time it finds a "terminator"
(valid command is …
That's what I was thinking, but the question was how to, in Python.
Did you find that command-series? Or just did it interactive?
I'll repeat a recent question, which is: "Is there a logfile which shows
applied commands in sequence, perhaps ev…
I imagine the first step is to see what the foundry would put
out from a "colored" layout that went all the way to mask fab.
What you find in that GDS / OASIS file ought to inform you
of the end outcome desired, how it's represented.
But …
How about
1) Make a deck that fails everything, but reports every fail's
measured number and coords to a log file
2) clean and sort that log file by the measurement value
3) inspect the little end.