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 add layer gds stream numbers (extracted from the techfile with the lpp) to the LSW display?
I am using v5.1.41
In reply to Andrew Beckett:
hmmm....as an alternative to modifying the GUI with a new column of gds numbers, there is no way that for example a SKILL script could extract the layer name and gds number from the techfile, concatenate the two separated by say 3 dashes, and populate the LSW with this new layer name and unaltered purpose string...? Create a new list of lpp's to populate the LSW with?
Does that sound possible?
In reply to jaleco:
You could use the "Abbreviation" column in the techPurposes and techLayers sections of the technology file. These are generally used to make a shorter name for displaying in the LSW, but you could add the number without affecting the real name. For example, the purpose drawing has an abbreviation of drw. You could have a datatype number like drw--0 and a layer number like metal1--15. You'll need to widen your LSW so you can see the full name.
leSetLSWBBox(bBox).cdsenv variable:layout lswLPIconPurposeLength int 3
In reply to dmay:
I will try this out...
...This could become a much larger industry question if we are asking why CAD users need to use gds numbers. Us humans have to confirm that what layer name we are seeing in the CAD tool is associated with the expected db number that will be or has been machine read, and we have to communicate using layer names as well as db numbers. The db format (numeric layer identifiers) is frequently used in conjunction with layer name in back-end production, reviews, design/mask changes, vendors, partner firms, etc. The visual aid of the LSW would help greatly if it displayed both names and numbers, or had the option to turn it on/off. As long as us humans have to communicate using both systems, I'm confused why it would seem a bother to have the LSW display both...especially if some similar ability has been invested in v6...?
you are right, I would probably prefer NOT to see the gds numbers all the time and the less is more approach to visual clutter is usually best, so ideally the gds numbers would be present when needed - turned on/off via scripting. I was hoping there was a built in option to add the gds numbers as opposed to a custom SKILL approach. Being a novice programmer, everything seems convoluted and a bother. But these accomplishments are very satisfying once reached, so I'm not deterred, I am rather encouraged that there is a potential solution!
I will see if I can get a function to re-load the techfile with or without a gds concatenated layer abbreviation, and use it to toggle the visibility of the gds number in the LSW.
Thank you both very much.