It looks like you're new here. If you want to get involved, click one of these buttons!
Pretty quick now I will be returning to the problem of
converting a paper groundrules and Tanner / Caliber
implementation, to klayout Ruby . In reading the manual
I found a couple of questions not addressed by the text
1) in the interest of debug and maintenance (along with
weak coding skills and limited attention span), I think it
might be good to make the deck "modular". That is,
maybe I work on the easy MET, CONT, PAD bits first
and individually get them right. I'd like to make these
separate files and then integrate them. If need be I
could "cat" them I suppose, but is there a way to have
the main DRC runset, invoke files from the filesystem
by path/name? What I got from the manual was that
everything gets done within the macro development
environment, I did not run across anything about
2) Where are the runsets created, stored by default?
Is there a searchpath specific to DRC that I can use?
Can I make what look like "internal" runsets reside in
external files? I see that the error databases can be
put to external files, but what about the input deck?
3) I see that layer operations can put derived data to
new layers. My question is, do the "target layers" need
to be defined beforehand in the layertable, or if not
found will they be created within the present layer
set? Is "output" that kind of idiot proof?