Three-dimensional design collision inspection report generation method and device, electronic equipment and medium

Abstract

The invention discloses a three-dimensional design collision check report generation method and device, electronic equipment and a medium, relates to the technical field of three-dimensional modeling design and application, and aims to automatically generate a report file with a model screenshot, so that a designer can visually see a collision position and can visually see the severity of collision, and the design efficiency is improved. Collision details do not need to be verified by manually executing a large amount of repeated work, and the efficiency and accuracy of three-dimensional design are improved. The method comprises the steps of obtaining collision inspection parameters in response to a collision inspection request, and determining a plurality of to-be-inspected models; according to the collision inspection parameters, performing collision inspection on the plurality of to-be-inspected models, and determining at least one collision position point where collision occurs in the plurality of to-be-inspected models; and intercepting a model three-dimensional view related to each collision position point, and generating and outputting a collision check report based on the model three-dimensional view related to each collision position point.

Description

Technical Field

[0001] This application relates to the field of 3D modeling design and application technology, and in particular to a method, device, electronic device and medium for generating 3D design collision check reports. Background Technology

[0002] In the field of 3D modeling and design technology, especially in the 3D modeling and design of large-scale engineering projects such as factories, buildings, and ships, a large number of designers from different professional fields (such as structural engineers, piping engineers, and electrical engineers) use 3D modeling software (such as AVEVA PDMS and AVEVA Everything3D) for collaborative design. This collaborative design method greatly improves design efficiency, but it also brings a key problem: collision interference between different professional models. If collision interference problems are not detected and handled in time during the design phase, they often cause serious problems in the subsequent construction, installation, and even operation phases, such as collisions between pipes and structural beams, and interference between electrical lines and equipment. These problems not only lead to design changes and increased costs, but may also affect the project schedule and even cause safety hazards. Therefore, collision detection is required when each sub-model design is completed to ensure spatial compatibility between different professional models.

[0003] In related technologies, due to the massive amount of data in 3D design models and the involvement of multiple professional fields, it is necessary to conduct regular, comprehensive multi-disciplinary collision detection across the entire area to meet the needs of project-level multi-disciplinary collaborative design management, and generate detection reports archived in spreadsheet format. However, the applicant recognizes that the detection reports only contain basic collision information described in text. After receiving the detection reports, relevant designers still need to continuously compare and query the 3D models in PDMS / E3D (Plant Design Management System / AVEVAEverything3D) to determine whether the collisions actually exist and further confirm their specific locations and severity. This process involves a large amount of repetitive work, such as frequently querying the 3D model, manually recording collision information, and sending and receiving collision reports. This is not only time-consuming and labor-intensive, but also prone to inaccurate information transmission or untimely processing due to human factors, affecting the efficiency and accuracy of 3D design. Summary of the Invention

[0004] In view of this, this application provides a method, apparatus, electronic device, and medium for generating 3D design collision inspection reports. The main purpose is to solve the problem that currently, after receiving a collision inspection report, designers still need to continuously compare and consult the 3D model in PDMS / E3D to determine whether a collision actually exists and to further confirm the specific location and severity of the collision. This process involves a large amount of repetitive work, such as frequently querying the 3D model, manually recording collision information, and sending and receiving collision reports. This is not only time-consuming and labor-intensive but also prone to inaccurate information transmission or untimely processing due to human factors, affecting the efficiency and accuracy of 3D design.

[0005] According to a first aspect of this application, a method for generating a 3D design collision check report is provided, the method comprising:

[0006] In response to a collision check request, obtain collision check parameters and identify multiple models to be checked;

[0007] Based on the collision check parameters, a collision check is performed on the plurality of models to be checked, and at least one collision location point is determined among the plurality of models to be checked.

[0008] Extract the 3D model view associated with each collision location point, and generate and output a collision inspection report based on the 3D model view associated with each collision location point.

[0009] According to a second aspect of this application, a three-dimensional design collision inspection report generation apparatus is provided, the apparatus comprising:

[0010] The determination module is used to respond to collision check requests, obtain collision check parameters, and determine multiple models to be checked;

[0011] The inspection module is used to perform collision checks on the plurality of models to be inspected according to the collision inspection parameters, and to determine at least one collision location point among the plurality of models to be inspected.

[0012] The generation module is used to capture the 3D view of the model associated with each collision location point, and to generate and output a collision inspection report based on the 3D view of the model associated with each collision location point.

[0013] According to a third aspect of this application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described in any of the first aspects above.

[0014] According to a fourth aspect of this application, a computer-readable storage medium is provided, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of the first aspects above.

