Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 16997
  • 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

Access to the DRC markers.

MedAn

Hi all!

I understand, that this question has already been raised several times. But I could not find the answer.

A lot of time we need to have access (or transfer to the layer or have access to the coordinates) to the DRC error markers after Assura, PVS or Calibre check.

But no any *hilight functions or another skill function doesn't help.

Can anyone help how to solve this problem?

Parents
  • Andrew Beckett

    I can't answer for Calibre because that's not a Cadence tool and so I don't have access to it to check. However, in general physical verification tools have the ability to output error markers to stream (GDS) format. Dracula had this, Assura has this (via the ?outErrorLayers avParameter RSF setting), PVS has it and I suspect Calibre will too.

    It would also be possible in Assura (say) and I'm sure PVS to write your rules to directly output OA layers.

    In addition, PVS offers this choice:

    If you do that, the markers can be seen in the annotation browser, and also the geometries found using cv~>markers

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    I can't answer for Calibre because that's not a Cadence tool and so I don't have access to it to check. However, in general physical verification tools have the ability to output error markers to stream (GDS) format. Dracula had this, Assura has this (via the ?outErrorLayers avParameter RSF setting), PVS has it and I suspect Calibre will too.

    It would also be possible in Assura (say) and I'm sure PVS to write your rules to directly output OA layers.

    In addition, PVS offers this choice:

    If you do that, the markers can be seen in the annotation browser, and also the geometries found using cv~>markers

    Regards,

    Andrew.

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.