Friday, November 21, 2008     Register | Login | Search | Contact Us
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Subject: Formal Analysis Metrics
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
ross.weber@unisys.com
Posts: 0
Online: User is Offline
1/26/2006 9:06 AM  
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.
ajeetha
Posts: 0
Online: User is Offline
2/02/2006 10:10 AM  
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
Posting to forums is available to community members only.
Login or Register



ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.