[0015] By utilizing the above technical solutions, this application provides a method, apparatus, electronic device, and medium for generating a 3D design collision check report. Responding to a collision check request, this application obtains collision check parameters, determines multiple models to be checked, performs collision checks on the multiple models based on the collision check parameters, identifies at least one collision location point among the multiple models, captures a 3D view of the model related to each collision location point, and generates and outputs a collision check report based on the 3D view of the model related to each collision location point. This automatically generates a report file with model screenshots, allowing designers to intuitively see the location and severity of the collision. It eliminates the need for manually performing a large amount of repetitive work to verify collision details, saving significant manpower and avoiding inaccurate information transmission or untimely processing due to human factors, thereby improving the efficiency and accuracy of 3D design.

[0016] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0017] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0018] Figure 1 This illustration shows a flowchart of a method for generating a 3D design collision check report according to an embodiment of this application.

[0019] Figure 2A This illustration shows a schematic flowchart of another method for generating a 3D design collision check report provided in an embodiment of this application;

[0020] Figure 2B This illustration shows a schematic flowchart of another method for generating a 3D design collision check report provided in an embodiment of this application;

[0021] Figure 3 This illustration shows a structural schematic diagram of a three-dimensional design collision inspection report generation device provided in an embodiment of this application;

[0022] Figure 4 A schematic diagram of the device structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0023] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0024] This application provides a method for generating a 3D design collision check report, such as... Figure 1 As shown, the method includes:

[0025] 101. In response to a collision check request, obtain collision check parameters and identify multiple models to be checked.

[0026] The technical solution of this application embodiment can be applied to a collision checking tool. This tool is based on AVEVA Everything 3D (E3D) and AVEVA PDMS software, and is a tool developed using PML.NET (Plant Design Management System Programming Language for .NET). It aims to provide designers with an efficient and convenient collision checking solution. The underlying logic of the collision checking tool revolves closely around PDMS / E3D model data and is deeply integrated into the software environment through a plug-in, achieving seamless integration with native functions. At the operational level, designers can easily retrieve various pre-set collision checking rules and quickly apply them to the corresponding 3D models. The rules set by designers can be flexibly saved as different configurations for easy switching and calling in different project scenarios. Furthermore, the generation and post-processing of collision checking data are automatically completed by the collision checking tool's backend, eliminating the need for designers to manually intervene in tedious data processing steps.

[0027] The core principle of collision detection tools lies in the deep analysis and processing of PDMS / E3D model data. During collision checks, it can perform comprehensive and detailed collision detection on multi-disciplinary models according to predefined rules. During the check, the tool accurately records key information such as collision location, related model name, relevant discipline, responsible personnel, and collision parameters. Simultaneously, using graphics processing technology, it automatically captures 3D views of the models related to the collision location and saves them as images. When taking screenshots, the tool intelligently calculates the camera position and gaze center position, ensuring that the model screenshot clearly shows the collision situation and avoids model occlusion, providing intuitive visual evidence for subsequent report generation. Furthermore, the tool can automatically generate report files in both Microsoft Excel and HTML (HyperText Markup Language) webpage formats. Excel reports facilitate data statistics and analysis, while HTML webpage reports present collision information in a graphical format, including detailed text descriptions and clear model screenshots, allowing relevant personnel to quickly understand the complete information about the collision location simply by viewing the report file. Furthermore, the collision detection tool also features a feedback function. Through the built-in message function of E3D / PDMS, it promptly sends notifications to personnel involved in the collision model, ensuring that issues are addressed in a timely manner. These functions significantly reduce the amount of work designers need to do by querying and retrieving E3D / PDMS models, substantially improving collision handling efficiency and providing strong support for project design and implementation.

[0028] A collision check request is a key instruction to initiate the 3D design collision check report generation process. It can be initiated by designers (hereinafter, users include designers with collision check requirements), such as by clicking the "Clash Check" button on the interface provided by the collision check tool, or it can be automatically triggered by the collision check tool based on preset rules, such as automatically executing after a specific design stage is completed.

[0029] After receiving a collision check request, the collision check tool will display a parameter setting window. Designers can enter or select collision check parameters in this window. These parameters are core elements controlling the collision check process, such as overlap distance, contact gap, and proximity distance values ​​for collision determination. After acquiring these parameters, the collision check tool will continue to read relevant model files to be checked from the database. These model files can be stored in a specific format, and the collision check tool calls the model loading module to load them into memory, thus identifying multiple models to be checked for subsequent processing. These models are various solid models in 3D design, such as walls, doors, and windows in architecture, and parts in mechanical design. They collectively constitute the whole to be checked. Thus, by acquiring the collision check parameters and the models to be checked, a clear direction and necessary data foundation are provided for the collision check, making the collision check more targeted and efficient.

[0030] 102. Based on the collision check parameters, perform collision checks on multiple models to be checked, and determine at least one collision location point among the multiple models to be checked.

[0031] In this embodiment, the collision checking tool performs collision checks on multiple models to be checked based on collision checking parameters, and determines at least one collision location point among the multiple models to be checked. Specifically, collision checking is a process in which the collision checking tool uses computer algorithms to analyze the spatial relationships of multiple models to be checked loaded into memory. During the checking process, the collision checking tool determines in real time whether there is a collision between the models.

[0032] When a collision detection tool detects spatial overlap or interference between models, it records the specific spatial coordinates of the collision, known as the collision location. This collision location is crucial for generating subsequent reports. For example, in mechanical design, if a collision detection tool finds that a gear model collides with another shaft model at a specific coordinate point, it will record that coordinate point as the collision location. Through precise collision detection algorithms and parameter settings, the collision location between models can be accurately identified, providing key data for generating detailed collision detection reports. This allows designers to clearly understand the specific location of the collision, providing a basis for further design optimization.

[0033] 103. Extract the 3D model view associated with each collision point, and generate and output a collision check report based on the 3D model view associated with each collision point.

[0034] In this embodiment, the collision detection tool captures a 3D model view associated with each collision location point, and generates and outputs a collision detection report based on this view. Capturing the 3D model view associated with each collision location point is to visually demonstrate the specific circumstances of the collision. The collision detection tool extracts the model portion surrounding the recorded collision location point from the loaded model and generates a 3D view. For example, for a previously discovered collision location point between a gear and a shaft, the collision detection tool captures a portion of the model containing the collision point, generates a 3D view, and displays the details of the collision area from different angles.

[0035] Next, based on the captured 3D view, the collision detection tool generates a collision detection report. The report may include the coordinates of the collision points, the names of the involved models, an assessment of the collision severity (quantified based on indicators such as collision area and depth), and the captured 3D view. After the report is generated, the collision detection tool outputs it to a specified location, such as the designer's local folder or a specific area within the project management collision detection tool. The report can be output in PDF or HTML format for easy viewing and sharing by designers. In this way, by capturing the 3D view and generating the report, designers can intuitively see the collision location and severity, eliminating the need for extensive manual repetitive work to verify collision details. This not only saves significant manpower but also avoids inaccurate information transmission or delayed processing due to human factors, greatly improving the efficiency and accuracy of 3D design. For example, in architectural design, designers can quickly understand the collision situation by viewing the 3D view in the report, adjust the design scheme in a timely manner, and ensure smooth construction.

[0036] The method provided in this application, in response to a collision check request, obtains collision check parameters, determines multiple models to be checked, performs collision checks on the multiple models to be checked based on the collision check parameters, determines at least one collision location point among the multiple models to be checked, captures a 3D view of the model associated with each collision location point, and generates and outputs a collision check report based on the 3D view of the model associated with each collision location point. This automatically generates a report file with model screenshots, allowing designers to intuitively see the location of the collision and the severity of the collision. It eliminates the need for manually performing a large amount of repetitive work to verify collision details, saving significant manpower and avoiding inaccurate information transmission or untimely processing due to human factors, thereby improving the efficiency and accuracy of 3D design.

[0037] Furthermore, as a refinement and extension of the specific implementation methods of the above embodiments, and to fully illustrate the specific implementation process of this embodiment, this application provides another method for generating a three-dimensional design collision check report, such as... Figure 2AAs shown, the method includes:

[0038] 201. Set collision check parameters according to user operations.

[0039] The technical solution of this application embodiment can be applied to collision inspection tools. For a detailed description of the collision inspection tool, please refer to the description of the collision inspection tool in step 101 of the above embodiment, which will not be repeated here.

[0040] In the 3D design clash detection workflow, setting clash detection parameters is a crucial initial step. When a user initiates a parameter setting request, the clash detection tool responds and determines the selected parameter setting mode. These modes are divided into two types: a collision detection list mode and an exclusion list mode. The collision detection list mode specifies the models or parts of a model that require clash detection, while the exclusion list mode excludes models or parts of a model from the clash detection scope, providing users with flexible options. For example, when designing a large building project, a user might only want to check for clashes between the building structure model and the MEP (Mechanical, Electrical, and Piping) model. In this case, the collision detection list mode can be selected to include only these two models in the collision detection list. In practical applications, users can also simultaneously set both the collision target list and the exclusion list to further clarify the parts that need clash detection.

[0041] Next, the collision detection tool retrieves the collision detection parameters uploaded by the user, which can include overlap distance, contact gap, and proximity distance values ​​used to determine collisions. Retrieving these parameters supports multiple methods, such as text input, table pasting, or importing from the tool's native list (e.g., using PDMS / E3D). The collision detection tool then organizes the collision detection parameters according to the user-selected parameter setting mode, generates a parameter configuration file, obtains the filename entered by the user, names the configuration file, and stores it. It's worth noting that different collision settings can be saved as separately named configuration files, allowing users to quickly select and adjust settings via dropdown lists.

[0042] Through the above process, users are provided with diverse parameter setting methods to meet the needs of different users in different scenarios. Moreover, by saving reusable configurations, the efficiency of parameter setting is greatly improved, avoiding the tedious work of resetting parameters for each test. For example, in a mechanical design project, after designers set and save the collision check parameters once, they only need to select the corresponding configuration from the drop-down list when performing collision checks periodically, saving a lot of time and effort.

[0043] 202. In response to the collision check request, obtain the collision check parameters and determine multiple models to be checked.

[0044] In this embodiment of the application, when the collision checking tool receives a collision checking request, in response to the request, the collision checking tool will determine the target file name carried in the collision request, query the target parameter configuration file named after the target file name, and read the collision checking parameters in the target parameter configuration file to prepare for subsequent multi-discipline model collision checks.

[0045] Next, the collision detection tool will obtain the list of models to be checked imported by the user based on the collision detection request, and will treat the multiple 3D design models included in the request as multiple models to be checked. Users can import the list of models to be checked based on the collision detection request, either through a text document or the collision detection tool's query interface. The query interface can be the native PDMS / E3D query interface. For example, in an industrial plant design project, designers might import a list containing multiple professional models such as building structures, equipment, and piping through a text document; the collision detection tool will then treat these models as models to be checked. This interface allows users focused on the currently designed model to perform quick checks, while users needing to perform batch checks on multiple models across the entire project can use the list to perform collision detection on a batch of models, meeting the diverse inspection needs of users in different work scenarios.

[0046] 203. Based on the collision check parameters, perform collision checks on multiple models to be checked, and determine at least one collision location point among the multiple models to be checked.

[0047] When the target parameter setting mode is the collision list mode, based on the collision detection parameters, multiple target regions to be collision detected are determined on multiple models to be inspected, collision detection is performed on multiple target regions, and at least one collision location point is determined in multiple target regions.

[0048] When the target parameter setting mode is the exclusion list mode, based on the collision detection parameters, at least one specified region to be excluded is determined on multiple models to be inspected, and multiple other regions other than the at least one specified region are determined on multiple models to be inspected. Collision detection is performed on the multiple other regions, and at least one collision location point where a collision occurs is determined in the multiple other regions.

[0049] As mentioned in step 201 above, users can set parameters using different parameter setting modes. Different collision check processes are required for different modes. Therefore, in this embodiment, when a collision check is needed, the collision check tool queries the target parameter setting mode indicated in the target parameter configuration file. When the target parameter setting mode is the collision list mode, the collision check tool determines multiple target areas to be collided with on multiple models to be checked based on the collision detection parameters, performs collision detection on these target areas, and thus determines at least one collision location. For example, in a bridge design project, the collision check tool, based on the collision list mode, determines the main bridge structure and piers as target areas to be collided with, performs collision checks on these areas, and finds that the main bridge structure and the pier collided at a certain location.

[0050] When the target parameter setting mode is set to exclusion list mode, the collision checking tool will determine at least one specified area to be excluded on multiple models to be checked based on the collision detection parameters. Then, it will perform collision checks on multiple other areas besides the specified areas to determine at least one collision location. For example, in a building decoration project, some decorative areas that have been determined not to collide are listed in the exclusion list, and collision checks are performed on the remaining areas to find possible collision locations.

[0051] In this way, the collision checking tool can perform targeted collision checks on the model based on different parameter settings, improving the accuracy and efficiency of the checks. At the same time, by differentiating different checking modes, it can meet the needs of different design stages and different users. For example, in the early stages of design, the exclusion list mode may be used to exclude some obviously non-collision areas, narrowing the scope of the checks and increasing the speed of the checks. In the later stages of design, the collision list mode is used to conduct detailed checks on key areas to ensure the accuracy of the design.

[0052] 204. Generate an inspection record list and output the inspection record requests.

[0053] In this embodiment, after completing the collision check, the collision check tool generates a list of inspection records and outputs the inspection record requests. Specifically, when generating the list of inspection records, the collision check tool generates a collision check record for each collision location, resulting in at least one collision check record. The record content includes the model name of the model to be inspected to which the collision location belongs, the coordinates of the collision location, and the collision type. For example, in a mechanical assembly project, for a collision between one part and another part at a specific coordinate point, the record will clearly specify the names of the two parts, the collision location coordinates, and the collision type (such as interference, insufficient clearance, etc.).

[0054] After generating a list of inspection records including at least one collision check record, the collision check tool will output and display the inspection record requests. If the collision check tool is developed using E3D / PDMS software, the collision check results can be viewed within E3D / PDMS in a manner similar to filtering keywords in an Excel spreadsheet. That is, when a user wants to filter, they can initiate a record filtering request. In response, the collision check tool will retrieve the keywords carried in the request, extract at least one target collision check record containing the keyword from the inspection record list, and display that target collision check record. For example, if a user wants to view all collision records related to "pipe," they only need to enter "pipe" as the keyword, and the collision check tool will filter and display the relevant records.

[0055] Meanwhile, the collision detection tool also supports quickly locating and marking relevant model positions by clicking on records. Specifically, when a specific collision detection record in the check record list is triggered, the tool reads the specified model name, coordinates of a specified location point, and specified collision type from the record. It then identifies the specified model from among multiple models to be checked, determines the specified collision location point on that model according to the specified location point coordinates, marks the collision location point, and annotates the specified collision type at the marked location, displaying the marked model. This marking and annotation function allows users to intuitively see the collision location and type, quickly locating problems. Furthermore, the record filtering function further improves the efficiency of viewing records, enabling users to quickly find the collision information they are interested in. For example, in a large architectural project, designers can use the filtering function to quickly find collision records related to a specific profession or model, allowing for timely design adjustments.

[0056] In practical applications, the collision checking tool can also construct a dedicated collision record display area within the current operating interface. This area can present all collision records in the form of a list or table. Each record contains key information, such as the name of the model to be checked to which the collision point belongs, the precise coordinates of the collision point, and the collision type (e.g., solid interference, insufficient gap, etc.). After entering this interface, all collision records are clearly visible to the user, facilitating a quick overview of the overall collision situation. This application does not limit the specific method of displaying collision records.

[0057] 205. Extract the 3D model view associated with each collision point, and generate and output a collision inspection report based on the 3D model view associated with each collision point.

[0058] In this embodiment, the collision detection tool automatically captures and saves 3D views of the model related to the collision location, and generates and outputs a collision detection report based on the 3D views of the model related to each collision location. When capturing the model, for each collision location, the collision detection tool automatically calculates the camera position and the gaze center position based on the size of the envelope box of the model of interest and the viewing direction. The envelope box is the smallest cuboid that can completely enclose the model. By analyzing the length, width, and height data of this cuboid, the collision detection tool can understand the approximate range and proportion of the model in 3D space. Simultaneously, the collision detection tool determines the viewing direction, i.e., the angle from which the user wants to observe the model. This viewing direction is usually determined by the viewing direction vector set by the user.

[0059] To calculate the camera position, the collision check tool uses the center of the model's envelope as a reference point. Depending on the view direction, the tool extends outwards along that direction vector by a certain distance. This distance is determined by considering both the size of the envelope and the desired view scaling. If the envelope is large, the tool increases the extension distance to ensure the model appears complete and not too small in the view; conversely, if the envelope is small, the tool decreases the extension distance to ensure the model appears clear and not too large. In this way, the collision check tool ensures the model is scaled appropriately in the view—neither too close, causing the model to appear too large and exceed the view's range, nor too far, causing the model to appear too small and obscure details.

[0060] When determining the gaze center, the collision detection tool directly uses the center of the model's envelope as the gaze center. This is because the center of the envelope represents the model's overall position in 3D space, and focusing the camera on this point ensures that the model is centered in the view, making it easier for the user to observe.

[0061] Next, the collision detection tool adjusts the size of the model to be captured, referencing the camera position and the gaze center, to minimize model occlusion. It then captures the area of ​​the adjusted model related to the collision location, creating a 3D view of the model corresponding to the collision location. This ensures the model is appropriately scaled and occlusion is minimized. For example, if the model has a protruding part in a certain direction, the collision detection tool may adjust the camera position to prevent this protrusion from completely obscuring other important parts of the model, ensuring the user can see the complete model information in the view. Through these calculations and adjustments, the collision detection tool generates high-quality model screenshots, providing users with a clear and accurate view of the collision location.

[0062] After obtaining the 3D view of the model associated with each collision point through the above process, the collision checking tool will generate and output a collision checking report based on the model-related parameters of the model to be checked corresponding to each model's 3D view. These model-related parameters include the model name, the model's specialty, and the model creator's information. The report format can include Excel and HTML. Excel collision reports can be exported and viewed, while HTML reports, in addition to including the collision model name, specialty, and personnel information, can also display corresponding model screenshots.

[0063] Furthermore, to ensure smooth operation and efficient resource utilization, the collision checking tool can incorporate built-in interruption conditions for collision check execution and report generation. This allows the tool to continuously monitor the response status of E3D / PDMS during large-scale data queries and report generation tasks. Specifically, the tool sets a response time threshold. If no valid feedback is received from E3D / PDMS within the specified time after initiating a collision check or report generation request, it is considered unresponsive. Upon detecting unresponsiveness, the tool immediately triggers the shutdown of the main interface, forcibly terminating the ongoing collision check or report generation process. Simultaneously, the tool revokes the user's current software operation permissions to prevent other operations from being disrupted due to abnormal resource consumption by the process, ensuring the stability and security of the software environment.

[0064] In addition to the automatic interruption mechanism based on unresponsive states, the collision checking tool also supports user-defined interruption conditions. Users can set specific interruption conditions in the collision checking tool according to their actual needs, such as setting a maximum running time or triggering specific error codes. During the collision checking process or the collision checking report generation process, the collision checking tool monitors various operational metrics and events in real time. Once an abnormal event is detected that matches the user-defined interruption conditions, the collision checking tool will quickly interrupt the corresponding process. For example, if the user sets the maximum running time to 2 hours, the collision checking tool will automatically interrupt the process if it runs for more than 2 hours without completion. After the process is interrupted, the collision checking tool will display a process interruption notification on the software interface, informing the user that the process has been interrupted and the reason for the interruption, allowing the user to understand the situation promptly and take appropriate measures.

[0065] Furthermore, to improve the timeliness and accuracy of information delivery, the collision checking tool can fully utilize the built-in message function of E3D / PDMS. After the collision check report is generated, it automatically generates a collision completion reminder message. This message not only includes a notification that the report has been completed but can also include a summary of key report information, such as the number of collisions and their severity. The collision checking tool will precisely push the collision completion reminder to the user-pre-defined reminder recipients, such as designers, project managers, and other personnel related to the collision model, including their email addresses and phone numbers. In this way, relevant personnel can be informed of the collision check results in a timely manner without having to actively search for them, greatly improving work efficiency and communication effectiveness, and ensuring that the project can be adjusted and optimized promptly based on the collision check results.

[0066] In summary, the logical process of the technical solution in this application is summarized as follows: See Figure 2B Users set collision parameters, and the relevant settings are stored in the configuration file by the collision checking tool. Next, the collision checking tool enters the collision checking phase, which can perform collision checks on a single model or a batch of models. After completing the collision check, the tool proceeds to the collision result processing step. During this process, it generates an Excel file and takes screenshots of the models, generating HTML files based on the screenshots to comprehensively present the relevant collision checking information and results.

[0067] The method provided in this application automatically generates a report file with model screenshots, allowing designers to intuitively see the location of the collision and the severity of the collision. This eliminates the need to manually perform a large amount of repetitive work to verify the collision details, saving a significant amount of manpower and avoiding inaccurate information transmission or untimely processing due to human factors, thereby improving the efficiency and accuracy of 3D design.

[0068] Furthermore, as Figure 1 To specifically implement the method, this application provides a three-dimensional design collision check report generation device, such as... Figure 3 As shown, the device includes: a determining module 301, an checking module 302, and a generating module 303.

[0069] The determining module 301 is used to obtain collision check parameters and determine multiple models to be checked in response to a collision check request;

[0070] The inspection module 302 is used to perform collision checks on the plurality of models to be inspected according to the collision inspection parameters, and to determine at least one collision location point in the plurality of models to be inspected.

[0071] The generation module 303 is used to capture the three-dimensional view of the model associated with each of the collision locations, and to generate and output a collision inspection report based on the three-dimensional view of the model associated with each of the collision locations.

[0072] In specific application scenarios, the device also includes:

[0073] The settings module is used to respond to parameter setting requests, determine the parameter setting mode selected by the user, wherein the parameter setting mode is either a collision list mode or an exclusion list mode; obtain the collision detection parameters to be set uploaded by the user, wherein the collision detection parameters to be set are uploaded by text input, table pasting, or tool native list import; organize the collision detection parameters to be set according to the parameter setting mode selected by the user to obtain a parameter configuration file; obtain the file name input by the user, name the parameter configuration file with the file name, and store the named parameter configuration file.

[0074] In a specific application scenario, the determining module 301 is used to determine the target file name carried in the collision check request when the collision check request is received, and to query the target parameter configuration file named after the target file name, and read the collision check parameters in the target parameter configuration file; to obtain the list of models to be checked imported by the user based on the collision check request, and to use the multiple 3D design models included in the request as the multiple models to be checked, wherein the list of models to be checked is imported through a text document or a collision check tool query interface.

[0075] In a specific application scenario, the determining module 301 is used to query the target parameter setting mode indicated by the target parameter configuration file; when the target parameter setting mode is the collision list mode, based on the collision detection parameters, multiple target regions to be collision detected are determined on the multiple models to be inspected, collision detection is performed on the multiple target regions, and at least one collision location point where a collision occurs is determined in the multiple target regions; when the target parameter setting mode is the exclusion list mode, based on the collision detection parameters, at least one designated region to be excluded is determined on the multiple models to be inspected, and multiple other regions other than the at least one designated region are determined on the multiple models to be inspected, collision detection is performed on the multiple other regions, and at least one collision location point where a collision occurs is determined in the multiple other regions.

