You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, QRC techfiles and technology LEFs are stackup-specific, so these should live in the "stackup" data structure. Right now, if you have multiple stackups, you'd need separate technology JSONs to support that. This is low priority since right now we don't support any technologies with multiple stackups, but we should fix it before we build too much infrastructure with the current APIs.
The text was updated successfully, but these errors were encountered:
Also, funnily enough, the tech LEF is an independent library and one could argue it belongs with the std cells, although I think it's also reasonable to keep it separate.
For example, QRC techfiles and technology LEFs are stackup-specific, so these should live in the "stackup" data structure. Right now, if you have multiple stackups, you'd need separate technology JSONs to support that. This is low priority since right now we don't support any technologies with multiple stackups, but we should fix it before we build too much infrastructure with the current APIs.
The text was updated successfully, but these errors were encountered: