Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 799
  • 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 'dbGet' the numeric "WireId" for a layer

jgentry

I'm trying to find the equivalent for:

dbLayerWireId $layerPtr

...using dbGet.  I see the .name (M11) and .extName (metal11) attributes but no .wireId attribute.

Am I missing something?  There are some commands that still expect the numeric representation of a layer (i.e. dbCreateWire) instead of the M/metal prefixed version.

Thanks,
JG

  • I did some research into this, and it was a conscious decision to omit .wireId as an attribute in dbGet.  The reason for this was because we're looking to make commands in the system align to the .extName (Metal1) as a standard, yet be tolerant of specifying layer in various formats.  For example, in 8.1.USR2 I see dbCreateWire accepting all 3 variations for layerId:

    encounter 9> dbCreateWire net 100 100 100 200 1 1
    0x2a9ec49b80
    encounter 10> dbCreateWire net 100 100 100 200 M1 1
    0x2a9ec49b50
    encounter 11> dbCreateWire net 100 100 100 200 Metal1 1
    0x2a9ec49b80
    encounter 12> getVersion
    08.10-s273_1

    If all of the commands in the system accept M1 or Metal1 style naming, do you still see a need for the simple wireId in dbGet?  I was thinking that it would perhaps still be useful to have simple wireId because it would be easier to compare with greater than/less than in a script.

    Others, feel free to chime in.

    Thanks,
    Bob

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.