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.
Does anyone know how to determine the environment a procedure was called from? There are many ways to call Skill code:icfb, pipo, si, dbAccess, cdsCopyShell, etc.Is there a way to know whether the Skill is running in icfb, pipo or cdsCopyShell? We have a very elaborate set of pcells and our technology library has a libInit file that takes several seconds to load. This is not a big deal in the Cadence environment since it happpens only once at the start of the session. However, if I call the ccpRename command to rename a lot of cells, I noticed that it spawns a sub-process for each rename and each sub-process calls the libInit.il. To do 100 renames will add 5 seconds of overhead per call. However, in this situation, the libInit.il code isn't even needed. Ideally, I would like the libInit.il code to selectively evaluate certain parts of the code depending on the calling environment. In the case of ccp sub-processes, I would do nothing. In the case of si, I would do a few schematic/netlist related things. In the case of pipo I would do all of the layout pcell things. In icfb, all of the libInit.il would be evaluated.
You could use the output of getVersion() to determine this.Andrew.
Or use isCallable('funcName) to determine whether a particular function is available. If you pick layout editor or schematic editor functions, these won't exist in pipo, cdsCopyShell, dbAccess etc.That could be a better approach, and depends less on parsing a version string.Andrew.
Thanks Andrew. I think the getVersion() will work best. It would be harder to differentiate between cdsCopyShell, pipo and dbAccess using the isCallable command unless I could find a function that was available in one but not the other. A parseString on getVersion would be the easiest.-Derek
I assumed you didn't really need to differentiate with that level of granularity - which was why I suggested the isCallable approach.Either way, take your pick...Andrew.
getVersion() is definitely the best way, but would parsing the environment variable CDS_MPS_SESSION also work?
CDS_MPS_SESSION will not be defined all the tine (dbAccess wouldn't have it, since it has no MPS support, for example), and also could be inherited from the parent application. So I don't think this is a good idea. Plus it's not documented...Andrew.