CN112306877B - Power system fault operation and maintenance method and system - Google Patents
Power system fault operation and maintenance method and system Download PDFInfo
- Publication number
- CN112306877B CN112306877B CN202011195977.5A CN202011195977A CN112306877B CN 112306877 B CN112306877 B CN 112306877B CN 202011195977 A CN202011195977 A CN 202011195977A CN 112306877 B CN112306877 B CN 112306877B
- Authority
- CN
- China
- Prior art keywords
- fault
- analysis
- test
- analysis software
- library
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 30
- 238000012423 maintenance Methods 0.000 title claims abstract description 27
- 238000012360 testing method Methods 0.000 claims abstract description 88
- 238000012216 screening Methods 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 abstract description 9
- 238000012795 verification Methods 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 8
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000013100 final test Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The disclosure provides a power system fault operation and maintenance method and system, comprising the following steps: establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software; analyzing the fault files in the test cases in the test case library by selecting analysis software with different versions from the analysis version library to obtain an analysis result of each fault file; and comparing the analysis result of each fault file with a standard test report of the fault file corresponding to the fault database to obtain a test result of the corresponding analysis software. By establishing a fault library and an analysis program version library, different faults are classified, various fault data are analyzed by using analysis software, and the acquired analysis reports are compared to judge whether the new analysis software has complete functions. The method and the device can improve the efficiency of fault operation and maintenance management and analysis software function verification.
Description
Technical Field
The disclosure belongs to the technical field of power system software monitoring, and particularly relates to a power system fault operation and maintenance method and system.
Background
The statements in this section merely provide background information related to the present disclosure and may not necessarily constitute prior art.
Many operation data can be generated in the power system, if the operation data can reflect the fault condition at the time, a computer is required to write corresponding software to analyze the operation data, but along with the diversification of the operation data, the corresponding software, namely an analysis program version library, is often changed, but the inventor finds that the problem which is processed is easily ignored in the process of changing in the research, so that the problem B is changed, the problem A is raised, and therefore, the analysis software in the analysis program version library is in the requirement of failing to meet the fault analysis which is actually changed continuously.
Disclosure of Invention
In order to overcome the defects in the prior art, the disclosure provides a fault operation and maintenance method of a power system, and finally analysis software obtains a fault analysis result by analyzing a waveform file uploaded when a fault occurs.
To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:
in a first aspect, a power system fault operation and maintenance method is disclosed, comprising:
establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software;
analyzing the fault files in the test cases in the test case library by selecting analysis software with different versions from the analysis version library to obtain an analysis result of each fault file;
and comparing the analysis result of each fault file with a standard test report of the fault file corresponding to the fault database to obtain a test result of the corresponding analysis software.
According to a further technical scheme, the fault database comprises various types of fault data, including areas where fault devices belong, fault types, fault phases and weather conditions when faults occur.
According to a further technical scheme, the establishment and maintenance of the analysis version library comprises the following steps: if the fault test case library to be analyzed does not exist, the fault test case library is a new fault, and the analysis version library is updated.
According to the further technical scheme, when the analysis result fails, analysis software of a corresponding version is changed and processed in time, and the failure data is changed partially along with the upgrading of a corresponding device and the difference of device manufacturers, so that the analysis software is upgraded in time.
According to the further technical scheme, after the analysis result of each fault file is obtained, whether the analysis software meets the use requirement is judged by comparing the test result with the standard result, and other fault information in the assumption is obtained on the premise that the determined fault result is not changed, so that the success of upgrading the software is ensured.
According to the further technical scheme, when the test result meets the requirement, the test result is used as a new test result corresponding to the fault data and used for comparing the results of the later new analysis software and inquiring the analysis result during fault maintenance.
According to a further technical scheme, a parameter file required by analysis software in analyzing a waveform file consists of two parts: one part is a wave recording file recorded by the device when a fault occurs, the other part is a model file matched with the fault device, and analysis software needs to analyze the waveform file through the model file so as to obtain an analysis result.
According to the further technical scheme, the fault database carries out unified storage management on faults according to the types, the affiliated lines and the affiliated areas, and the national fault distribution condition is obtained.
According to the technical scheme, when a test case library required by test software is established, unified analysis is carried out on one or more fault files under different conditions, screening is carried out according to the fault type, the fault type and the region of the fault when the fault is selected, and screening is carried out under the condition of specific weather when the fault under severe weather is required to be analyzed.
According to the further technical scheme, in the analysis version libraries, the analysis software of each version records the corresponding relevant characteristics, the sequence numbers and the creation time, so that the inquiry is convenient, each version library needs to upload the corresponding analysis program, and the analysis program files can be updated and maintained in the process of maintaining the analysis version libraries.
In a second aspect, a power system fault operation and maintenance system is disclosed, comprising:
a library building module configured to: establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software;
an analysis module configured to: analyzing the fault files in the test cases in the test case library by selecting analysis software with different versions from the analysis version library to obtain an analysis result of each fault file;
a contrast module configured to: and comparing the analysis result of each fault file with a standard test report of the fault file corresponding to the fault database to obtain a test result of the corresponding analysis software.
The one or more of the above technical solutions have the following beneficial effects:
according to the technical scheme, the operation and maintenance management tool for fault maintenance and analysis management in the power system can obtain fault conditions when faults occur by analyzing operation data of the power system, corresponding analysis software also frequently performs version iteration along with technical improvement and diversification of the operation data, the problems which are possibly modified appear in the version iteration process are reappeared, different faults are classified by establishing a fault library and an analysis program version library, various fault data are analyzed by using the analysis software, and the acquired analysis report is compared to judge whether the new analysis software functions are complete. The method and the device can improve the efficiency of fault operation and maintenance management and analysis software function verification.
Additional aspects of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure, illustrate and explain the exemplary embodiments of the disclosure and together with the description serve to explain the disclosure, and do not constitute an undue limitation on the disclosure.
Fig. 1 is a flow chart of an embodiment of the present disclosure.
Detailed Description
It should be noted that the following detailed description is exemplary and is intended to provide further explanation of the present disclosure. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of exemplary embodiments in accordance with the present disclosure. As used herein, the singular is also intended to include the plural unless the context clearly indicates otherwise, and furthermore, it is to be understood that the terms "comprises" and/or "comprising" when used in this specification are taken to specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof.
Embodiments of the present disclosure and features of embodiments may be combined with each other without conflict.
Example 1
The embodiment discloses a power system fault operation and maintenance method, which comprises the steps of establishing a fault library, analyzing all problems in the fault library by using software (how many test items are used for one test case and the corresponding test results are available), obtaining N results, classifying the results after aggregation, storing the results in a designated mysql database, establishing a new analysis program version library when the results are subsequently called, analyzing the results obtained by combining the test function with the corresponding test case, and then carrying out automatic analysis to see whether the results can be matched with the previous analysis results when the analysis program version library is modified.
Specifically, the analysis software obtains a fault analysis result by analyzing the waveform file uploaded when the fault occurs. The parameter file required by the software in analyzing the waveform file is composed of two parts: one part is a wave recording file recorded by the device when a fault occurs, the wave recording file consists of three files of hdr, dat and cfg, the three files have slight differences according to the information recorded by different standard versions, and the hdr file records the basic description of the fault and comprises the information of head time, device state, communication state and the like; the dat file records the used standard version, the wave recording data of all lines on the device and the sampling frequency; the cfg file comprises the names of all lines on the device and the starting time of recording waves; and the other part of files are matched with the model files of the fault device, wherein the analysis software needs to analyze the waveform files through the dmf files so as to obtain analysis results.
The method comprises the steps of establishing a fault library through statistics of historical recording data, carrying out unified storage management on faults according to the types and the types of the faults, belonging to the circuits, and obtaining national fault distribution conditions, wherein when a test case is established, in order to test the performance of analysis software, unified analysis is required to be carried out on one or more fault files under different conditions, screening is generally required to be carried out according to the types of the faults, the types of the faults and the belonging to the regions when the faults are selected, and screening is also required to be carried out under specific weather conditions when the faults under severe weather are required to be analyzed.
And recording analysis software of each current version, and establishing a software analysis program version library. The analysis software of each version records the corresponding relevant characteristics (mainly including version number, time, serial number and private description of the analysis software of the version), serial number and creation time, and is convenient for developers to inquire. Each version library needs to upload the corresponding analysis program, and the analysis program file can be updated and maintained in the process of maintaining the analysis program version library.
Analyzing the same fault data by using analysis software of different versions to obtain new analysis results, and comparing the analysis results with standard results to obtain a test report of the tested software.
By establishing a fault library and an analysis program version library, corresponding test cases can be established according to different test requirements. The test case library consists of two parts: the fault information base selects the corresponding fault file and the analysis program selected from the analysis program version base. Test cases are divided into two types: single-ended test cases and double-ended test cases. The single-ended test case needs to select a single-ended case when the basic information is configured, the matched fault information comprises all fault wave recording files, the double-ended test case needs to select a double-ended case when the basic information is configured, the faults matched with the double-ended test case are double-ended line faults, and the double-ended faults comprise fault files of two devices of a local end and an opposite end and are mostly used for fault ranging analysis. According to the different test contents of the test cases of the analysis software, a fault library meeting the conditions, such as fault data under thunderstorm weather or certain type of fault data in a certain area, can be established through screening, and in order to test the analysis results of the analysis software on various fault files, a plurality of test cases are required to be established in a targeted manner, and a final test report is generated through unified test.
After selecting the case type and specific fault data, the analysis program to be tested is selected. The number of the analysis program reflects the generation time and specific version of the program, so that the selection of a tester is facilitated, and before the test, an analysis program version library of a corresponding version needs to be created and uploaded. One test case can select one or more analysis programs, and test results do not affect each other. Besides establishing a new test case, the established test case can be selected, the fault library configuration is not required to be changed, and only the version of the analysis program version library to be tested is required to be added in the analysis program version library part.
After the test case is generated, a test report is generated through a test program. The test report is to compare the test result obtained by the test software analysis with the standard fault analysis result, and judge whether the analysis function of the tested program is complete or not by comparing different data obtained by the analysis, at least ensuring that the determined analysis function is not lost. And under the condition that multiple analysis software are tested simultaneously, analyzing faults in the same fault library by using analysis software of different versions, automatically comparing the obtained analysis result with a standard result corresponding to the faults, if no corresponding standard file exists, taking the test result as the standard file and indicating the standard file in a test report, and finally obtaining a final test report of the tested analysis software.
Comparison of test program results with standard results there are three cases: one is that the analysis results are completely consistent, in which case the latest generated test report will automatically become a standard analysis report for the corresponding fault; the second case is that the number of faults of analysis reports is more than that of standard reports, at the moment, power engineering personnel are required to analyze the newly-appearing faults in combination with operation data, and when the fault information is determined to be error-free, the fault report is manually set as a new standard detection report of the series of analysis software, and the version characteristic description of the corresponding analysis program is updated; and finally, if the number of faults in the analysis report is less than the standard test result or the fault result does not accord with the actual condition of the corresponding fault data, the analysis software of the corresponding version needs to be checked, the problems of the software are found out according to the analyzed actual condition, and the problems are quickly processed by a developer, so that the main functions of the auxiliary management analysis software are achieved.
After the software test is completed, the test results of each software test are classified according to the test time, the serial numbers of the test software and the versions of the test software, and all test records of the analysis software of a specific version can be quickly queried through a test report query function, so that modification and update records of corresponding analysis programs and differences among other versions of programs of the series can be intuitively reflected. Meanwhile, in the process of checking the test result again, the test result of a certain fault can be manually set as a standard analysis result corresponding to the analysis program.
In the aspect of fault management, the conventional fault operation and maintenance management system refers to the use habit of field operation maintenance personnel, establishes a region/station/equipment/line multistage fault data management mode, and meets the practical requirements of power engineering software design.
Example two
It is an object of the present embodiment to provide a computing device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing specific steps in the above method when executing the program.
Example III
An object of the present embodiment is to provide a computer-readable storage medium.
A computer readable storage medium having stored thereon a computer program which when executed by a processor performs specific steps in the above method.
Example IV
An object of the present embodiment is to provide a power system fault operation and maintenance system, implemented based on a server, including:
a library building module configured to: establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software;
an analysis module configured to: analyzing the fault files in the test cases in the test case library by selecting analysis software with different versions from the analysis version library to obtain an analysis result of each fault file;
a contrast module configured to: and comparing the analysis result of each fault file with a standard test report of the fault file corresponding to the fault database to obtain a test result of the corresponding analysis software.
The steps involved in the devices of the second, third and fourth embodiments correspond to those of the first embodiment of the method, and the detailed description of the embodiments can be found in the related description section of the first embodiment. The term "computer-readable storage medium" should be taken to include a single medium or multiple media including one or more sets of instructions; it should also be understood to include any medium capable of storing, encoding or carrying a set of instructions for execution by a processor and that cause the processor to perform any one of the methods of the present disclosure.
It will be appreciated by those skilled in the art that the modules or steps of the disclosure described above may be implemented by general-purpose computer means, alternatively they may be implemented by program code executable by computing means, so that they may be stored in storage means and executed by computing means, or they may be fabricated separately as individual integrated circuit modules, or a plurality of modules or steps in them may be fabricated as a single integrated circuit module. The present disclosure is not limited to any specific combination of hardware and software.
The foregoing description of the preferred embodiments of the present disclosure is provided only and not intended to limit the disclosure so that various modifications and changes may be made to the present disclosure by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.
While the specific embodiments of the present disclosure have been described above with reference to the drawings, it should be understood that the present disclosure is not limited to the embodiments, and that various modifications and changes can be made by one skilled in the art without inventive effort on the basis of the technical solutions of the present disclosure while remaining within the scope of the present disclosure.
Claims (10)
1. A power system fault operation and maintenance method, comprising:
establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test analysis software;
analyzing the fault files in the test cases in the test case library by selecting analysis software with different versions from the analysis version library to obtain an analysis result of each fault file;
comparing the analysis result of each fault file with a standard test report of the fault file corresponding to the fault database to obtain a test result of the corresponding analysis software;
the test case library consists of two parts: the fault database selects corresponding fault files and analysis software selected from the analysis version library;
faults within the same fault database are analyzed by using different versions of analysis software.
2. A power system fault operation and maintenance method as claimed in claim 1, wherein the fault database contains various types of fault data including the region to which the fault device belongs, the fault type, the fault phase and the weather condition at the time of occurrence of the fault.
3. The power system fault operation and maintenance method as claimed in claim 1, wherein the establishing and maintaining of the analysis version library includes: if the faults to be analyzed do not exist in the test case library, the faults are new faults, and the analysis version library is updated;
when the analysis result fails, the analysis software of the corresponding version is changed and processed in time, and the failure data is partially changed along with the upgrading of the corresponding device and the difference of device manufacturers, so that the analysis software is upgraded in time.
4. The power system fault operation and maintenance method according to claim 1, wherein after the analysis result of each fault file is obtained, whether the analysis software meets the use requirement is judged by comparing the test result with the standard result, and other fault information in the assumption is obtained on the premise of ensuring that the determined fault result is not changed, so that the success of the software upgrading is ensured;
when the test result meets the requirement, the test result is used as a new test result corresponding to the fault data and used for comparing the results of the later new analysis software and inquiring the analysis result during fault maintenance.
5. A power system fault operation and maintenance method as claimed in claim 1, wherein the parameter file required by the analysis software in analyzing the waveform file is composed of two parts: one part is a wave recording file recorded by the device when a fault occurs, the other part is a model file matched with the fault device, and analysis software needs to analyze the waveform file through the model file so as to obtain an analysis result;
and the fault database performs unified storage management on faults according to the types, the affiliated lines and the affiliated areas to obtain the national fault distribution condition.
6. The power system fault operation and maintenance method as claimed in claim 1, wherein when a test case library required by test analysis software is established, unified analysis is performed on fault files under one or more different conditions, screening is performed according to the type of fault and the region to which the fault belongs when the fault is selected, and screening is performed under the condition of severe weather when the fault under the severe weather is required to be analyzed.
7. The power system fault operation and maintenance method as claimed in claim 1, wherein in the analysis version library, the analysis software of each version records the corresponding relevant characteristics, the sequence number and the creation time, so that the inquiry is convenient, each version library needs to upload the corresponding analysis software, and the update maintenance is performed on the files of the analysis software in the process of maintaining the analysis version library.
8. A power system fault operation and maintenance system based on the method of any one of claims 1-7, comprising:
a library building module configured to: establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test analysis software;
an analysis module configured to: analyzing the fault files in the test cases in the test case library by selecting analysis software with different versions from the analysis version library to obtain an analysis result of each fault file;
a contrast module configured to: and comparing the analysis result of each fault file with a standard test report of the fault file corresponding to the fault database to obtain a test result of the corresponding analysis software.
9. A computing device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the specific steps of the method of any of claims 1-7 when the program is executed.
10. A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the specific steps of the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011195977.5A CN112306877B (en) | 2020-10-30 | 2020-10-30 | Power system fault operation and maintenance method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011195977.5A CN112306877B (en) | 2020-10-30 | 2020-10-30 | Power system fault operation and maintenance method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112306877A CN112306877A (en) | 2021-02-02 |
| CN112306877B true CN112306877B (en) | 2024-02-20 |
Family
ID=74333222
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011195977.5A Active CN112306877B (en) | 2020-10-30 | 2020-10-30 | Power system fault operation and maintenance method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112306877B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113011606A (en) * | 2021-01-30 | 2021-06-22 | 河南帅臣停车设备科技有限公司 | Operation and maintenance management method and system for mechanical parking equipment |
| CN113051582B (en) * | 2021-04-28 | 2023-03-14 | 重庆电子工程职业学院 | Computer software technology development and debugging system |
| CN113626288B (en) * | 2021-08-12 | 2023-08-25 | 杭州朗和科技有限公司 | Fault processing method, system, device, storage medium and electronic equipment |
| CN117130945B (en) * | 2023-10-26 | 2024-02-09 | 中国证券登记结算有限责任公司 | Test method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6651034B1 (en) * | 1999-10-28 | 2003-11-18 | General Electric Company | Apparatus and method for performance and fault data analysis |
| CN101014955A (en) * | 2004-10-01 | 2007-08-08 | 明导公司 | Feature failure correlation |
| CN102707195A (en) * | 2012-06-01 | 2012-10-03 | 江苏省电力公司检修分公司 | Oscilloscope fault analysis platform and establishment method thereof |
| CN103853765A (en) * | 2012-12-04 | 2014-06-11 | 天津市电力公司 | Method for comparing waveform features of power system faults |
| CN108804301A (en) * | 2017-04-27 | 2018-11-13 | 株洲中车时代电气股份有限公司 | A kind of train control system software testing system and method based on E & FR data |
| CN109813999A (en) * | 2019-01-22 | 2019-05-28 | 山东大学 | A kind of Fault Diagnosis of Distribution Network algorithm automatically testing platform, method and application |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101269549B1 (en) * | 2009-05-08 | 2013-06-04 | 한국전자통신연구원 | System and method for testing software reliability using fault injection |
-
2020
- 2020-10-30 CN CN202011195977.5A patent/CN112306877B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6651034B1 (en) * | 1999-10-28 | 2003-11-18 | General Electric Company | Apparatus and method for performance and fault data analysis |
| CN101014955A (en) * | 2004-10-01 | 2007-08-08 | 明导公司 | Feature failure correlation |
| CN102707195A (en) * | 2012-06-01 | 2012-10-03 | 江苏省电力公司检修分公司 | Oscilloscope fault analysis platform and establishment method thereof |
| CN103853765A (en) * | 2012-12-04 | 2014-06-11 | 天津市电力公司 | Method for comparing waveform features of power system faults |
| CN108804301A (en) * | 2017-04-27 | 2018-11-13 | 株洲中车时代电气股份有限公司 | A kind of train control system software testing system and method based on E & FR data |
| CN109813999A (en) * | 2019-01-22 | 2019-05-28 | 山东大学 | A kind of Fault Diagnosis of Distribution Network algorithm automatically testing platform, method and application |
Non-Patent Citations (3)
| Title |
|---|
| Facilitating Fault-Simulation Comprehension through a Fault-Lists Analysis Tool;P. Bernardi 等;《2019 IEEE 10th Latin American Symposium on Circuits & Systems (LASCAS)》;第77-80页 * |
| Review: power system analysis software tools;L. Bam 等;《IEEE Power Engineering Society General Meeting , 2005》;第1卷;第139-144页 * |
| 基于多信号流图的系统测试性建模分析及软件设计;丁昊;《中国优秀硕士学位论文全文数据库 信息科技辑》;I138-411 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112306877A (en) | 2021-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112306877B (en) | Power system fault operation and maintenance method and system | |
| CN110209568B (en) | Coverage rate test method and device and storage equipment | |
| US9116779B2 (en) | Test management domain asset discovery and analysis | |
| CN110737594A (en) | Database standard conformance testing method and device for automatically generating test cases | |
| US11704186B2 (en) | Analysis of deep-level cause of fault of storage management | |
| CN112631607A (en) | Method for detecting dependency conflict in python environment | |
| CN117009243A (en) | Chip performance automatic test method, device, computer equipment and storage medium | |
| CN113126993A (en) | Automatic testing method and system applied to vehicle detection software | |
| CN109376073B (en) | Test environment memory and recovery method | |
| CN115658402A (en) | Test case management method and device, electronic equipment and readable storage medium | |
| CN111414299B (en) | SSD (solid State disk) extension information acquisition method and device based on hdchart | |
| CN111240999A (en) | Method and system for improving script test execution efficiency | |
| CN113342632A (en) | Simulation data automatic processing method and device, electronic equipment and storage medium | |
| CN112231202A (en) | Automatic Bug lifting method based on log monitoring and monitored module monitoring | |
| US6389370B1 (en) | System and method for determining which objects in a set of objects should be processed | |
| CN111949281A (en) | Database installation method based on AI configuration, user equipment and storage medium | |
| CN113806119A (en) | Memory card processing method, device, equipment and storage medium | |
| CN107102938B (en) | Test script updating method and device | |
| CN114448851B (en) | Automatic data testing method and system | |
| CN110795297B (en) | Electronic equipment testing method and device | |
| CN112148459B (en) | Processing method, device, readable medium and equipment for node association data | |
| US20230216727A1 (en) | Identification of root causes in data processing errors | |
| US8751870B2 (en) | Method and system for providing a random sequence coverage | |
| CN114546692A (en) | Fault classification method and device of solid state disk, storage medium and computer equipment | |
| CN115168124A (en) | Stability test method and device for concurrently executing multiple files on hard disk, computer equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |