<@U01EK2VDMDG> <@U016EM8L91B> Hi, I was updating o...
# ieee-sscs-dc-23
a
@Amro Tork @Tim Edwards Hi, I was updating our klayout installation scripts with efabless primitives and validation repositories. I've found that the primitive library has a directory for xschem (cells/xschem) and it has much more content than volare's configuration, including symbols and tests. Should we migrate to the primitive library configuration for xschem or we can stay with the one given by volare?
๐Ÿ‘€ 1
s
The Xschem new symbols have been merged recently (18 Dec 2023) into efabless gf180mcu repo.
a
Interesting, so that explains the new symbols and tests. I'm seeing that for the old ones there are not so many changes. cap_mim_2p0fF is deprecated and pnp_10p00x10p00 now uses the correct model, not vpbp_10x10. I've found some differences in the ngspice models, in sm141064.ngspice there's added the rm4 model and in some devices the mulu0 parameter. In smbb000149.ngspice has improved parasitics in both fet_10v0_asym. I hope the next volare commit will integrate this changes.
๐Ÿ‘ 1
s
the
cap_mim_2p0fF.sym
was a typo, the correct name is
cap_mim_2f0fF.sym
. However both symbols will remain available and they netlist exactly the same (they are electrically identical). The reason is I can not remove
cap_mim_2p0fF.sym
immediately as this might break existing designs. If you open a schematic with such component you see the deprecated text and a hint to replace with
cap_mim_2f0fF.sym
. Over some time the deprecated symbol will be removed.
a
Yep, our team already handled that situation but I wasn't aware of the pnp symbol problem. Good to see them fixed.
๐Ÿ‘ 1