[0076] In specific application scenarios, the generation module 303 is also used to generate a collision check record for each collision location point, obtaining at least one collision check record. The collision check record corresponding to each collision location point includes the model name of the model to be checked to which the collision location point belongs, the location coordinates of the collision location point, and the collision type of the collision location point; generate a check record list including the at least one collision check record, and output and display the check record request.

[0077] Accordingly, the generation module 303 is further configured to, when a specified collision check record included in the check record list is detected to be triggered, read a specified model name, specified location point coordinates, and specified collision type from the specified collision check record; determine the specified model to be checked indicated by the specified model name among the plurality of models to be checked; determine a specified collision location point on the specified model to be checked according to the specified location point coordinates; mark the specified collision location point on the specified model to be checked; and mark the specified collision type at the marked position, and display the marked specified model to be checked; and / or, in response to a record filtering request, obtain the keywords carried by the record filtering request; extract at least one target collision check record including the keywords from the check record list; and display the at least one target collision check record.

[0078] In a specific application scenario, the generation module 303 is used to perform the following processing on each of the collision location points: taking the model to be inspected to which the collision location point belongs as the model to be screenshotted; calculating the camera position point and the gaze center position point according to the envelope box size and viewing direction of the model to be screenshotted; adjusting the model size of the model to be screenshotted with reference to the camera position point and the gaze center position point; and taking a screenshot of the area related to the collision location point on the adjusted model to be screenshotted to obtain a 3D view of the model related to the collision location point; obtaining the 3D view of the model related to each of the collision location points; and generating and outputting the collision inspection report according to the model-related parameters of the model to be inspected corresponding to each 3D view of the model, wherein the model-related parameters include the model name, the major to which the model belongs, and the model creator information.

[0079] In specific application scenarios, the device also includes:

[0080] The reminder module is used to receive interruption conditions set by the user, and when an abnormal time that meets the interruption conditions is detected in the collision check process or the collision check report generation process, interrupt the collision check process or the collision check report generation process, and display a process interruption reminder; and / or, use the collision check report to generate a collision completion reminder, and push the collision completion reminder to the reminder recipient set by the user.

[0081] The device provided in this application embodiment automatically generates a report file with model screenshots, enabling designers to intuitively see the location of the collision and the severity of the collision. This eliminates the need to manually perform a large amount of repetitive work to verify the collision details, saving a significant amount of manpower and avoiding inaccurate information transmission or untimely processing due to human factors, thereby improving the efficiency and accuracy of 3D design.

[0082] It should be noted that other corresponding descriptions of the functional units involved in the three-dimensional design collision inspection report generation device provided in this application embodiment can be found in the following references. Figure 1 and Figures 2A to 2B The corresponding descriptions in [the document] will not be repeated here.

[0083] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0084] The above embodiments and the technical features in the embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0085] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

[0086] In an exemplary embodiment, see Figure 4Furthermore, an electronic device is provided, comprising a bus, a processor, a memory, and a communication interface. It may also include input / output interfaces and a display device, wherein the various functional units can communicate with each other via the bus. The memory stores a computer program, and the processor executes the program stored in the memory to perform the 3D design collision check report generation method described in the above embodiments.

[0087] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for generating a 3D design collision check report.

[0088] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented in hardware or by using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) and includes several instructions to cause an electronic device (such as a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0089] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of a preferred embodiment, and the modules or processes shown in the drawings are not necessarily essential for implementing this application.

[0090] Those skilled in the art will understand that the modules in the apparatus of the implementation scenario can be distributed within the apparatus of the implementation scenario as described, or they can be located in one or more apparatuses different from this implementation scenario, with corresponding changes. The modules of the above-described implementation scenario can be combined into one module, or they can be further divided into multiple sub-modules.

[0091] The serial numbers in this application are for descriptive purposes only and do not represent the superiority or inferiority of the implementation scenario.

[0092] The above disclosures are only a few specific implementation scenarios of this application. However, this application is not limited to these. Any variations that can be conceived by those skilled in the art should fall within the protection scope of this application.

Claims

1. A method for generating a 3D design collision check report, characterized in that, include: In response to a collision check request, obtain collision check parameters and identify multiple models to be checked; Based on the collision check parameters, a collision check is performed on the plurality of models to be checked, and at least one collision location point is determined among the plurality of models to be checked. Extract the 3D model view associated with each collision location point, and generate and output a collision inspection report based on the 3D model view associated with each collision location point.

