Method for quickly creating multiple decoration contents in room in building model

Abstract

The invention relates to a method for quickly creating decoration content in a building model, which applies a red-black tree and a hash table data structure, utilizes binary query to quickly position when acquiring actual attributes of components, adopts a hash table to store component types, and cooperates to avoid tedious operations such as multiple inputs, so that the efficiency and accuracy are improved. Depending on an attribute linkage mechanism, all room conditions can be checked when component types are deleted, linkage operation is carried out to ensure that attributes are consistent and accurate, automatic processing can be carried out according to target floor room conditions when attributes are copied, and manual errors and omission are reduced. According to the scheme, all attributes are firstly aggregated, then the room is created, the components meeting the conditions are automatically generated, and the operation steps and time are greatly reduced. Performance is guaranteed through combination of a data structure and algorithm optimization, an efficient data structure is adopted and an optimization algorithm is combined, system resources are reasonably utilized, slow software lagging reaction is avoided, meanwhile, an operation logic process is optimized, unnecessary data read-write and calculation are reduced, and therefore modeling efficiency and accuracy are greatly improved.

Description

Technical Field

[0001] The present application relates to the field of computer graphics technology, and in particular to a method, system, computer device and computer-readable storage medium for quickly creating multiple decoration contents in a room in a building model. Background Art

[0002] BIM (Building Information Modeling) is a comprehensive management system based on digital 3D models, which integrates various information of the entire life cycle of construction projects from planning, design, construction to operation and maintenance. BIM civil engineering quantity calculation is an application of engineering quantity calculation for civil engineering projects (such as the foundation, structure, wall, floor slab, etc. of a building) based on the BIM technology platform.

[0003] In the related technologies, when processing room attributes, civil engineering quantity calculation software cannot achieve one-click creation, real-time update and deletion. It requires multiple input, deletion or addition operations and repeated refreshes to achieve the expected attribute status. The operation process is complicated and time-consuming. In order to avoid performance issues such as software freezes and slow response, most software does not have a one-click attribute operation function, and cannot provide efficient and convenient attribute processing capabilities while ensuring performance.

[0004] Taking all the above factors into consideration, the existing technology has low overall modeling efficiency and difficulty in ensuring accuracy during the modeling process due to the lack of attribute operation methods. Although the final result may be the same, the process is time-consuming and laborious. Summary of the invention

[0005] The embodiments of the present application provide a method, system, computer device and computer-readable storage medium for quickly creating decoration content in a building model, so as to at least solve the problem of low overall modeling efficiency in related technologies.

[0006] In a first aspect, an embodiment of the present application provides a method for quickly creating decoration content in a building model, which is applied to BIM civil engineering quantity calculation software, and the method includes:

[0007] Receive a component selection instruction input by a user, select multiple component types, and obtain actual attributes corresponding to the component types from cache data of the component, wherein the cache data adopts a red-black tree data structure;

[0008] Determine association information between multiple component types according to the outer envelope of each component type, and create multiple types of component entities in the room according to the actual attributes of the components and the association information;

[0009] When a deletion instruction is received, some component types are deleted from the room through the attribute linkage mechanism.

[0010] In some embodiments, upon receiving a deletion instruction, deleting a component type through a property linkage mechanism includes:

[0011] According to the outer envelope and engineering envelope of the room, all components of the room are detected and acquired;

[0012] Obtain the component information to be deleted, traverse all components in the room, and determine whether there is a related component matching the component information to be deleted. If so, delete the related component.

[0013] In some embodiments, determining whether there is a related component that matches the type of the component to be deleted includes:

[0014] According to the property information of the component to be deleted, type comparison is performed in the cache data of all components in the room;

[0015] According to the result of the type comparison, the related components are determined and deleted, and the visual representation of the related components is removed in the front-end user interface.

[0016] In some embodiments, the method further comprises:

[0017] Determine whether the component type to be deleted is a type included in the room attributes, and if so, traverse the data sets of component types in all rooms to obtain whether other rooms contain the component type to be deleted, wherein the data set is stored in a hash table data structure;

[0018] If so, the property corresponding to the component to be deleted is set to empty, and the entity of the related component is deleted, wherein the cache data adopts a red-black tree structure, and when the component property acquisition fails, a prompt message is generated and displayed on the front-end user interface.

[0019] In some embodiments, the method further comprises:

[0020] When the user modifies the component type in the room, traverse the component types of all rooms to obtain whether other rooms contain the component type to be deleted;

[0021] If so, the attributes corresponding to the component type to be deleted in other rooms are adjusted to the values ​​modified by the user, and the component entity corresponding to the component type in the room is updated.

[0022] In some embodiments, when the component selection instruction is a component name input by a user, the method further includes:

[0023] By using a string table comparison algorithm, it is determined whether there is a matching component with the same component name as the component.

[0024] If so, obtaining the actual attributes of the component from the cache data of the matching component through a binary query algorithm;

[0025] If not, a component matching the component name is generated according to the local default configuration, wherein when the component is a component of different materials with additional distinction, a component entity of the corresponding material is generated according to the wall type to which the component is attached.

[0026] In some embodiments, before selecting the plurality of types of component types, the method further comprises:

[0027] Get the top contours of all components to get edge information, and get the material information and edge source information of all components;

[0028] Based on the maximum outer contour of all edge information, the room contour is obtained, or the corresponding wall thickness is obtained according to the edge source information, and the relevant edge information is moved to the inner edge of the wall according to the wall thickness to obtain the room contour;

[0029] Based on the room outline, multiple types of component entities are created in the room according to the component actual attribute information and the association information.

[0030] In a second aspect, an embodiment of the present application provides a system for quickly creating decoration content in a building model, the system comprising: a receiving module, a creating module and a deleting module, wherein:

[0031] The receiving module is used to receive a component selection instruction input by a user, select multiple component types, and obtain actual properties corresponding to the component types from cache data of the component, wherein the cache data adopts a red-black tree data structure;

[0032] The creation module is used to determine association information between multiple component types according to the outer envelope of each component type, and create multiple types of component entities in the room according to the actual attributes of the components and the association information;

[0033] The deletion module is used to delete some component types from the room through the attribute linkage mechanism when receiving a deletion instruction.

[0034] In a third aspect, an embodiment of the present application provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in the first aspect above when executing the computer program.

[0035] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect above.

[0036] Compared with the related art, the method for quickly creating decoration content in the building model provided by the embodiment of the present application uses red-black tree and hash table data structures to quickly locate the actual attributes of the component by binary query. On the other hand, the component type is stored in a hash table. The two work together to avoid tedious operations such as multiple inputs, thereby improving efficiency and accuracy. In addition, relying on the attribute linkage mechanism, when deleting the component type, all room conditions will be checked and the linkage operation will ensure that the attributes are consistent and accurate. When copying the attributes, it can be automatically processed according to the room conditions on the target floor, reducing manual errors and omissions. Finally, unlike other software that manually arranges aggregated components, in this embodiment, all attributes are aggregated first, and then the room is created and components that meet the conditions are automatically generated, which greatly reduces the operation steps and time. Performance is guaranteed by combining data structure and algorithm optimization, using efficient data structures and combining optimization algorithms, rationally utilizing system resources, avoiding slow software response, and optimizing the operation logic flow at the same time, reducing unnecessary data reading and writing and calculation, thereby greatly improving modeling efficiency and accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0038] Figure 1 is a flow chart of a method for quickly creating decoration content in a building model according to an embodiment of the present application;

[0039] Figure 2 It is a schematic diagram of splitting and judging the positions of different materials according to an embodiment of the present application;

[0040] Figure 3 is a schematic diagram of room content generated according to an embodiment of the present application;

[0041] Figure 4 is a schematic diagram of editing a component in a room according to an embodiment of the present application;

