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

    Thanks! BobD

    I think the way to iterate all the vias you proposed is workable. I will later post my own tcl to iterate all the wires and vias of a specified NET. Yesterday I follow the db manual to write, but find my script a little bit strange.

    For the way of getting all the drc boxes, I really did not find correspond db commands, sigh. But your idea has enlighted me!


    Originally posted in cdnusers.org by eminemshow
Reply
  • archive

    Thanks! BobD

    I think the way to iterate all the vias you proposed is workable. I will later post my own tcl to iterate all the wires and vias of a specified NET. Yesterday I follow the db manual to write, but find my script a little bit strange.

    For the way of getting all the drc boxes, I really did not find correspond db commands, sigh. But your idea has enlighted me!


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