2. The method according to claim 1, characterized in that, Before responding to a collision check request, obtaining collision check parameters, and determining multiple models to be checked, the method further includes: In response to a parameter setting request, the parameter setting mode selected by the user is determined, wherein the parameter setting mode is either a collision list mode or an exclusion list mode; Obtain the collision check parameters to be set uploaded by the user. The collision check parameters to be set are uploaded by text input, table pasting, or tool native list import. According to the parameter setting mode selected by the user, the collision detection parameters to be set are organized to obtain a parameter configuration file; Obtain the file name input by the user, name the parameter configuration file using the file name, and store the named parameter configuration file.

3. The method according to claim 1, characterized in that, In response to a collision check request, collision check parameters are obtained, and multiple models to be checked are identified, including: Upon receiving the collision check request, determine the target file name carried in the collision check request, and query the target parameter configuration file named after the target file name, and read the collision check parameters from the target parameter configuration file; Obtain the list of models to be checked imported by the user based on the collision check request, and use the multiple 3D design models included in the collision check request as the multiple models to be checked, wherein the list of models to be checked is imported through a text document or the collision check tool query interface.

4. The method according to claim 3, characterized in that, The step of performing collision checks on the plurality of models to be checked according to the collision check parameters, and determining at least one collision location point among the plurality of models to be checked, includes: Query the target parameter setting mode indicated in the target parameter configuration file; When the target parameter setting mode is the collision list mode, based on the collision detection parameters, multiple target regions to be collision detected are determined on the multiple models to be inspected, collision detection is performed on the multiple target regions, and at least one collision location point where a collision occurs is determined in the multiple target regions. When the target parameter setting mode is the exclusion list mode, based on the collision detection parameters, at least one designated area to be excluded is determined on the plurality of models to be inspected, and a plurality of other areas other than the at least one designated area are determined on the plurality of models to be inspected. Collision detection is performed on the plurality of other areas, and at least one collision location point where a collision occurs is determined in the plurality of other areas.

5. The method according to claim 1, characterized in that, After performing collision checks on the plurality of models to be checked according to the collision check parameters, and determining at least one collision location point among the plurality of models to be checked, the method further includes: A collision check record is generated for each collision location point to obtain at least one collision check record. The collision check record corresponding to each collision location point includes the model name of the model to be checked to which the collision location point belongs, the location coordinates of the collision location point, and the collision type of the collision location point. Generate a list of inspection records including the at least one collision inspection record, and output and display the inspection record request; Accordingly, the method further includes: When a specified collision check record included in the check record list is triggered, the specified model name, specified location point coordinates, and specified collision type are read from the specified collision check record. The specified model to be checked, indicated by the specified model name, is determined from the plurality of models to be checked. A specified collision location point is determined on the specified model to be checked according to the specified location point coordinates. The specified collision location point is marked on the specified model to be checked, and the specified collision type is marked at the marked location. The marked specified model to be checked is then displayed; and / or, In response to a record filtering request, the keyword carried in the record filtering request is obtained, at least one target collision check record including the keyword is extracted from the check record list, and the at least one target collision check record is displayed.

6. The method according to claim 1, characterized in that, The process of extracting the 3D model view associated with each collision location point, and generating and outputting a collision inspection report based on the 3D model view associated with each collision location point, includes: For each collision location, the following processing is performed: the model to be inspected to which the collision location belongs is taken as the model to be screenshotted; the camera position point and the gaze center position point are calculated according to the envelope box size and viewing direction of the model to be screenshotted; the model size of the model to be screenshotted is adjusted with reference to the camera position point and the gaze center position point; and the area related to the collision location point on the adjusted model to be screenshotted is screenshotted to obtain a three-dimensional view of the model related to the collision location point. Obtain a 3D view of the model associated with each collision location point. Generate and output the collision inspection report based on the model-related parameters of the model to be inspected corresponding to each 3D view of the model. The model-related parameters include the model name, the major to which the model belongs, and the model creator information.

7. The method according to claim 1, characterized in that, The method further includes: Upon receiving user-defined interruption conditions, if an abnormal time matching the interruption conditions is detected during the collision check process or the collision check report generation process, the system will interrupt the collision check process or the collision check report generation process and display a process interruption alert; and / or, The collision check report is used to generate a collision completion reminder, and the collision completion reminder is pushed to the reminder recipient set by the user.

8. A three-dimensional design collision check report generation device, characterized in that, include: The determination module is used to respond to collision check requests, obtain collision check parameters, and determine multiple models to be checked; The inspection module is used to perform collision checks on the plurality of models to be inspected according to the collision inspection parameters, and to determine at least one collision location point among the plurality of models to be inspected. The generation module is used to capture the 3D view of the model associated with each collision location point, and to generate and output a collision inspection report based on the 3D view of the model associated with each collision location point.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images