[0042] Figure 5 is a schematic diagram of a room outline according to an embodiment of the present application;

[0043] Figure 6 is a schematic diagram of an operation interface for a user to create a new room according to an embodiment of the present application;

[0044] Figure 7is a schematic diagram of an operation interface for a user to create a new room attribute according to an embodiment of the present application;

[0045] Figure 8 is a schematic diagram of an operation interface for editing properties according to an embodiment of the present application;

[0046] Fig. 9 It is a structural block diagram of a system for quickly creating decoration content in a building model according to an embodiment of the present application;

[0047] Fig.10 It is a schematic diagram of the internal structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is described and illustrated below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments provided in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0049] Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. In addition, it can also be understood that although the efforts made in this development process may be complicated and lengthy, for ordinary technicians in this field related to the content disclosed in this application, some changes in design, manufacturing or production based on the technical content disclosed in this application are just conventional technical means, and should not be understood as insufficient content disclosed in this application.

[0050] Reference to "embodiments" in this application means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those of ordinary skill in the art that the embodiments described in this application may be combined with other embodiments without conflict.

[0051] Unless otherwise defined, the technical terms or scientific terms involved in this application should be understood by people with ordinary skills in the technical field to which this application belongs. The words "one", "a", "a", "the" and the like involved in this application do not indicate a quantitative limitation, and may represent the singular or plural. The terms "include", "comprise", "have" and any of their variations involved in this application are intended to cover non-exclusive inclusions; for example, a process, method, system, product or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units that are not listed, or may also include other steps or units inherent to these processes, methods, products or devices. The words "connect", "connected", "coupled" and the like involved in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The "multiple" involved in this application refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships, for example, "A and / or B" can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects before and after are in an "or" relationship. The terms "first", "second", "third", etc. involved in this application are only used to distinguish similar objects and do not represent a specific ordering of the objects.

[0052] There are many problems with the current civil engineering quantity calculation software. First of all, for the setting of the properties of each component in the room, such as floor, wall, ceiling, etc., you need to manually enter the relevant information one by one. For example, to set the wall properties of a room, you may need to enter multiple parameters such as wall material (latex paint, wallpaper or tile, etc.), color, texture, etc., and each parameter needs to be entered accurately. If there are multiple different types of walls in the room (such as different wall requirements for different functional areas of the room), you need to repeat this input process many times, which takes a lot of time and effort.

[0053] Secondly, when you need to adjust the room properties, for example, if you find that the wrong floor material is selected for a room, you need to delete the original floor property settings first, and then re-add the correct floor properties. This process not only involves finding the wrong properties and deleting them, but also requires reselecting or entering new property content. And when adding new properties, you also need to check again whether the related associated properties need to be adjusted. For example, changes in floor material may affect the settings of the properties of skirting boards and wall skirts adjacent to the floor.

[0054] In addition, since the operation results cannot be seen in real time, users often need to repeat the process of input, deletion, addition and refresh many times to achieve the expected attribute status.

[0055] In order to avoid performance issues such as software freezes and slow responses, most software does not have a one-click attribute operation function, and cannot provide efficient and convenient attribute processing capabilities while ensuring performance. Existing software usually requires manual arrangement and aggregation of components in the room one by one, which is labor-intensive and inefficient. Taking all the above factors into consideration, the existing technology has low overall modeling efficiency and difficulty in ensuring accuracy during the modeling process due to the shortcomings of attribute operation and component arrangement aggregation methods. Although the final result may be the same, the process is time-consuming and labor-intensive.

[0056] In view of this, the embodiment of the present application provides a method for quickly creating decoration content in a building model. Figure 1 is a flow chart of a method for quickly creating decoration content in a building model according to an embodiment of the present application. Figure 1 As shown, the process includes the following steps:

[0057] S101, receiving a component selection instruction input by a user, selecting multiple component types, and obtaining actual component properties from cached data of the component types;

[0058] Receive component selection instructions input by the user, and create different types of components in the room, wherein the component types include but are not limited to: floor, wall (concrete), wall (brick), skirting, dado, ceiling, suspended ceiling and column, etc.;

[0059] Among them, the component type in this embodiment is equivalent to the property of the room, which is mainly used to describe the characteristics of different types of components in the room; for wall components, its properties include the type distinction of wall (concrete) or wall (brick), and also involve materials (such as concrete material or brick material), decorative properties (such as the settings of skirting, wall skirt, etc.). The properties largely determine the generation method and final form of the component entity. When creating components in the room, the system generates different component entities according to the properties selected by the user or configured by default.

[0060] When the user selects the corresponding component type in the room, the actual properties of the component of this type will be obtained through a specific data structure and retrieval method; specifically, in this embodiment, a red-black tree data structure is used, and the operation is performed with the help of a binary query tree subnode. It should be noted that the red-black tree is a self-balancing binary search tree, which has good search performance and an average search time complexity of O(log n), where n is the number of nodes in the tree. In this way, even when faced with a large amount of component cache data, the required data can be quickly located from the cache data, thereby efficiently obtaining the actual properties of the component.

[0061] Among them, the binary search method is an efficient search algorithm, which quickly locates the target element by continuously reducing the search range by half. In this embodiment, the binary search method is used to traverse the component types of all rooms, and it can be determined in a relatively short time whether the component type to be deleted exists in other rooms, thereby improving the search efficiency.

[0062] Furthermore, after obtaining the actual properties of the component selected by the user through the red-black tree data structure and other methods, the relevant components such as columns, walls, beams, etc. in the room will be judged as a whole. The purpose of this step is to clarify the relationship between the selected component and other key components (columns, walls, beams) in the room, so as to perform subsequent modeling operations more accurately.

[0063] S102, determining association information between multiple component types according to the outer envelope of each type of component type, and creating multiple types of component entities in the room according to the actual attribute information and association information of the component;

[0064] The association determination method used in this embodiment is to determine whether there is an association through the outer envelope of the component shape. The outer envelope of the component can be understood as a virtual geometric shape formed around the component shape that can contain the entire spatial range of the component.

[0065] It can be understood that the above association judgment plays an auxiliary role in the subsequent generation of physical components, avoiding the problem of incorrect component overlap.

[0066] In addition, if the user does not select the corresponding component type, but manually enters a new component name, additional detection operations are required. By traversing the existing component types and using a string comparison algorithm to determine whether there is a component type with the same name. If they are exactly the same, it means that there is a component type with the same name; if the same name is not found, it means that there is no component type with the same name. This detection method can more accurately determine whether the newly entered component name has been used in the model, thereby ensuring the uniqueness of the component naming and the accuracy of the model data.

[0067] Finally, after the association between components is determined, different component entities are created according to the component generation logic based on the above actual attributes and association information. It should be noted that the component generation logic is determined based on multiple factors such as building design specifications, structural requirements, and actual attributes of components obtained previously.

[0068] Figure 2 is a schematic diagram of splitting and judging the positions of different materials according to an embodiment of the present application, such as Figure 2As shown, for example, based on the relationship between beams and columns and the actual properties of the beams themselves (such as the length, cross-sectional dimensions, material, etc. of the beams), details such as the connection structure of the beams at the column nodes can be accurately created, so that the created beam component entity in the building model not only meets its own property requirements, but also the connection relationship with other related components (such as columns) also conforms to the logic of the actual building structure.

[0069] In addition, if there is no component type with the same name after detection, the system will generate a component of this type according to the local default configuration. This ensures that when the user manually enters the name of a new component and there is no conflict with the same name, an initial component form that meets the basic specifications and requirements can still be provided, so that the properties of the component can be further improved and adjusted later.

[0070] Figure 3 is a schematic diagram of room contents generated according to an embodiment of the present application, such as Figure 3 As shown, through the above step S102, a technical means is provided for performing association judgment after obtaining the actual attributes of the component, processing the manually input component name, and creating the component entity according to the judgment result. Through a one-time editing, all the attributes in the room can be generated, and the building model component entity with accurate and reasonable distribution can be generated.

