• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Enforcing unique cell name in library manager

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 11686
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enforcing unique cell name in library manager

RK56
RK56 over 4 years ago

Hi,

We are beginning a new project and would like to know if we can enforce unique cell names across multiple libraries while creating a new cell. Is this possible?

We want to prevent people creating same cell names though they are in different libraries.

-Ramakrishnan

  • Cancel
  • AurelBuche
    AurelBuche over 4 years ago

    Hi Ramakrishnan,

    I don't really think this is good practice and you have to guarantee that all your available libraries for which you want this behavior are loaded in all your sessions

    I guess you could make a pre-checkin trigger using ddRegTrigger

    If your cell is new (no previous version checked-in already) you could parse all your libraries and raise an error in case another cell with same name exists already

    I believe it can be really slow according to the number of libraries you have and the cells they contain

    Hope this can help

    Cheers,

    Aurel

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to AurelBuche

    Ramakrishnan,

    I tend to agree with Aurel here. I had in the back of my mind that I'd written something to do this in the past, but when I checked it was specifically to check whether the same lib/cell had been created and checked in another workspace using TDM (an old Cadence-provided design management system; has been end-of-lifed for many years). This could happen because another user could have created the cell and checked it in since the last time the current workspace was updated. So my code (which was written in 1998 - so I have a small excuse at least for not remembering the precise details!) checked specifically for the same library rather than looking across other libraries, and it was also checking in the DM environment - so I don't think it would be very useful for you.

    The code used a ddRegTrigger preCreateObj trigger to do the check. That gets called a lot so you definitely would want to be very cautious about making that expensive in checking many libraries - hence my agreeing with Aurel here.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RK56
    RK56 over 4 years ago in reply to Andrew Beckett

    Thank you Aurel and Andrew for your inputs. I had not thought about DM in place when this script is policing.

    Also while thinking on the same line, we have enabled auto add cellview in our DM and also it reserves the name when a new cell is created. With DM doing its own policing work and can I now look only on my session when creating new cell names?

    Do I miss anything?

    -Ramakrishnan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information