{"id":3419,"date":"2025-06-25T15:48:41","date_gmt":"2025-06-25T19:48:41","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/calibre\/?p=3419"},"modified":"2026-03-26T16:24:06","modified_gmt":"2026-03-26T20:24:06","slug":"calibre-vision-ai-a-new-era-of-fast-scalable-chip-level-drc-debug","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/calibre\/2025\/06\/25\/calibre-vision-ai-a-new-era-of-fast-scalable-chip-level-drc-debug\/","title":{"rendered":"Calibre Vision AI: a new era of fast, scalable chip-level DRC debug"},"content":{"rendered":"\n<p>By James Paris<\/p>\n\n\n\n<p>As chip designs grow more complex and SoCs reach new heights in size and integration, the challenges of physical verification demand smarter tools and workflows. For teams managing parallel block development, incremental verification and volumes of \u201cdirty\u201d data, legacy methods just can\u2019t keep up. Enter <strong><a href=\"https:\/\/resources.sw.siemens.com\/en-US\/video-calibre-vision-ai-overview\" target=\"_blank\" rel=\"noreferrer noopener\">Calibre Vision AI<\/a><\/strong>\u2014a major leap forward in debugging methodology for today\u2019s large and complex designs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why DRC debug breaks down at scale<\/h2>\n\n\n\n<p>Modern physical implementation leverages parallelism: blocks and partitions are created alongside the top-level design, with verification happening at multiple levels simultaneously. While this parallelism boosts efficiency, it also means that checking design rule compliance (DRC)\u2014especially at advanced nodes\u2014can generate millions or even billions of errors. Debug cycles slow to a crawl as engineers wade through seemingly endless lists, using scripts and manual filtering long before they ever get to real root causes.<\/p>\n\n\n\n<p>Traditional debug approaches rely on ASCII output from Calibre nmDRC, which teams review with Calibre RVE (see Figure 1). For small- to mid-size designs, this flow is familiar and practical. But as projects outgrow these solutions, major bottlenecks arise.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"961\" height=\"309\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig1-debug-flow-72dpi.jpg\" alt=\"Diagram showing DRC results flowing into Calibre RVE for manual error review and distribution\u2014highlighting manual intervention and file size issues.\" class=\"wp-image-3422\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig1-debug-flow-72dpi.jpg 961w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig1-debug-flow-72dpi-600x193.jpg 600w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig1-debug-flow-72dpi-768x247.jpg 768w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig1-debug-flow-72dpi-900x289.jpg 900w\" sizes=\"auto, (max-width: 961px) 100vw, 961px\" \/><figcaption class=\"wp-element-caption\">Figure 1. The traditional chip-level debug cycle works for many projects, but struggles with modern, error-heavy and incomplete SoCs.<\/figcaption><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p>Two critical limitations stand out:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ASCII file constraints: To keep file sizes manageable, default error outputs are capped (often at 1,000 errors per rule). Raising the cap explodes file sizes, causing multi-gigabyte ASCII logs that take minutes just to load. OASIS format, by contrast, holds billions of errors in a file that loads in seconds.<\/li>\n\n\n\n<li>Slow root cause discovery: ASCII databases offer little context\u2014identifying root patterns and systematic failures is largely a manual effort, compounded by file splitting, lack of hierarchy and missed cross-block issues.<\/li>\n<\/ul>\n\n\n\n<p>When violations soar into the billions or block completion is delayed, the old approach slows debug to a crawl. Clearly, the industry needs something purpose-built for the new realities of SoC complexity and verification scale.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Calibre Vision AI: a smarter approach for modern debug<\/h2>\n\n\n\n<p><strong><a href=\"https:\/\/resources.sw.siemens.com\/en-US\/fact-sheet-calibre-vision-ai\/\" target=\"_blank\" rel=\"noopener\">Calibre Vision <\/a><a href=\"https:\/\/resources.sw.siemens.com\/en-US\/fact-sheet-calibre-vision-ai\/\" target=\"_blank\" rel=\"noreferrer noopener\">A<\/a><a href=\"https:\/\/resources.sw.siemens.com\/en-US\/fact-sheet-calibre-vision-ai\/\" target=\"_blank\" rel=\"noopener\">I<\/a> <\/strong>is engineered precisely for this new world. It completely redefines the debug paradigm by combining high-speed, instance-complete OASIS results with AI-powered signal grouping. Rather than forcing designers to slog through error lists, Vision AI quickly classifies violations by spatial pattern and context\u2014streamlining the path from error dump to actionable insight.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"986\" height=\"380\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig2-debug-flow-Vision-AI-72dpi.jpg\" alt=\"Flow diagram showing DRC data going into an OASIS results database, which feeds directly into Calibre Vision AI\u2019s interface for AI-guided grouping and debug.\" class=\"wp-image-3423\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig2-debug-flow-Vision-AI-72dpi.jpg 986w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig2-debug-flow-Vision-AI-72dpi-600x231.jpg 600w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig2-debug-flow-Vision-AI-72dpi-768x296.jpg 768w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/blog-fig2-debug-flow-Vision-AI-72dpi-900x347.jpg 900w\" sizes=\"auto, (max-width: 986px) 100vw, 986px\" \/><figcaption class=\"wp-element-caption\">Figure 2. The Calibre Vision AI workflow: nmDRC results are written to OASIS, then instantly loaded and grouped by pattern for root cause triage.<\/figcaption><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why OASIS format changes everything<\/h2>\n\n\n\n<p>By exporting results in <strong><a href=\"https:\/\/blogs.sw.siemens.com\/calibre\/2023\/04\/25\/cross-platform-database-validation-dont-add-applications-without-it\/\" target=\"_blank\" rel=\"noreferrer noopener\">OASIS<\/a><\/strong>, Calibre nmDRC creates a database that is up to fifty times smaller than equivalent ASCII\u2014with all errors, cell relationships and instance hierarchies captured. In one real-world case, an OASIS file just 1.4GB in size contained 3.5 billion errors and loaded in 45 seconds. Traditional ASCII output of the same results would consume 71GB and take over 15 minutes to open.<\/p>\n\n\n\n<p>This efficiency unlocks new capabilities in debug:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Complete across-the-die error visualization<\/li>\n\n\n\n<li>Fast error highlighting and navigation<\/li>\n\n\n\n<li>Block instances analysis of chip-level errors<\/li>\n<\/ul>\n\n\n\n<p>Teams maintain continuity while accessing truly scalable SoC-level debug\u2014not a compromise between completeness and performance.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">AI-driven Signal analysis: from error flood to root cause<\/h2>\n\n\n\n<p>The heart of Calibre Vision AI is Signal-based grouping. <a href=\"https:\/\/blogs.sw.siemens.com\/cicv\/2025\/06\/10\/blueprint-for-achieving-excellence-in-eda-ai-industry-experts-weigh-in\/\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>AI algorithms<\/strong><\/a> sift billions of violation markers, automatically clustering checks into one of seven signal types\u2014depending on spatial distribution and pattern. Some signals reflect global failures (\u201cFails Everywhere\u201d) while others pinpoint local or recurring hotspots (Signature Signals).<\/p>\n\n\n\n<p>This method slashes debug time: what once took days of guesswork now becomes a set of prioritized analysis groups that engineers can visualize, triage and address in minutes. The workflow is intuitive:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Activate Signals<\/li>\n\n\n\n<li>Explore densities with heatmaps<\/li>\n\n\n\n<li>Drill into contextual details (all overlaid on design data)<\/li>\n<\/ul>\n\n\n\n<p>This AI-guided, instance-aware approach changes the scale\u2014and the experience\u2014of DRC debug.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Integrating debug and design closure<\/h2>\n\n\n\n<p>Solving errors in isolation isn\u2019t enough. Calibre Vision AI connects error review directly to action, enabling users to highlight issues in external tools (like place and route), or to share HTML summaries and signal group findings with colleagues. Engineers can flag error locations, assign them for follow-up and maintain full context throughout analysis.<\/p>\n\n\n\n<p>By keeping debug tightly linked to design iteration and team collaboration, Vision AI accelerates closure\u2014not just for one error type or run, but across the complete physical verification cycle.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/eda.sw.siemens.com\/en-US\/ic\/calibre-design\/interfaces\/vision-ai\/\" target=\"_blank\" rel=\" noreferrer noopener\"><img loading=\"lazy\" decoding=\"async\" width=\"728\" height=\"208\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/banner.jpeg\" alt=\"\" class=\"wp-image-3424\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/banner.jpeg 728w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/banner-600x171.jpeg 600w\" sizes=\"auto, (max-width: 728px) 100vw, 728px\" \/><\/a><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Results that drive decisions\u2014not delays<\/h2>\n\n\n\n<p>Traditional ASCII workflows are finally outpaced. Calibre Vision AI\u2014by leveraging OASIS data, AI-driven grouping and seamless tool integration\u2014brings speed, clarity and focus to DRC debug, no matter how big the dataset. Design teams can now:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>See all errors and their hierarchy, no matter the volume<\/li>\n\n\n\n<li>Target systemic issues before pouring effort into low-priority lists<\/li>\n\n\n\n<li>Move between block and full-chip debug modes without switching context or tools<\/li>\n\n\n\n<li>Share actionable results and summaries quickly, at any point in the flow<\/li>\n<\/ul>\n\n\n\n<p>These capabilities mean less time fighting your debug platform\u2014and more time delivering reliable, on-schedule silicon.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ready to dive deeper?<\/h2>\n\n\n\n<p>Traditional DRC debug workflows simply aren\u2019t built for the complexity of today\u2019s designs. Calibre Vision AI with OASIS and AI-driven triage changes that\u2014making true chip-level debug fast, intuitive and scalable. To see full technical results, workflow diagrams and Signal grouping explanations, read the complete <strong><a href=\"https:\/\/resources.sw.siemens.com\/en-US\/technical-paper-calibre-vision-ai-a-revolution-in-chip-level-drc-debug-using-ai-guided\" target=\"_blank\" rel=\"noreferrer noopener\">Calibre Vision AI technical paper<\/a>.<\/strong><\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>By James Paris As chip designs grow more complex and SoCs reach new heights in size and integration, the challenges&#8230;<\/p>\n","protected":false},"author":71645,"featured_media":3420,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[355],"tags":[312,372],"industry":[],"product":[90],"coauthors":[712],"class_list":["post-3419","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-realtimeinterface","tag-ic-design","tag-physical-verification","product-calibre"],"featured_image_url":"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/50\/2025\/06\/image.jpeg","_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/posts\/3419","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/users\/71645"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/comments?post=3419"}],"version-history":[{"count":2,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/posts\/3419\/revisions"}],"predecessor-version":[{"id":3426,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/posts\/3419\/revisions\/3426"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/media\/3420"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/media?parent=3419"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/categories?post=3419"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/tags?post=3419"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/industry?post=3419"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/product?post=3419"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/calibre\/wp-json\/wp\/v2\/coauthors?post=3419"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}