[0071] In addition, it should be noted that there is an additional distinction between wall (concrete) and wall (brick) (the host material type is obtained through the host relationship cached by the component itself to distinguish whether it is concrete material or brick material); when setting the corresponding properties, the wall of the corresponding material will be generated according to the attached wall type.

[0072] This method can ensure the consistency between the wall properties in the building model and the actual building structure. Walls of different materials correspond to different physical properties, decorative effects and construction requirements. Only by generating accurate wall properties according to the actual wall type can accurate information support be provided in the subsequent stages of building design, construction and operation management. When the system determines that the wall is a wall (concrete) type, it will generate the corresponding wall properties based on the relevant characteristics of the concrete material and the preset attribute template. These properties may include settings for the thickness, strength grade, surface roughness, and decorative surface layer of the concrete wall. Similarly, when it is determined to be a wall (brick) type, properties such as brick type (red brick, green brick, etc.), masonry method, plastering requirements, and decorative surface layer will be generated according to the characteristics of the brick material.

[0073] S103, upon receiving a deletion instruction, deleting some component types from the room through the attribute linkage mechanism.

[0074] This step mainly includes two key steps: first, detect and obtain all the components of the room, and then traverse these components to determine and delete the relevant components that match the information of the components to be deleted.

[0075] Step 1, detect and obtain all components of the room according to the outer envelope or engineering envelope of the room;

[0076] Among them, the outer envelope of the room refers to the external boundaries, outlines and other related concepts of the room, and the engineering envelope is a general definition of the relevant scope or space of the room from an engineering perspective, involving comprehensive considerations of spatial layout, component distribution and other aspects related to engineering implementation.

[0077] In this embodiment, the detection operation is performed according to the outer envelope of the room. Through the comprehensive consideration of these two aspects, the spatial range in the room and which components should exist within this range can be fully determined, thereby achieving detection and acquisition of all components in the room.

[0078] Step 2, obtain the information of the component to be deleted, traverse all the components in the room, and determine whether there is a related component that matches the information of the component to be deleted. If so, delete the related component.

[0079] Before processing the components in the room, it is necessary to first clarify the specific information of the components to be deleted. This information may include the type, properties, size and other aspects of the components, so that the relevant components that match them can be accurately found among the many components later.

[0080] Furthermore, after obtaining all components of the room, these components are traversed. During the traversal process, the information of each component is compared with the information of the component to be deleted to determine whether there is a related component that matches it. The matching judgment here is based on the standard set by the information of the component to be deleted.

[0081] For example, if the component information to be deleted specifies a certain type of wall component, then during the traversal process it will be checked whether each component is a wall component of this type.

[0082] After determining that there are related components that match the information of the component to be deleted, these matching related components are deleted from the component set of the room. In this way, through the attribute linkage mechanism, components of the same type can be accurately deleted according to the received deletion instructions, ensuring that the component layout and attribute settings in the room meet the expected adjustment requirements.

[0083] In addition, based on the above attribute linkage mechanism, other related rooms can also be processed, including:

[0084] Step 1, determine whether the component type to be deleted is the type included in the room attributes. If so, traverse the component types of all rooms through binary search to obtain whether other rooms contain the component type to be deleted, where the component type is stored in a hash table data structure;

[0085] After determining that the component type to be deleted is a type included in the room attributes, the component types of all rooms are traversed to obtain whether other rooms contain the component type to be deleted.

[0086] At the same time, the component types in this embodiment are stored in a hash table data structure. The hash table can map the key (here, the component type) to the corresponding storage location through a specific hash function to achieve fast access and search. In this embodiment, the use of a hash table to store component types can be further combined with a binary search method, so that when traversing and searching for component types in other rooms, it is possible to more quickly and accurately determine whether there is a component type to be deleted.

