Project

General

Profile

Actions

Feature #7443

closed

Calculate and show additional statistics on Safes, Unsafes and Unknowns

Added by Evgeny Novikov almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Urgent
Category:
Bridge
Target version:
-
Start date:
08/01/2016
Due date:
08/22/2016
% Done:

100%

Estimated time:
Published in build:
34b07ee

Description

One fails to quickly get very useful and important statistics on safes, unsafes and unknowns when try to intensively use Klever to verify many modules against many rules. The only way to do this is to open corresponding pages (Safes, Unsafes, Unknowns) and either set up appropriate filters through views or copy-paste to some sheets for further investigation. When the number of corresponding table rows more than 100, tables are opened very slowly (it is by design and it is well but I am sure that can be optimized). For say 100000 row tables it is almost impossible to wait for corresponding pages to be opened.

This feature becomes even more important after support of lightweight verification results (#7368) that already replace the most of the most large heavyweight verification results by default. Lightweight verification results don't contain any details on Safes that constitute the most of verification results and almost aren't interesting.

It is suggested to calculate and show additional statistics on Safes, Unsafes and Unknowns, namely:
  1. Specify lists of attribute names for various job classes. For instance, it looks that initially just Rule specification should be specified for all job classes. If there won't be the specified attribute, especially for Unknowns, you can use special attribute value Others.
  2. Calculate additional caches keeping the number of Safes, Unsafes and Unknowns grouped by values of the specified attribute names. I think that these caches should be bound to all component reports as other caches do.
  3. Show pretty tables with corresponding sorted statistics. It would be great if one will be able to click on corresponding values to get pages with respectively filtered lists of corresponding reports. I think that views don't need to support anything regarding these tables except (not) showing them at all (by default they should be shown).
Actions #1

Updated by Vladimir Gratinskiy over 7 years ago

  • Due date set to 08/22/2016
  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Done in branch feature_7443. Please test it on real jobs yourself. I didn't test "Others" attribute at all.

Actions #2

Updated by Evgeny Novikov over 7 years ago

  • Status changed from Resolved to Closed
  • Published in build set to 34b07ee

Works like a charm! I tested this feature in various test cases and even revealed some old issues.

Actions #3

Updated by Evgeny Novikov over 7 years ago

One more detected issue was fixed in 8a1d79d. It turned out that attributes weren't saved even if they are specified for unknown reports like for safe and unsafe reports. I hope that I properly fixed this issue.

Actions #4

Updated by Evgeny Novikov over 7 years ago

I forgot to add that after update one needs to migrate databases.

Actions

Also available in: Atom PDF