• 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. How to add comments on pcell created?

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 15177
  • 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

How to add comments on pcell created?

Messi
Messi over 14 years ago

Hi everybody,

  I have created a pcell.now i would like to add string comments on it.How can i do so??

Thanks,

  Messi  

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    Hi Messi,

    Hmm, the email notification from the forum said:

    I have created a pcell which helps to check for width,overlap,spacing check of layers.So if do width check i like to have comment written on the pcell as "width check".Similarly for space and ovelap check.comment should  "space check" and "ovelap check".

    This comment should vary with pcell parameter called comment which i pass in the formal arguments section

    You seem to have edited the description to say even less than your original question, which wasn't much!

    I must be missing something, because this would seem fairly obvious to me. Use dbCreateLabel() to create some text? Or even just have a fixed label on the pcell (created with dbCreateLabel) where you do:

    label=dbCreateLabel(pcCellView "text" 0:0 "ilInst~>comment" "lowerLeft" "R0" "stick" 0.1)
    label~>labelType="ILLabel"

    In this case you wouldn't need comment to be a pcell formal parameter (which means that you reduce the number of variants, which is good for efficiency). If you want it to be a parameter, you could do:

    dbCreateLabel(pcCellView "text" 0:0 comment "lowerLeft" "R0" "stick" 0.1)

    You can of course change the location of the label (at the origin here), the height, and font etc.

    Another alternative (in IC61X) might be to use dbCreateMarker so that you can look at the messages in the Annotation Browser. Rather depends on your objectives (I'm having to guess here, because  your description is a bit light...)

    Regards,

    Andrew.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    Hi Messi,

    Hmm, the email notification from the forum said:

    I have created a pcell which helps to check for width,overlap,spacing check of layers.So if do width check i like to have comment written on the pcell as "width check".Similarly for space and ovelap check.comment should  "space check" and "ovelap check".

    This comment should vary with pcell parameter called comment which i pass in the formal arguments section

    You seem to have edited the description to say even less than your original question, which wasn't much!

    I must be missing something, because this would seem fairly obvious to me. Use dbCreateLabel() to create some text? Or even just have a fixed label on the pcell (created with dbCreateLabel) where you do:

    label=dbCreateLabel(pcCellView "text" 0:0 "ilInst~>comment" "lowerLeft" "R0" "stick" 0.1)
    label~>labelType="ILLabel"

    In this case you wouldn't need comment to be a pcell formal parameter (which means that you reduce the number of variants, which is good for efficiency). If you want it to be a parameter, you could do:

    dbCreateLabel(pcCellView "text" 0:0 comment "lowerLeft" "R0" "stick" 0.1)

    You can of course change the location of the label (at the origin here), the height, and font etc.

    Another alternative (in IC61X) might be to use dbCreateMarker so that you can look at the messages in the Annotation Browser. Rather depends on your objectives (I'm having to guess here, because  your description is a bit light...)

    Regards,

    Andrew.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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