C
Craig
Guest
Our ITK application is solely concerned with visual rendering of the
design data.
Prior to Cadence 6.1, Vias were cells whose special nature was solely
encapsulated in the Technology file. So, without my actually
realizing it, my code "just worked", as I processed the geometries for
Vias just as for any other cells:
-- open cellview
-- iterate through LPs for that cell
-- iterate through each shape on each LP
Now, Vias are first-class objects. I can iterate through all the Via
Header in a cellview, and all the Vias for a header. However, it is
not clear to me how I can extract the geometry information. Do I need
to "construct" it from the various properties on each Via? Or can I
somehow still treat these more like cells?
I have examined the DF OA Adoption documentation and the ITK
documentation, so I suspect I cannot proceed naively as I once did. I
just wanted to see if I was missing anything before I jump into a
bunch of work.
Thank you!
- Craig Handler
Sr. Developer
Pinebush Technologies, Inc.
design data.
Prior to Cadence 6.1, Vias were cells whose special nature was solely
encapsulated in the Technology file. So, without my actually
realizing it, my code "just worked", as I processed the geometries for
Vias just as for any other cells:
-- open cellview
-- iterate through LPs for that cell
-- iterate through each shape on each LP
Now, Vias are first-class objects. I can iterate through all the Via
Header in a cellview, and all the Vias for a header. However, it is
not clear to me how I can extract the geometry information. Do I need
to "construct" it from the various properties on each Via? Or can I
somehow still treat these more like cells?
I have examined the DF OA Adoption documentation and the ITK
documentation, so I suspect I cannot proceed naively as I once did. I
just wanted to see if I was missing anything before I jump into a
bunch of work.
Thank you!
- Craig Handler
Sr. Developer
Pinebush Technologies, Inc.