• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. Using vManager to identify line coverage from a specific...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 3174
  • 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

Using vManager to identify line coverage from a specific test

scottbadi
scottbadi 11 months ago

I have been using the rank feature to identify tests that are redundant in our environment, but then I realized I'd also like to be able to see exactly what coverage goes into increasing the delta_cov value for a given test. If I had a test in my rank report that contributed 0.5% of the delta_cov, how could I got about seeing exactly where that 0.5% was coming from? It seems like that might be part of the correlate function, but I couldn't mange to find a way to see what specific coverage was being contributed for a given test.

  • Cancel
  • StephenH
    StephenH 11 months ago

    Hi Scott.

    I don't think there is a built-in way to achieve this directly, however you could do it in a few steps in IMC as follows. Assume you have N runs with a positive rank, and you want to know how which bins were uniquely hit by run N.

    1. Manually merge the coverage for all the runs 1 to N-1

    2. Use the "report_unique -run1 merged -run2 run_N -one_way" to produce a JSON report of the bins that were hit only by run_N.

    Note that these "unique" bins might be hit by other, lower-ranked runs as well; the ranking sorts by the efficiency of the run in terms of how many new bins are hit per CPU second. Don't forget also that any randomisation in the tests may mean that these ranked runs might not produce the same results when you run with the same test+seed combinations after any code changes. Use ranking as an indicator of test quality, but do not use it to produce "golden" test lists that go stale quickly...

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information