Design drawing file detection method, system and equipment and storage medium

Abstract

The invention discloses a design drawing file detection method, system and device and a storage medium, and is applied to the technical field of drawing detection, and the method comprises the following steps: obtaining an initial design drawing file and a to-be-detected design drawing file; the method comprises the following steps of: scanning an initial design drawing file and a to-be-tested design drawing file, and taking unique database identifiers of components as partitions of different components to obtain pin associated information of each pin of each component in the initial design drawing file as a first file; obtaining respective pin associated information of each pin of each component in the to-be-tested design drawing file as a second file; comparing the first file with the second file to obtain different pins; and when the difference condition of the pins does not accord with a preset negligible rule, listing the pins in a to-be-rechecked file. By applying the scheme of the invention, the detection of the design drawing file can be effectively completed, the detection efficiency is improved, the error probability is reduced, and the comprehensiveness of problem discovery is improved.

Description

Technical Field

[0001] The present application relates to the technical field of drawing detection, and in particular to a method, system, device and storage medium for detecting design drawing files. Background Art

[0002] With the popularization of technologies such as 5G communications and AI computing, the complexity of server design has increased exponentially. The average number of pages in a single server design drawing file is more than 200, which makes the current manual inspection solution face challenges.

[0003] Currently, when a design file undergoes a revision, manual verification of the latest revision requires page-by-page verification, which is time-consuming and carries a high error rate. Alternatively, designers export a bill of materials (BOM), which contains information such as the model, quantity, supplier, and lifecycle status (e.g., discontinued or replacement) of all components in the design file. Errors are then reported, allowing staff to troubleshoot each error step-by-step. However, this approach often generates a large number of errors, making manual verification time-consuming. Furthermore, most errors are manually identified as normal revision changes, making this approach ineffective for troubleshooting. Furthermore, changes to component symbols, such as pinouts, often go unreported, making this approach prone to hidden risks. For example, a CPU power pin symbol was updated without generating an error, and staff were unaware of the issue, leading to production downtime and significant losses.

[0004] In summary, how to effectively complete the detection of design drawing files, improve detection efficiency, reduce the probability of errors, and improve the comprehensiveness of problem discovery is a technical problem that technical personnel in this field urgently need to solve. Summary of the Invention

[0005] The present application provides a method, system, device and storage medium for detecting design drawing files to effectively complete the detection of design drawing files, improve detection efficiency, reduce the probability of error, and improve the comprehensiveness of problem discovery.

[0006] To solve the above technical problems, this application provides the following technical solutions:

[0007] In a first aspect, the present invention provides a method for detecting a design drawing file, comprising:

[0008] Acquire an initial design drawing file for representing component connection relationships, and a design drawing file to be tested obtained after the initial design drawing file is updated;

[0009] By scanning the initial design file and the design file to be tested, using the unique database identifier of the component as a division of different components, pin association information of each pin of each component in the initial design file is obtained as a first file, and pin association information of each pin of each component in the design file to be tested is obtained as a second file;

[0010] Comparing the first file and the second file to obtain pins having differences;

[0011] For any pin with a difference, determine whether the difference of the pin meets the preset ignorable rule;

[0012] If not, the pin is listed in the file for review.

[0013] On the other hand, the pin association information of the pin includes the pin symbol of the pin, and also includes one or more of the material attributes of the pin, the position coordinates in the design drawing file, the packaging parameters, and the connection relationship.

[0014] On the other hand, for any pin with a difference, determining whether the difference of the pin meets the preset ignorable rule includes:

[0015] For any pin with differences, when only a single item of the pin association information of the pin is different in the first file and the second file, it is determined that the difference of the pin meets the preset ignorable rule.

[0016] On the other hand, it also includes:

[0017] When the difference of the pins meets the preset ignorable rule, the pins are listed in the ignorable file;

[0018] Determine the proportion of pins of the target type in the total number of pins in the ignorable file;

[0019] If the proportion is higher than a first threshold, generating an alarm file including pins of all target types and pushing the alarm file;

[0020] The pins of the target type in the ignorable file indicate that the pin-related information of the pins in the first file and the second file differs only in material attributes.

[0021] On the other hand, it also includes:

[0022] According to the differences in the pins, the pins in the file to be reviewed are divided into risk levels to obtain a plurality of sub-files to be reviewed.

[0023] On the other hand, according to the differences in the pins, the pins in the to-be-reviewed file are divided into risk levels to obtain a plurality of to-be-reviewed sub-files, including:

[0024] According to the differences in the pins, based on the preset classification rules, the pins in the file to be reviewed are classified into risk levels to obtain a plurality of sub-files to be reviewed;

[0025] The division rules include:

