follow up to the question about using abstract vie...
# magic
h
follow up to the question about using abstract views in magic: I successfully created an abstract view such that when writing gds it uses the 3rd-party GDS file. However, when I try and use it in the user_analog_project_wrapper, the GDS result looks fine but the precheck says
{{PARSING LAYOUT FAILED}} The user_analog_project_wrapper layout fails parsing because: The layout has multiple top cells in Layout.top_cell
t
It sounds like a cell definition is included in the GDS file that is never instantiated, which would implicitly make it another top-level cell.
If you can load it in klayout, a screenshot of the cell hierarchy would be helpful.
h
Ahh that seems very possible the naming is a bit odd, I'll have it soon
t
Klayout will show cells in parentheses if they are defined but not used.
h
Ahhh good to know
When I read GDS into magic I did get some {UNMAMED} which is almost certainly the issue
Should be able to fix that
t
The "(UNNAMED)" cell is magic's default cell name. It would exist in magic but it should not be something that came from the GDS.
h
ah -there are no fewer than 6 (UNNAMED) cells in KLayout. that'll do it
t
Arrgh, magic is not supposed to write (UNNAMED) cells into anything; it's just supposed to throw an error. The underlying fault here is that a layout was created but not saved under a proper name, and then GDS was written that contained that cell. There is also an error, though, that magic allowed the (UNNAMED) cell to be written to GDS without raising an error.
h
I see
t
I can confirm that it is possible to write the (UNNAMED) cell directly into GDS, so I will fix that part of the problem.
👍 1
h
is there a way of configuring what layers
lef write
outputs? I don't really want it writing nwell or contacts
t
"lef write -nomaster" will write LEF without generating the masterslice layers (nwell and pwell).
h
oo thank you