DVCLUB Europe May 2018 It’s Been 24 Hours – Should I Kill My Formal Run?

It’s Been 24 Hours – Should I Kill My Formal Run?

Conference:	DVCLUB Europe \| Formal Verification
Speaker:	Jeremy Levitt, Principal Engineer, Questa Formal R&D, Mentor, A Siemens Business
Abstract:	This time yesterday you kicked off a formal analysis – and it’s still running! Is it making any progress, or should you kill it now and start over? In this talk we will show how to make an informed decision using “engine health” monitoring, a snapshot of the active logic being used by the analysis, and making an honest appraisal of the assumptions you applied at the beginning of the run. Plus: we’ll show how a secure mobile app can be employed to keep track of progress of formal runs when you are away from your workstation. Be careful that your initial assumptions are not too broad Confirm the relevance of the DUT logic being included in the analysis Leverage “engine health” indicators
Speaker Biography:	Dr. Levitt is a Principal Engineer in the Formal Verification Group of Mentor, A Siemens Business. He oversees R&D with a focus on algorithm development. Jeremy earned his Ph.D in Electrical Engineering from Stanford in 1997, M.S. in 1993 and a B.A.Sc in Engineering Science from the University of Toronto in 1991.
Presentation Downloads:	Visit the main Formal Verification page to download the presentations.

ML Verification Turns Convention on its Head

The verification of processor architectures designed for Machine Learning (ML) applications represent a departure from conventional techniques. Conventional constrained random testbenches, which focus on stimulus driving coverage, cannot scale for many ML algorithm realizations. ML architectures involve neural networks of processors that “learn” by manipulating coefficients across the network to match ideal outputs to a large quantity of input data. Furthermore, smart compiler technology is employed to leverage the many paths available in the network. An effective verification strategy can leverage planning algorithms that start with the desired output and optimize input values to achieve that output. Ensuring the paths that the compiler might trigger have all been tested, and that the test content can scale from individual processors to the entire network are critical challenges. Breker will share various approaches to this problem, developed through cooperation with three noted AI processor providers.

3 Key Points:

Current verification methodologies cannot scale to meet ML processor challenges

ML verification approach: consider desired outputs, optimize inputs to match

Test Suite Synthesis enable planning algorithm approach to target ML requirements

An Emulation Strategy for Artificial Intelligence Designs

The emergence of Artificial Intelligence is the “next big thing” and presents a unique opportunity for disruptive semiconductor development. End applications could range from ADAS, to 3D facial recognition, to voice and image processing, or to intelligent search. The SoCs for AI applications whether targeted for training or inference will have their own unique characteristics, but present quite common verification challenges that we will present in this session.

Supporting designs as big as 15 billion gates, Mentor’s Veloce Strato has unique virtualization capabilities that enable highly accurate pre-silicon execution of AI benchmarking applications like MLPerf. The Veloce Power App enables analysis of peak and average. We will cover how Veloce Strato and its supporting solutions are the best tool to help address the verification challenges of SoCs targeted for AI applications.

3 Key Points:

Deterministic solution for AI chips verification

Full virtual solution for HW/SW verification

TERAOPS/Watt assessement prior silicon availability

AI chips must get the math right

Most AI chips and hardware accelerators that power machine learning (ML) and deep learning (DL) applications include floating-point units (FPUs). Algorithms used in neural networks are often based on operations that use multiplication and addition of floating-point values. FPUs are difficult to implement. The IEEE 754 standard defines many corner-case scenarios and non-ordinary values. Even a minor rounding mistake could accumulate over many iterations and produce a large error. An FPU formal verification app compliant with IEEE-754 provides an efficient and rigorous solutions to FPU functional verification

3 Key Points:

Floating-point unit (FPU) for AI chips

FPU Formal Verification App

Compliance with IEEE-754

Name: Mike Bartley

Designation: Senior Vice President – VLSI Design

Title: Introduction

Biography:

Mike Bartley has a PhD in Mathematics from Bristol University, an MSc in Software Engineering, an MBA from the Open University and over 25 years of experience in software testing and hardware verification. He has built and managed state-of-the-art test and verification teams in a number of companies who still use the methodologies he established. Since founding TVS in 2008 he has grown the company to over 100 employees worldwide. Dr Bartley is Chair of both the Bristol branch of the British Computer Society and the West of England Bristol Local Enterprise Partnership (LEP). He has had over 50 articles and presentations published on the subjects of hardware verification, software testing and outsourcing.

It’s Been 24 Hours – Should I Kill My Formal Run?

Sponsors

About Tessolve

Solutions

Tessolve Labs

Insights

Connect with us

ML Verification Turns Convention on its Head

An Emulation Strategy for Artificial Intelligence Designs

AI chips must get the math right

Please fill the form below

Please fill the form below

Please fill the form below

Please fill the form below

Please fill the form below

Please fill the form below

Please fill the form below