[0026] For any pin with a difference, when the difference of the pin meets any difference situation in a preset specific difference situation set, the risk level of the pin is determined to be the third risk level;

[0027] For any pin with a difference, when the difference of the pin does not conform to the specific difference condition set, and only two items of the pin-related information of the pin differ between the first file and the second file, the risk level of the pin is determined to be the first risk level;

[0028] For any pin with a difference, when the difference of the pin does not conform to the specific difference set, and there are two or more contents of the pin association information of the pin different in the first file and the second file, the risk level of the pin is determined to be the second risk level.

[0029] On the other hand, it also includes:

[0030] For different sub-files to be reviewed, corresponding processing measures are executed according to preset processing rules.

[0031] In a second aspect, the present invention provides a system for detecting design drawing files, comprising:

[0032] A design drawing file acquisition module, used to acquire an initial design drawing file for representing the connection relationship of components, and a design drawing file to be tested obtained after the initial design drawing file is updated;

[0033] a scanning module configured to scan the initial design file and the design file to be tested, using the unique database identifier of the component as a division of different components, obtain pin association information for each pin of each component in the initial design file as a first file, and obtain pin association information for each pin of each component in the design file to be tested as a second file;

[0034] A comparison module, configured to compare the first file and the second file to obtain pins having differences;

[0035] A filtering module is used to determine, for any pin with a difference, whether the difference of the pin meets the preset ignorable rule; if not, trigger the pending review module;

[0036] The module to be reviewed is used to list the pins in the file to be reviewed.

[0037] In a third aspect, the present invention provides a device for detecting a design drawing file, comprising:

[0038] Memory for storing computer programs;

[0039] A processor is used to execute the computer program to implement the steps of the design drawing file detection method as described above.

[0040] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for detecting design drawing files as described above.

[0041] By applying the technical solution provided by the embodiments of the present invention, design files can be automatically tested, thereby effectively improving detection efficiency and reducing the probability of error. Furthermore, the scanning is achieved through a "database identifier-association information" approach, enabling pin differences to be effectively determined. Specifically, after obtaining the initial design file and the design file to be tested, the initial design file and the design file to be tested are scanned. Furthermore, using the component's unique database identifier as a classification for different components, pin association information for each pin of each component in the initial design file is obtained as a first file, and pin association information for each pin of each component in the design file to be tested is obtained as a second file. After obtaining the first and second files, a comparison can be made to identify the pins that differ between the first and second files. Furthermore, to further improve efficiency, the present invention provides that when a pin difference meets a preset ignorable rule, it indicates that the pin association information for the pin in the first and second files differs due to a normal version update, and therefore the pin can be ignored. In some cases, the pin can also be included in the ignorable file. Of course, pins in the ignorable file do not require manual verification. Conversely, if the pin does not meet the ignorable rule, the pin should be included in the pending review file, and subsequent staff can simply check the pins in the pending review file. In addition, because the present application solution can obtain the individual pins with differences through the pin association information in the first and second files, it helps reduce hidden risks and effectively improves the comprehensiveness of problem discovery.

[0042] In summary, the present application solution can effectively complete the detection of design drawing files, improve detection efficiency, reduce the probability of error, and improve the comprehensiveness of problem discovery. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0044] Figure 1 A flowchart of a method for detecting a design drawing file provided in a specific embodiment of the present invention;

[0045] Figure 2 This is a schematic diagram illustrating an example of pin modification in a specific embodiment of the present invention;

[0046] Figure 3 A schematic diagram of the principle of hierarchical processing of documents to be reviewed in a specific implementation method;

[0047] Figure 4 A structural flow chart of a system for detecting design drawing files provided in a specific embodiment of the present invention;

[0048] Figure 5 A structural flow chart of a detection device for a design drawing file provided in a specific embodiment of the present invention;

[0049] Figure 6 This is a schematic structural diagram of a computer-readable storage medium of the present invention. DETAILED DESCRIPTION

[0050] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0051] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0052] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0053] Please refer to Figure 1 , Figure 1 This is a flowchart of a method for detecting a design drawing file provided in a specific embodiment of the present invention. The method for detecting a design drawing file may include the following steps:

[0054] Step S101: obtaining an initial design drawing file for representing component connection relationships, and a design drawing file to be tested obtained after the initial design drawing file is updated.

[0055] The initial design drawing file is the principle design drawing file before the update, and the principle design drawing file obtained after the update is called the design drawing file to be tested. It is understandable that, ideally, for each difference between the design drawing file to be tested and the initial design drawing file, it should be checked by the staff to ensure that the difference is a normal update and modification, and to find errors in time. However, since the design drawing file has many pages and each page contains a large amount of content, if the difference check between the initial design drawing file and the design drawing file to be tested is performed manually, not only will the efficiency be very low, but the error omission rate will also be very high. The present application solution will automatically scan and analyze the initial design drawing file and the design drawing file to be tested, and finally obtain the file to be reviewed for manual verification, which effectively reduces the workload of the staff, improves efficiency, and can also improve the comprehensiveness of problem discovery and reduce hidden risks.

[0056] The initial design drawing file is the principle design drawing file before the update, which can reflect the connection relationship of components and can be in PDF, EDIF and other formats, and can be set according to actual needs. Similarly, the design drawing file to be tested can also reflect the connection relationship of components and can also be in PDF, EDIF and other formats. Since the design drawing file to be tested is obtained after the initial design drawing file is updated, there must be certain differences between the two, that is, there are modifications. Ideally, these modifications should be correct modifications. However, it is understandable that due to the large number of components and complex connection relationships in actual applications, erroneous modifications are inevitable in the design stage during the continuous version update process. At this time, manual review is required to effectively discover erroneous modifications and then correct them.

[0057] Step S102: By scanning the initial design drawing file and the design drawing file to be tested, the unique database identifier of the component is used as the division of different components, and the pin association information of each pin of each component in the initial design drawing file is obtained as the first file, and the pin association information of each pin of each component in the design drawing file to be tested is obtained as the second file.

[0058] By scanning the initial design drawing file, the first file can be obtained. Specifically, the present application scheme implements scanning in the form of "database identifier-association information", that is, scanning in the form of "DBID-segs". DBID (Database Identifier) ​​refers to the unique database identifier of each component in the design drawing file, which is used to associate its attributes and signal connection relationships. It can usually be encoded in hexadecimal. For example, if the database identifier of a component is "0x3A5F", it can be understood that in the initial design drawing file, the relevant content belonging to the component can be located through "0x3A5F". Segs (Signal Segments) refers to a collection of signal segments, which can represent the logical connection path between components in the design drawing file and can support multi-level nested structures (such as power supply networks, clock trees). In the present application scheme, through DBID-segs, each component in the initial design drawing file can be located, and then the pin association information of each pin of each component can be determined, thereby serving as the first file obtained.

[0059] Furthermore, in actual applications, since the initial design drawing file typically has multiple pages, it can be scanned page by page. For example, after scanning page 1 of the initial design drawing file, the relevant results are stored in table_DBID_segs-NF5500_1. After scanning page 2 of the initial design drawing file, the relevant results are stored in table_DBID_segs-NF5500_2. After scanning page 3 of the initial design drawing file, the relevant results are stored in table_DBID_segs-NF5500_3. Similarly, after scanning page N of the initial design drawing file, the relevant results are stored in table_DBID_segs-NF5500_N. Finally, the above table_DBID_segs-NF5500_1 to table_DBID_segs-NF5500_N can form an identifiable file, such as table_DBID_segs-8250_A, which is the first file in this example.

[0060] The design file to be tested can be scanned using the same scanning method to obtain a second file. This scanning can also be achieved using the "database identifier-association information" method. Using DBID-segs, each component in the design file to be tested can be located, and the pin association information for each pin of each component can be determined, thereby obtaining the second file.

[0061] Similarly, since the design drawing file to be tested usually has multiple pages, it can be scanned page by page. For example, in one case, after scanning page by page, the final recognizable file is recorded as table_DBID_segs-8250_B, which is the second file in this example.

[0062] Step S103: Compare the first file and the second file to obtain pins with differences.

[0063] By comparing the first file and the second file, the pins with differences can be obtained. It can be understood that for a certain pin of a component, when the pin association information of the pin in the first file is completely consistent with the pin association information of the pin in the second file, it can be determined that there is no difference in the pin. Conversely, if the pin association information of the pin in the first file is not completely consistent with the pin association information of the pin in the second file, it can be determined that there is a difference in the pin.

[0064] For example, if a component A1 is added to the design file to be tested, it can be understood that while the database identifier for component A1 does not exist in the initial design file, it does exist in the design file to be tested. Furthermore, the pin association information for each pin of component A1 can be obtained through "DBID-segs" and recorded in the second file. Therefore, it can be understood that in this example, each pin of component A1 recorded in the second file is a different pin. If these pins subsequently fail to meet the pre-set ignorability rule, they will be included in the file to be reviewed.

[0065] For another example, a component A2 in the initial design drawing file does not appear in the design drawing file to be tested, which means that component A2 was deleted by the designer during this update process. It can be understood that the database identifier of component A2 does not exist in the design drawing file to be tested, but exists in the initial design drawing file. Moreover, the pin association information of each pin of component A2 can be obtained through "DBID-segs" and recorded in the first file. Therefore, it can be understood that in this example, each pin of component A2 recorded in the first file is a different pin. If it does not meet the preset ignorable rules later, these pins of component A2 will be included in the file to be reviewed.

