@Sakib Pathen Thanks for the week 6 presentation. I think the question at the 25 minute mark about supporting different transistor types may be critical. For sky130 there are at least the following transistor types:

sky130_fd_pr__nfet_01v8
sky130_fd_pr__nfet_01v8_lvt
sky130_fd_pr__nfet_03v3_nvt
sky130_fd_pr__nfet_05v0_nvt
sky130_fd_pr__nfet_20v0
sky130_fd_pr__nfet_20v0_nvt
sky130_fd_pr__nfet_g5v0d10v5
sky130_fd_pr__nfet_g5v0d16v0
sky130_fd_pr__pfet_01v8
sky130_fd_pr__pfet_01v8_hvt
sky130_fd_pr__pfet_01v8_lvt
sky130_fd_pr__pfet_01v8_mvt
sky130_fd_pr__pfet_20v0
sky130_fd_pr__pfet_g5v0d10v5
sky130_fd_pr__pfet_g5v0d16v0

I agree, we'll need to make this a priority.

I'll look into this and get back to you all tomorrow. Thanks for pointing this out.

@Sakib Pathen I don’t know how much flexibility you want to add. glayout uses layer translation to provide support for multiple pdks. At a minimum, maybe thin-ox vs thick-ox, and standard Vth, low Vth or High Vth would be a good starting point. The drc rules for each combination may be different though.

Currently the way glayout mostly implements separations in a way that the maximum possible layer to layer separation is accommodated (a similar concept applies for other rule pairs) As for support, any layer can be instantiated as a property of Gdsfactory (there is an example of an opamp helper function in the repo which places low voltage layer rectangles over certain fets). It is up to the designer to use these in whatever way they see fit Please let me know if I have misunderstood your requirement or the task at hand