CN111506544B - Power grid safety and stability control device strategy model file verification method and device - Google Patents
Power grid safety and stability control device strategy model file verification method and device Download PDFInfo
- Publication number
- CN111506544B CN111506544B CN202010133980.8A CN202010133980A CN111506544B CN 111506544 B CN111506544 B CN 111506544B CN 202010133980 A CN202010133980 A CN 202010133980A CN 111506544 B CN111506544 B CN 111506544B
- Authority
- CN
- China
- Prior art keywords
- data block
- strategy
- definition
- formula
- model file
- 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 38
- 238000012795 verification Methods 0.000 title claims description 62
- 238000011217 control strategy Methods 0.000 claims abstract description 43
- 238000005259 measurement Methods 0.000 claims abstract description 26
- 239000000470 constituent Substances 0.000 claims description 31
- 238000006243 chemical reaction Methods 0.000 claims description 9
- 230000008520 organization Effects 0.000 claims description 7
- 230000001934 delay Effects 0.000 claims description 5
- 238000003825 pressing Methods 0.000 claims description 3
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000012423 maintenance Methods 0.000 abstract description 4
- 230000003993 interaction Effects 0.000 abstract description 3
- 230000000875 corresponding effect Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 238000004088 simulation Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001276 controlling effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/90335—Query processing
- G06F16/90344—Query processing by using string matching techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/06—Energy or water supply
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S10/00—Systems supporting electrical power generation, transmission or distribution
- Y04S10/50—Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Water Supply & Treatment (AREA)
- Tourism & Hospitality (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Primary Health Care (AREA)
- Marketing (AREA)
- Library & Information Science (AREA)
- Human Resources & Organizations (AREA)
- General Health & Medical Sciences (AREA)
- Public Health (AREA)
- Computational Linguistics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method and a device for checking a strategy model file of a power grid safety and stability control device, which aim at the strategy model description file of the power grid safety and stability control device based on a common model description specification (CIM/E) format of a power grid, carry out correctness checking on the format specification of the strategy file, further respectively carry out validity and validity checking on seven component element stability control strategies, execution strategies, control measures, fault definitions, section definitions, formula definitions and element measurement definitions of the strategy model on the basis, and finally output the checking state of the file and specific error information of contents which the corresponding checking does not pass. According to the invention, the effectiveness and the correctness of the contents of the policy model file of the power grid safety and stability control device are automatically verified, so that the maintenance and interaction efficiency of the policy model can be effectively improved.
Description
Technical Field
The invention belongs to the technical field of power systems and automation, and particularly relates to a method and a device for verifying a policy model file of a power grid safety and stability control device.
Background
The safety and stability control system and the device are important safety automatic control equipment for ensuring safe and stable operation of the power grid, and the operation condition and the corresponding action behavior of the safety and stability control system and the device need to be considered when the actual power grid dispatching operation is controlled. Due to the differences among the problems, specific control ranges and control modes to be solved by different safety and stability control systems and devices, the safety and stability control strategy model is poor in universality and complex to maintain.
At present, a policy model file is generally manually written according to policy logic of a stability control device, and abnormal conditions such as format errors, character string length exceeding the maximum limit, numerical values not within an effective range, absence of associated equipment in a model library, keyword spelling errors in formula definition and the like can exist. In order to improve the efficiency of writing and maintaining the policy model file, a method for verifying the policy model of the power grid safety and stability control device is urgently needed.
Chinese invention patent application no: 201810935484.7A method for evaluating the feasibility of the current value strategy of a safety and stability control device of an electric power system, which aims at the limitations of the control strategy modeling and simulation technology of the safety and stability control device of the existing electric power system, provides a method for evaluating the feasibility of the current value strategy of the safety and stability control device of the electric power system, can realize the uniform description of the stability control strategy, the identification of the current value strategy and the simulation of the action behavior, and further evaluates whether the action result is in line with the expectation or not on the basis, thereby effectively improving the intelligent level of the on-line monitoring and early warning of the safety and stability control device of the electric power system. However, an automatic verification method of the control strategy model of the safety and stability control device of the power system is not considered.
Chinese invention patent application no: 201410844016.0A simulation system and method for power system safety control strategy, providing a power system safety and stability control strategy simulation system and method based on script analysis technique, describing the control strategy of the power system safety and stability control device based on the power system mode description language, and realizing the simulation of the control strategy logic and action based on the description. The method can flexibly describe various customized control strategies based on the script language, but the maintenance is complex, and a unified automatic checking mechanism is not provided for a strategy model.
Disclosure of Invention
The invention discloses a method and a device for checking a strategy model file of a power grid safety and stability control device, which aim at the strategy model description file of the power grid safety and stability control device based on a common model description specification-CIM/E format of a power grid, carry out correctness checking on the format specification of the strategy file, further carry out validity and validity checking on seven component element stability control strategies, execution strategies, control measures, fault definitions, section definitions, formula definitions and element measurement definitions of the strategy model respectively on the basis, and finally output the checking state of the file and specific error information which does not pass corresponding checking. According to the invention, the effectiveness and the correctness of the contents of the policy model file of the power grid safety and stability control device are automatically verified, so that the maintenance and interaction efficiency of the policy model can be effectively improved.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
an embodiment of the present invention provides a method for checking a policy model file of a power grid safety and stability control device, including:
reading a strategy model file of the stability control device;
if the content format of the strategy model file conforms to the specification, analyzing and organizing the content of the strategy model file according to the data blocks; carrying out validity and validity check on each record in each data block in the strategy model file;
if the content format of the strategy model file does not meet the specification or the recording error of the data block is detected, outputting a corresponding error prompt;
and summarizing and counting the content format of the policy model file and the verification result of the data block, and outputting a verification state and an error prompt.
Further, the process of determining whether the content format of the policy model file meets the specification includes:
obtaining the name of the stable control device from the system statement of the strategy model file, searching device records in the device model according to the device name, and giving an error prompt if the device records cannot be searched;
checking whether the initial mark and the end mark of the data block are matched, if so, determining that the format of the data block is correct, otherwise, giving an error prompt;
checking whether the appointed data block name is consistent with the data block name contained in the data block starting mark and the data block ending mark, if so, judging that the data block name is correct, otherwise, giving an error prompt;
checking whether the number of the columns in the attribute row of the data block is equal to the number of the columns in the recording row of the device, if so, judging that the data block is correct, otherwise, giving an error prompt;
checking whether the names of the attribute columns of the appointed data block are consistent with the names of all the columns of the attribute rows in the data block or not, if so, judging that the data block is correct, otherwise, giving an error prompt;
and if the verification is in accordance with the standard, the content format of the model file is in accordance with the standard.
Further, the analyzing and organizing the content of the policy model file according to the data block includes:
the method comprises the following steps of dividing the content of a strategy model file into a stability control strategy data block, an execution strategy data block, a control measure data block, a fault definition data block, a section definition data block, a formula definition data block and an element measurement definition data block.
Further, the checking the validity and validity of each record in each data block in the policy model file includes:
verifying each record in each data block in the strategy model file according to a pre-written verification program of the data block; the verification program is obtained by writing according to the constituent elements of the data block;
the stability control strategy data block comprises stability control strategy names, a stability control device, strategy types, strategy rounds, round relations, control step lengths, priority rules, mode constraints, fault constraints, load flow constraints, priority formulas, constraint conditions and control strategy expression forming elements;
the execution strategy data block comprises the constituent elements of an execution strategy name, a stable control device, a control type, an adjustment quantity type, a control step length, a priority rule, binding execution, a control quantity conversion coefficient, a priority formula, a constraint condition and an execution strategy expression;
the control measure data block comprises control measure names, space names of the measure, a stability control device, associated equipment, control types, adjustment quantity types, measure delay, execution time, gear control quantity, adjustment upper limits, priority rules, binding execution, priority formulas and constraint condition forming elements;
the fault definition data block comprises a fault name and a fault definition component element;
the section definition data block comprises a section name and a section definition component element;
the formula definition data block comprises formula names, formula definitions and formula type constituent elements;
the component measurement definition data block comprises component names, measurement point names and component alias forming elements.
Further, the writing of the verification program for each stability control policy record according to the constituent elements of the data block includes:
3.1a) the stability control strategy name does not exceed the maximum length limit of the appointed character string and has no repetition in the current data block;
3.1b) the stable control device to which the device belongs exists in the device model;
3.1c) the strategy type, the strategy turn, the turn relation, the control step length and the priority rule value are all in an effective range;
3.1d) if the power flow constraint, the priority formula and the constraint condition are not empty, the current constraint, the priority formula and the constraint condition exist in the formula definition data block, and the corresponding formula passes the verification of the verification logic according to the formula definition;
3.1e) the operation mode name of the mode constraint association reference exists in the formula definition data block, and the logical verification is passed according to the operation mode;
3.1f) the fault name related and referred by the fault constraint exists in the fault definition data block, and the logic verification is passed according to the fault definition;
3.1g) the control strategy expression comprises constituent elements of an execution strategy expression, a control mode and a quantity-needed formula, wherein the execution strategy name related and quoted by the execution strategy expression exists in the execution strategy data block, the value range of the control mode comprises three types of minimum over-cut, minimum under-cut and closest, and the quantity-needed formula is verified to be logical check-passed according to formula definition.
Further, the writing of the verification program according to the constituent elements of the data block for each execution policy record includes:
3.2a) the execution policy name does not exceed the agreed maximum length of string limit and there is no duplication within the current data block;
3.2b) the stable control device to which the device belongs exists in the device model;
3.2c) the control type, the adjustment quantity type, the control step length, the priority rule, the binding execution and the control quantity conversion coefficient value are all in an effective range;
3.2d) if the priority formula and the constraint condition are not empty, the priority formula and the constraint condition exist in the formula definition data block, and the corresponding formula passes the verification of the verification logic according to the formula definition;
3.2e) the execution policy names related and referred to by the execution policy expression exist in the execution policy data block, and the referred measure space names exist in the control measure data block.
Further, writing a verification program according to the constituent elements of the data block for each control measure record, including:
3.3a) controlling the measure name and the measure space name not to exceed the maximum length limit of the appointed character string;
3.3b) the stable control device exists in the device model;
3.3c) the control type, the adjustment quantity type, the measure delay, the execution time, the gear control quantity, the adjustment upper limit, the priority rule and the binding execution value are all in an effective range;
3.3d) if the priority formula and the constraint condition are not empty, the priority formula and the constraint condition exist in the formula definition data block, and the corresponding formula passes the verification of the verification logic according to the formula definition;
3.3e) associated equipment is present in the component metrology definition data block or in the equipment model library.
Further, writing a verification program for each fault definition record according to the constituent elements of the data block, including:
3.4a) the fault name does not exceed the agreed maximum length limit of the string and there is no duplication in the current data block;
3.4b) the fault definition string length does not exceed the maximum length limit;
3.4c) the number of left and right brackets in the fault definition match;
3.4d) the fault definition contains that the fault keywords are legal;
3.4e) the key word parameters in the fault definition are legal;
3.4f) all the devices referenced in the fault definition are present in the component metrology definition data block or device model library;
3.4g) the fault definition indicates that the format of the connector is correct when multiple faults are combined.
Further, the writing of the verification program according to the constituent elements of the data block for each section definition record includes:
3.5a) the section name does not exceed the agreed maximum length limit of the string and there is no duplication in the current data block;
3.5b) all section composition equipment types in the section definition are legal and all composition equipment exists in the component measurement definition data block or the equipment model library;
3.5c) section definition string length does not exceed maximum length limit.
Further, the writing of the verification program according to the constituent elements of the data block for each formula definition record includes:
3.6a) the formula name does not exceed the agreed maximum length string limit and there is no duplication within the current data block;
3.6b) formula defines that the length of the character string does not exceed the maximum length limit;
3.6c) the value of formula type is in effective range;
3.6d) the number of left and right brackets in the formula definition is matched;
3.6e) all operators/operations in the formula definition agree;
3.6f) the keywords contained in the formula definition are all legal;
3.6g) the key word parameters in the formula definition are all legal;
3.6h) all primary equipment referenced in the formula definition are present in the component metrology definition data block or the equipment model library;
3.6i) the sections referenced in the formula definition are present in the section definition data block;
3.6j) the safety control device/fixed value/pressing plate/channel quoted in the formula definition exists in the safety control model library;
3.6k) other formula names that are nested references in the formula definition are present in the formula definition data block.
Further, the writing of the verification program according to the constituent elements of the data block for each element measurement definition record includes:
3.7a) the element name does not exceed the agreed maximum length limit of the string;
3.7b) the element alias does not exceed the agreed maximum length of string limit and there is no duplication within the current data block;
3.7c) component names are present in the device model library;
3.7d) element measurement points exist in the equipment model library;
3.7e) all column string lengths do not exceed the maximum allowed length for that column.
Another aspect of the embodiments of the present invention provides a device for checking a policy model file of a power grid safety and stability control device, including:
the content format checking module is used for reading the policy model file of the stability control device, checking whether the content format of the policy model file meets the specification or not, and checking the policy model file with the content format not meeting the specification to give a file content format error prompt;
the organization module is used for analyzing and organizing the content of the strategy model file according to the data blocks;
the data block checking module is used for checking the legality and the validity of each record in each data block in the strategy model file and giving corresponding error prompt to the record with the detected error;
and the statistical module is used for summarizing and counting the verification results of the content format verification module and the data block verification module and outputting verification status and error prompt.
Further, the organization module is particularly adapted for,
the content of the strategy model file is divided into 7 data blocks of stability control strategy, execution strategy, control measure, fault definition, section definition, formula definition and element measurement definition.
Further, the data block check module is specifically configured to,
storing a verification program written according to the composition elements of the data block:
for each record in each data block, running a check program of the data block;
the stability control strategy data block comprises stability control strategy names, a belonging stability control device, strategy types, strategy rounds, a round relation, a control step length, a priority rule, mode constraints, fault constraints, load flow constraints, a priority formula, constraint conditions and control strategy expression forming elements;
the execution strategy data block comprises the constituent elements of an execution strategy name, a stable control device, a control type, an adjustment quantity type, a control step length, a priority rule, binding execution, a control quantity conversion coefficient, a priority formula, a constraint condition and an execution strategy expression;
the control measure data block comprises control measure names, affiliated measure space names, affiliated stability control devices, associated equipment, control types, adjustment quantity types, measure delays, execution time, gear control quantities, adjustment upper limits, priority rules, binding execution, priority formulas and constraint conditions;
the fault definition data block comprises a fault name and a fault definition component element;
the section definition data block comprises a section name and a section definition component element;
the formula definition data block comprises formula names, formula definitions and formula type constituent elements;
the component measurement definition data block comprises component names, measuring point names and component alias forming elements.
The invention achieves the following beneficial effects:
the invention provides a method for checking a policy model file of a power grid safety and stability control device, which is used for automatically checking a policy model file compiled based on a power system safety and stability control device specification, a policy table and a fixed value list, and finally outputting a file checking state and specific error information that the corresponding checking fails, thereby effectively improving the efficiency of policy model maintenance and interaction.
Drawings
FIG. 1 is a flow chart of the method of the present invention.
Detailed Description
The invention is further described below. The following examples are only for illustrating the technical solutions of the present invention more clearly, and the protection scope of the present invention is not limited thereby.
The embodiment of the invention provides a method for checking a policy model file of a power grid safety and stability control device, which comprises the following steps:
1) reading a policy model file of the stability control device, checking whether the content format of the policy model file conforms to the specification, and entering the step 2) if the content format conforms to the specification; if the format is not in accordance with the specification, giving a file content format error prompt, and entering the step 4);
specifically, whether the content format of the policy model file meets the specification or not is verified according to the power grid common model description specification-CIM/E format according to the following steps:
1.1) obtaining the name of a stable control device from a system declaration part of a strategy model file and checking the correctness of the stable control device;
searching a device record in the device model according to the device name, if the device record cannot be searched, indicating that the device does not exist in the device model, and giving an error prompt;
1.2) checking the correctness of the format of the data block according to whether the starting mark and the ending mark of the data block are matched;
1.3) checking whether the data block names contained in the starting mark and the ending mark of the data block are strictly consistent with the data block names according to the appointed data block names;
1.4) checking whether the number of columns in the attribute row of the data block is equal to the number of columns in the recording row of the device in the device model;
1.5) checking whether the names of all the columns of the attribute rows in the data block are strictly consistent with the names of the attribute columns of the agreed data block;
and if the verification is in accordance with the standard, the content format of the model file is in accordance with the standard.
2) And respectively analyzing and organizing the content of the strategy model file according to the data blocks.
Specifically, the contents of the policy model file are read and then are organized into data blocks.
Finally generating 7 data blocks of stability control strategy, execution strategy, control measure, fault definition, section definition, formula definition and element measurement definition.
3) For each data block in the strategy model file, respectively carrying out validity and validity verification on each line of data of each record contained in the strategy model file, if an error is detected, outputting a corresponding error prompt until the verification of all the data blocks is completed, and entering step 4), wherein the specific verification is automatically realized through computer programming according to the following verification logic as follows:
3.1) carrying out the following verification on each record in the stability control strategy data block;
the stability control strategy data block comprises stability control strategy names, a belonging stability control device, strategy types, strategy rounds, a round relation, a control step length, a priority rule, mode constraints, fault constraints, load flow constraints, a priority formula, constraint conditions and control strategy expression forming elements;
for a single stable control strategy record, if the following conditions are all satisfied, the content of the record is considered to pass the verification:
3.1a) the stability control strategy name does not exceed the maximum length limit of the appointed character string and has no repetition in the current data block;
3.1b) the stable control device to which the device belongs exists in the device model;
3.1c) the value of the numerical sequence (strategy type, strategy round, round relation, control step length and priority rule) is in the effective range;
3.1d) if the power flow constraint, the priority formula and the constraint condition are not empty, the current constraint, the priority formula and the constraint condition exist in the formula definition data block, and the corresponding formula passes the verification of the verification logic according to the formula definition;
3.1e) the operation mode name of the mode constraint association reference exists in the formula definition data block, and the logical verification is passed according to the operation mode;
3.1f) the fault name related and quoted by the fault constraint exists in the fault definition data block, and the logic check passes according to the fault definition;
3.1g) the control strategy expression comprises constituent elements of an execution strategy expression, a control mode and a required control quantity formula, wherein the execution strategy name related and quoted by the execution strategy expression exists in an execution strategy data block, the value range of the control mode comprises three types, namely minimum over cut (> =), minimum under cut (< (=) and closest (=), and the required control quantity formula passes the verification of the verification logic according to formula definition.
3.2) checking each record in the execution strategy data block as follows;
the execution strategy data block comprises the constituent elements of an execution strategy name, a stable control device, a control type, an adjustment quantity type, a control step length, a priority rule, binding execution, a control quantity conversion coefficient, a priority formula, a constraint condition and an execution strategy expression;
the check is considered to pass if all of the following conditions are satisfied:
3.2a) the execution policy name does not exceed the agreed maximum length of string limit and there is no duplication within the current data block;
3.2b) the stable control device exists in the device model;
3.2c) the numerical value column (control type, regulating variable type, control step length, priority rule, binding execution and control variable conversion coefficient) is in the effective range;
3.2d) if the priority formula and the constraint condition are not empty, the priority formula and the constraint condition exist in the formula definition data block, and the corresponding formula passes the verification of the verification logic according to the formula definition;
3.2e) the execution policy names related and referred to by the execution policy expression exist in the execution policy data block, and the referred measure space names exist in the control measure data block.
Example 1:
the execution policy data block has 1 record named "execution policy 1", and the content of the execution policy expression is: the "execution policy 2" indicates that the execution policy 1 refers to the execution policy 2 in a nested manner, and the "execution policy 2" is a record corresponding to the "execution policy 2" name in the execution policy data block.
Example 2:
the execution policy data block has 1 record named "execution policy 3", and the content of the execution policy expression is: "measure space 1", which indicates that the execution policy 3 refers to the measure space 1, and "measure space 1" indicates a control measure record with the name "measure space 1" for all measure spaces in the control measure data block.
3.3) checking each record in the control measure data block as follows;
the control measure data block comprises control measure names, affiliated measure space names, affiliated stability control devices, associated equipment, control types, adjustment quantity types, measure delays, execution time, gear control quantities, adjustment upper limits, priority rules, binding execution, priority formulas and constraint conditions;
the check is considered to pass if all of the following conditions are satisfied:
3.3a) the control measure name and the space name of the measure do not exceed the maximum length limit of the appointed character string;
3.3b) the stable control device of the device exists in the device model;
3.3c) the numerical value array (control type, adjustment quantity type, measure delay, execution time, gear control quantity, adjustment upper limit, priority rule and binding execution) is in the effective range;
3.3d) if the priority formula and the constraint condition are not empty, the priority formula and the constraint condition exist in the formula definition data block, and the corresponding formula passes the verification of the verification logic according to the formula definition;
3.3e) associated equipment is present in the component metrology definition data block or in the equipment model library.
3.4) carrying out the following verification on each record in the fault definition data block;
the fault definition data block includes a fault name and a fault definition component.
The check is considered to pass if all of the following conditions are satisfied:
3.4a) the fault name does not exceed the agreed maximum length limit of the string and there is no duplication in the current data block;
3.4b) the fault definition string length does not exceed the maximum length limit;
3.4c) the number of left and right brackets in the fault definition match;
3.4d) the fault definition contains that the fault keywords are legal;
3.4e) the key word parameters in the fault definition are legal;
3.4f) all the devices referenced in the fault definition are present in the component metrology definition data block or device model library;
3.4g) the fault definition indicates that the format of the connector is correct when multiple faults are combined.
3.5) carrying out the following verification on each record in the section definition data block;
the section definition data block includes a section name and a section definition component.
The check is considered to pass if all of the following conditions are satisfied:
3.5a) the section name does not exceed the agreed maximum length limit of the string and there is no duplication in the current data block;
3.5b) all section composition equipment types in the section definition are legal and all composition equipment exists in the component measurement definition data block or the equipment model library;
3.5c) section definition string length does not exceed maximum length limit.
3.6) carrying out the following verification on each record in the formula definition data block;
the formula definition data block comprises formula names, formula definitions and formula type constituent elements.
The check is considered to pass if all of the following conditions are satisfied:
3.6a) the formula name does not exceed the agreed maximum length string limit and there is no duplication within the current data block;
3.6b) formula defines that the length of the character string does not exceed the maximum length limit;
3.6c) the value of the formula type is in an effective range;
3.6d) the number of left and right brackets in the formula definition is matched;
3.6e) all operators/operations in the formula definition agree;
3.6f) the keywords contained in the formula definition are all legal;
3.6g) the key word parameters in the formula definition are all legal;
3.6h) all primary equipment referenced in the formula definition are present in the component metrology definition data block or the equipment model library;
3.6i) the sections referenced in the formula definition are present in the section definition data block;
3.6j) the safety control device/fixed value/pressing plate/channel quoted in the formula definition exists in the safety control model library;
3.6k) other formula names that are nested references in the formula definition are present in the formula definition data block.
3.7) carrying out the following verification on each record in the element measurement definition data block;
the component measurement definition data block comprises component names, measuring point names and component alias forming elements.
The check is considered to pass if all of the following conditions are satisfied:
3.7a) the component name does not exceed the agreed maximum length of string limit;
3.7b) the element alias does not exceed the agreed maximum length of string limit and there is no duplication within the current data block;
3.7c) component names are present in the device model library;
3.7d) element measurement points exist in the equipment model library;
3.7e) all column string lengths do not exceed the maximum allowed length for that column.
4) And summarizing and counting the format of the strategy model file and the verification result of each data block, and outputting verification status and error information prompt.
Another aspect of the embodiments of the present invention provides a device for checking a policy model file of a power grid safety and stability control device, including:
the content format checking module is used for reading the policy model file of the stability control device, checking whether the content format of the policy model file meets the specification or not, and checking the policy model file with the content format not meeting the specification to give a file content format error prompt;
the organization module is used for analyzing and organizing the content of the strategy model file according to the data blocks;
the data block checking module is used for checking the legality and the validity of each record in each data block in the strategy model file and giving corresponding error prompt to the record with the detected error;
and the statistical module is used for summarizing and counting the verification results of the content format verification module and the data block verification module and outputting verification state and error prompt.
Further, the organization module is particularly adapted for,
the content of the strategy model file is divided into 7 data blocks of stability control strategy, execution strategy, control measure, fault definition, section definition, formula definition and element measurement definition.
Further, the data block check module is specifically configured to,
storing a verification program written according to the composition elements of the data block:
for each record in each data block, running a check program of the data block;
the stability control strategy data block comprises stability control strategy names, a belonging stability control device, strategy types, strategy rounds, a round relation, a control step length, a priority rule, mode constraints, fault constraints, load flow constraints, a priority formula, constraint conditions and control strategy expression forming elements;
the execution strategy data block comprises the constituent elements of an execution strategy name, a stable control device, a control type, an adjustment quantity type, a control step length, a priority rule, binding execution, a control quantity conversion coefficient, a priority formula, a constraint condition and an execution strategy expression;
the control measure data block comprises control measure names, affiliated measure space names, affiliated stability control devices, associated equipment, control types, adjustment quantity types, measure delays, execution time, gear control quantities, adjustment upper limits, priority rules, binding execution, priority formulas and constraint conditions;
the fault definition data block comprises a fault name and a fault definition component element;
the section definition data block comprises a section name and a section definition component element;
the formula definition data block comprises formula names, formula definitions and formula type constituent elements;
the component measurement definition data block comprises component names, measurement point names and component alias forming elements.
It is to be noted that the apparatus embodiment corresponds to the method embodiment, and the implementation manners of the method embodiment are all applicable to the apparatus embodiment and can achieve the same or similar technical effects, so that the details are not described herein.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Finally, it should be noted that: although the present invention has been described in detail with reference to the above embodiments, it should be understood by those skilled in the art that: modifications and equivalents may be made to the embodiments of the invention without departing from the spirit and scope of the invention, which is to be covered by the claims.
Claims (11)
1. A method for checking a strategy model file of a power grid safety and stability control device is characterized by comprising the following steps:
reading a policy model file of the stability control device, and judging whether the content format of the policy model file meets the specification;
if the content format of the strategy model file conforms to the specification, analyzing and organizing the content of the strategy model file according to the data blocks; carrying out validity and validity check on each record in each data block in the strategy model file;
if the content format of the strategy model file does not meet the specification or the recording error of the data block is detected, outputting a corresponding error prompt;
summarizing and counting the content formats of the strategy model files and the verification results of the data blocks, and outputting verification states and error prompts;
the method for judging whether the content format of the strategy model file meets the specification comprises the following steps:
obtaining the name of the stable control device from the system statement of the strategy model file, searching device records in the device model according to the device name, and giving an error prompt if the device records cannot be searched;
checking whether the initial mark and the end mark of the data block are matched, if so, the format of the data block is correct, otherwise, giving an error prompt;
checking whether the appointed data block name is consistent with the data block name contained in the data block starting mark and the data block ending mark, if so, judging that the data block name is correct, otherwise, giving an error prompt;
checking whether the number of the columns in the attribute row of the data block is equal to the number of the columns in the recording row of the device, if so, judging that the data block is correct, otherwise, giving an error prompt;
checking whether the appointed data block attribute column name is consistent with each column name of the attribute row in the data block, if so, judging that the data block attribute column name is correct, and otherwise, giving an error prompt;
if the verification is in accordance with the standard, the content format of the model file is in accordance with the standard;
the content analysis and organization of the policy model file according to the data blocks comprises the following steps:
dividing the content of a strategy model file into a stability control strategy data block, an execution strategy data block, a control measure data block, a fault definition data block, a section definition data block, a formula definition data block and an element measurement definition data block;
the method for checking the legality and the validity of each record in each data block in the policy model file comprises the following steps:
verifying each record in each data block in the strategy model file according to a pre-written verification program of the data block; the verification program is obtained by writing according to the constituent elements of the data block;
the stability control strategy data block comprises stability control strategy names, a belonging stability control device, strategy types, strategy rounds, a round relation, a control step length, a priority rule, mode constraints, fault constraints, load flow constraints, a priority formula, constraint conditions and control strategy expression forming elements;
the execution strategy data block comprises the constituent elements of an execution strategy name, a stable control device, a control type, an adjustment quantity type, a control step length, a priority rule, binding execution, a control quantity conversion coefficient, a priority formula, a constraint condition and an execution strategy expression;
the control measure data block comprises control measure names, affiliated measure space names, affiliated stability control devices, associated equipment, control types, adjustment quantity types, measure delays, execution time, gear control quantities, adjustment upper limits, priority rules, binding execution, priority formulas and constraint conditions;
the fault definition data block comprises a fault name and a fault definition component element;
the section definition data block comprises a section name and a section definition component element;
the formula definition data block comprises formula names, formula definitions and formula type constituent elements;
the component measurement definition data block comprises component names, measurement point names and component alias forming elements.
2. The method for verifying the policy model file of the grid safety and stability control device according to claim 1, wherein for each stability control policy record, a verification program is written according to the constituent elements of the data block, and the method comprises the following steps:
3.1a) the stability control strategy name does not exceed the maximum length limit of the appointed character string and has no repetition in the current data block;
3.1b) the stable control device to which the device belongs exists in the device model;
3.1c) the strategy type, the strategy turn, the turn relation, the control step length and the priority rule value are all in the effective range;
3.1d) if the power flow constraint, the priority formula and the constraint condition are not empty, the current constraint, the priority formula and the constraint condition exist in the formula definition data block, and the corresponding formula passes the verification of the verification logic according to the formula definition;
3.1e) the operation mode name of the mode constraint association reference exists in the formula definition data block, and the logical verification is passed according to the operation mode;
3.1f) the fault name related and quoted by the fault constraint exists in the fault definition data block, and the logic check passes according to the fault definition;
3.1g) the control strategy expression comprises constituent elements of an execution strategy expression, a control mode and a quantity-needed formula, wherein the execution strategy name related and quoted by the execution strategy expression exists in the execution strategy data block, the value range of the control mode comprises three types of minimum over-cut, minimum under-cut and closest, and the quantity-needed formula is verified to be logical check-passed according to formula definition.
3. The method for verifying the strategy model file of the power grid safety and stability control device according to claim 1, wherein the step of writing a verification program according to the constituent elements of the data block for each execution strategy record comprises:
3.2a) the execution policy name does not exceed the agreed maximum length of string limit and there is no duplication within the current data block;
3.2b) the stable control device exists in the device model;
3.2c) the control type, the adjustment quantity type, the control step length, the priority rule, the binding execution and the control quantity conversion coefficient value are all in an effective range;
3.2d) if the priority formula and the constraint condition are not empty, the priority formula and the constraint condition exist in the formula definition data block, and the corresponding formula passes the verification of the verification logic according to the formula definition;
3.2e) the execution policy names related and referred to by the execution policy expression exist in the execution policy data block, and the referred measure space names exist in the control measure data block.
4. The method for verifying the policy model file of the grid safety and stability control device according to claim 1, wherein for each control measure record, a verification program is written according to the constituent elements of the data block, and the method comprises the following steps:
3.3a) controlling the measure name and the measure space name not to exceed the maximum length limit of the appointed character string;
3.3b) the stable control device exists in the device model;
3.3c) the control type, the adjustment quantity type, the measure delay, the execution time, the gear control quantity, the adjustment upper limit, the priority rule and the binding execution value are all in an effective range;
3.3d) if the priority formula and the constraint condition are not empty, the priority formula and the constraint condition exist in the formula definition data block, and the corresponding formula passes the verification of the verification logic according to the formula definition;
3.3e) associated equipment is present in the component metrology definition data block or in the equipment model library.
5. The method for verifying the policy model file of the grid safety and stability control device according to claim 1, wherein for each fault definition record, a verification program is written according to the constituent elements of the data block, and the method comprises the following steps:
3.4a) the fault name does not exceed the agreed maximum length limit of the string and there is no duplication in the current data block;
3.4b) the length of the fault definition character string does not exceed the maximum length limit;
3.4c) the number of left and right brackets in the fault definition match;
3.4d) the fault definition contains that the fault keywords are legal;
3.4e) the key word parameters in the fault definition are legal;
3.4f) all the devices referenced in the fault definition are present in the component metrology definition data block or device model library;
3.4g) the fault definition indicates that the format of the connector is correct when multiple faults are combined.
6. The method for verifying the strategy model file of the power grid safety and stability control device according to claim 1, wherein the step of writing a verification program according to the constituent elements of the data block for each section definition record comprises:
3.5a) the section name does not exceed the agreed maximum length limit of the string and there is no duplication in the current data block;
3.5b) all section composition equipment types in the section definition are legal and all composition equipment exists in the component measurement definition data block or the equipment model library;
3.5c) section definition string length does not exceed maximum length limit.
7. The method for verifying the policy model file of the grid safety and stability control device according to claim 1, wherein the step of writing a verification program for each formula definition record according to the constituent elements of the data block comprises:
3.6a) the formula name does not exceed the agreed maximum length string limit and there is no duplication within the current data block;
3.6b) formula defines that the length of the character string does not exceed the maximum length limit;
3.6c) the value of formula type is in effective range;
3.6d) the number of left and right brackets in the formula definition is matched;
3.6e) all operators/operations in the formula definition agree;
3.6f) the keywords contained in the formula definition are all legal;
3.6g) the key word parameters in the formula definition are all legal;
3.6h) all primary equipment referenced in the formula definition exist in the component metrology definition data block or the equipment model library;
3.6i) the sections referenced in the formula definition are present in the section definition data block;
3.6j) the safety control device/fixed value/pressing plate/channel quoted in the formula definition exists in the safety control model library;
3.6k) other formula names that are nested references in the formula definition are present in the formula definition data block.
8. The method for verifying the policy model file of the grid safety and stability control device according to claim 1, wherein the step of writing a verification program according to the constituent elements of the data block comprises:
3.7a) the component name does not exceed the agreed maximum length of string limit;
3.7b) element alias does not exceed the agreed maximum length string limit and has no repetition within the current data block;
3.7c) component names are present in the device model library;
3.7d) element measurement points exist in the equipment model library;
3.7e) all column string lengths do not exceed the maximum allowed length for that column.
9. A power grid safety and stability control device strategy model file checking device is characterized in that the checking device adopts the power grid safety and stability control device strategy model file checking method of any one of claims 1 to 8 to check a power grid safety and stability control device strategy model file;
the verification device includes:
the content format checking module is used for reading the policy model file of the stability control device, checking whether the content format of the policy model file meets the specification or not, and checking the policy model file with the content format not meeting the specification to give a file content format error prompt;
the organization module is used for analyzing and organizing the content of the strategy model file according to the data blocks;
the data block checking module is used for checking the legality and the validity of each record in each data block in the strategy model file and giving corresponding error prompt to the record with the detected error;
and the statistical module is used for summarizing and counting the verification results of the content format verification module and the data block verification module and outputting verification status and error prompt.
10. The verification apparatus for the policy model file of the grid safety and stability control apparatus according to claim 9, wherein the organization module is specifically configured to,
the content of the strategy model file is divided into 7 data blocks of stability control strategy, execution strategy, control measure, fault definition, section definition, formula definition and element measurement definition.
11. The verification device for the policy model file of the grid safety and stability control device according to claim 10, wherein the data block verification module is specifically configured to,
storing a verification program written according to the composition elements of the data block:
for each record in each data block, running a check program of the data block;
the stability control strategy data block comprises stability control strategy names, a belonging stability control device, strategy types, strategy rounds, a round relation, a control step length, a priority rule, mode constraints, fault constraints, load flow constraints, a priority formula, constraint conditions and control strategy expression forming elements;
the execution strategy data block comprises the constituent elements of an execution strategy name, a stable control device, a control type, an adjustment quantity type, a control step length, a priority rule, binding execution, a control quantity conversion coefficient, a priority formula, a constraint condition and an execution strategy expression;
the control measure data block comprises control measure names, affiliated measure space names, affiliated stability control devices, associated equipment, control types, adjustment quantity types, measure delays, execution time, gear control quantities, adjustment upper limits, priority rules, binding execution, priority formulas and constraint conditions;
the fault definition data block comprises a fault name and a fault definition component element;
the section definition data block comprises a section name and a section definition component element;
the formula definition data block comprises formula names, formula definitions and formula type constituent elements;
the component measurement definition data block comprises component names, measurement point names and component alias forming elements.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010133980.8A CN111506544B (en) | 2020-03-02 | 2020-03-02 | Power grid safety and stability control device strategy model file verification method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010133980.8A CN111506544B (en) | 2020-03-02 | 2020-03-02 | Power grid safety and stability control device strategy model file verification method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111506544A CN111506544A (en) | 2020-08-07 |
| CN111506544B true CN111506544B (en) | 2022-07-08 |
Family
ID=71875689
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010133980.8A Active CN111506544B (en) | 2020-03-02 | 2020-03-02 | Power grid safety and stability control device strategy model file verification method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111506544B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114118019B (en) * | 2022-01-27 | 2022-05-17 | 温州电力建设有限公司 | Stability control strategy normalization design method and system based on XML |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103576562A (en) * | 2013-11-07 | 2014-02-12 | 国家电网公司 | Electric power system stability control strategy on-line simulation calibration method |
| CN104331838A (en) * | 2014-10-11 | 2015-02-04 | 中国南方电网有限责任公司 | Method for realizing maintenance-free stability control information model |
| CN106408438A (en) * | 2015-07-31 | 2017-02-15 | 中国电力科学研究院 | Method for automatically checking safety and stability control strategy based on dynamic simulation of whole process |
| CN106446332A (en) * | 2016-08-18 | 2017-02-22 | 国电南瑞科技股份有限公司 | Method for automatically generating topology of channel between security and stability emergency control devices |
-
2020
- 2020-03-02 CN CN202010133980.8A patent/CN111506544B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103576562A (en) * | 2013-11-07 | 2014-02-12 | 国家电网公司 | Electric power system stability control strategy on-line simulation calibration method |
| CN104331838A (en) * | 2014-10-11 | 2015-02-04 | 中国南方电网有限责任公司 | Method for realizing maintenance-free stability control information model |
| CN106408438A (en) * | 2015-07-31 | 2017-02-15 | 中国电力科学研究院 | Method for automatically checking safety and stability control strategy based on dynamic simulation of whole process |
| CN106446332A (en) * | 2016-08-18 | 2017-02-22 | 国电南瑞科技股份有限公司 | Method for automatically generating topology of channel between security and stability emergency control devices |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111506544A (en) | 2020-08-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106777101B (en) | Data processing engine | |
| US6002869A (en) | System and method for automatically testing software programs | |
| CN102541521B (en) | Automatic operating instruction generating device based on structured query language and method | |
| CN107844424A (en) | Model-based testing system and method | |
| EP1160712A2 (en) | System and method for predicting the timing of future service events of a product | |
| US20120116561A1 (en) | Program testing apparatus, method of testing a program, and program testing program | |
| CN103718119B (en) | Automatically the method and apparatus for executable security function being created to equipment | |
| CN111459698A (en) | Database cluster fault self-healing method and device | |
| Kang et al. | Development of a Bayesian belief network model for software reliability quantification of digital protection systems in nuclear power plants | |
| CN103488460B (en) | The system and method for automatic mark source code | |
| CN111506544B (en) | Power grid safety and stability control device strategy model file verification method and device | |
| CN109753490A (en) | Database optimizing method, system, equipment and medium based on loophole reparation | |
| CN111966587A (en) | Data acquisition method, device and equipment | |
| CN117009243A (en) | Chip performance automatic test method, device, computer equipment and storage medium | |
| CN114091383A (en) | Test sequence generation method, device and system and related equipment | |
| CN103226503B (en) | A kind of module modeling automatic testing method integrated with model inspection | |
| Griesmeyer et al. | A reference manual for the event progression analysis code (EVNTRE) | |
| CN112783916A (en) | SQL statement auditing method and device, storage medium and electronic equipment | |
| CN115248783B (en) | Software testing method, system, readable storage medium and computer equipment | |
| US8051048B2 (en) | System and method for automated transfer and evaluation of the quality of mass data of a technical process or a technical project | |
| CN113360388B (en) | Method for integrally managing test process of unmanned aerial vehicle ground station software | |
| CN101782849A (en) | Control method and device for software annotation | |
| Penttinen et al. | An open modelling approach for availability and reliability of systems-OpenMARS | |
| CN114385649A (en) | Automatic updating system and method for interlocking logic rule configuration file | |
| Schlich et al. | Applying model checking to an automotive microcontroller application |
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 |