[0066] For example, if a component A3 is present in the initial design file and also in the design file to be tested, it can be understood that the database identifier for component A3 exists in both the initial design file and the design file to be tested. The pin association information for each pin of component A3 can be obtained from the initial design file using "DBID-segs" and recorded in the first file. The pin association information for each pin of component A3 can also be obtained from the design file to be tested using "DBID-segs" and recorded in the second file. For example, in the initial design file, the pin symbol of a pin of component A3 is "PMIC_V2" and is left floating. However, in the design file to be tested, the pin symbol of the same pin of component A3 is changed to "PMIC_V5" and the connection relationship is changed to ground. It can be understood that, after comparing the first and second files, it can be determined that the pin of component A3 is a different pin. If it subsequently does not meet the preset ignorability rule, the pin of component A3 will be included in the file to be reviewed.

[0067] Step S104: for any pin with a difference, determine whether the difference of the pin meets the preset ignorable rule.

[0068] If not, execute step S105: list the pin in the file to be reviewed.

[0069] In the present application, not all pins with differences need to be manually checked by staff. Instead, it will first be determined whether the differences in the pins meet the preset ignorable rules.

[0070] If the pin's difference meets the pre-set ignorability rule, the pin's difference is ignorable. This means the update to that pin is likely a normal modification and not an error. Therefore, the pin can be ignored, effectively reducing staff workload. Alternatively, if the pin's difference meets the pre-set ignorability rule, the pin can be included in the ignorable file. Of course, the ignorable file does not require staff review.

[0071] Of course, if the difference in the pins does not meet the preset ignorable rules, it means that the update and modification of the pin may be wrong. Therefore, the pin needs to be included in the file to be reviewed, so that the staff can subsequently review the pins in the file to be reviewed. That is, the staff can check the differences of each pin in the file to be reviewed, and thus determine whether the update and modification of these pins are normal updates and modifications.

[0072] In practice, to facilitate staff review of pins in the pending review file, when a pin is listed in the pending review file, the pin's associated information in the first file and the pin's associated information in the second file are typically included in the pending review file. Furthermore, in some implementations, other information may be entered as needed, such as the timestamp of the pin's version update, the timestamp of the last modification made by the designer to the pin, the designer's ID, and other related information. This allows staff to quickly address and correct any errors if a subsequent pin update or modification is found to be erroneous, based on this information.

[0073] The specific content of the ignorable rules can be set according to actual needs, and it is understood that generally, reasonable ignorable rules will be set according to the degree of pin change. Specifically, if the pin has undergone a major change, it usually requires staff attention, that is, staff review, and therefore does not meet the ignorable rules, and the pin will be included in the pending review file. Conversely, if the pin has undergone a minor change, it is likely a normal update and modification, and therefore the difference can be confirmed to meet the ignorable rules.

[0074] In a specific embodiment of the present invention, the pin association information of the pin includes the pin symbol of the pin, and also includes one or more of the pin's material attributes, position coordinates in the design drawing file, packaging parameters, and connection relationship.

[0075] This implementation method takes into account that a pin is usually provided with a symbol of the pin. For example, in the above example, the pin symbol of a pin is specifically "PMIC_V2". Therefore, the pin association information of the pin usually includes the pin symbol of the pin.

[0076] In addition to the pin symbol, the pin-related information of the pin may include the material properties of the pin, the position coordinates in the design drawing, the packaging parameters, and one or more of the connection relationships. It can be set according to actual needs to ensure the flexibility of the implementation of the present application. Of course, if you want to reduce hidden risks and effectively improve the comprehensiveness of problem discovery, the pin-related information of the pin should be set more comprehensively, that is, it can include the material properties of the pin, the position coordinates in the design drawing, the packaging parameters, and each of the connection relationships. For example, Figure 2 In an implementation manner, for the initial design drawing file and the design drawing file to be tested, by scanning to obtain the first file and the second file and comparing them, the modification status of the pins can be determined. There may be unmodified pins, or there may be one or more of the following situations: modification of material properties, modification of pin symbols, modification of position coordinates, modification of connection relationships, and modification of packaging parameters.

[0077] A pin's pin symbol is also the pin's name. A pin's material properties indicate the pin's availability, which can be categorized as "available" or "unavailable." A pin's default state is typically "available" unless actively modified. A pin's position coordinates within the design file reflect the pin's location. For example, a pin's position coordinates of (Page 32, X=50mm, Y=20mm) indicate that the pin is located on page 32 of the design file, specifically at the position 50mm (x) and 20mm (y). A pin's package parameters reflect the pin's package information, including information such as the pin's old symbol. A pin's connection relationship reflects the specific connection destination of the pin. For example, for the pin "PMIC_V2" mentioned above, its connection relationship might be "PMIC_V2 of component A1 connected to PMIC_V6 of component A7," meaning that the PMIC_V2 pin of component A1 is connected to the PMIC_V6 pin of component A7.

[0078] In a specific embodiment of the present invention, step S104 may specifically include:

[0079] For any pin with differences, when only a single item of the pin-related information of the pin is different in the first file and the second file, it is determined that the difference of the pin meets the preset ignorable rule.

[0080] As described above, the specific content of the ignorable rules can be set according to actual needs, and generally speaking, reasonable ignorable rules are set according to the degree of pin change.

[0081] This implementation method takes into account that, through experience summary and rationality analysis, it can be determined that when the pin-related information of a certain pin in the first file and the second file is different in only a single item, it means that the pin has undergone a minor change. The difference between the pin in the first file and the second file is usually a normal update by the staff, and the probability of error is very low. It is a ignorable pin, so it can be determined that the difference in the pin meets the preset ignorable rule.

[0082] Using the "PMIC_V2" pin symbol as an example, if, in both the first and second files, only the material attribute for this pin's pin-related information changes from "available" to "unavailable," it's likely that the designer disabled the pin for design purposes. This is a normal update and modification, and the difference in this pin can be ignored. For another example, if only the location coordinates of this pin have changed in its pin-related information—for example, the pin's location coordinates in the initial design file are (Page 32, X=50mm, Y=20mm), while the pin's location coordinates in the design file under test are (Page 32, X=55mm, Y=20mm)—then it's likely that the designer moved the pin for routing purposes, without adjusting other associated information such as the pin's connection relationships. This is a normal update and modification, and the difference in this pin can be ignored.

[0083] In a specific embodiment of the present invention, it may further include:

[0084] When the pin difference meets the preset ignorable rules, the pin is included in the ignorable file;

[0085] Determine the ratio of pins of the target type to the total number of pins in the ignorable file;

[0086] If the proportion is higher than the first threshold, an alarm file including pins of all target types is generated and the alarm file is pushed;

[0087] Among them, the pins of the target type in the file can be ignored, which means that the pin-related information of the pins in the first file and the second file is different only in the material attribute.

[0088] When a pin's difference meets the preset ignorable rules, it can be included in the ignorable file to indicate that the pin's difference can be considered a normal update or modification. However, this implementation further considers that if the proportion of pins of the target type in the ignorable file is too high compared to the total number of pins, that is, if the proportion is higher than a first threshold, it indicates an abnormal situation. To ensure reliability, it is necessary to generate an alarm file including all pins of the target type and push the alarm file to the staff to notice the situation and conduct a review.

[0089] The target type of pin described in this implementation method refers to the pin-related information of the pin in the first file and the second file, and only the material attribute is different. According to the principle of the above implementation method, the difference in such pins is most likely a normal modification. This implementation method further takes into account that if the material attributes of a large number of pins change, it is not a common situation. It may be a normal modification and update by the designer, but it may also be caused by program errors and other reasons. Therefore, generating an alarm file and pushing it can effectively improve the reliability of the application solution and reduce hidden risks.

[0090] In a specific embodiment of the present invention, it may further include:

[0091] According to the differences in the pins, the risk levels of the pins in the to-be-reviewed file are divided to obtain a plurality of to-be-reviewed sub-files.

[0092] This implementation further takes into account that for the pins in the file to be reviewed, the risk levels of the pins in the file to be reviewed can be further divided according to the differences in the pins, thereby obtaining multiple sub-files to be reviewed. This allows the staff to perform differentiated processing during subsequent reviews, that is, for high-risk pins, the staff can check more carefully and handle them in a timely manner. When some fatal errors occur, more stringent response methods such as immediate termination of the design process can be adopted. Correspondingly, for low-risk pins, such as pin differences caused by redundant routing, non-standard symbols, etc., a response method of incorporating them into subsequent version iterations can be adopted.

[0093] In a specific embodiment of the present invention, it may further include:

[0094] For different sub-files to be reviewed, corresponding processing measures are executed according to the preset processing rules.

[0095] In this embodiment, for different sub-files to be reviewed, since the corresponding risk levels are different, different processing measures can be executed according to the preset processing rules. For example, for sub-files to be reviewed with a higher risk level, in addition to outputting the sub-file to be reviewed to the staff, a detailed error report can also be output to assist the staff in reviewing, and for example, at least 2 staff members can also be required to review, that is, only when the feedback of "review passed" from at least 2 staff members is detected, it will be determined that the pin in the sub-file to be reviewed is indeed a normal modification, and not an error. Otherwise, an alarm can be issued periodically to remind the relevant staff to deal with it in time. For sub-files to be reviewed with a lower corresponding risk level, some milder processing measures can be adopted, such as only outputting the sub-file to be reviewed to the staff. For sub-files to be reviewed with a moderate corresponding risk level, moderate processing measures can be adopted, such as prompting the existence of potential risks and requiring processing within 24 hours.

