{"id":31378,"date":"2002-03-01T23:23:09","date_gmt":"2002-03-01T23:23:09","guid":{"rendered":"https:\/\/silvaco.com\/%eb%b6%84%eb%a5%98%eb%90%98%ec%a7%80-%ec%95%8a%ec%9d%8c\/enhanced-lvs-reports-in-guardian-and-their-inspection\/"},"modified":"2021-07-16T22:03:26","modified_gmt":"2021-07-17T05:03:26","slug":"enhanced-lvs-reports-in-guardian-and-their-inspection","status":"publish","type":"post","link":"https:\/\/silvaco.com\/ko\/simulation-standard-ko\/enhanced-lvs-reports-in-guardian-and-their-inspection\/","title":{"rendered":"Enhanced LVS Reports in Guardian and Their Inspection"},"content":{"rendered":"
\n

Enhanced LVS Reports in\u00a0Guardian\u00a0and Their Inspection<\/h1>\n

Introduction<\/h3>\n

It is well known that analyzing LVS reports is often a difficult and brain-teasing task because the “global” nature of connectivity. Unlike DRC reports, where geometrical violations are usually restricted to two shapes, in LVS one must take into account many “widely separated” elements. In addition, quite often a small netlist error will propagate itself in an avalanche manner. Therefore many efforts are directed to localization of LVS errors in Guardian reports, as well as to means of efficient inspection of these reports.<\/p>\n<\/div><\/section><\/div>

<\/div>