Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 13037
  • 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

Formal Analysis Metrics

archive

What kind of metrics are Formal Analysis users collecting?

Below are some metrics I am or have thought about collecting for our designs.

• The module that was verified
• The version of the module that was verified and all associated files used in the run.
• The HDL parameters that were used in the verification
• The properties that were verified
o Time it took for each property
o Engines used for each property (time for each engine)
o Explored Depth for properties not proved
o Trigger: pass/fail, depth
o Status: pass/fail depth
• Percentage of state elements touched by proved properties

Often times metrics are not kept and we lose track of what was verified, what is left to be verified, and how to best run the tool for future modules.


Originally posted in cdnusers.org by ross.weber@unisys.com

  • Hi,
    You almost left nothing for others :-) My 2 cents:

    I like to use Cover properties in a formal engine to look for tough corner cases that I couldn't hit in simulation. In that context here are few:

    * How many cover properties
    * How many got covered, can I write out HDL/HDVL tests from the formal tool for easy re-run/regress?
    * Integration of Formal + Coverage analysis (similar to what TransEDA seems to promote - not sure how much it works in reality).

    During our PSL book work, we explored few more interesting cases such as "latency analysis" etc. But tools were too immature then to handle a "battery of PSL code". Will be nice to get some recent experience on that front.

    Regards
    Ajeetha, CVC


    Originally posted in cdnusers.org by ajeetha

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.