[0096] See Figure 3 , which is a schematic diagram of the principle of hierarchical processing of files to be reviewed in a specific implementation. For sub-files to be reviewed at the third risk level, since the risk level is the highest, the treatment measure of immediately terminating the design process can be taken. For sub-files to be reviewed at the second risk level, since the risk level is moderate, moderate treatment measures can be taken, such as prompting potential risks and requiring 24-hour processing. For sub-files to be reviewed at the first risk level, since the risk level is low, more moderate treatment measures can be taken, such as recommending optimization and prompting staff to include pins in the sub-file to be reviewed in subsequent version iterations.

[0097] In a specific embodiment of the present invention, the pins in the to-be-reviewed file are divided into risk levels according to the differences in the pins, and the resulting multiple to-be-reviewed sub-files may specifically include:

[0098] According to the differences in the pins, based on the preset classification rules, the pins in the review file are divided into risk levels to obtain multiple sub-files to be reviewed;

[0099] The division rules include:

[0100] For any pin with a difference, when the difference of the pin meets any difference situation in the preset specific difference situation set, the risk level of the pin is determined to be the third risk level;

[0101] For any pin with a difference, when the difference of the pin does not meet the specific difference condition set, and only two items of the pin-related information of the pin are different in the first file and the second file, the risk level of the pin is determined to be the first risk level;

[0102] For any pin with differences, when the pin difference does not conform to the specific difference condition set and two or more items of the pin association information of the pin are different in the first file and the second file, the risk level of the pin is determined to be the second risk level.

[0103] In this implementation, the pins in the review document can be effectively classified into risk levels based on their differences. Specifically, when a pin's difference meets any of the preset specific difference conditions, it indicates that the pin's difference is not common, or that the pin's difference is often caused by incorrect modification, requiring staff to conduct a focused review. Therefore, in this implementation, such a pin will be determined to have the highest risk level, i.e., the third risk level described in this implementation.

[0104] In addition, it can be understood that the preset specific difference situations are concentrated, and the specific differences included can be set and adjusted according to actual needs, but they should be uncommon, or the pin differences are large, or they are often caused by erroneous modifications.

[0105] For example, in a specific scenario, if the pin symbol of a pin and the position coordinates of the pin in the design drawing file have changed, the staff needs to focus on reviewing whether there are any errors. In this case, such differences can be included in a specific difference set. That is, the specific difference set includes differences such as "in the first file and the second file, the pin symbol of the pin and the position coordinates of the pin in the design drawing file are different."

[0106] For example, in a specific scenario, if four or more items in a pin's pin-related information have changed, then that pin will require staff to conduct a thorough review to determine if there are any errors. This discrepancy can be included in a specific set of discrepancies. For example, if a component does not appear in the initial design file, indicating that it is a newly added component in the design file to be tested, then for any pin of that component, by comparing the first file with the second file, each item in that pin's pin-related information can be considered a difference in the pin-related information between the first and second files (e.g., there are five items in total). This pin's discrepancy then meets the pre-defined set of specific discrepancies, requiring staff to conduct a thorough review to determine if there are any errors.

[0107] In this embodiment, for any pin with a difference, if the pin's difference does not conform to the specific difference condition set, and only two items of the pin-related information for the pin differ between the first file and the second file, the pin's risk level can be determined to be the first risk level, indicating a relatively low risk. If the pin's difference does not conform to the specific difference condition set, but at least two items of the pin-related information for the pin differ between the first file and the second file, the pin's risk level can be determined to be the second risk level, indicating an appropriately increased risk level.

[0108] In a specific embodiment of the present invention, the method may further include: receiving a version check instruction for a target pin listed in a file to be reviewed, and obtaining a historical modification record for the target pin. This embodiment takes into account that when a staff member reviews a pin, he or she may need to view the historical modification record of the pin to effectively determine whether the pin is incorrectly modified, and if so, the source of the version that caused the error can be effectively located through the historical modification record. It can be seen that this embodiment can effectively assist the staff in the review work and is conducive to the discovery and handling of pin errors.

[0109] By applying the technical solution provided by the embodiments of the present invention, design files can be automatically tested, thereby effectively improving detection efficiency and reducing the probability of error. Furthermore, the scanning is achieved through a "database identifier-association information" approach, enabling pin differences to be effectively determined. Specifically, after obtaining the initial design file and the design file to be tested, the initial design file and the design file to be tested are scanned. Furthermore, using the component's unique database identifier as a classification for different components, pin association information for each pin of each component in the initial design file is obtained as a first file, and pin association information for each pin of each component in the design file to be tested is obtained as a second file. After obtaining the first and second files, a comparison can be made to identify the pins that differ between the first and second files. Furthermore, to further improve efficiency, the present invention provides that when a pin difference meets a preset ignorable rule, it indicates that the pin association information for the pin in the first and second files differs due to a normal version update, and therefore the pin can be ignored. In some cases, the pin can also be included in the ignorable file. Of course, pins in the ignorable file do not require manual verification. Conversely, if the pin does not meet the ignorable rule, the pin should be included in the pending review file, and subsequent staff can simply check the pins in the pending review file. In addition, because the present application solution can obtain the individual pins with differences through the pin association information in the first and second files, it helps reduce hidden risks and effectively improves the comprehensiveness of problem discovery.

[0110] In summary, the present application solution can effectively complete the detection of design drawing files, improve detection efficiency, reduce the probability of error, and improve the comprehensiveness of problem discovery.

[0111] Corresponding to the above method embodiment, the present invention also provides a system for detecting design drawing files, which can be referenced in conjunction with the above.

[0112] See Figure 4 , is a schematic structural diagram of a design drawing file detection system in the present invention, comprising:

[0113] The design file acquisition module 401 is used to acquire an initial design file for representing the connection relationship between components, and a design file to be tested obtained after the initial design file is updated;

[0114] Scanning module 402 is configured to scan the initial design file and the design file to be tested, using the unique database identifier of the component as a classification of different components, obtain pin association information for each pin of each component in the initial design file as a first file, and obtain pin association information for each pin of each component in the design file to be tested as a second file;

[0115] A comparison module 403 is configured to compare the first file and the second file to obtain pins having differences;

[0116] The filtering module 404 is used to determine whether the difference of any pin with a difference meets the preset ignorable rule; if not, the pending review module 405 is triggered;

[0117] The pending review module 405 is used to list the pins in the pending review file.

[0118] In a specific embodiment of the present invention, the pin association information of the pin includes the pin symbol of the pin, and also includes one or more of the pin's material attributes, position coordinates in the design file, packaging parameters, and connection relationships.

[0119] In a specific embodiment of the present invention, the filtering module 404 is specifically used to:

[0120] For any pin with differences, when only a single item of the pin-related information of the pin is different in the first file and the second file, it is determined that the difference of the pin meets the preset ignorable rule.

[0121] In a specific embodiment of the present invention, a material attribute mass change alarm module is further included, which is used to:

[0122] When the pin difference meets the preset ignorable rules, the pin is included in the ignorable file;

[0123] Determine the ratio of pins of the target type to the total number of pins in the ignorable file;

[0124] If the proportion is higher than the first threshold, an alarm file including pins of all target types is generated and the alarm file is pushed;

[0125] Among them, the pins of the target type in the file can be ignored, which means that the pin-related information of the pins in the first file and the second file is different only in the material attribute.

[0126] In a specific embodiment of the present invention, a risk level classification submodule is further included, which is used to:

[0127] According to the differences in the pins, the risk levels of the pins in the to-be-reviewed file are divided to obtain a plurality of to-be-reviewed sub-files.

[0128] In a specific embodiment of the present invention, the risk level classification submodule is specifically used to:

[0129] According to the differences in the pins, based on the preset classification rules, the pins in the review file are divided into risk levels to obtain multiple sub-files to be reviewed;

[0130] The division rules include:

[0131] For any pin with a difference, when the difference of the pin meets any difference situation in the preset specific difference situation set, the risk level of the pin is determined to be the third risk level;

[0132] For any pin with a difference, when the difference of the pin does not meet the specific difference condition set, and only two items of the pin-related information of the pin are different in the first file and the second file, the risk level of the pin is determined to be the first risk level;

[0133] For any pin with differences, when the pin difference does not conform to the specific difference condition set and two or more items of the pin association information of the pin are different in the first file and the second file, the risk level of the pin is determined to be the second risk level.

[0134] In a specific embodiment of the present invention, a hierarchical processing module is further included for:

[0135] For different sub-files to be reviewed, corresponding processing measures are executed according to the preset processing rules.

[0136] Corresponding to the above method and system embodiments, embodiments of the present invention further provide a design drawing file detection device, a computer-readable storage medium, and a computer program product, which can be referenced in correspondence with the above.

[0137] See also Figure 5 As shown, the device may include:

[0138] Memory 501, used for storing computer programs;

