Si2 oaScript Symposium: Scripting Made Easy

Si2 oaScript Symposium:
Scripting Made Easy

DAC 2017
Austin Convention Center, Room 7
Tuesday, June 20, 2017, 1:00 – 3:00 p.m.

  • Can you easily write new applications for your users?
    We’ll show you how.
  • Can you easily integrate script tools into your applications?
    We’ll show you how.
  • Do your applications have a fast-track learning system?
    We’ll show you ours.

Join us at DAC 2017 to learn how EDA engineers, product developers and designers are more productive using oaScript.

Click here for details

System level co-design of chip, package and PCB using native design databases in a unified 3D cockpit

Author:  James Church

Today’s advanced packaging design requires low layer count and high pin density to satisfy the cost pressures facing the electronics industry. By leveraging the native design formats, rules and technologies of each substrate designers can achieve a cohesive, optimized and properly constrained product.

Combining the OpenAccess IC layout database and Zuken’s own Package/PCB database format into a single hierarchically linked 3D system, enables system level optimization and visualization for a top-down or bottom-up flow that is not achievable in discrete point tools.

This paper was voted “Best Paper” by an audience survey taken after every presentation.

dac2015_openaccess

EDA Scripting Unleashed (Voted-Best-Paper)

Author:  James Masters, Intel

In many traditional design flows, high-performance robust EDA capabilities are limited to formal EDA tools. Design Automation (DA) engineers build additional project-specific capabilities either by using an EDA tool’s proprietary scripting API or by creating a standalone lightweight script that relies upon translation of design data into other formats. This results in extra runtime overhead, additional possible points of failure, and a burden of working with lossy design data formats.

With the advent of oaScript, DA engineers can quickly write scripts that directly read and write OpenAccess (OA) data using one of their favorite scripting languages – Perl, Python, Ruby, or Tcl. Also, a new OA extension is now available which provides high-speed layer manipulation and boolean operations directly within an oaScript – called “oaxPop” (OA eXtension Polygon Operators).

The combination of oaScript with oaxPop enables a DA engineer to write high-performance robust EDA capabilities without the overhead of using a formal EDA tool. This presentation will demonstrate how oaScript and oaxPop have been used together to create real-life applications that are used in a production design flow.

james_masters_-_eda_scripting_unleashed_-_real-life_examples_using_oascript_and_oaxpop

BIO:

James Masterjames_master_1000x1000s graduated from the University of Phoenix with a Bachelor of Science in Information Technology with an emphasis on computer programming. He has worked at Intel Corporation for 20 years in various full-custom design implementation roles.

James is currently managing a team focused on improving custom layout productivity for Intel’s advanced process technologies. James is an advocate of open standards that help streamline the design flow and maximize productivity and reuse.

Outside of work James enjoys outdoor activities such as camping, fishing, hiking, gardening, etc.

Building Successful OpenAccess Applications While Avoiding Bumps in the Road

DAC 2016

Description

The OpenAccess Database is the world’s most widely used, open reference database for IC design, with a supporting standard C++ API. It is superb for developing a stand-alone design tool and can also provide interoperability between EDA tools from different companies. The API is available in scripting languages through our extensions offering if C++ is more than you require. During this panel discussion, application developers using OpenAccess and OpenAccess extensions will describe their experiences along the way. The panel will be moderator by OpenAccess Coalition leadership.

What you will learn

  • The valuable role OpenAccess plays in the EDA world

  • Potential obstacles developers may encounter, and proven solutions

  • Helpful hints for OpenAccess developers

Panelists

  • * Moderator: Michaela Guiney, Product Engineering Director, Cadence Design Systems

  • Shiv Sikand, Executive Vice President of Engineering, IC Manage

  • Rudy Albachten, Principal Member of the Technical Staff, Intel

  • Brian Bradburn, Senior Director, Silvaco, Inc.

  • Ted Chou, Manager of Corporate Support, AnaGlobe Technology

  • Paul Clewes, Vice President, Research and Development, Pulsic

Building Successful OpenAccess Applications While Avoiding Bumps in the Road

What is Open about Si2 OpenAccess?

Marshall 200sq

 

 

 

 

By Marshall Tiner
Director of Production Standards
Si2

What is open about Si2 OpenAccess?

It seems these days everything is “open,” and the terms get confusing. Here is a short history of a few key areas to help clarify things. The label “open source” is credited to the free software movement of 1998. In February of that year, the Open Source Initiative (OSI) was founded and the Open Source Definition adopted. OSI tried to trademark the term “open source,” in an effort to control its usage.

So, what does open source mean?

The term refers to a licensing methodology whereby the source code is made publicly available. Depending on the license terms, others may then download, modify, and publish their version (fork) back to the community. The Apache Software Foundation’s license has become a standard within the open source world.

Silicon Integration Initiative (Si2) was born out of the 1988 CAD Framework Initiative (CFI), with a goal of enabling design tool interoperability. Cadence developed the OpenAccess API to standardize the design database, which resulted in just such a means of interoperability. With the contribution of the OpenAccess API, the OpenAccess Coalition was formed within Si2. To the design tool user this meant a huge productivity increase when using tools from different suppliers.

Before the OpenAccess Coalition, designs, measurements, and results were passed back and forth between tools via time-consuming, error-prone, file transfers. OpenAccess in effect “opened” the design database so all coalition members could develop tools that shared the database. This removed the cost of the file transfer and allowed two tools to act upon the same data. While file transfer seems like a small thing, it can represent significant cost-of-engineering time on a large design. In addition, it enables the user to check-fix-check errors one at a time instead of several at a time, reducing long file transfer time. Ultimately it benefitted the entire industry enabling “best of “design flows, which are very common today.

So is OpenAccess open source software?

The answer is no. The difference is who it is open to. OpenAccess is licensed much like open source software, though not open to the general public. The license benefits OpenAccess Coalition members that provide the resources required to keep the standard viable for use by the Coalition. There is a significant resource investment associated with OpenAccess. OpenAccess Coalition members have access to the source code and some of the derivative products (called Extensions) to use and even modify if necessary. Much like the Open Software Foundation works for the general public, Si2 and the OpenAccess Coalition provide a means of collaborative development for design product interaction/interoperability. The really great part is that the members realize a 1/N cost advantage while developing the standard.

Is Si2 OpenAccess “open?”

Yes, OpenAccess is open to the OpenAccess Coalition membership, which consists of many electronic design automation tool development companies, and semiconductor companies. That’s pretty open.

OpenAccess Membership Documents

OpenAccess Membership Required Documents

First: For access to current OpenAccess and oaScript (and other extensions) source code, the member must join the OpenAccess Coalition.

OpenAccess  Membership agreement:   OAC_Generic_Membership_Agreement.pdf  

oac_generic_membership_agreement

Second:   Use of OpenAccess requires the OpenAccess–Internal Use and Distribution License V 4.0 Oct. 1, 2004. 

openaccessinternaluseanddistributionlic_v4_041001

Third:   Use of Si2 OpenAccess Scripting Interface requires the ESG (Extensions Steering Group) OpenAccess ESG License v2.0 (January 31, 2013)

si2_esg_license_v2_0_01-31-2013

 

 

Paul Stabler New Chairman of Si2 OpenAccess Board

paulstablerPaul Stabler, senior engineering manager in the IBM EDA organization, has been elected chairman of Si2 OpenAccess Coalition for 2017. He replaces Rudy Albachten of Intel, who assumes an advisory role as vice chairman.

The OAC board oversees operational decisions for OpenAccess, the world’s most widely used, open-reference database with its own supporting standard API.

A 35-year IBM veteran, Stabler currently manages clocking, design for manufacturing, and integration tools and methodology. He has been an OAC volunteer for five years.