port reference designs from GDS into Code

[joamatab]

These layouts were manually generated, how can we turn them into code?

• https://github.com/IHP-GmbH/TO_Sep2025
  - [ ] https://github.com/IHP-GmbH/TO_Sep2025/tree/main/Greyhound
• https://github.com/IHP-GmbH/TO_Apr2025
• https://github.com/IHP-GmbH/TO_Apr2025
• https://github.com/IHP-GmbH/TO_Nov2024
• https://github.com/IHP-GmbH/TO_July2025
• https://github.com/IHP-GmbH/TO_May2024
• https://github.com/IHP-GmbH/TO_Dec2024
• https://github.com/IHP-GmbH/TO_May2025

Best one to start with

• https://github.com/IHP-GmbH/TO_Apr2025

And from those maybe start with the mixer

• https://github.com/IHP-GmbH/TO_Apr2025/tree/main/Mixer5GHz

[mdmaas]

One way to do this could be to rely on import_netlist.py from the IHP PDK, which parses a .spice file (generated from xschem) and uses the regex templates in ihp130_pcell_templates.py to identify device types and extract their parameters (w, l, ng, m, etc.), which are mapped to KLayout PCells.

(Alternatively, one could parse the .sch files, and/or convert them to YAML as referenced in #37)

From there, instead of directly placing PCell instances like is done in the create_subckt_instance function, we could generate Python code with the correct gdsfactory components.