Stats

  • Locked Locked
  • Replies 7
  • Subscribers 90
  • Views 16122
  • 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 make a iteration of all the VIAs in SOC Encounter database?

archive

Hi, all:

I am Roc Sun. Recently, I got a few problems.

One is how can I iterate all the via instances in SoC Encounter. I can find the command 'dbViaCellName' or something, but I can not find the way to get via instances. As you know, in SoC52, it 'split via' utility is not working. So, I want write my own version using database command.

The other is that, how can I get all the drc box coordinates, I mean the white boxes after we made a DRC check in SOC Encounter. I want to write this script in db commands.

Best Regard!


Originally posted in cdnusers.org by eminemshow
Parents
  • archive

    As you can see from your scripted example, there isn't exactly a notion of a "via instance" in SoC-E. Vias are modeled as a unique kind of wire segment that happens to be an instantiation of a via cell.

    I'd like to know (for your benefit as well as others who might come across this post) what would you do with the via instance pointer if you were able to get it? You mention that you're having trouble with a "split via" utility- but I'm not clear on what that means.

    Thanks,
    Bob


    Originally posted in cdnusers.org by BobD
Reply
  • archive

    As you can see from your scripted example, there isn't exactly a notion of a "via instance" in SoC-E. Vias are modeled as a unique kind of wire segment that happens to be an instantiation of a via cell.

    I'd like to know (for your benefit as well as others who might come across this post) what would you do with the via instance pointer if you were able to get it? You mention that you're having trouble with a "split via" utility- but I'm not clear on what that means.

    Thanks,
    Bob


    Originally posted in cdnusers.org by BobD
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.