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.
perhaps the circuit has two or more DC operating points, in other words the solutions are metastable states? One solution is a dcOp and the other starts from a dcOp and the voltage is swept - this can lead to different solutions. What kind of circuit is it? Have you tried using initial conditions rather than nodesets? I believe the former is a "suggested starting point" whereas the latter is more of a fixed quantity - if the nodeset values are not correct, this will force the simulation in a certain direction which may be why you arrive at a different solution?
Andrew will have more useful input I'm sure (and may even correct me if I'm wrong), but hopefully the above might be useful to you?
In reply to skillUser:
In reply to aditeman:
I'm not sure that the statement that a DC Sweep is a sweep (or set) of DCops is correct - I think that a sweep starts from a dcOp and then the parameter is swept, so this means that you could arrive at a different solution than a single dcOp - i.e. it picks "the wrong" metastable state for the operating point solution. IC's are used for transient simulations and a transient starts from a dcOp, so I assumed that IC's would apply, my apologies if this is incorrect, and also if I've got the nodeset vs. the IC mixed up! The fact that you need to use nodesets tells me that there has already been difficulty arriving at "the correct" solution, so this does indeed sound like a metastable state problem. Have you tried sweeping down from 1.1 to see if the solution is different? What can a transient simulation tell you?
what about a parametric sweep of dcOps?
Try using rebuild_matrix=yes (on the Analog Options form). This will force spectre to restart completely at each point. Note that you effectively have multiple operating points - so this can disguise the fact you may have such a scenario.
In reply to Andrew Beckett: