please note that using the "skip LVS" option when launching the precheck on the platform leads to a ...
j
please note that using the "skip LVS" option when launching the precheck on the platform leads to a passing precheck... but of course we understand the risks of this and therefore the concern above
m
@Jorge Marin the current platform lvs in precheck is broken due to a pdk discrepancy. We’re working on it, but please skip the platform lvs for now if the local lvs passes.
j
Hello @Mitch Bailey, thanks so much for the notice. Is there any place were we can get this information in "real time"? Since we received this large disclaimer when skipping lvs, we thought it was very important and spent long time trying to debug. Maybe some message in the same platform?
m
I’ll make a suggestion.
j
thanks a lot!
@Mitch Bailey can you give a bit more detail on what you mean by "pdk discrepacy"? how does the PDK affect the LVS in this case?
m
With the recent change to combined spice models (as opposed to binned), the extraction rules where changed to extract devices that didn’t fit the combined model parameters as special models and the spice libraries were updated accordingly. The LVS system uses an independent technology that enables soft connection checks. Unfortunately, the tech file in LVS precheck is not in sync with the pdk that has the source spice library.