Identification of key errors in a system having a large number of error events

Patent metadata

Field	Value
Publication number	US-11385986-B2
Application number	US-201716088990-A
Country	US
Kind code	B2
Filing date	Mar 31, 2017
Priority date	Mar 31, 2016
Publication date	Jul 12, 2022
Grant date	Jul 12, 2022

Abstract

A report of results of validating a circuit can simplify a large number of error events, that can be generated when designing electrical circuits using computer aided design tools, by first filtering the large number of error events according to a user defined filter criteria. The filter results are processed by one or more report rules. Each of the report rules may generate one or more report results based on, at least, the filtered error events.

First claim

What is claimed is:

1. A system comprising:
a memory for storing instructions; and
a computing system including one or more processing devices, the one or more processing devices, in response to executing the instructions, configured to:
validate a test circuit, which identifies error events indicative of problems associated with the test circuit;
filter the error events to identify a subset of the error events based on a filtering criteria;
select one or more report rules to retrieve from a report rules database storing a plurality of the report rules, wherein the selected report rules, when processed by the computing system, are configured to generate one or more report messages from the subset of the error events;
use the selected report rules retrieved from the report rules database to process the subset of the error events, which generates the one or more report messages; and
generate an error report using the one or more report messages generated by processing the subset of the error events using the selected report rules.

2. The system of claim 1 , further comprising a display, wherein the instructions, when executed, further configure the one or more processing devices to present the generated error report to a user on the display.

3. The system of claim 1 , wherein each of the error events comprises one or more of:
information describing the error associated with the error event;
a test identifier of a test that generated the error event;
a version number of the circuit the error event was generated for;
a revision number of the circuit the error event was generated for;
a date the test that generated the error event was run; and
a time the test that generated the error event was run.

4. The system of claim 3 , wherein the filtering criteria corresponds to one or more of:
the test identifier associated with the error event;
the version number associated with the error event;
the revision number associated with the error event;
the date associated with the error event;
the time associated with the error event;
a severity associated with the error event;
a location within the circuit of the error associated with the error event; and
components connected to a portion of the circuit associated with the error event.

5. The system of claim 1 , wherein the filtering of the error events to identify the subset of the error events is a coarse grain filtering of error events.

6. The system of claim 1 , wherein the one or more report rules selected from the error report are retrieved from a plurality of pre-existing report rules.

7. The system of claim 6 , wherein the one or more report rules are selected based on user input or a user selected report template.

8. The system of claim 1 , wherein each of the one or more report rules specify the processing utilized to generate a particular report message.

9. The system of claim 1 , wherein at least one of the one or more report rules generates the one or more report messages based on processing of at least one of the subset of the error events and one or more of:
error events stored in an error event database;
one or more report messages generated by report rules; and
a previous generation of reports.

10. The system of claim 1 , wherein at least one of the one or more report rules adds one or more additional report rules for processing or removes one or more report rules from processing.

11. A method comprising:
validating a test circuit, which identifies error events indicative of problems associated with the test circuit;
filtering the error events to identify a subset of the error events based on a filtering criteria;
selecting one or more report rules to retrieve from a report rules database storing a plurality of the report rules, wherein the selected report rules, when processed by the computing system, are configured to generate one or more report messages from the subset of the error events;
using the selected report rules retrieved from the report rules database to process the subset of the error events, which generates the one or more report messages; and
generating an error report using the one or more report messages generated by processing the subset of the error events using the selected report rules.

12. The method of claim 11 , further comprising displaying the generated error report on a display.

13. The method of claim 11 , wherein each of the error events comprises one or more of:
information describing the error associated with the error event;
a test identifier of a test that generated the error event;
a version number of the circuit the error event was generated for;
a revision number of the circuit the error event was generated for;
a date the test that generated the error event was run; and
a time the test that generated the error event was run.

14. The method of claim 13 , wherein the filtering criteria corresponds to one or more of:
the test identifier associated with the error event;
the version number associated with the error event;
the revision number associated with the error event;
the date associated with the error event;
the time associated with the error event; a severity associated with the error event;
a location within the circuit of the error associated with the error event; and
components connected to a portion of the circuit associated with the error event.

15. The method of claim 11 , wherein the filtering of the error events to identify the subset of the error events is a coarse grain filtering of error events.

16. The method of claim 11 , wherein the one or more report rules selected from the error report are retrieved from a plurality of pre-existing report rules.

17. The method of claim 16 , wherein the one or more report rules are selected based on user input or a user selected report template.

18. The method of claim 11 , wherein each of the one or more report rules specify the processing utilized to generate a particular report message.

19. The method of claim 11 , wherein at least one of the one or more report rules generates the one or more report messages based on processing of at least one of the subset of the error events and one or more of:
error events stored in the error event database;
one or more report messages generated by report rules; and
a user's previous generation of reports.

20. The method of claim 11 , wherein at least one of the one or more report rules adds one or more additional report rules for processing or removes one or more report rules from processing.

21. A non-transitory computer-readable medium storing a computer program product comprising instructions configured to cause one or more processing devices to perform operations comprising:
validating a test circuit, which identifies error events indicative of problems associated with the test circuit;
filtering the error events to identify a subset of the error events based on a filtering criteria;
selecting one or more report rules to retrieve from a report rules database storing a plurality of the report rules, wherein the selected report rules, when processed by the computing system, are configured to generate one or more report messages from the subset of the error events;
using the selected report rules retrieved from the report rules database to process the subset of the error events, which generates the one or more report messages; and
generating an error report using the one or more report messages generated by processing the subset of the er

Assignees

• Siemens Ind Software Inc

Inventors

• Alam Michael

Classifications

• G06F11/1471

  involving logging of persistent data for recovery · CPC title

• G06F11/3692

  for test results analysis · CPC title

• G06F30/367

  Design verification, e.g. using simulation, simulation program with integrated circuit emphasis [SPICE], direct methods or relaxation methods · CPC title

• G06F11/321

  Display for diagnostics, e.g. diagnostic result display, self-test user interface · CPC title

• G06F30/398

  Design verification or optimisation, e.g. using design rule check [DRC], layout versus schematics [LVS] or finite element methods [FEM] (optical proximity correction [OPC] design processes G03F1/36) · CPC title