• 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 Design
  3. How to create evenly spaced pins in Virtuoso?

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 15746
  • 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 create evenly spaced pins in Virtuoso?

Finn
Finn over 16 years ago
I have a evenly spaced bus but their pin numbers are spaced larger than one, like A<1>, A<3>, A<5> ... I know I can create A<1:5> by specifying delta X or delta Y, but A<1:5:2> doesn't work here. Could someone help me? Thanks a lot!
  • Cancel
Parents
  • skillUser
    skillUser over 16 years ago

    Hi,

    Yes, that was the idea, basically to create the superfluous pins so that the automatic pin creation could be used, and then to delete the unwanted pins, either manually or through SKILL.

    The latter would be relatively easy to do, for example, the
    terminal objects can be found one at a time by using the SKILL function dbFindTermByName(), or something like this:


    cv = geGetEditCellView()
    a_terms = setof(term cv~>terms rexMatchp("A<" term~>name))
    => (db:215089524 db:215089592 db:215090640 db:215090688 db:215062840)
    a_terms~>name
    => ("A<5>" "A<4>" "A<3>" "A<2>" "A<1>")

    or
    even_a_terms = setof(term cv~>terms rexMatchp("A<" term~>name) && evenp(atoi(cadr(parseString(term~>name "<>"))))
    => (db:215089592 db:215090688)


    Once you have the terminal object you should be able to delete it and any associated physical shapes.  E.g.

    foreach(eventerm even_a_terms 
      dbDeleteObject(car(eventerm~>pins))
      dbDeleteObject(eventerm)
    )


    There may be more things to remove...

    Regards,

    Lawrence

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 16 years ago

    Hi,

    Yes, that was the idea, basically to create the superfluous pins so that the automatic pin creation could be used, and then to delete the unwanted pins, either manually or through SKILL.

    The latter would be relatively easy to do, for example, the
    terminal objects can be found one at a time by using the SKILL function dbFindTermByName(), or something like this:


    cv = geGetEditCellView()
    a_terms = setof(term cv~>terms rexMatchp("A<" term~>name))
    => (db:215089524 db:215089592 db:215090640 db:215090688 db:215062840)
    a_terms~>name
    => ("A<5>" "A<4>" "A<3>" "A<2>" "A<1>")

    or
    even_a_terms = setof(term cv~>terms rexMatchp("A<" term~>name) && evenp(atoi(cadr(parseString(term~>name "<>"))))
    => (db:215089592 db:215090688)


    Once you have the terminal object you should be able to delete it and any associated physical shapes.  E.g.

    foreach(eventerm even_a_terms 
      dbDeleteObject(car(eventerm~>pins))
      dbDeleteObject(eventerm)
    )


    There may be more things to remove...

    Regards,

    Lawrence

    • 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