(Quote)
Yes. In my netlist visualization it helps to have net names.
(Quote)
I see. Thank you for the answer! Will give it a try. A fundamental problem with this is non-uniqueness if network elements on different layers are at the exactly the same …
Not sure if I understood everything, but I think Cells belong to a single layout and you cannot add a cell instance into the second layout by referring the cell by its index in the first layout. I guess you can copy the Cell from one layout to other…
Have you already read the LayerMap docstring? From that I understand that multiple physical layers can be mapped to a single logical on but the reverse does not makes sense. If you just want to "see" the stuff in the GUI on the same "…
Thanks! I made use of the cell_mapping.
Just for record for future readers, in your example the internal_cell and original_cell are not Cell objects but cell indices.
if cm.has_mapping(internal_cell.cell_index()): original_cell_inde…
I think I figured it out :)
name=pin_ref.subcircuit().circuit_ref().name
gives a name which also exists in the layout and the PCell can be retrieved by
cell = layout.cell(name).
Now I figured out that the cell indexes actually refer to the internal_layout and I can get the correct cell name from
ltn.internal_layout().cell(pin_ref.subcircuit().circuit_ref().cell_index).name.
However, these are static copies of PCells. Is t…
With Ege We are using PCells created in Pyhton. Sometimes we change the PCell generation code and reload the python module. If KLayout has references to these PCells it crashes. To avoid crash we can use "Deep delete" in the Cell list in t…
I don't want to push more but just for record for other people reading this.
PCell hidden parameters would not be suitable solutions, since the expensive calculation produces subcells, shapes and metadata. While I could limit the metadata format to…
(Quote)
Does not solve the problem, if I cannot set the hidden parameters in produce. Parameters only seem to be intended as "inputs" for generating the Cell and not "outputs" as metadata.
The problem seems to be, that the Porpe…
So you are saying, that during loading the PCells will be generated again? Is there a command-line flag perhaps which would leave my macro unloaded, such that I could easily open the file and see the same thing as a person without my libraries?
I keep trying to redesign my architecture, but I keep pumping into this constraint.
Invoking coerce_parameters does not solve my problem. First, it would require rerunning the geometry calculations. Secondly, as it does not have access to the Cell …
Thank you for a detailed reply! I had a look at pcell_declaration_helper.lymand learned about what you described. However, I think I still did not make my goal clear. Sorry for insisting.
(Quote)
I never intend to change instance from PCell declara…
I keep pumping into the same issue and from reading the Q&A regarding the Circle PCell parameters I think other people have reached the same point. I define a lot of features in PCellDeclarationHelper. It generates geometry, but some of the inte…
Thank you for the reply (and the great software)!
Is instances inheriting properties of the cell variants a bad idea? Obliviously many instances would share the inherited properties. And cell variants could get properties during the production.
I …
My specific goal was to export Sonnet project files and use properties to define port locations. Then, a script could export all cells irrespective if they are PCell variants or manually created.
I think I can use the properties of the shapes in th…
Nice! Thanks!
I did not notice it as there is the other function with the same name does something completely different. I expected something similar to num_points of Polygon object.