A picture attribute data checking method, device and related equipment
By parsing and associating various engineering files in the nuclear power digital instrumentation and control system, generating symbol attribute records and automatically comparing them, the problem of low efficiency in screen attribute data verification is solved, and efficient and accurate verification and error location are achieved.
Patent Information
- Application Number
- CN202611245304.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-17
- Publication Date
- 2026-11-17
AI Technical Summary
In nuclear power digital instrumentation and control systems, the verification efficiency of screen attribute data is low, requiring a lot of manual time and manpower, and it is difficult to uniformly record and locate configuration errors.
By parsing multiple project files and associating attribute data of the same symbol, attribute records are generated, and attribute data is automatically compared according to verification requirements, reducing the workload of manual copying, summarizing, and item-by-item comparison.
It improves the efficiency of verifying screen attribute data, reduces manual operations, improves the accuracy and efficiency of verification, and facilitates the location and modification of configuration errors.
Smart Images

Figure CN123115448A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus and related equipment for verifying image attribute data. Background Technology
[0002] In a nuclear power plant's digital control system (DCS), the screen typically includes various icons such as buttons, indicator lights, digital displays, and dynamic icons. Each icon is configured with multiple attribute data, which determines how the icon is displayed and what operations it performs. Before the system is put into operation, it is necessary to check whether the actual icon attribute data configured in the engineering documents is consistent with the specified icon attribute data.
[0003] Verification of screen attribute data is usually done manually by the user. When verifying screen attribute data, the user needs to open multiple project files and design files, and check the attribute data of each symbol item by item to determine whether the attribute data of the symbols in the screen meets the verification requirements.
[0004] As the number of images and the number of symbols in the images increase, the amount of attribute data that needs to be verified also increases. Manual verification requires a lot of time and manpower, resulting in low verification efficiency for the attribute data of symbols in the images. Summary of the Invention
[0005] This invention provides a method, apparatus, and related equipment for verifying image attribute data, thereby reducing the workload of manual transcription, summarization, and item-by-item comparison during the verification of large amounts of image attribute data and improving the verification efficiency of image attribute data.
[0006] Firstly, embodiments of this application provide a method for verifying screen attribute data. Specifically, when executing this method, multiple project files are DCS project files, and the attribute data in each project file corresponds to icons in the screen. Different project files may include different attribute data for the same icon. For example, one project file may include attribute data such as the icon's name, the screen it belongs to, and its location, while another project file may include attribute data such as the icon's calling device identifier, display parameters, or callback functions. Then, the attribute data belonging to the same icon in the multiple project files are associated to obtain an attribute record for the icon. This attribute record includes multiple attribute data belonging to the icon obtained from different project files. Finally, according to the verification requirements corresponding to the icon, the attribute data in the icon's attribute record is verified to obtain a verification result. The verification requirements indicate the requirements that the icon's attribute data should meet, and the verification result indicates whether the attribute data meets the corresponding verification requirements. For example, the verification requirements may specify preset attribute data, format specifications, or logical constraints between multiple attribute data that the icon's attribute data should meet.
[0007] Because the verification of image attribute data involves parsing multiple DCS project files to obtain symbol attribute data scattered across different files, the workload of manually reviewing each project file and copying attribute data is reduced. Among the attribute data parsed from multiple project files, different attribute data belonging to the same symbol are associated as attribute records for that symbol, further reducing the workload of manually determining attribute data attribution and summarizing. Based on this, the attribute data in the attribute records is verified according to the verification requirements corresponding to the symbol, enabling automatic comparison of symbol attribute data, thus reducing the workload of manual comparison. Therefore, when verifying the symbol attribute data of a large number of images, the workload of manual copying, summarizing, and comparison can be reduced, improving the efficiency of image attribute data verification.
[0008] In one possible implementation, the various project files include at least two of the following: screen files, binary files, and Hypertext Markup Language (HTML) reports. The screen file stores the attribute data of the icons in the screen in a custom format; the binary file stores the attribute data of the icons in the screen in binary encoded form; and the HTML report stores the attribute data of the icons in the screen in HTML format. By employing a parsing method that matches the storage format of each project file, the icon attribute data in each project file is extracted. This allows for the acquisition of icon attribute data scattered across project files of different formats, reducing the workload of manually examining and transcribing attribute data from different formats, and improving the efficiency of acquiring screen attribute data.
[0009] In one possible implementation, multiple project files, including screen files, can also be obtained, along with widget palette files (PAL) files. When parsing the multiple project files corresponding to the screen to obtain the attribute data for each project file, specifically, the PAL file can be parsed to obtain symbol attribute definition information. This symbol attribute definition information describes the attribute names of different symbol types, or the content represented by different attribute values of different symbol types. The screen files are then parsed using this symbol attribute definition information to obtain the attribute data included in the screen files. In this way, based on the meaning expressed by the attribute names or attribute values of different symbol types defined in the PAL file, the symbol attribute data stored in a custom format in the screen file can be identified. This reduces the workload of manually searching for symbol attribute definitions and interpreting the meaning of attribute values, improving the parsing efficiency and accuracy of attribute data in the screen files.
[0010] In one possible implementation, multiple project files include binary files. When parsing the multiple project files corresponding to the screen to obtain the attribute data included in each project file, specifically, the binary file can be converted into characters to obtain data to be parsed; the starting position of the icon identifier of the target icon is determined in the data to be parsed, and this icon identifier is used to distinguish different icons in the screen; based on this starting position and a preset offset rule, the data to be parsed is parsed to obtain the attribute data of the target icon, where the preset offset rule specifies the offset of the location of different attribute data relative to the starting position. In this way, the starting position of the icon identifier of the target icon can be used as a reference to locate and extract the different attribute data of the target icon according to the preset offset rule, reducing the workload of manually searching for icons one by one in the binary file and determining the data storage location of attribute data, thus improving the parsing efficiency and accuracy of attribute data in the binary file.
[0011] In one possible implementation, multiple project files include HTML reports. When parsing the various project files corresponding to the screen to obtain the attribute data included in each project file, specifically, this can involve identifying HTML tags in the HTML report and the relationships between these HTML tags. These HTML tags are used to organize the attribute data of the icons in the screen. Based on the relationships between the HTML tags, attribute data is extracted from the content corresponding to the HTML tags. In this way, the organization of the icon attribute data in the HTML report can be determined based on the HTML tags and their relationships, and attribute data can be extracted from the content corresponding to the corresponding tags. This reduces the workload of manually reviewing each item in the HTML report and searching for and copying attribute data, improving the parsing efficiency and accuracy of attribute data in the HTML report.
[0012] In one possible implementation, the attribute record includes a screen identifier, which indicates the screen in which the icon is located. Specifically, an attribute data page can be generated based on the screen identifier. This attribute data page stores the attribute records of at least one icon located within the screen indicated by the screen identifier. In this way, the attribute records of icons belonging to the same screen can be stored in the corresponding attribute data page based on the screen identifier. This allows the attribute records of icons to be grouped according to the screen, reducing the workload of manually distinguishing the screen to which an icon belongs and organizing the attribute records. It also facilitates viewing and verifying the attribute records of icons at the screen-by-screen granularity, improving the management and verification efficiency of screen attribute data.
[0013] In one possible implementation, the verification requirement includes a first verification requirement, which verifies whether at least one attribute data in the attribute record of the icon is consistent with the preset attribute data corresponding to the icon. Specifically, when verifying the attribute data in the attribute record of the icon according to the verification requirement corresponding to the icon, the verification result can be obtained by verifying at least one attribute data in the attribute record of the icon based on the first verification requirement, thus obtaining a first verification result. This first verification result indicates whether at least one attribute data is consistent with the corresponding preset attribute data. In this way, the attribute data of the icon can be automatically compared with the corresponding preset attribute data, reducing the workload of manually searching for and performing consistency comparisons of preset attribute data item by item, and improving the efficiency and accuracy of the consistency verification of the icon's attribute data.
[0014] In one possible implementation, the verification requirement can be a second verification requirement. This second verification requirement is used to verify whether at least one attribute data in the attribute record of the icon meets the data specification, which stipulates the requirements that the attribute data should meet in terms of naming, format, etc. Specifically, when verifying the attribute data in the attribute record of the icon according to the verification requirement corresponding to the icon, the verification result can be obtained by verifying at least one attribute data in the attribute record of the icon based on the second verification requirement, and obtaining a second verification result. This second verification result is used to indicate whether at least one attribute data meets the corresponding data specification. In this way, the attribute data of the icon can be automatically verified according to a unified data specification, reducing the workload of manually checking each attribute data item and judging its compliance, and improving the efficiency of standardization verification of icon attribute data.
[0015] In one possible implementation, the verification requirement can be a third verification requirement. This third verification requirement is used to verify whether the attribute data in the attribute records of the icon satisfies a logical relationship, which represents the constraints that the attribute data should satisfy. Specifically, when verifying the attribute data in the attribute records of the icon according to the verification requirement corresponding to the icon, the verification result can be obtained by verifying at least one attribute data in the attribute records of the icon based on the third verification requirement, thus obtaining a third verification result. This third verification result indicates whether the corresponding logical relationship is satisfied between or within the attribute data. In this way, the configuration logic between multiple attribute data of the icon can be automatically verified, reducing the workload of manually judging the logical correctness of each attribute data item by item, and improving the efficiency of logical verification of icon attribute data.
[0016] Secondly, embodiments of this application provide a screen attribute data verification device, which includes a parsing module, an association module, and a verification module. The parsing module is used to parse multiple project files corresponding to a screen, obtaining attribute data included in each project file. The attribute data in the multiple project files respectively correspond to icons in the screen, and different project files include different attribute data of the same icon. The project files are DCS project files. The association module is used to associate attribute data belonging to the same icon in the multiple project files to obtain attribute records of the icon. The verification module is used to verify the attribute data in the attribute records of the icon according to the verification requirements corresponding to the icon, obtaining a verification result. The verification result is used to indicate whether the attribute data meets the verification requirements.
[0017] In one possible implementation, the various project files can be at least two of the following: screen files, binary files, and HTML reports. The screen file is a file that stores the attribute data of the icons in the screen in a custom format, the binary file is a file that stores the attribute data of the icons in the screen in binary encoding, and the HTML report is a report that stores the attribute data of the icons in the screen in HTML format.
[0018] In one possible implementation, the project file can be a screen file, and the screen attribute data verification device further includes an acquisition module for acquiring the widget palette PAL file; a parsing module for parsing the PAL file to obtain symbol attribute definition information, which describes the attribute names of different symbol types, or the symbol attribute definition information describes the content represented by different attribute values of different symbol types; and the screen file is parsed using the symbol attribute definition information to obtain the attribute data included in the screen file.
[0019] In one possible implementation, the project file can be a binary file. The parsing module is used to convert characters in the binary file to obtain the data to be parsed. The starting position of the target icon's icon identifier in the parsed data is determined in the parsed data. The icon identifier is used to distinguish different icons in the screen. According to the starting position and the preset offset rule, the parsed data is extracted to obtain the attribute data of the target icon. The preset offset rule is used to specify the offset of the position of different attribute data relative to the starting position.
[0020] In one possible implementation, the project file may be an HTML report, and a parsing module is used to identify HTML tags in the HTML report and the relationships between the HTML tags, wherein the HTML tags are used to organize the attribute data of the icons in the image; and to extract attribute data from the content corresponding to the HTML tags according to the relationships between the HTML tags.
[0021] In one possible implementation, the attribute record can be a screen identifier, which is used to indicate the screen where the icon is located. The screen attribute data verification device also includes a generation module, which is used to generate an attribute data page based on the screen identifier. The attribute data page is used to store the attribute record of at least one icon located in the screen.
[0022] In one possible implementation, the verification requirement can be a first verification requirement, which is used to verify whether at least one attribute data in the attribute record of the symbol is consistent with the preset attribute data corresponding to the symbol; the verification module is used to verify at least one attribute data in the attribute record of the symbol based on the first verification requirement, and obtain the first verification result.
[0023] In one possible implementation, the verification requirement can be a second verification requirement, which is used to verify whether at least one attribute data in the attribute record of the symbol meets the data specification. The data specification is used to ensure the standardization of the attribute data. The verification module is used to verify at least one attribute data in the attribute record of the symbol based on the second verification requirement to obtain the second verification result.
[0024] In one possible implementation, the verification requirement can be a third verification requirement, which is used to verify whether different attribute data in the attribute record of the symbol satisfy a logical relationship. The logical relationship is used to characterize the constraints that the attribute data in the attribute record of the symbol should satisfy. The verification module is used to verify at least one attribute data in the attribute record of the symbol based on the third verification requirement to obtain the third verification result.
[0025] Thirdly, this application provides a computing device, which includes a processor and a memory. The processor and the memory communicate with each other. The processor executes instructions stored in the memory to cause the computing device to perform a screen attribute data verification method as described in the first aspect or any implementation thereof. It should be noted that the memory can be integrated into the processor or can be independent of the processor. The computing device may also include a bus. The processor is connected to the memory via the bus. The memory may include readable storage and random access memory.
[0026] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on a computing device, cause the computing device to perform the operation steps of the screen attribute data verification method described in the first aspect or any implementation thereof.
[0027] Fifthly, this application provides a computer program product containing instructions that, when run on a computing device, causes the computing device to perform the operation steps of the screen attribute data verification method described in the first aspect or any implementation thereof.
[0028] Furthermore, the technical effects of any of the implementation methods in the second to fifth aspects can be found in the technical effects of different implementation methods in the first aspect, and will not be repeated here.
[0029] Based on the implementation methods provided in the above aspects, this application can be further combined to provide more implementation methods. Attached Figure Description
[0030] Figure 1 This is a schematic diagram of the structure of a screen attribute data verification system provided in an embodiment of this application; Figure 2 A flowchart illustrating a screen attribute data verification method provided in an embodiment of this application; Figure 3 A schematic diagram illustrating an engineering file parsing process provided in an embodiment of this application; Figure 4 A schematic diagram illustrating an attribute data verification process provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a screen attribute data verification device provided in an embodiment of this application; Figure 6 This is a schematic diagram of the hardware structure of a computing device provided in an embodiment of this application. Detailed Implementation
[0031] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate; this is merely a method of distinction used in describing objects with the same attributes in the embodiments of this application.
[0032] In this application's embodiments, "at least one" includes one or more, and "more than one" includes two or more. Unless the context clearly indicates otherwise, the terms "comprising" and "having" in this application's embodiments indicate an open-ended inclusion relationship. The technical features described in different embodiments can be combined with each other without conflict.
[0033] For ease of understanding and explanation, some of the technical terms mentioned in this application will be explained by example below.
[0034] A screen, in a DCS (Distributed Control System), refers to the human-machine interface used to present system operating information to users and allow them to input operating commands. System operating information may include, for example, process parameters, equipment operating status, and alarm information. Typically, a screen may include one or more icons.
[0035] A symbol is a visual object placed on a screen to display information or receive operations. Examples include buttons, indicator lights, digital displays, or dynamic symbols. Different symbols can have different functions and attribute data. For example, display symbols can be used to display equipment status or process parameters, while operation symbols can be used to receive user input commands. Symbol types indicate the functional category to which the symbol belongs; different symbol types can correspond to different attribute names, attribute values, or validation requirements.
[0036] Attribute data refers to information used to describe the characteristics and configuration of a graphic symbol. In the embodiments of this application, attribute data can be used to describe the symbol's identity, screen it belongs to, location, size, display method, associated objects, or interactive functions. For example, attribute data may include the symbol name, screen identifier, horizontal axis, vertical axis, width, height, device identifier, display parameters, data type, value range, callback function, or option content, etc.
[0037] Project files refer to files generated, exported, or saved within the DCS (Distributed Control System) engineering environment. In this application's embodiments, project files can be screen files, binary files, or HTML reports. Different project files may include different attribute data for the same symbol.
[0038] Screen files refer to files that store the attribute data of icons in a screen using a custom format of the DCS platform.
[0039] A binary file is a file that uses binary encoding to store the attribute data of icons in a screen.
[0040] An HTML report is a report that uses HTML format to record the attribute data of icons in a screen.
[0041] PAL files can be configuration files used to assist in parsing screen files. PAL files can be in plain text format and are used to store attribute names corresponding to different icon types, as well as the mapping relationship between Choice codes and option content.
[0042] An attribute record is a structured record formed by a computing device by associating attribute data belonging to the same symbol across multiple engineering files according to symbol affiliation. One attribute record can correspond to one symbol and can store the symbol's attribute fields, attribute values, the engineering file where the attribute data is located, and the position of the attribute data within the corresponding engineering file.
[0043] An attribute data page is a data page that organizes attribute records of at least one icon according to the screen layout. One attribute data page can correspond to one screen and store the attribute records of at least one icon located in that screen. Attribute data pages can take the form of a worksheet in a spreadsheet, an HTML page, or other data formats that can organize attribute records, and are not limited to a specific display interface for users to view.
[0044] Verification requirements refer to the requirements used to verify the attribute data of a symbol. Verification requirements may include a first verification requirement to verify whether the attribute data is consistent with preset attribute data, a second verification requirement to verify whether the attribute data meets data specifications, and a third verification requirement to verify whether the attribute data satisfies logical relationships.
[0045] The validation result refers to the result obtained after validating the attribute data of a symbol. The validation result may include indication information indicating whether the attribute data has passed the validation. For attribute data that fails the validation, the validation result may also include at least one of the following: symbol type, symbol name, device identifier, attribute name, actual value, expected value, error category, error description, source file path where the attribute data is located, or the line number, page name, symbol identifier, or attribute field location corresponding to the attribute data.
[0046] See Figure 1 , Figure 1 This diagram illustrates the structure of a screen attribute data verification system according to an embodiment of this application. The screen attribute data verification system 10 may include a computing device 100 and a client 200. The computing device 100 and the client 200 can communicate with each other.
[0047] The computing device 100 is used to implement the corresponding functions or services. For example, the computing device 100 can provide data source file loading services, project file parsing services, symbol attribute data association services, or symbol attribute data validation services, etc., without limitation.
[0048] Client 200 is used for data interaction with the user. For example, client 200 can obtain configuration information input by the user. This configuration information may include a list of icon types to be exported, as well as data source file paths such as the station file directory, database file directory, and PAL file directory. The station file directory can be used to store the project files corresponding to the target station. Client 200 can also present the user with icon attribute records, verification results, or check logs generated by computing device 100. Exemplarily, client 200 can be an application running on the user's terminal device or a web client accessed through a browser; there is no limitation on this.
[0049] The computing device 100 can also send the attribute records and / or verification results of the symbols to the client 200. The client 200 can display the attribute records and / or verification results of the symbols for the user to view. For example, the client 200 can display attribute data pages organized by screen, mark attribute data that failed verification in the attribute data pages, and display the corresponding error descriptions. The client 200 can also display or provide the inspection log generated by the computing device 100.
[0050] It should be noted that, Figure 1 The computing device 100 and client 200 shown are primarily for illustrating their functional relationship and do not constitute a limitation on the number of devices or deployment method of the screen attribute data verification system 10. The computing device 100 and client 200 can be located in different devices or integrated into the same device. Furthermore, Figure 1 The PAL file and the project file are shown separately to distinguish their roles in the verification process of the attribute data of the symbols in the screen: the project file is used to provide the computing device 100 with the attribute data of the symbols to be verified, while the PAL file is used to assist the computing device 100 in recognizing and parsing the attribute data of the symbols in the screen file.
[0051] In practical applications, icons on the screen are used to display process parameters, equipment operating status, or receive operation commands. Whether an icon can perform its function as designed depends on whether its attribute data is configured correctly. For example, incorrect equipment identification configuration may cause the icon to be associated with the wrong equipment; incorrect display parameters or value range configuration may cause the displayed content to be inconsistent with the actual operating status; and incorrect callback function configuration may affect the icon's response to operation commands. Therefore, the attribute data of the icons needs to be validated before the screen is put into use.
[0052] Typically, different attribute data for the same symbol are scattered across different files, and these files differ in format and data organization. When validating symbol attribute data, users need to open each file separately, search for attribute data belonging to the same symbol, and then determine whether each item meets design requirements based on the symbol type and specific attributes. When the number of screens and symbols is large, users need to repeatedly view files, search for data, match symbols, and manually compare, resulting in a lengthy verification process. Furthermore, manual verification makes it difficult to uniformly record all discrepancies and their locations, increasing the difficulty of subsequently locating and correcting erroneous attribute data.
[0053] Based on this, the image attribute data verification system 10 provided in this application uses a computing device 100 to process and verify the icon attribute data, and provides the processing results to the user through a client 200. The computing device 100 converts attribute data from different files into attribute records in units of icons, enabling the originally scattered attribute data to be processed uniformly at the icon level. On this basis, the computing device 100 identifies attribute data that does not meet the requirements according to the corresponding verification requirements, and provides the identified difference information to the client 200.
[0054] In this way, the screen attribute data verification system 10 can reduce the user's operations of searching, matching, and comparing attribute data across files, thereby improving the verification efficiency of screen attribute data. At the same time, by marking the attribute data that fails verification and outputting the inspection log, users can locate the corresponding symbols and attribute data based on the error description and log information, which facilitates the modification and review of configuration errors.
[0055] To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, various non-limiting embodiments of the present application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.
[0056] See Figure 2 , Figure 2 This is a flowchart illustrating a screen attribute data verification method provided in an embodiment of this application. This method can be applied to... Figure 1 The image attribute data verification system 10 shown can be applied to other applicable image attribute data verification systems. For ease of explanation, this embodiment uses an application... Figure 1 The screen attribute data verification system 10 shown is used as an example for illustration. For ease of explanation, the computing device 100 will be used as the execution subject in the following description.
[0057] Figure 2 The screen attribute data verification method shown may include steps S201 to S203.
[0058] S201: The computing device 100 analyzes the various project files corresponding to the screen and obtains the attribute data included in each project file.
[0059] The project file corresponding to a screen refers to the file generated, exported, or saved during the screen configuration process, including the attribute data of the symbols in the screen. A screen can include at least one symbol, and the attribute data of the same symbol can be stored in different project files. For example, the basic attribute data, specific attribute data, and supplementary attribute data of a symbol can be stored in different project files. Among them, the basic attribute data can be general attribute data used to identify or describe the symbol; the specific attribute data can be attribute data corresponding to a specific symbol type or symbol function; and the supplementary attribute data can be further extracted from other project files to supplement the missing attribute data of the symbol.
[0060] Because different project files have different file formats and attribute data organization methods, the computing device 100 cannot directly read the attribute data in each project file using the same method. Therefore, the computing device 100 can parse the corresponding project file according to its file type, using a parsing method corresponding to that file type.
[0061] In this embodiment, the following non-limiting implementation methods for parsing project files are provided.
[0062] See Figure 3, Figure 3 This diagram illustrates a project file parsing process according to an embodiment of this application. The screen file parsing branch, the binary file parsing branch, and the HTML report parsing branch are all specific implementations of parsing the project file in step S201. The computing device 100 can execute at least two of these parsing branches, or it can execute all of them. The parsing branches can be executed in parallel or in any order.
[0063] In the first implementation, the project file may include a screen file. For example... Figure 3 As shown, the computing device 100 can execute steps S301 to S303.
[0064] S301: Computing device 100 obtains PAL file.
[0065] The PAL file can be a configuration file used to assist in parsing the screen file. For example, the screen file can be a file with the .wgtw extension, used to record specific attribute values for each symbol in the screen. Since some attribute values in the screen file are organized according to the attribute structure specified in the PAL file, and the attribute values of the Choice type can be represented using numerical encoding, the computing device 100 can obtain the PAL file used to parse the screen file, determine the attribute names corresponding to the attribute values in the screen file based on the PAL file, and determine the option content corresponding to the Choice encoding.
[0066] S302: Computing device 100 parses the PAL file and obtains the symbol attribute definition information.
[0067] Symbol attribute definition information describes the attribute data of different symbol types and the meaning of the attribute values. Symbol attribute definition information can include the correspondence between symbol types and attribute names, as well as the mapping between Choice codes and option content.
[0068] It should be noted that the icon attribute definition information is not the actual attribute data of a specific icon, but rather the definition information used to interpret the attribute data in the screen file. For example, icon attribute definition information can indicate which attributes a certain type of icon includes, and which option content a certain Choice code represents.
[0069] For example, computing device 100 can read the text content of a PAL file line by line and identify the corresponding attribute definitions according to the format of each line of text. For instance, computing device 100 can identify text lines that begin with "r=" or "i=", extract attribute names from the corresponding text lines, and add the extracted attribute names to the attribute name set of the corresponding symbol type. For text lines that include a single comma but do not include an equals sign, computing device 100 can split the text line according to the comma to obtain the Choice code and the option content corresponding to the Choice code, and establish a mapping relationship between the two.
[0070] After the computing device 100 completes the parsing of the PAL file, it can obtain the set of attribute names corresponding to each symbol type and the corresponding Choice encoding mapping relationship, and use them as symbol attribute definition information.
[0071] S303: The computing device 100 parses the screen file according to the symbol attribute definition information and obtains the attribute data corresponding to the screen file.
[0072] The computing device 100 can determine the type of symbol to be identified based on the symbol attribute definition information, and generate a predetermined list of symbol types based on the determined symbol types. The list of symbol types may include the type name of at least one symbol type.
[0073] The computing device 100 can read the screen file line by line and check whether the currently read text line matches any type name in the symbol type list. When the current text line matches a type name in the symbol type list, the computing device 100 can determine that type name as the symbol type of the current symbol and create a new empty data record for the current symbol so that the empty data record can be used later to store the attribute name and attribute value corresponding to the current symbol.
[0074] After identifying the symbol type of the current symbol, the computing device 100 can continue reading the text lines following the current text line and detect whether the read text lines include field identifiers that begin with "r=" or "i=". When the text line includes such field identifiers, the computing device 100 can recognize the string following the field identifier as an attribute name and extract the attribute value corresponding to that attribute name.
[0075] Attribute values can be recorded in the text line containing the field identifier, or they can be recorded consecutively in multiple text lines following the field identifier. When attribute values are recorded consecutively in multiple text lines, the computing device 100 can read and merge the values in the corresponding text lines sequentially until it reads the field identifier of the next attribute, the name of the next icon type, or the end of the screen file, thereby obtaining the complete attribute value corresponding to that attribute name.
[0076] The attribute values in the image file can be represented using numeric encoding or decimal integers. In order to convert the above attribute values into content that is easy to identify and verify, the computing device 100 can further determine the data type of the extracted attribute values and process the attribute values accordingly based on the determination result.
[0077] The computing device 100 can query the icon attribute definition information based on the icon type, attribute name, and attribute value. In one example, when a mapping relationship corresponding to the icon type, attribute name, and attribute value is found in the icon attribute definition information, the computing device 100 can determine that the attribute value is a Choice code. Based on this mapping relationship, it replaces the numeric code with the option content corresponding to that numeric code, thereby converting the Choice code into readable text. For example, the icon type is a button icon "PtButton", the attribute name is "HandAutoState", and the attribute value is the numeric code "1". The computing device 100 queries the icon attribute definition information based on "PtButton", "HandAutoState", and "1", and finds that the option content corresponding to the numeric code "1" is "Auto". Therefore, the computing device 100 can replace the attribute value "1" with "Auto" to indicate that the button icon is in an automatic state.
[0078] In another example, when the attribute value does not belong to the Choice code and the attribute name includes "Color", the computing device 100 can determine that the attribute value is a color value and call the red-green-blue (RGB) conversion algorithm to convert the color value, represented as a decimal integer, into a readable string in the format "[R:xx, G:yy, B:zz]". Here, R represents the red component, G represents the green component, B represents the blue component, and xx, yy, and zz represent the numerical values of the corresponding color components. For example, if the icon's attribute name is "BackgroundColor" and the attribute value is the decimal integer "65280", and the computing device 100 cannot find a Choice code mapping for this attribute value, the computing device 100 can determine that the attribute value is a color value because "BackgroundColor" includes "Color". It can then call the RGB conversion algorithm to convert the decimal integer "65280" into "[R:0, G:255, B:0]", indicating that the color corresponding to this attribute is green.
[0079] In another example, for attribute values that are not part of the Choice code and whose attribute names do not include "Color", the computing device 100 can retain the original form of the attribute value. For example, the icon's attribute name is "Width" and its attribute value is "120". The computing device 100 does not find a Choice code mapping for this attribute value, and the attribute name "Width" does not include "Color". Therefore, the computing device 100 can retain the original form of the attribute value "120" to indicate that the icon's width is 120.
[0080] Therefore, the computing device 100 can write the extracted attribute names and the attribute values that have been converted or retained in their original form into the data record of the current symbol.
[0081] When the computing device 100 reads the name of the next symbol type, it can determine that the attribute data of the current symbol has been read completely. The computing device 100 then stores the data record of the current symbol in the symbol set corresponding to that symbol type. Subsequently, the computing device 100 can determine the read name of the next symbol type as the symbol type of the next symbol, and create a new empty data record for the next symbol to continue extracting the attribute data of the next symbol.
[0082] When the computing device 100 reads to the end of the screen file, the computing device 100 can determine that the attribute data of the currently processed icon has been read and store the data record of the icon in the icon set of the corresponding icon type.
[0083] Therefore, the computing device 100 can obtain the attribute data corresponding to the screen file. The attribute data can be stored in the form of "attribute name=attribute value" or "attribute name=code", with different fields separated by commas. The attribute data corresponding to the screen file may include a symbol identifier, symbol type, attribute name, and attribute value. The symbol identifier is used to determine the symbol to which the attribute data belongs, so that the attribute data can be subsequently associated with attribute data belonging to the same symbol parsed from other project files such as HTML reports and binary files.
[0084] Thus, the computing device 100 can parse the PAL file to obtain the mapping relationship between the attribute names and attribute values corresponding to different symbol types, and identify and extract attribute values from the screen file based on the aforementioned symbol attribute definition information. The computing device 100 can also convert or retain Choice codes, color values, and other attribute values according to the data type of the attribute values, thereby converting data organized according to a specific structure or represented in an encoded form in the screen file into attribute data with clear attribute names and meanings. This provides a data foundation for subsequently associating attribute data belonging to the same symbol and verifying the attribute data.
[0085] It should be noted that the above-described method of parsing the screen file by reading line by line and matching feature strings is merely an exemplary implementation for extracting specific attribute data from the screen file and does not constitute a limitation on the method of parsing the screen file. In other embodiments, when the screen file provides a standard parsing interface, the computing device 100 can call the standard parsing interface to extract specific attribute data of the icons from the screen file; when the screen file uses Extensible Markup Language (XML), JavaScript Object Notation (JSON), or other standard structured formats to store the specific attribute data of the icons, the computing device 100 can also use a standard parser matching the corresponding file format to extract the specific attribute data. The above methods change the specific means of reading and parsing the screen file, but do not change the processing purpose of obtaining specific attribute data of the icons from the screen file.
[0086] In the second implementation, the project files may include binary files. For example... Figure 3 As shown, the computing device 100 can execute steps S311 to S313.
[0087] S311: The computing device 100 performs character conversion on the binary file to obtain the data to be parsed.
[0088] A binary file can be a file that stores icon attribute data in binary format. For example, a binary file can be a file with the .dfn extension; such as abapp.dfn. The abapp.dfn file can store supplementary attribute data for special icons such as JumpOne and PtButton.
[0089] Since the attribute data in a binary file cannot be read directly in the same way as a regular text file, the computing device 100 can read the entire binary file in binary mode to obtain a byte array composed of the bytes in the binary file.
[0090] For example, computing device 100 can convert the byte array into an ASCII string according to the American Standard Code for Information Interchange (ASCII) encoding method, and replace the null characters in the ASCII string with spaces to obtain the data to be parsed. By replacing null characters with spaces, spaces can be used to determine the boundaries between different strings, so that the corresponding attribute values can be extracted from the data to be parsed later.
[0091] During the conversion process, the byte positions in the byte array correspond to the character positions in the ASCII string, so that the computing device 100 can determine the corresponding character positions in the converted ASCII string based on the byte offsets in the binary file.
[0092] S312: The computing device 100 determines the starting position in the data to be parsed based on the symbol name of the target symbol.
[0093] The target icon can be an icon from which attribute data needs to be extracted from a binary file. The icon name of the target icon can be used to locate the data area corresponding to that icon in the data to be parsed.
[0094] The computing device 100 can obtain the name of the target icon and search for a string with the same name in the data to be parsed. When the name of the target icon is found in the data to be parsed, the computing device 100 can determine the index position of the icon name in the data to be parsed and use this index position as the starting position for extracting the attribute data of the target icon. For example, the name of the target icon is "JumpOne_001". The computing device 100 can search for "JumpOne_001" in the converted ASCII string. When "JumpOne_001" is found, the computing device 100 can determine the index position of the first character of this string in the ASCII string and use this index position as the starting position corresponding to the target icon.
[0095] S313: The computing device 100 extracts the attribute data corresponding to the binary file from the data to be parsed according to the starting position and offset rules.
[0096] Offset rules describe the byte offsets of different attribute fields of a target icon relative to the starting position of the icon name. Offset rules can be predetermined by analyzing the data structure of a binary file and its data storage patterns. Different attribute fields can correspond to different byte offsets and truncation lengths.
[0097] For example, the abapp.dfn file can be opened using a text editor to observe the recognizable symbol names and attribute values. It should be noted that opening the abapp.dfn file with a text editor is for observing and analyzing the data storage patterns within the file; it does not imply that the abapp.dfn file is a plain text file, nor does it imply that the computing device 100 reads the file in the manner of a plain text file, nor does it imply that the computing device 100 can only implement this process using a text editor.
[0098] The offset of different attribute values relative to the starting position of the icon name can be preset. The computing device 100 locates the starting position of the icon name in the abapp.dfn file, and according to the preset offset of the corresponding attribute field, offsets from that starting position to the corresponding storage location, and reads the attribute value of that attribute field. For example, the preset offset for the Window field can be 64 bytes, and the preset offset for the CallbacksFunction field can be 128 bytes. These preset offsets constitute the offset rules.
[0099] The computing device 100 can determine the byte offset corresponding to the target attribute from the offset rules based on the target attribute to be extracted, and add the starting position of the target icon to the byte offset to obtain the starting position of the target attribute in the data to be parsed. The computing device 100 can then extract the string from this starting position according to a predetermined truncation length corresponding to the target attribute. For example, when it is necessary to extract the Window attribute value of the target icon named “JumpOneAPG2201001”, the target icon name is searched in the data to be parsed to obtain the position of the “JumpOneAPG2201001” target icon in the data to be parsed. The following is a partial example of the data to be parsed: “JumpOneAPG2201001………………………………………..REN2202………”. For illustrative purposes, each “.” represents a space, each space represents a byte, and each space is obtained by replacing the corresponding null character. Thus, computing device 100 can use the starting position "J" of "JumpOneAPG2201001" as the first byte of the starting position, and offset 64 bytes from the first byte "J" to determine the starting position of the attribute value of the Window field. Computing device 100 then extracts a string of a predetermined length from this starting position of the attribute value. For example, computing device 100 extracts 16 bytes, thus obtaining a string containing the Window attribute value and spaces: "REN2202…", where "REN2202" is the Window attribute value. When computing device 100 needs to extract the CallbacksFunction attribute value of the target icon, similar to the method described above for obtaining the Window attribute value, computing device 100 can offset 128 bytes from the starting position of "JumpOne APG2201001" to determine the starting position of the CallbacksFunction field attribute, and extract a string of a predetermined length from this starting position, thus obtaining a string containing the CallbacksFunction attribute value and spaces.
[0100] Since the extracted string may include attribute values and spaces before or after the attribute values, the computing device 100 can further perform space cleanup and boundary processing on the extracted string. Specifically, the computing device 100 can first remove spaces at the beginning of the extracted string, then determine the first space in the remaining string as the end position of the attribute value, and retain the content from the beginning position of the remaining string to the first space, thereby obtaining the target attribute value. For example, if the computing device 100 offsets the starting position of "JumpOneAPG2201001" by 64 bytes and extracts the string according to a predetermined length, the resulting string may include the Window attribute value and spaces after the attribute value. The computing device 100 can determine the first space in this string as the end position of the Window attribute value, and retain the content before the space, thereby obtaining the Window attribute value corresponding to "JumpOneAPG2201001".
[0101] The computing device 100 can store the icon identifier, attribute name, and corresponding target attribute value of the target icon to obtain the attribute data corresponding to the binary file. The icon identifier can include the icon name and screen identifier, used to determine the icon to which the attribute data belongs, so that the attribute data can be subsequently associated with attribute data belonging to the same icon parsed from other project files such as screen files and HTML reports.
[0102] Thus, even without access to the binary file format specification, the fixed offsets of different attribute fields relative to the starting positions of the symbol names can be pre-determined by analyzing the data structure and data storage patterns of the binary file. The computing device 100 can convert the binary file into data to be parsed, locate the corresponding symbols based on the symbol names, and extract key attributes according to the offset rules, thereby obtaining the attribute data corresponding to the binary file.
[0103] It should be noted that the method described above, which determines the starting position based on the symbol name and extracts attribute data according to a fixed offset, is applicable to situations where a binary file format specification is not available or the binary file does not provide a standard access interface. This method is merely an exemplary implementation for parsing binary files. In other embodiments, when the binary file format specification is available, the computing device 100 can determine the storage location and data structure of different attribute data in the binary file according to the format specification, and read the supplementary attribute data of special symbols from the corresponding positions. When the screen design platform or the binary file provides a standard access interface, the computing device 100 can also call the standard access interface to read the supplementary attribute data of special symbols without having to truncate the string according to a fixed offset. The above method changes the specific means of reading and parsing the binary file, but does not change the processing purpose of obtaining the supplementary attribute data of special symbols from the binary file.
[0104] In the third implementation, the project file may include an HTML report, which can be a report exported by the screen design platform using the report generation function, used to record the attribute data of symbols in the screen. The HTML report may include one or more HTML files.
[0105] For example, an HTML report can be stored as a file package. This file package may include a general.html file, widgets / .html files and callbacks / .html files. The general.html file can be used to record an overall view of the screen and overview information for different icon types, and can also serve as an index for the HTML report; widgets / .html files can be used to record the basic attributes of different symbols; callbacks / The .html file can be used to record callback function information for different icons. Computing device 100 can load widgets / .html files and callbacks / The .html file is loaded, and steps S321 and S322 are performed on the loaded HTML file to obtain the attribute data corresponding to the HTML report.
[0106] S321: Computing device 100 identifies HTML tags in an HTML report and the relationships between HTML tags.
[0107] HTML reports can organize the attribute data of icons in the screen using HTML tags. Different HTML tags can be used to represent different data organization structures and can have containment relationships, hierarchical relationships, and arrangement order relationships. For example, an HTML report may include table tags, tr tags, th tags, and td tags. A table tag may include one or more tr tags, and a tr tag may include one or more th tags or td tags.
[0108] The computing device 100 can read HTML reports, identify the tag type, start position, and end position of each HTML tag, and determine the inclusion and hierarchical relationships between different HTML tags based on their nesting. It can also determine the order of multiple HTML tags based on their appearance in the HTML report. For example, when the first and second `tr` tags are both within a `table` tag, and multiple `th` tags are within the first `tr` tag, the computing device 100 can determine the inclusion and hierarchical relationships between these tags and determine their order based on the appearance order of sibling tags.
[0109] In one example, computing device 100 can invoke an HTML parser to parse an HTML report. The HTML parser can identify start and end tags in the HTML report and build a document object model (DOM) based on the correspondence between start and end tags and the nesting of different HTML tags.
[0110] The DOM can use a tree structure to represent the tag nodes corresponding to different HTML tags and the relationships between these tag nodes. An HTML tag containing other tags can correspond to a parent node, and the contained HTML tag can correspond to a child node; multiple tag nodes with the same parent node can be arranged according to the order in which the corresponding HTML tags appear in the HTML report. Therefore, the computing device 100 can obtain the HTML tags in the HTML report, as well as the inclusion relationships, hierarchical relationships, and arrangement order relationships between different HTML tags.
[0111] It should be noted that the above-described invocation of the HTML parser is merely an exemplary implementation for identifying HTML tags and the relationships between them, and does not constitute a limitation on the HTML report parsing method. The computing device 100 may execute step S321 using any program, module, or processing method capable of identifying HTML tags and the relationships between them.
[0112] S322: The computing device 100 extracts attribute data from the content corresponding to the HTML tags based on the relationships between the HTML tags.
[0113] The computing device 100 can determine the target tag for organizing the icon attribute data based on the HTML tags identified in step S321 and the relationship between the HTML tags, and extract the attribute data from the content corresponding to the target tag.
[0114] In one example, computing device 100 can determine the data rows in a table based on the inclusion relationship between the table tag and the tr tag; determine the cells in each data row based on the inclusion relationship between the tr tag and the th tag or the td tag; and determine the arrangement position of each cell in the corresponding data row based on the arrangement order of multiple cell tags in the same data row.
[0115] The computing device 100 can extract attribute names from the content corresponding to the th tag, extract attribute values from the content corresponding to the td tag, and match the attribute values with the corresponding attribute names according to the arrangement of the th and td tags in the corresponding data rows.
[0116] For widgets / The computing device 100 can extract the basic attribute data of the icon using the .html file as described above. The basic attribute data may include at least one of the following: icon name, screen name, horizontal coordinate, vertical coordinate, width, height, and callback quantity. For example, when the table header records the icon name, screen name, horizontal coordinate, vertical coordinate, width, height, and callback quantity in an ordered manner, the computing device 100 can determine the attribute values of the extracted content from each data cell according to their respective positions. The computing device 100 can then store the attribute values in the same data row along with their corresponding attribute names to obtain the basic attribute data of the corresponding icon.
[0117] For callbacks / The computing device 100 can extract callback attribute data from icons in the manner described above, using an .html file. Callback attribute data may include at least one of the following: function name, callback type, and file name. The computing device 100 can also determine the icon corresponding to a callback function based on the correspondence between callback functions and icons recorded in the HTML report, and then match the extracted callback attribute data with the corresponding icon. When the same icon corresponds to multiple callback functions, the computing device 100 can either match multiple callback attribute data points to that icon individually, or combine multiple callback attribute data points into a set of callback information corresponding to that icon.
[0118] Therefore, the computing device 100 can obtain the attribute data corresponding to the HTML report. This attribute data may include symbol identifiers, basic attribute data, and callback attribute data. The symbol identifier may include the symbol name; when symbols with the same name exist in different screens, the symbol identifier may also include the symbol name and the screen name. The computing device 100 can store the attribute data corresponding to the HTML report as a structured list of data objects to facilitate subsequent association of attribute data belonging to the same symbol in different project files.
[0119] It should be noted that the above-described implementation method for parsing multiple project files is illustrative and not intended to limit the scope. In other embodiments, the computing device 100 may also use other methods to parse multiple project files. Furthermore, the computing device 100 may parse three types of project files: screen files, binary files, and HTML reports, or it may parse any two of these types of project files, or it may parse other types of project files; there is no limitation on this.
[0120] In another possible implementation, before executing step S201, the computing device 100 may obtain a pre-configured configuration file, which may include a list of symbol types to be exported and the file paths of each data source. The file paths of each data source may include a station file directory, a database file directory, and a PAL file directory. The computing device 100 can determine the symbol types to be processed based on the list of symbol types to be exported and load the corresponding data source files according to the file paths of each data source.
[0121] S202: The computing device 100 associates attribute data belonging to the same symbol in multiple engineering files to obtain the attribute record of the symbol.
[0122] Associating attribute data belonging to the same symbol refers to the computing device 100 determining the symbol to which attribute data extracted from different project files belongs, and organizing the attribute data belonging to the same symbol together. In the embodiments of this application, "the same symbol" can refer to the same symbol in the same frame.
[0123] Since the attribute data of the same symbol is scattered across multiple project files, it is difficult to obtain a relatively complete set of attribute information for the symbol by processing only the attribute data in a single project file. Therefore, the computing device 100 can determine whether the attribute data in different project files belong to the same symbol and associate the attribute data that belong to the same symbol.
[0124] Specifically, the computing device 100 can match attribute data extracted from different project files based on the symbol identifiers included in the attribute data. The symbol identifiers can include symbol names and screen identifiers. The screen identifier can be a screen name, screen code, or a Module field in the project file.
[0125] For example, the computing device 100 can identify attribute data with the same icon name and the same screen identifier as attribute data belonging to the same icon. When icons with the same name exist in different screens, the computing device 100 can use the screen identifier to distinguish the aforementioned icons with the same name, thereby avoiding incorrect association of icons with the same name in different screens.
[0126] After identifying multiple sets of attribute data belonging to the same symbol, the computing device 100 can associate these multiple sets of attribute data to form attribute records for the corresponding symbol. One attribute record can correspond to one symbol and may include multiple attribute fields and corresponding attribute values extracted from different project files that belong to that symbol. For example, an attribute record may include at least two of the following: basic attribute data and callback attribute data extracted from an HTML report, specific attribute data extracted from a screen file, and supplementary attribute data extracted from a binary file.
[0127] The computing device 100 can write attribute data of different types belonging to the same symbol into the same attribute record. For example, the computing device 100 can determine that attribute data extracted from screen files, binary files, and HTML reports correspond to the same symbol based on the symbol name and screen identifier, and store the attribute names and attribute values from the aforementioned attribute data in the attribute record of that symbol. Thus, a single attribute record can centrally record the attribute data of the corresponding symbol in different project files.
[0128] In another implementation, the computing device 100 can also construct multiple attribute data pages at the screen level based on the screen identifiers included in the attribute records of multiple symbols. Specifically, the computing device 100 can read the Module field or other screen identifiers in the attribute records and write the attribute records of multiple symbols with the same screen identifier to the same attribute data page. Each attribute data page corresponds to one screen and is used to centrally record or present the attribute records corresponding to multiple symbols in that screen. When symbols with the same name exist in different screens, the computing device 100 can write the attribute records of the corresponding symbols to different attribute data pages according to the screen identifier, thereby avoiding confusion between symbols with the same name in different screens.
[0129] For example, the computing device 100 can create an independent attribute data page for each screen and name the attribute data page with the screen code of the corresponding screen. When multiple attribute data pages are stored in a workbook, an attribute data page can be a worksheet in the workbook, and each worksheet can be used to record the attribute records of each icon in a screen.
[0130] The computing device 100 can also construct a summary page and record the screen codes corresponding to multiple screens in the summary page. The computing device 100 can establish links between the screen codes in the summary page and the corresponding attribute data pages. For example, the computing device 100 can set hyperlinks pointing to the corresponding attribute data pages for each screen code in the summary page. When a selection operation for a screen code is received, the computing device 100 can jump to the attribute data page of the corresponding screen according to the link relationship corresponding to that screen code to display the attribute records of each icon in that screen.
[0131] Therefore, the computing device 100 can first convert the attribute data, which was originally scattered according to the project documents, into attribute records organized at the icon level. Then, based on the screen identifier, it can group the attribute records of multiple icons according to the screen and construct corresponding pages at the screen level. In this way, different attribute data belonging to the same icon can be processed uniformly, and attribute records of multiple icons belonging to the same screen can also be centrally recorded and managed, thus providing a data foundation for subsequent attribute data verification at the icon level.
[0132] S203: The computing device 100 verifies the attribute data in the attribute record of the symbol according to the verification requirements corresponding to the symbol, and obtains the verification result.
[0133] Validation requirements indicate the conditions that the attribute data of a symbol must meet. Different types of symbols can have different attribute data and functional requirements; therefore, different types of symbols can correspond to different validation requirements.
[0134] After obtaining the attribute record of a symbol, the computing device 100 can determine the corresponding verification requirement based on the symbol type in the attribute record, and verify the corresponding attribute data in the attribute record according to the determined verification requirement. For example, the computing device 100 can pre-store the correspondence between symbol types and verification requirements, and query the verification requirement applicable to the symbol from the correspondence based on the symbol type in the attribute record.
[0135] This embodiment provides the following non-limiting implementation methods for validating attribute data according to validation requirements.
[0136] See Figure 4 , Figure 4This is a flowchart illustrating an attribute data verification process provided in an embodiment of this application. Steps S400, S410, and S420 are all specific implementations of step S203, which verifies the attribute data according to verification requirements. The computing device 100 can execute any one of steps S400, S410, and S420, or any combination of multiple steps therein. The above steps can be executed in parallel or in any order.
[0137] In the first embodiment, the verification requirements include a first verification requirement, such as... Figure 4 As shown, computing device 100 can execute step S400.
[0138] S400: The computing device 100 verifies whether the attribute data in the attribute record of the symbol is consistent with the preset attribute data based on the first verification requirement, and obtains the first verification result.
[0139] The first verification requirement is to ensure consistency between the attribute data in the attribute record used to indicate the symbol and the preset attribute data. The preset attribute data can be predetermined data used as the basis for attribute data verification. The preset attribute data can be derived from at least one of the following: panel configuration file, display class database, or device call information table.
[0140] The computing device 100 can determine the corresponding preset attribute data based on the symbol type and the attribute data to be verified, and compare the attribute data in the attribute record with the corresponding preset attribute data. When the attribute data in the attribute record matches the preset attribute data, the computing device 100 can generate a first verification result indicating that the corresponding attribute data matches; when the attribute data in the attribute record does not match the preset attribute data, the computing device 100 can generate a first verification result indicating that the corresponding attribute data does not match.
[0141] In the first example, the computing device 100 can compare attribute data in the attribute record with preset attribute data in the panel configuration file. The panel configuration file may include at least one of a digital panel configuration file (dig_panel) or an analog panel configuration file (ana_panel).
[0142] The computing device 100 can search for the corresponding panel configuration record in the panel configuration file based on the device identifier, symbol identifier, or other matching information in the attribute record, and compare at least one of the device identifier, symbol, and panel type in the attribute record with the corresponding preset attribute data in the panel configuration record.
[0143] In the second example, the computing device 100 can compare attribute data in the attribute record with preset attribute data in the display class database. The display class database may include at least one of an analog display database and a digital display database. For example, the analog display database and the digital display database may be corresponding display class databases.
[0144] For analog display symbols, digital display symbols, or threshold display symbols, the computing device 100 can search for the corresponding database record in the corresponding display class database based on the screen code, variable point name, or other matching information in the attribute record, and compare at least one of the screen code, variable point name, upper limit of range, lower limit of range, threshold, and hysteresis in the attribute record with the corresponding preset attribute data in the database record.
[0145] When the hysteresis in the attribute record is expressed as a percentage, while the hysteresis in the display database is expressed as a numerical value, the computing device 100 can calculate the corresponding hysteresis value based on the upper limit of the range, the lower limit of the range, and the hysteresis percentage, and compare the calculated hysteresis value with the hysteresis recorded in the display database. For example, the hysteresis value can be obtained using the following formula:
[0146] In the third example, the computing device 100 can compare the attribute data in the attribute record with the preset attribute data in the device call information table. The computing device 100 can also look up the corresponding device call record in the device call information table based on the device identifier in the attribute record. Furthermore, the computing device 100 can compare the device identifier and call page name in the attribute record with the device identifier and call page name in the device call record to verify whether the correspondence between the corresponding device and the page that calls that device is consistent.
[0147] In the second implementation, the verification requirement includes a second verification requirement. For example... Figure 4 As shown, computing device 100 can execute step S410.
[0148] S410: The computing device 100 verifies whether the attribute data in the attribute record of the symbol meets the data specification based on the second verification requirement, and obtains the second verification result.
[0149] The second verification requirement can be used to indicate the data specifications that attribute data must meet. Data specifications can define the name, format, or value form that attribute data should take. The computing device 100 can determine the target attribute that needs to be verified for data specifications based on the symbol type, and verify whether the attribute value of the target attribute meets the corresponding data specifications.
[0150] In the first example, the computing device 100 can verify whether the naming of the symbol conforms to a preset naming format. This naming format can consist of a screen code, a separator, and the symbol name in sequence. For example, when the separator is an underscore, the naming format can be represented as "screen code_symbol name". When the symbol name conforms to the format "screen code_symbol name", the computing device 100 can determine that the symbol name meets the data specifications; when the symbol name does not conform to the above format, the computing device 100 can determine that the symbol name does not meet the data specifications.
[0151] In the second example, for a symbol whose HomePage attribute needs to be validated, the computing device 100 can read the HomePage attribute from the attribute record and verify whether the attribute value of the HomePage attribute contains a specified column identifier. The column identifier may include at least one of "Column A", "Column B", and "Column C". When the attribute value of the HomePage attribute contains the specified column identifier, the computing device 100 can determine that the HomePage attribute meets the data specification; when the attribute value of the HomePage attribute does not contain the specified column identifier, the computing device 100 can determine that the HomePage attribute does not meet the data specification.
[0152] In the third example, for dynamic icons, the computing device 100 can read the attribute value of the icon name column and the icon type name in the attribute record, and verify whether the dynamic icon has been renamed by comparing the attribute value of the icon name column with the icon type name. When the attribute value of the icon name column is equal to the icon type name, the computing device 100 can determine that the dynamic icon has not been renamed, that is, the dynamic icon does not meet the data specification; when the attribute value of the icon name column is not equal to the icon type name, the computing device 100 can determine that the dynamic icon has been renamed, that is, the dynamic icon meets the data specification.
[0153] The computing device 100 can generate a second verification result based on whether the attribute data meets the data specifications. The second verification result can be used to indicate whether the corresponding attribute data meets or does not meet the data specifications.
[0154] In the third implementation, the verification requirements include a third verification requirement. For example... Figure 4 As shown, computing device 100 can execute step S420.
[0155] S420: The computing device 100 verifies, based on the third verification requirement, whether one or more attributes in the attribute record of the symbol meet the preset logical relationship, and obtains the third verification result.
[0156] The third validation requirement can be used to indicate the preset logical relationship that must be satisfied between one or more attributes. The preset logical relationship may include the internal format relationship that the attribute value of one attribute must satisfy, or the association relationship that the attribute values of multiple attributes must satisfy.
[0157] In the first example, when the value of the operation attribute ISOP in the attribute record is "OP", or the value of the quality attribute Q is "RECTS", the computing device 100 can verify whether the value of the TRAIN attribute is not "NoneT" and whether Callbacks exist. When the value of the TRAIN attribute is "NoneT" or Callbacks do not exist, the computing device 100 can determine that the corresponding attributes do not satisfy the preset logical relationship; when the value of the TRAIN attribute is not "NoneT" and Callbacks exist, the computing device 100 can determine that the corresponding attributes satisfy the preset logical relationship.
[0158] In the second example, when the HandAutoState attribute value in the attribute record is "Manual" or "Auto", the computing device 100 can search for the configuration record corresponding to the icon in the relevant panel configuration file and verify whether the A / M point name in the configuration record is empty. When the A / M point name is not empty, the computing device 100 can determine that the HandAutoState attribute and the A / M point name satisfy the preset logical relationship; when the A / M point name is empty, the computing device 100 can determine that the HandAutoState attribute and the A / M point name do not satisfy the preset logical relationship; when the HandAutoState attribute is empty, the computing device 100 does not trigger the verification.
[0159] In the third example, computing device 100 can verify whether the attribute value of user data attribute Pt_ARG_USER_DATA meets a preset format. The preset format may include a variable name, a separator, and a number arranged in sequence, with the separator being a semicolon. For example, the attribute value of Pt_ARG_USER_DATA can be in the format "variable name;number". When the content before the semicolon conforms to the variable name format and the content after the semicolon conforms to the number format, computing device 100 can determine that the attribute value of Pt_ARG_USER_DATA meets the preset format; otherwise, it can determine that the attribute value of Pt_ARG_USER_DATA does not meet the preset format.
[0160] It should be noted that the above-described implementation method for validating attribute data according to verification requirements is an illustrative example and is not intended to limit the scope. In other embodiments, the computing device 100 may also employ other methods to validate attribute data according to verification requirements.
[0161] Furthermore, the computing device 100 can determine the symbols that need to be exported and verified based on the pre-configured inspection scope. In one embodiment, the computing device 100 can read the "Symbol Overview" worksheet in a predefined Excel configuration table to obtain the types of symbols to be exported and the corresponding Symbol type mappings for each symbol type, and export the attribute data of the corresponding symbols based on the obtained configuration information.
[0162] As an optional implementation, the computing device 100 may also provide a graphical configuration interface, through which it receives a user-configured list of symbols to be inspected and verification rules, and determines the symbols to be inspected and their corresponding verification rules based on the configuration results. Whether using an Excel configuration table or a graphical configuration interface, the computing device 100 can flexibly configure the export range and verification range of symbols according to actual inspection needs.
[0163] The computing device 100 can obtain the verification result of the symbol based on at least one of the first verification result, the second verification result, and the third verification result. The verification result can be used to indicate whether the attribute data in the attribute record of the symbol has passed the corresponding verification.
[0164] In one implementation, the computing device 100 can determine the attribute data that failed validation based on the validation results and mark the differences for the attribute data that failed validation. When the attribute records of the icon are output in the form of an Excel file, the computing device 100 can determine the cell containing the attribute data that failed validation, set the background color of the corresponding cell to red, and add a comment including an error description to the corresponding cell. The user can locate the attribute data that failed validation based on the cell display style and view the reason for the failure of the corresponding attribute data through the comment.
[0165] For example, the computing device 100 can also generate independent inspection log files based on the verification results. The inspection log files can be in Excel format and can have multiple worksheets set up according to error categories. Each worksheet stores the inspection logs belonging to the corresponding error category. For example, error categories can include at least one of the following: inconsistent attribute data, attribute data not meeting data specifications, and attribute data not meeting preset logical relationships.
[0166] Each inspection log entry may include at least one of the following: symbol type, line number, symbol name, device identifier, attribute name, attribute value, error category, or detailed description. The line number indicates the location of the failed attribute data in the Excel file; the attribute value can be the actual value of the failed attribute data; and the detailed description explains the reason why the corresponding attribute data failed validation. This allows for structured storage of discrepancy information and facilitates the location, modification, review, and traceability of failed attribute data.
[0167] Furthermore, the attribute records and inspection logs of the symbols are not limited to being output in the form of Excel files. In other embodiments, the computing device 100 may output the attribute records and inspection logs of the symbols as comma-separated values (CSV) files, HTML files, or database records, according to user requirements. Different output formats can employ verification result recording methods adapted to the corresponding file formats or data storage formats. The changes in the above-mentioned output formats do not affect the computing device 100's verification of the attribute data in the attribute records of the symbols based on verification requirements.
[0168] The above combination Figures 1 to 4 The image attribute data verification method provided in the embodiments of this application will be introduced. Next, the structure of the image attribute data verification device and computing device provided in the embodiments of this application will be described with reference to the accompanying drawings.
[0169] This application also provides a screen attribute data verification device. See also Figure 5 , Figure 5 A schematic diagram of a screen attribute data verification device according to an embodiment of this application is shown. The screen attribute data verification device 500 can be applied to a screen attribute data verification system or deployed in a computing device used for screen attribute data verification. The screen attribute data verification device 500 may include a parsing module 510, an association module 520, and a verification module 530.
[0170] The parsing module 510 is used to parse multiple project files corresponding to the screen, obtain the attribute data included in each project file, the attribute data in the multiple project files correspond to the icons in the screen, and different project files in the multiple project files include different attribute data of the same icon. The project file is the project file of DCS.
[0171] The association module 520 is used to associate attribute data belonging to the same symbol in multiple project files to obtain the attribute record of the symbol.
[0172] The verification module 530 is used to verify the attribute data in the attribute record of the symbol according to the verification requirements corresponding to the symbol, and obtain the verification result. The verification result is used to indicate whether the attribute data meets the verification requirements.
[0173] In one possible implementation, the various project files can be at least two of the following: screen files, binary files, and HTML reports. The screen file is a file that stores the attribute data of the icons in the screen in a custom format, the binary file is a file that stores the attribute data of the icons in the screen in binary encoding, and the HTML report is a report that stores the attribute data of the icons in the screen in HTML format.
[0174] In one possible implementation, the project file can be a screen file, and the screen attribute data verification device further includes an acquisition module for acquiring the widget palette PAL file; a parsing module 510 for parsing the PAL file to obtain symbol attribute definition information, which describes the attribute names of different symbol types, or the symbol attribute definition information describes the content represented by different attribute values of different symbol types; the screen file is parsed using the symbol attribute definition information to obtain the attribute data included in the screen file.
[0175] In one possible implementation, the project file can be a binary file. The parsing module 510 is used to perform character conversion on the binary file to obtain the data to be parsed. The starting position of the target icon's icon identifier in the parsed data is determined in the parsed data. The icon identifier is used to distinguish different icons in the screen. According to the starting position and the preset offset rule, the parsed data is extracted to obtain the attribute data of the target icon. The preset offset rule is used to specify the offset of the position of different attribute data relative to the starting position.
[0176] In one possible implementation, the project file may be an HTML report. The parsing module 510 is used to identify HTML tags in the HTML report and the relationships between the HTML tags. The HTML tags are used to organize the attribute data of the icons in the image. Based on the relationships between the HTML tags, attribute data is extracted from the content corresponding to the HTML tags.
[0177] In one possible implementation, the attribute record can be a screen identifier, which is used to indicate the screen where the icon is located. The screen attribute data verification device also includes a generation module, which is used to generate an attribute data page based on the screen identifier. The attribute data page is used to store the attribute record of at least one icon located in the screen.
[0178] In one possible implementation, the verification requirement can be a first verification requirement, which is used to verify whether at least one attribute data in the attribute record of the symbol is consistent with the preset attribute data corresponding to the symbol; the verification module 530 is used to verify at least one attribute data in the attribute record of the symbol based on the first verification requirement to obtain the first verification result.
[0179] In one possible implementation, the verification requirement can be a second verification requirement, which is used to verify whether at least one attribute data in the attribute record of the symbol meets the data specification. The data specification is used to ensure the standardization of the attribute data. The verification module 530 is used to verify at least one attribute data in the attribute record of the symbol based on the second verification requirement to obtain the second verification result.
[0180] In one possible implementation, the verification requirement can be a third verification requirement, which is used to verify whether different attribute data in the attribute record of the symbol satisfy a logical relationship. The logical relationship is used to characterize the constraints that the attribute data in the attribute record of the symbol should satisfy. The verification module 530 is used to verify at least one attribute data in the attribute record of the symbol based on the third verification requirement to obtain the third verification result.
[0181] The screen attribute data verification device 500 provided in this embodiment corresponds to the above-mentioned... Figures 2 to 4 The image attribute data verification method in the illustrated embodiment is described above. Therefore, the functions and technical effects of each module in this embodiment can be found in the foregoing. Figures 2 to 4 The relevant descriptions in the illustrated embodiments will not be repeated here.
[0182] Figure 6 This is a schematic diagram of the hardware structure of a computing device provided in this application. Figure 6 As shown, the computing device 600 includes a processor 610, a memory 620, a communication interface 630, and a bus 640. The processor 610, memory 620, and communication interface 630 communicate via the bus 640. The bus 640 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 6 The symbol is represented by a single thick line, but this does not indicate that there is only one bus or one type of bus. The communication interface 630 is used for external communication.
[0183] It should be understood that in the embodiments of this application, the processor 610 may be a CPU, or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete device assemblies, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.
[0184] The memory 620 may include read-only memory and random access memory, and provides instructions and data to the processor 610. The memory 620 may also include non-volatile random access memory.
[0185] The memory 620 can be volatile memory or non-volatile memory, or it can include both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).
[0186] The memory 620 stores executable code, and the processor 610 executes the executable code to perform the aforementioned actions. Figures 2 to 4 The method performed in the illustrated embodiment.
[0187] It should be understood that the computing device 600 in this application embodiment may correspond to the computing device 100 in this application embodiment, and may correspond to the execution of the embodiments in this application embodiment. Figure 2 and Figure 4The method executed by computing device 100 in the illustrated method; the above and other operations or functions implemented by computing device 600 can be realized. Figure 2 and Figure 4 The method flow executed by the computing device 100 in the method shown will not be described in detail here for the sake of brevity.
[0188] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct a computing device to perform the above-described digest verification method.
[0189] This application also provides a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computing device, all or part of the processes or functions described in this application are generated.
[0190] The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, or data center to another website, computer, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.
[0191] The computer program product can be a software installation package. When the aforementioned screen attribute data verification method is required, the computer program product can be downloaded and executed on a computing device.
[0192] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.
[0193] The terminology used in the above embodiments is for the purpose of describing specific embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, “one or more” refers to one, two, or more; the character “ / ” generally indicates that the preceding and following objects are in an “or” relationship. In the embodiments of this application, “simultaneously” refers to the same time period, including situations where they are at the same moment.
[0194] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0195] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for verifying image attribute data, characterized in that, The method includes: The screen is analyzed to obtain the attribute data of each type of project file. The attribute data in the various project files correspond to the symbols in the screen. Different project files in the various project files include different attribute data of the same symbol. The project file is a file of the nuclear power digital instrumentation and control system (DCS). The attribute data belonging to the same symbol in the various engineering files are associated to obtain the attribute record of the symbol; According to the verification requirements corresponding to the symbol, the attribute data in the attribute record of the symbol is verified to obtain a verification result, which is used to indicate whether the attribute data meets the verification requirements.
2. The method according to claim 1, characterized in that, The various project files include at least two of the following: screen files, binary files, and HTML reports. The screen file is a file that stores the attribute data of the icons in the screen in a custom format. The binary file is a file that stores the attribute data of the icons in the screen in binary encoding. The HTML report is a report that stores the attribute data of the icons in the screen in HTML format.
3. The method according to claim 2, characterized in that, The various project files include the screen files, and the method further includes: Obtain the widget palette PAL file; The analysis screen corresponds to multiple project files, and the attribute data included in each project file are obtained, including: Parse the PAL file to obtain symbol attribute definition information. The symbol attribute definition information is used to describe the attribute names of different symbol types, or the symbol attribute definition information is used to describe the content represented by different attribute values of different symbol types. The image file is parsed using the icon attribute definition information to obtain the attribute data included in the image file.
4. The method according to claim 2, characterized in that, The various project files include the binary file. The various project files corresponding to the parsed screen are used to obtain attribute data for each project file, including: The binary file is converted into characters to obtain the data to be parsed; The starting position of the symbol identifier of the target symbol in the data to be parsed is determined, and the symbol identifier is used to distinguish different symbols in the image; Based on the starting position and the preset offset rule, the data to be parsed is extracted to obtain the attribute data of the target icon. The preset offset rule is used to specify the offset of the position of different attribute data relative to the starting position.
5. The method according to claim 2, characterized in that, The various project files include the HTML report, and the various project files corresponding to the parsed screen are used to obtain attribute data for each project file, including: Identify the HTML tags in the HTML report and the relationships between the HTML tags, which are used to organize the attribute data of the icons in the image; Based on the relationships between the HTML tags, attribute data is extracted from the content corresponding to the HTML tags.
6. The method according to claim 1, characterized in that, The attribute record includes a screen identifier, which indicates the screen where the icon is located. The method further includes: Based on the screen identifier, an attribute data page is generated, which is used to store attribute records of at least one icon located in the screen.
7. The method according to any one of claims 1 to 6, characterized in that, The verification requirement includes a first verification requirement, which is used to verify whether at least one attribute data in the attribute record of the icon is consistent with the preset attribute data corresponding to the icon; The step of verifying the attribute data in the attribute record of the icon according to the verification requirements corresponding to the icon, and obtaining the verification result, includes: Based on the first verification requirement, at least one attribute data in the attribute record of the icon is verified to obtain a first verification result.
8. The method according to any one of claims 1 to 6, characterized in that, The verification requirement includes a second verification requirement, which is used to verify whether at least one attribute data in the attribute record of the icon meets the data specification, and the data specification is used to ensure the standardization of the attribute data; The step of verifying the attribute data in the attribute record of the icon according to the verification requirements corresponding to the icon, and obtaining the verification result, includes: Based on the second verification requirement, at least one attribute data in the attribute record of the icon is verified to obtain the second verification result.
9. The method according to any one of claims 1 to 6, characterized in that, The verification requirement includes a third verification requirement, which is used to verify whether the different attribute data in the attribute record of the symbol satisfy a logical relationship. The logical relationship is used to characterize the constraint conditions that the attribute data in the attribute record of the symbol should satisfy. The step of verifying the attribute data in the attribute record of the icon according to the verification requirements corresponding to the icon, and obtaining the verification result, includes: Based on the third verification requirement, at least one attribute data in the attribute record of the icon is verified to obtain the third verification result.
10. A device for verifying image attribute data, characterized in that, The device includes: The parsing module is used to parse the various engineering files corresponding to the screen and obtain the attribute data included in each engineering file. The attribute data in the various engineering files correspond to the symbols in the screen. Different engineering files in the various engineering files include different attribute data of the same symbol. The engineering files are files of the nuclear power digital instrumentation and control system (DCS). The association module is used to associate attribute data belonging to the same symbol in the various engineering files to obtain the attribute record of the symbol; The verification module is used to verify the attribute data in the attribute record of the symbol according to the verification requirements corresponding to the symbol, and obtain the verification result. The verification result is used to indicate whether the attribute data meets the verification requirements.
11. A computing device, characterized in that, The computing device includes a processor and memory; The memory is used to store instructions, and the processor executes the instructions stored in the memory to cause the computing device to perform the method as described in any one of claims 1 to 9.
12. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on at least one computing device, cause the at least one computing device to perform the method as described in any one of claims 1 to 9.
13. A computer program product containing instructions, characterized in that, When it is run on at least one computing device, it causes the at least one computing device to perform the method as described in any one of claims 1 to 9.
