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.
Few of the cells I opened in read mode and when drawn a ruler are thought to be checked out through design sync. But actually I did not make any changes to the layout cell. Even after I open up the cell and clear rulers(I made the ruler not selectable during the setup), it keeps me giving that warning when ever I close the data or try to do a stream out. Is this a bug?
I use IC6.1.5. I would appreciate any help on this issue.
Few of the cells I opened in read mode and when drawn a ruler are thought to be checked out through design sync. But actually I did not make any changes to the layout cell. Even after I open up the cell and clear rulers, it keeps me giving that warning when ever I close the data or try to do a stream out. Is this a bug?
It's not really a bug - more of a "feature". OpenAccess allows readonly cellViews to be modified in memory only (this is akin to the "scratch" mode that existed in CDB). The Create Ruler command takes advantage of this by storing rulers as a marker object in the database - this has benefit in that it allows you to have persistent rulers saved from one session to the next, to treat rulers as editable objects - so they can be stretched and so on, and other benefits. There's an option on the Editor Options to control whether rulers get saved (it deletes them at save time), but for readonly cellViews it modifies the database in memory to add the ruler marker objects. This is nothing to do with whether they are selectable or not.
When you stream out, it detects any cellViews which have been modified but not saved. Unfortunately it's not filtering out any cellViews which are readonly - so still prompts you to ask if you want to save them (if you try to save them, it will fail because the cellView is readonly - you'd have to make it editable which would then force a design management check out).
So it doesn't think they are checked out - it just notices that they have been saved.
One could argue either way as to whether it should prompt you to save readonly cellViews - if you don't like this behaviour, please contact customer support - maybe we can alter it or provide an option as to whether it prompts you or not.
Oh, and by the way, I merged your two separate questions on this into a single thread.
In reply to Andrew Beckett:
Thanks for the explanation. We recently migrated from IC 5 to IC6. But I never noticed thsi in IC5. Is this a new feature with open access?
In reply to fun4skilled:
Rulers as objects in the database are new in IC614 (I think that's when they appeared). Before that they were just display graphics and so were not savable in the database.
Being able to edit readonly cellViews in memory (as opposed to having to use "scratch" mode) is a change as a result of the move to OpenAccess.
So it's a combination of the two things which explains why you didn't see this in IC5, but do in IC6 (specifically IC614 onwards)