Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
Is there a way to only select vias that cross a shape boundry?
I have a very large FET that has numerous Source and Drain Vias and the top level metal covering them now has to be slotted leaving a large amount of existing Vias to be manually deleted where the slots pass over them.
I can generate another layer that consists of simply the slots and then, if CDS OA 6.1.5 has the capability, then one could simply select only the Vias that touch the newly created shapes.
Is that possible to do in Skill?
Use the bBox from your slots and then this Skill command to get your vias. Finally you can use geSelectFig for each of the vias.
dbViaQuery( d_cellviewIdl_bBox[ x_startLevel ] [ x_stopLevel ][ n_filterSize ] [ l_transform ] ) => ld_via | nil
Returns a list of all the vias in a cellview whose bounding boxes overlap the region specified by l_bBox.
In reply to dmay:
Building on what Derek suggested (nice tip!), here is some more code around it. Assume that the slot shapes have been selected and then stored in a list, in my example I used testShapes and 'lcv' is the layout cellview database object, then you can identify and delete the overlapped vias like this:
vias = apply('nconc foreach(mapcar shape testShapes dbViaQuery(lcv shape~>bBox )))
The first step build a "flat" list of the list-of-list shapes returned by the foreach-mapcar; the dbViaQuery might return more than one shape. Then map the function dbDeleteObject over this list to delete each via found.
Hopefully this will answer your question?
In reply to skillUser:
A little further optimization (just to give an alternative and illustrate some of the flexibility of SKILL) - use:
vias=foreach(mapcan shape testShapes dbViaQuery(lcv shape~>bBox))mapc('dbDeleteObject vias)
The foreach mapcan will append the lists as it goes along - no need to use the apply 'nconc afterwards. And for the deletion, since there's not much likelihood that you'll want the return value of the mapcar (which will be a list of t's and nil's depending upon the success of the dbDeleteObject), use mapc which just returns the original list (and so is cheaper).