Hi, Is the gdsfactory module gf180 having support?...
# gf180mcu
a
Hi, Is the gdsfactory module gf180 having support? We are trying to use it in a programmatic way but it doesn't have ports defined in the cells. Where should we define them?
a
@aquiles viza All pcells in GF180 are based on GDS Factory here: https://github.com/efabless/globalfoundries-pdk-libs-gf180mcu_fd_pr
a
So the official gdsfactory gf180 port is not recommended. Instead, we should use the pcells defined in the pdk. I'm not sure how to import them in python. Do you see a clean way to develop? I think in adding "klayout/pymacros" to PYTHONPATH and do "import cells", or maybe develop in the same folder.
In our development environment we use
volare
to download the latest pdk. It's the same as the shared link? Which source of pcells shoud we use? Volare, Efabless repo or Mabrains repo?
a
Yes
Volare is the same as the above.
Volare use the above link to build the PDK.
Mabrains for dev. Please don't use it.
I don't recommend the one in gdsfactory as it's not fully updated.
a
Hi Amro, in the
klayout/pymacros/cells
directory are 2 types of generators, ones that are linked to klayout interface, and other that uses the gdsfactory gf.cell decorator. I've seen that
fet.py
uses
draw_fet.py
internally, but I'm not sure what the intended way of working is. I think that we should use the
draw_*.py
family of generators, but I don't know what does the "layout" parameter means, or if we can see the outcome in the klayout integration over gdsfactory.
a
@aquiles viza we don't use the integration method documented above. As you mentioned, we use gdsfactory to do the actual drawing. And we use klayout interface to take the user input per cell and pass it to the gdsfactory cell.
a
I'm not sure what is the development workflow. We are used to develop with an editor like PyCharm or VSCode, but it seems that we should use Klayout Macro Development view. How your team validates that a change in the code reflects on the drawing?
a
That's something of your choice