[0139] The processor 502 is configured to execute a computer program to implement the steps of the method for detecting a design drawing file in any of the above embodiments.

[0140] The computer program product includes a computer program / instruction, which, when executed by a processor, implements the steps of the method for detecting a design drawing file in any of the above embodiments.

[0141] See Figure 6 The computer-readable storage medium 60 stores a computer program 61. When executed by a processor, the computer program 61 implements the steps of the method for detecting a design file in any of the above-described embodiments. The computer-readable storage medium 60 herein includes RAM (Random Access Memory), internal memory, ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), registers, a hard disk, a removable disk, or any other form of storage medium known in the art.

[0142] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0143] This document uses specific examples to illustrate the principles and implementation methods of this application. The description of the above examples is only intended to help understand the method and core ideas of this application. It should be noted that for those skilled in the art, without departing from the principles of this application, various improvements and modifications can be made to this application, and such improvements and modifications also fall within the scope of protection of this application.

Claims

1. A method for detecting a design drawing file, characterized in that: include: Acquire an initial design drawing file for representing component connection relationships, and a design drawing file to be tested obtained after the initial design drawing file is updated; By scanning the initial design file and the design file to be tested, using the unique database identifier of the component as a division of different components, pin association information of each pin of each component in the initial design file is obtained as a first file, and pin association information of each pin of each component in the design file to be tested is obtained as a second file; Comparing the first file and the second file to obtain pins having differences; For any pin with a difference, determine whether the difference of the pin meets the preset ignorable rule; If not, the pin is listed in the file for review.

2. The method for detecting design drawing files according to claim 1, characterized in that: The pin association information of a pin includes the pin symbol of the pin, and also includes one or more of the material attributes of the pin, the position coordinates of the pin in the design drawing file, the packaging parameters, and the connection relationship.

3. The method for detecting design drawing files according to claim 1, characterized in that: For any pin with a difference, determining whether the difference of the pin meets the preset ignorable rule includes: For any pin with differences, when only a single item of the pin association information of the pin is different in the first file and the second file, it is determined that the difference of the pin meets the preset ignorable rule.

4. The method for detecting design drawing files according to claim 3, characterized in that: Also includes: When the difference of the pins meets the preset ignorable rule, the pins are listed in the ignorable file; Determine the proportion of pins of the target type in the total number of pins in the ignorable file; If the proportion is higher than a first threshold, generating an alarm file including pins of all target types and pushing the alarm file; The pins of the target type in the ignorable file indicate that the pin-related information of the pins in the first file and the second file differs only in material attributes.

5. The method for detecting a design drawing file according to any one of claims 1 to 4, characterized in that: Also includes: According to the differences in the pins, the pins in the file to be reviewed are divided into risk levels to obtain a plurality of sub-files to be reviewed.

6. The method for detecting design drawing files according to claim 5, characterized in that: According to the differences in the pins, the pins in the file to be reviewed are divided into risk levels to obtain multiple sub-files to be reviewed, including: According to the differences in the pins, based on the preset classification rules, the pins in the file to be reviewed are classified into risk levels to obtain a plurality of sub-files to be reviewed; The division rules include: For any pin with a difference, when the difference of the pin meets any difference situation in a preset specific difference situation set, the risk level of the pin is determined to be the third risk level; For any pin with a difference, when the difference of the pin does not conform to the specific difference condition set, and only two items of the pin-related information of the pin differ between the first file and the second file, the risk level of the pin is determined to be the first risk level; For any pin with a difference, when the difference of the pin does not conform to the specific difference set, and there are two or more contents of the pin association information of the pin different in the first file and the second file, the risk level of the pin is determined to be the second risk level.

7. The method for detecting a design drawing file according to claim 6, wherein: Also includes: For different sub-files to be reviewed, corresponding processing measures are executed according to preset processing rules.

8. A design drawing file detection system, characterized in that: include: A design drawing file acquisition module, used to acquire an initial design drawing file for representing the connection relationship of components, and a design drawing file to be tested obtained after the initial design drawing file is updated; a scanning module configured to scan the initial design file and the design file to be tested, using the unique database identifier of the component as a division of different components, obtain pin association information for each pin of each component in the initial design file as a first file, and obtain pin association information for each pin of each component in the design file to be tested as a second file; A comparison module, configured to compare the first file and the second file to obtain pins having differences; A filtering module is used to determine, for any pin with a difference, whether the difference of the pin meets the preset ignorable rule; if not, trigger the pending review module; The module to be reviewed is used to list the pins in the file to be reviewed.

9. A device for detecting design drawing files, characterized in that: include: memory for storing computer programs; A processor, configured to execute the computer program to implement the steps of the method for detecting a design drawing file as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the method for detecting a design drawing file according to any one of claims 1 to 7.

Images