[0087] Step 2, if yes, set the property corresponding to the component to be deleted to empty, and delete the entity of the related component. The cache data adopts a red-black tree structure. In the case of failure to obtain the component property, a prompt message is generated and displayed on the front-end user interface.

[0088] If the above search finds that other rooms do contain the component type to be deleted, first, the properties corresponding to the component to be deleted will be set to null. At the same time, the entity of the related component will also be deleted. This is a more thorough processing method, which directly removes the component of this type from the physical composition of the room, ensuring that the actual composition of the room matches the property setting, avoiding errors such as properties pointing to non-existent entities, and ensuring the consistency and accuracy of the overall room data.

[0089] In addition, if the component attribute acquisition fails, a prompt message will be generated and displayed on the front-end user interface. This is to let users know in time that there is a problem during the operation and the required component attributes cannot be obtained, so that users can take corresponding measures, such as checking whether the data is complete or whether the system has a fault. At the same time, it also avoids subsequent processing errors caused by the failure of attribute acquisition, ensuring the standardization and accuracy of the entire operation process.

[0090] Based on the above attribute association mechanism, global adjustment of attributes can also be achieved, including:

[0091] Step 1, when the user modifies the component type in the room, traverse the component types of all rooms to obtain whether other rooms contain the component type to be deleted;

[0092] Step 2, if yes, adjust the properties corresponding to the component type to be deleted in other rooms to the values ​​modified by the user, and update the corresponding type entity of the component entity in the room.

[0093] also, Figure 4 is a schematic diagram of editing a component in a room according to an embodiment of the present application, such as Figure 4 As shown, this application solution can support users to add, modify, delete drawing areas, etc. for the decoration content that the sound test will give you in the room;

[0094] When the user modifies the component type in the room attribute, all components in the room are checked through the hash table to confirm whether there is a component of the corresponding type, and then the component is modified in a linked manner. If the type included in the room attribute is modified, all room types will be checked to determine whether the room attribute contains the component type. If so, the attribute will be adjusted to the value modified by the user, and the corresponding type entity in the room entity will be updated.

[0095] in addition, Figure 5 is a schematic diagram of a room outline according to an embodiment of the present application, such as Figure 5 As shown, this application solution supports the differentiated generation of different positions of concrete, masonry, beams, and columns. The top contours of concrete walls, brick walls, beams, and columns will be obtained and recorded as edge information, and the material information and edge source information will be recorded together. After summarizing all the edges, the system will take the largest outer contour as the room contour.

[0096] In addition, if the inner edge of the wall is generated, the corresponding wall thickness will be obtained according to the recorded source information, and the corresponding edge will be offset to the inner edge of the wall, and the surrounding edges will be connected. After the room outline is generated, the system will generate the wall, skirting, wall skirt and column of the corresponding material for each edge according to the property settings in the room, while the generation of floor, ceiling and ceiling will be based on the room outline. It should be noted that the generation of floor will be based on the bottom outline of the component to avoid errors when the top and bottom surfaces of the component are different.

[0097] In addition, this application also supports a convenient attribute copying function, which can quickly apply specific attributes to other floors. When performing an attribute copying operation, if the corresponding room does not exist on the target floor, a room with completely consistent attributes with the original room will be automatically generated on the target floor. After that, the various attributes in the room will be deeply checked. If there are other types of component attributes, it will be recursively checked to see if the type already exists; if not, the same configuration of the component attributes of this type will be created based on the original configuration to ensure the integrity and consistency of the room attributes.

[0098] If a room with the same name already exists on another floor, the properties of the room will be accurately copied to the target floor, and the properties of the room on the target floor will be tested immediately. Once other types of component properties are found, the system will completely copy the configuration of that type to the target floor; if not, it will create the same type with the same configuration. At the same time, the system will also fully detect all rooms and components that use this type, and seamlessly apply this configuration to the corresponding components on other floors, thereby effectively ensuring the uniformity and coordination of the properties of the entire building model between different floors.

