A method and system for generating project problem reports during the Revit modeling process

Abstract

The present application relates to the field of secondary development technology, and in particular to a method and system for generating a project problem report during the Revit modeling process, which uses the programming language C#, Revit API, and WPF Microsoft framework programming to realize automatic entry of problem reports, automatically captures the model problem positioning axis grid and enters it by box selection, automatically obtains the record date, can recognize the name of the imported drawing in the software and automatically enter the drawing name, can take screenshots of the model problem two-dimensional and three-dimensional models with one click, associates the automatically obtained information with the *.docx version problem report template, can export the final *.docx version problem report, and realize that the screenshot is automatically centered in the table of the *.docx version problem report, is associated and synchronized with the *.docx version problem report in the editing state, and can also import the problem report after exporting the *.docx version problem report, saving a lot of work such as text entry, image capture, and problem report organization in the project problem report, and realizing the digital management level of BIM modeling and application.

Description

Technical Field

[0001] The present application relates to the technical field of secondary development based on the programming language C#, Revit API and WPF Microsoft framework, and in particular to a method and system for generating a project problem report during the Revit modeling process. Background Art

[0002] With the advancement of science and technology, building information technology (BIM) is gaining increasing popularity in the construction industry. As a key vehicle for building information technology, Building Information Modeling (BIM) permeates every key phase of the construction project lifecycle, guiding design, construction, and operation and maintenance management. BIM technology has been actively promoted in the construction industry due to its numerous advantages, including visualization, coordination, simulation, plotting capabilities, and comprehensive information, which facilitates communication and coordination. Revit software is a platform-level modeling software designed for BIM, offering powerful 3D modeling capabilities. Its rich functionality meets the needs of most scenarios, such as parametric modeling, quantity takeoff, and drawing production. However, various problems inevitably arise during the modeling process, such as conflicts between drawings, model inconsistencies, and parameter errors. If these problems are not promptly identified and resolved, they can seriously impact project quality and progress. Current methods for generating project problem reports during the modeling process often require manual recording, which is both inefficient and error-prone.

[0003] With the increasing popularity of Building Information Modeling (BIM), Revit has become one of the most commonly used modeling software in the construction industry. However, with the continuous increase in project scale and complexity, problems in the Revit modeling process have become increasingly prominent. These problems may lead to negative impacts such as project delays, cost overruns and reduced quality. Summary of the Invention

[0004] To achieve the above objectives, this application provides the following technical solutions:

[0005] According to a first aspect of the present invention, the present invention claims protection for a method for generating a project problem report during the Revit modeling process, which is a secondary development plug-in based on the programming language C#, the Revit API, and the WPF Microsoft framework, comprising:

[0006] Obtain the project engineering records corresponding to the drawings of the project to be evaluated;

[0007] Inputting the project engineering records into a *.docx version problem report template, wherein the *.docx version problem report template is used to generate the importance of the project drawings to be evaluated for at least two man-made accidents corresponding to each of at least one historical problem strategy, the *.docx version problem report template includes at least three problem collection Revit APIs, the problem collection Revit APIs are used to capture the connections between the project engineering records on different types of man-made accidents, the at least three problem collection Revit APIs are divided into at least two different problem collection Revit API groups during the iteration process of the *.docx version problem report template, and the problem collection Revit API group includes at least one problem collection Revit API from the at least three problem collection Revit APIs;

[0008] Output the *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two human-induced accidents corresponding to the at least one historical problem strategy.

[0009] Furthermore, the step of inputting the project engineering records into the *.docx version of the problem report template includes:

[0010] Inputting the physical indicator metadata corresponding to the project engineering record into the at least three problem collection Revit APIs, and outputting the accident handling status identifier output by the at least three problem collection Revit APIs, wherein the physical indicator metadata is the numerical information of the project engineering record, and the accident handling status identifier is the representation of the physical indicator metadata for the different man-made accident types;

[0011] The accident handling status identifier is input into the problem strategy output layer in the *.docx version problem report template, and the *.docx version problem report is output.

[0012] Furthermore, before inputting the project engineering records into the *.docx version problem report template, the method further includes:

[0013] Acquire a plurality of incident processing projects, wherein the incident processing projects are condition information having the same condition type as the historical problem policy;

[0014] Iterating the initial generative model using the multiple accident handling projects and the at least two different problem collection Revit API groups, and outputting the iterated generative model;

[0015] The iterated generation model is decided as the *.docx version problem report template.

[0016] Furthermore, the initial generation model is iterated using the multiple accident handling projects and the at least two different problem collection Revit API groups, and the iterated generation model is output, including:

[0017] Repeat the following steps until the iterative generation model is output:

[0018] Determine the problematic human project from among the multiple accident handling projects;

[0019] Inputting the physical indicator metadata corresponding to the problem artificial item into a first problem collection RevitAPI group in the current generation model, and outputting a first accident handling status identifier output by the first problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the first problem collection RevitAPI group; and inputting the physical indicator metadata corresponding to the problem artificial item into a second problem collection RevitAPI group in the current generation model, and outputting a second accident handling status identifier output by the second problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the second problem collection RevitAPI group;

[0020] Inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report;

[0021] If the first *.docx version problem report and the second *.docx version problem report do not meet the discharge deadline condition, modify the model parameters of the currently generated model and determine the next item from the multiple accident processing items as the problem artificial item;

[0022] In a case where the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition, the current generation model is decided as the iterated generation model.

[0023] Furthermore, after inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report, the method further includes:

[0024] Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, and the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, wherein the at least two man-made accidents include the first man-made accident and the second man-made accident;

[0025] calculating a first importance difference between the first occurrence importance and the third occurrence importance, and a second importance difference between the second occurrence importance and the fourth occurrence importance;

[0026] When the first importance difference is not greater than a first limit value, and / or the second importance difference is not greater than a second limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.

[0027] Furthermore, after inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report, the method further includes:

[0028] Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, and the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, wherein the at least two man-made accidents include the first man-made accident and the second man-made accident;

[0029] Obtain the fifth occurrence importance of the first man-made accident corresponding to the first X items of the problematic man-made items, and the sixth occurrence importance of the second man-made accident corresponding to the first Y items of the problematic man-made items, where X and Y are natural numbers;

[0030] calculating a third importance difference between the first occurrence importance and the fifth occurrence importance, and a fourth importance difference between the second occurrence importance and the sixth occurrence importance;

[0031] When the third importance difference is greater than the third limit value, and / or the fourth importance difference is greater than the fourth limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.

[0032] Furthermore, the modifying of the model parameters of the currently generated model and the determination of the next item from the multiple accident handling items as the problematic artificial item include at least one of the following:

[0033] Correcting a first problem ratio of the at least two different problem collection Revit API groups, wherein the model parameters include the first problem ratio;

[0034] A second problem ratio of the problem strategy output layer is modified, wherein the model parameters include the second problem ratio.

[0035] Furthermore, before inputting the physical indicator metadata corresponding to the problem artificial item into the first problem collection RevitAPI group in the current generation model and outputting the first accident handling status identifier output by the first problem collection RevitAPI group, the method further includes: determining Z problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the Z problem collection RevitAPIs, where Z is a natural number; combining the problem collection RevitAPIs other than the Z problem collection RevitAPIs from the at least three problem collection RevitAPIs, and outputting the first problem collection RevitAPI group;

[0036] Before inputting the physical indicator metadata corresponding to the problem artificial item into the second problem collection RevitAPI group in the current generation model and outputting the second accident handling status identifier output by the second problem collection RevitAPI group, the method also includes: deciding K problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the K problem collection RevitAPIs, where K is a natural number; combining the problem collection RevitAPIs other than the K problem collection RevitAPIs in the at least three problem collection RevitAPIs, and outputting the second problem collection RevitAPI group.

[0037] Furthermore, the method further includes: clicking on rule settings to enter a custom collision rule interface where collision rules can be added; after selecting the collision subject and object, clicking [Save Settings] and closing the interface, the rules will be automatically saved to the system. Before collision analysis, the set collision rules can be selected by opening a drop-down menu;

[0038] Select a collision rule to start the program, select Start Analysis or Quick Analysis, wait for the analysis to be completed, and the collision analysis results will be generated in a list;

[0039] Each collision result is composed of a subject and an object, the dark color is the collision subject, and the white color is the collision object;

[0040] When the progress is manually interrupted, the analyzed data will be retained;

[0041] Before viewing the collision results, you need to set the view; set the model transparency to 10% to clearly display the intersection view;

[0042] View collision results: Double-click the analysis result you want to view, and the view will automatically navigate to the cut 3D view;

[0043] Collision result coloring description: The plug-in provides a coloring method to display the collision components. By default, the component display state is "Color Intersection" + "Show Coloring". The coloring method is controlled by the coloring all hidden coloring in the lower right corner.

[0044] Shading Intersections highlights the intersection of two components; Shading All highlights the two colliding components.

[0045] If you click Hide Coloring, the coloring will be canceled regardless of the current coloring state.

[0046] According to a second aspect of the present invention, the present invention claims protection for a system for generating a project problem report during a Revit modeling process, comprising:

[0047] The first acquisition module is used to obtain the project engineering records corresponding to the drawings of the project to be evaluated;

[0048] an input module configured to input the project engineering records into a *.docx version problem report template, wherein the *.docx version problem report template is configured to generate a degree of importance of the project drawings to be evaluated for at least two man-made accidents corresponding to each of at least one historical problem strategy; the *.docx version problem report template includes at least three problem collection Revit APIs, each of which is configured to capture the connections between the project engineering records and different types of man-made accidents; the at least three problem collection Revit APIs are divided into at least two different problem collection Revit API groups during an iteration of the *.docx version problem report template, each problem collection Revit API group including at least one problem collection Revit API from the at least three problem collection Revit APIs;

[0049] A generation module is used to output a *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two human-induced accidents corresponding to at least one historical problem strategy.

[0050] The present application relates to the technical field of secondary development based on the programming language C#, Revit API and WPF Microsoft framework, and in particular to a method and system for generating a project problem report during the Revit modeling process, which uses the programming language C#, Revit API and WPF Microsoft framework programming to realize automatic entry of problem reports, automatically captures the model problem positioning axis grid by box selection and enters it, automatically obtains the record date, can recognize the name of the imported drawing in the software and automatically enter the drawing name, can take screenshots of the model problem two-dimensional and three-dimensional models with one click, associates the automatically obtained information with the *.docx version problem report template, can export the final *.docx version problem report, and realize that the screenshot is automatically centered in the table of the *.docx version problem report, is associated and synchronized with the *.docx version problem report in the editing state, and can also import the problem report after exporting the *.docx version problem report, saving a lot of work such as text entry, image capture, and problem report organization in the project problem report, and realizing the digital management level of BIM modeling and application. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 A workflow diagram of a method for generating a project problem report in a Revit modeling process as claimed in an embodiment of the present application;

[0052] Figure 2This is a structural diagram of a system for generating a project problem report during a Revit modeling process as claimed in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The following will be combined with the 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 the embodiments. 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.

[0054] According to the first embodiment of the present invention, the present invention claims a method for generating a project problem report during the Revit modeling process, based on the secondary development plug-in of the programming language C# and RevitAPI and WPF Microsoft framework, referring to Figure 1 ,include:

[0055] Obtain the project engineering records corresponding to the drawings of the project to be evaluated;

[0056] Inputting the project engineering records into a *.docx version problem report template, wherein the *.docx version problem report template is used to generate the importance of at least two man-made accidents corresponding to each of the drawings of the project to be evaluated for at least one historical problem strategy, the *.docx version problem report template includes at least three problem collection RevitAPIs, the problem collection RevitAPIs are used to capture the connections between the project engineering records on different types of man-made accidents, the at least three problem collection RevitAPIs are divided into at least two different problem collection RevitAPI groups during the iteration process of the *.docx version problem report template, and the problem collection RevitAPI group includes at least one problem collection RevitAPI from the at least three problem collection RevitAPIs;

[0057] Output the *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two human-induced accidents corresponding to the at least one historical problem strategy.

[0058] Furthermore, the step of inputting the project engineering records into the *.docx version of the problem report template includes:

[0059] Inputting the physical indicator metadata corresponding to the project engineering record into the at least three problem collection Revit APIs, and outputting the accident handling status identifier output by the at least three problem collection Revit APIs, wherein the physical indicator metadata is the numerical information of the project engineering record, and the accident handling status identifier is the representation of the physical indicator metadata for the different man-made accident types;

[0060] The accident handling status identifier is input into the problem strategy output layer in the *.docx version problem report template, and the *.docx version problem report is output.

[0061] Furthermore, before inputting the project engineering records into the *.docx version problem report template, the method further includes:

[0062] Acquire a plurality of incident processing projects, wherein the incident processing projects are condition information having the same condition type as the historical problem policy;

[0063] Iterating the initial generative model using the multiple accident handling projects and the at least two different problem collection Revit API groups, and outputting the iterated generative model;

[0064] The iterated generation model is decided as the *.docx version problem report template.

[0065] Furthermore, the initial generation model is iterated using the multiple accident handling projects and the at least two different problem collection Revit API groups, and the iterated generation model is output, including:

[0066] Repeat the following steps until the iterative generation model is output:

[0067] Determine the problematic human project from among the multiple accident handling projects;

[0068] Inputting the physical indicator metadata corresponding to the problem artificial item into a first problem collection RevitAPI group in the current generation model, and outputting a first accident handling status identifier output by the first problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the first problem collection RevitAPI group; and inputting the physical indicator metadata corresponding to the problem artificial item into a second problem collection RevitAPI group in the current generation model, and outputting a second accident handling status identifier output by the second problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the second problem collection RevitAPI group;

[0069] Inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report;

[0070] If the first *.docx version problem report and the second *.docx version problem report do not meet the discharge deadline condition, modify the model parameters of the currently generated model and determine the next item from the multiple accident processing items as the problem artificial item;

[0071] In a case where the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition, the current generation model is decided as the iterated generation model.

[0072] Furthermore, after inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report, the method further includes:

[0073] Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, and the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, wherein the at least two man-made accidents include the first man-made accident and the second man-made accident;

[0074] calculating a first importance difference between the first occurrence importance and the third occurrence importance, and a second importance difference between the second occurrence importance and the fourth occurrence importance;

[0075] When the first importance difference is not greater than a first limit value, and / or the second importance difference is not greater than a second limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.

[0076] Furthermore, after inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report, the method further includes:

[0077] Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, and the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, wherein the at least two man-made accidents include the first man-made accident and the second man-made accident;

[0078] Obtain the fifth occurrence importance of the first man-made accident corresponding to the first X items of the problematic man-made items, and the sixth occurrence importance of the second man-made accident corresponding to the first Y items of the problematic man-made items, where X and Y are natural numbers;

[0079] calculating a third importance difference between the first occurrence importance and the fifth occurrence importance, and a fourth importance difference between the second occurrence importance and the sixth occurrence importance;

[0080] When the third importance difference is greater than the third limit value, and / or the fourth importance difference is greater than the fourth limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.

[0081] Furthermore, the modifying of the model parameters of the currently generated model and the determination of the next item from the multiple accident handling items as the problematic artificial item include at least one of the following:

[0082] Correcting a first problem ratio of the at least two different problem collection Revit API groups, wherein the model parameters include the first problem ratio;

[0083] A second problem ratio of the problem strategy output layer is modified, wherein the model parameters include the second problem ratio.

[0084] Furthermore, before inputting the physical indicator metadata corresponding to the problem artificial item into the first problem collection RevitAPI group in the current generation model and outputting the first accident handling status identifier output by the first problem collection RevitAPI group, the method further includes: determining Z problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the Z problem collection RevitAPIs, where Z is a natural number; combining the problem collection RevitAPIs other than the Z problem collection RevitAPIs from the at least three problem collection RevitAPIs, and outputting the first problem collection RevitAPI group;

[0085] Before inputting the physical indicator metadata corresponding to the problem artificial item into the second problem collection RevitAPI group in the current generation model and outputting the second accident handling status identifier output by the second problem collection RevitAPI group, the method also includes: deciding K problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the K problem collection RevitAPIs, where K is a natural number; combining the problem collection RevitAPIs other than the K problem collection RevitAPIs in the at least three problem collection RevitAPIs, and outputting the second problem collection RevitAPI group.

[0086] Furthermore, the method further includes: clicking on rule settings to enter a custom collision rule interface where collision rules can be added; after selecting the collision subject and object, clicking [Save Settings] and closing the interface, the rules will be automatically saved to the system. Before collision analysis, the set collision rules can be selected by opening a drop-down menu;

[0087] Select a collision rule to start the program, select Start Analysis or Quick Analysis, wait for the analysis to be completed, and the collision analysis results will be generated in a list;

[0088] Each collision result is composed of a subject and an object, the dark color is the collision subject, and the white color is the collision object;

[0089] When the progress is manually interrupted, the analyzed data will be retained;

[0090] Before viewing the collision results, you need to set the view; set the model transparency to 10% to clearly display the intersection view;

[0091] View collision results: Double-click the analysis result you want to view, and the view will automatically navigate to the cut 3D view;

[0092] Collision result coloring description: The plug-in provides a coloring method to display the collision components. By default, the component display state is "Color Intersection" + "Show Coloring". The coloring method is controlled by the coloring all hidden coloring in the lower right corner.

[0093] Shading Intersections highlights the intersection of two components; Shading All highlights the two colliding components.

[0094] If you click Hide Coloring, the coloring will be canceled regardless of the current coloring state.

[0095] In this embodiment, the programming language C#, Revit API, and WPF Microsoft framework programming are used to realize automatic entry of problem reports. The model problem positioning axis grid is automatically captured and entered by box selection. During the modification process, the model two-dimensional plane position and three-dimensional view position can be found with one click, and the modified view range can be saved. At the same time, the record date is automatically obtained. The name of the imported drawing can be recognized in the software to automatically enter the drawing name. The two-dimensional and three-dimensional model screenshots of the model problem can be taken with one click. The above automatically obtained information is associated with the *.docx version of the problem report template, and the final *.docx version of the problem report can be exported. The screenshot is automatically centered in the table of the *.docx version of the problem report, and is associated and synchronized with the *.docx version of the problem report in the editing state. After the *.docx version of the problem report is exported, the problem report can be imported, thereby saving a lot of work such as text entry, image capture, and problem report organization in the project problem report, and realizing the digital management level of BIM modeling and application.

[0096] To develop the plug-in, we analyzed Revit's API and data structure, determined its functional requirements and implementation, and achieved deep integration with Revit using the C# programming language. The plug-in supports stable operation across different versions of Revit, and optimized algorithms and data structures ensure minimal additional computing resources are consumed during runtime.

[0097] The introduction of this plug-in makes the Revit modeling process more efficient, accurate, and reliable. Designers can receive real-time feedback during the modeling process and correct errors promptly, thus avoiding the rework and delays caused by late-stage problems in traditional modeling. This innovation not only provides designers and engineers with a powerful tool but also opens up new directions for research and application in engineering.

[0098] According to the second embodiment of the present invention, the present invention claims a system for generating a project problem report during Revit modeling, referring to Figure 2 ,include:

[0099] The first acquisition module is used to obtain the project engineering records corresponding to the drawings of the project to be evaluated;

[0100] an input module configured to input the project engineering records into a *.docx version problem report template, wherein the *.docx version problem report template is configured to generate a degree of importance of the project drawings to be evaluated for at least two man-made accidents corresponding to each of at least one historical problem strategy; the *.docx version problem report template includes at least three problem collection Revit APIs, each of which is configured to capture the connections between the project engineering records and different types of man-made accidents; the at least three problem collection Revit APIs are divided into at least two different problem collection Revit API groups during an iteration of the *.docx version problem report template, each problem collection Revit API group including at least one problem collection Revit API from the at least three problem collection Revit APIs;

[0101] A generation module is used to output a *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two human-induced accidents corresponding to at least one historical problem strategy.

[0102] The above detailed description of the specific embodiments of the invention is intended only as an example, and the present application is not limited to the specific embodiments described above. For those skilled in the art, any equivalent modifications or substitutions of the invention are also within the scope of the present application. Therefore, equivalent changes, modifications, and improvements made without departing from the spirit and scope of the present application should be included within the scope of the present application.

Claims

1. A method for generating a project problem report during the Revit modeling process, based on a secondary development plug-in using the programming language C#, Revit API, and the WPF Microsoft framework, characterized in that: include: Obtain the project engineering records corresponding to the drawings of the project to be evaluated; Enter the project engineering records into docx version of the problem report template, where The docx version of the problem report template is used to generate the importance of the occurrence of no less than two man-made accidents corresponding to no less than one historical problem strategy for the project to be evaluated. The docx version of the problem report template includes no less than three problem collection Revit APIs, which are used to capture the connection between the project engineering records on different types of man-made accidents. The iteration process of the docx version of the problem report template is divided into at least two different problem collection RevitAPI groups, and the problem collection RevitAPI group includes at least one problem collection RevitAPI among the at least three problem collection RevitAPIs; Output docx version of the problem report template output docx version problem report, where The docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two human-caused accidents corresponding to at least one historical problem strategy; The project engineering records are input into docx version of the problem report template, including: Inputting the physical indicator metadata corresponding to the project engineering record into the at least three problem collection Revit APIs, and outputting the accident handling status identifier output by the at least three problem collection Revit APIs, wherein the physical indicator metadata is the numerical information of the project engineering record, and the accident handling status identifier is the representation of the physical indicator metadata for the different man-made accident types; The accident handling status identifier is input into the The problem strategy output layer in the docx version of the problem report template outputs the docx version problem report; In the case of inputting the project engineering records into Before the docx version of the problem report template, the method also includes: Acquire a plurality of incident processing projects, wherein the incident processing projects are condition information having the same condition type as the historical problem policy; Iterating the initial generative model using the multiple accident handling projects and the at least two different problem collection Revit API groups, and outputting the iterated generative model; The iterated generation model is decided as docx version of the problem report template.

2. The method according to claim 1, characterized in that The method of iterating the initial generation model using the multiple accident handling projects and the at least two different problem collection Revit API groups and outputting the iterated generation model includes: Repeat the following steps until the iterative generation model is output: Determine the problematic human project from among the multiple accident handling projects; Inputting the physical indicator metadata corresponding to the problem artificial item into a first problem collection RevitAPI group in the current generation model, and outputting a first accident handling status identifier output by the first problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the first problem collection RevitAPI group; and inputting the physical indicator metadata corresponding to the problem artificial item into a second problem collection RevitAPI group in the current generation model, and outputting a second accident handling status identifier output by the second problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the second problem collection RevitAPI group; The first accident handling state identifier is input into the problem strategy output layer in the current generation model, and the first docx version of the problem report; input the second accident handling status identifier into the problem strategy output layer, and output the second docx version problem report; In the first docx version problem report and the second If the docx version of the problem report does not meet the discharge deadline conditions, the model parameters of the currently generated model are modified, and the next item is determined from the multiple accident processing items as the problem artificial item; In the first docx version problem report and the second When the docx version of the problem report meets the discharge deadline condition, the current generation model is decided as the iterated generation model.

3. The method according to claim 2, characterized in that In the step of inputting the first accident handling state identifier into the problem strategy output layer of the current generation model, outputting the first docx version problem report; And, input the second accident handling status identifier into the problem strategy output layer, output the second After the docx version problem report, the method further includes: Get the first The first and second generation sub-schemes in the docx version of the problem report, and the second The third and fourth generation sub-schemes in the docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, and the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, the at least two man-made accidents including the first man-made accident and the second man-made accident; calculating a first importance difference between the first occurrence importance and the third occurrence importance, and a second importance difference between the second occurrence importance and the fourth occurrence importance; In the case where the first importance difference is not greater than a first limit value, and / or the second importance difference is not greater than a second limit value, the first docx version problem report and the second The docx version of the problem report meets the discharge deadline conditions.

4. The method according to claim 3, characterized in that In the step of inputting the first accident handling state identifier into the problem strategy output layer of the current generation model, outputting the first docx version problem report; And, input the second accident handling status identifier into the problem strategy output layer, output the second After the docx version problem report, the method further includes: Get the first The first and second generation sub-schemes in the docx version of the problem report, and the second The third and fourth generation sub-schemes in the docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, and the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, the at least two man-made accidents including the first man-made accident and the second man-made accident; Obtain the fifth occurrence importance of the first man-made accident corresponding to the first X items of the problematic man-made items, and the sixth occurrence importance of the second man-made accident corresponding to the first Y items of the problematic man-made items, where X and Y are natural numbers; calculating a third importance difference between the first occurrence importance and the fifth occurrence importance, and a fourth importance difference between the second occurrence importance and the sixth occurrence importance; In the case where the third importance difference is greater than the third limit value, and / or the fourth importance difference is greater than the fourth limit value, the first docx version problem report and the second The docx version of the problem report meets the discharge deadline conditions.

5. The method according to claim 4, characterized in that The step of modifying the model parameters of the currently generated model and determining the next item from the multiple accident handling items as the problematic artificial item includes at least one of the following: Correcting a first problem ratio of the at least two different problem collection Revit API groups, wherein the model parameters include the first problem ratio; A second problem ratio of the problem strategy output layer is modified, wherein the model parameters include the second problem ratio.

6. The method according to claim 4, characterized in that Before inputting the physical indicator metadata corresponding to the problem artificial item into the first problem collection RevitAPI group in the current generation model and outputting the first accident handling status identifier output by the first problem collection RevitAPI group, the method further includes: determining Z problem collection RevitAPIs from the at least three problem collection RevitAPIs and closing the Z problem collection RevitAPIs, where Z is a natural number; combining the problem collection RevitAPIs other than the Z problem collection RevitAPIs from the at least three problem collection RevitAPIs and outputting the first problem collection RevitAPI group; Before inputting the physical indicator metadata corresponding to the problem artificial item into the second problem collection RevitAPI group in the current generation model and outputting the second accident handling status identifier output by the second problem collection RevitAPI group, the method also includes: deciding K problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the K problem collection RevitAPIs, where K is a natural number; combining the problem collection RevitAPIs other than the K problem collection RevitAPIs in the at least three problem collection RevitAPIs, and outputting the second problem collection RevitAPI group.

7. The method according to any one of claims 1 to 6, characterized in that The method further includes: clicking on rule settings to enter a custom collision rule interface where collision rules can be added; selecting a collision subject and object, then clicking "Save Settings" and closing the interface. The rules will be automatically saved to the system, and the set collision rules can be selected by opening a drop-down menu before collision analysis; Select a collision rule to start the program, select Start Analysis or Quick Analysis, wait for the analysis to be completed, and the collision analysis results will be generated in a list; Each collision result is composed of a subject and an object, the dark color is the collision subject, and the white color is the collision object; When the progress is manually interrupted, the analyzed data will be retained; Before viewing the collision results, you need to set the view; set the model transparency to 10% to clearly display the intersection view; View collision results: Double-click the analysis result you want to view, and the view will automatically navigate to the cut 3D view; Collision result coloring instructions: The plug-in provides a coloring method to display collision components. By default, the component display state is "color intersection" + "show coloring". The coloring method is controlled by the coloring all hidden coloring in the lower right corner. Coloring Intersection will highlight the intersection of the two components; Coloring All will highlight the two colliding components; If you click Hide Coloring, the coloring will be canceled regardless of the current coloring state.

8. A system for generating project problem reports during Revit modeling, characterized in that: include: The first acquisition module is used to obtain the project engineering records corresponding to the drawings of the project to be evaluated; Input module, used to input the project engineering records docx version of the problem report template, where The docx version of the problem report template is used to generate the importance of the occurrence of no less than two man-made accidents corresponding to no less than one historical problem strategy for the project to be evaluated. The docx version of the problem report template includes no less than three problem collection Revit APIs, which are used to capture the connection between the project engineering records on different types of man-made accidents. The iteration process of the docx version of the problem report template is divided into at least two different problem collection RevitAPI groups, and the problem collection RevitAPI group includes at least one problem collection RevitAPI among the at least three problem collection RevitAPIs; Generate a module for outputting the docx version of the problem report template output docx version problem report, where The docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two human-caused accidents corresponding to at least one historical problem strategy; The system for generating a project problem report during Revit modeling is used to execute the method for generating a project problem report during Revit modeling as described in any one of claims 1 to 7.

Images