[0099] In addition, an exemplary interactive process for personnel to quickly create decoration content in BIM civil engineering quantity calculation software is as follows:

[0100] Step 1: Create a new room; Figure 6 is a schematic diagram of an operation interface for a user to create a new room according to an embodiment of the present application;

[0101] Step 2, create new room attributes; Figure 7 is a schematic diagram of an operation interface for a user to create a new room attribute according to an embodiment of the present application;

[0102] Step 3, arrange the room (specifically including obtaining the room outline and splitting different materials);

[0103] Step 4, modify attributes, delete attributes; Figure 8 It is a schematic diagram of an operation interface for editing properties according to an embodiment of the present application.

[0104] Through the above steps S101 to S103, the red-black tree and hash table data structures are used to quickly locate the actual attributes of the component by using binary query, with an average time complexity of O(logn). The hash table stores the component type, and the search is ideally close to O(1). The two work together to avoid tedious operations such as multiple inputs, thereby improving efficiency and accuracy. In addition, relying on the attribute linkage mechanism, when deleting the component type, all room conditions will be checked and linked operations will be performed to ensure that the attributes are consistent and accurate. When copying attributes, they can be automatically processed according to the room conditions on the target floor, reducing manual errors and omissions. Finally, unlike other software that manually arranges aggregated components, this embodiment aggregates all attributes first, then creates a room and automatically generates components that meet the conditions, greatly reducing the number of operation steps and time. By combining data structure and algorithm optimization to ensure performance, using efficient data structures and combining optimization algorithms, rationally utilizing system resources, avoiding software jams and slow responses, and optimizing the operation logic process, reducing unnecessary data reading and writing and calculations, and achieving a balance between function and performance, thereby greatly improving modeling efficiency and accuracy.

[0105] It should be noted that the steps shown in the above process or the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0106] This embodiment also provides a system for quickly creating decoration content in a building model. Fig. 9 is a structural block diagram of a system for quickly creating decoration content in a building model according to an embodiment of the present application, such as Fig. 9 As shown, the system is applied to BIM civil engineering quantity calculation software, and the system includes: a receiving module 90, a creating module 91 and a deleting module 92, wherein:

[0107] The receiving module 90 is used to receive a component selection instruction input by a user, select multiple component types, and obtain actual properties corresponding to the component types from the cache data of the component, wherein the cache data adopts a red-black tree data structure;

[0108] The creation module 91 is used to determine the association information between multiple component types according to the outer envelope of each component type, and create multiple types of component entities in the room according to the actual attributes of the components and the association information;

[0109] The deletion module 92 is used to delete some component types from the room through the attribute linkage mechanism when receiving a deletion instruction.

[0110] Through this system, red-black tree and hash table data structures are used to quickly locate the actual properties of components using binary queries. Ideally, they are close when searching. The two work together to avoid tedious operations such as multiple inputs, thereby improving efficiency and accuracy. In addition, relying on the attribute linkage mechanism, when deleting a component type, all room conditions will be checked and linked operations will be performed to ensure that the properties are consistent and accurate. When copying properties, they can be automatically processed according to the room conditions on the target floor, reducing manual errors and omissions. Finally, unlike other software that manually arranges aggregated components, this embodiment aggregates all properties first, then creates a room and automatically generates components that meet the conditions, greatly reducing the number of operation steps and time. Performance is guaranteed by combining data structure and algorithm optimization, using efficient data structures and combining optimization algorithms, making rational use of system resources, avoiding slow software response, and optimizing the operation logic process, reducing unnecessary data reading and writing and calculations, and achieving a balance between function and performance, thereby greatly improving modeling efficiency and accuracy.

[0111] In one embodiment, Fig.10 is a schematic diagram of the internal structure of an electronic device according to an embodiment of the present application, such as Fig.10 As shown, an electronic device is provided, which may be a server, and its internal structure diagram may be as shown in Fig.10As shown. The electronic device includes a processor, a network interface, an internal memory and a non-volatile memory connected through an internal bus, wherein the non-volatile memory stores an operating system, a computer program and a database. The processor is used to provide computing and control capabilities, the network interface is used to communicate with an external terminal through a network connection, the internal memory is used to provide an environment for the operation of the operating system and the computer program, the computer program is executed by the processor to realize a system for quickly creating decoration content in a building model, and the database is used to store data.

[0112] Those skilled in the art will understand that Fig.10 The structure shown in the figure is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the electronic device to which the scheme of the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0113] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0114] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for quickly creating decoration content in a building model, characterized in that: Applied to BIM civil engineering quantity calculation software, the method includes: Receive a component selection instruction input by a user, select multiple component types, and obtain actual attributes corresponding to the component types from cache data of the component, wherein the cache data adopts a red-black tree data structure; Determine association information between multiple component types according to the outer envelope of each component type, and create multiple types of component entities in the room according to the actual attributes of the components and the association information; When a deletion instruction is received, some component types are deleted from the room through the attribute linkage mechanism.

2. The method according to claim 1, characterized in that: When receiving a delete instruction, the component types deleted through the attribute linkage mechanism include: Detect and obtain all components of the room according to the outer envelope and the engineering envelope of the room; Obtain the component information to be deleted, traverse all components in the room, and determine whether there is a related component matching the component information to be deleted. If so, delete the related component.

3. The method according to claim 2, characterized in that Determining whether there are related components that match the type of the component to be deleted includes: According to the property information of the component to be deleted, type comparison is performed in the cache data of all components in the room; According to the result of the type comparison, the related components are determined and deleted, and the visual representation of the related components is removed in the front-end user interface.

4. The method according to claim 2, characterized in that: The method further comprises: Determine whether the component type to be deleted is a type included in the room attributes, and if so, traverse the data sets of component types in all rooms to obtain whether other rooms contain the component type to be deleted, wherein the data set is stored in a hash table data structure; If so, the property corresponding to the component to be deleted is set to empty, and the entity of the related component is deleted, wherein the cache data adopts a red-black tree structure, and when the component property acquisition fails, a prompt message is generated and displayed on the front-end user interface.

5. The method according to claim 4, characterized in that The method further comprises: When the user modifies the component type in the room, traverse the component types of all rooms to obtain whether other rooms contain the component type to be deleted; If so, the attributes corresponding to the component type to be deleted in other rooms are adjusted to the values ​​modified by the user, and the component entity corresponding to the component type in the room is updated.

6. The method according to claim 1, characterized in that When the component selection instruction is a component name input by a user, the method further includes: By using a string table comparison algorithm, it is determined whether there is a matching component with the same component name as the component. If so, obtaining the actual attributes of the component from the cache data of the matching component through a binary query algorithm; If not, a component matching the component name is generated according to the local default configuration, wherein when the component is a component of different materials with additional distinction, a component entity of the corresponding material is generated according to the wall type to which the component is attached.

7. The method according to claim 1, characterized in that Before selecting a plurality of types of component types, the method further includes: Get the top contours of all components to get edge information, and get the material information and edge source information of all components; Based on the maximum outer contour of all edge information, the room contour is obtained, or the corresponding wall thickness is obtained according to the edge source information, and the relevant edge information is moved to the inner edge of the wall according to the wall thickness to obtain the room contour; Based on the room outline, multiple types of component entities are created in the room according to the component actual attribute information and the association information.

8. A system for quickly creating decoration content in a building model, characterized in that: The system comprises: a receiving module, a creating module and a deleting module, wherein: The receiving module is used to receive a component selection instruction input by a user, select multiple component types, and obtain actual properties corresponding to the component types from cache data of the component, wherein the cache data adopts a red-black tree data structure; The creation module is used to determine association information between multiple component types according to the outer envelope of each component type, and create multiple types of component entities in the room according to the actual attributes of the components and the association information; The deletion module is used to delete some component types from the room through the attribute linkage mechanism when receiving a deletion instruction.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

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

Images