Method for quickly creating multiple furnishing contents in a room in a building model

Abstract

The application relates to a method for quickly creating decoration content in a building model, which utilizes a red-black tree and a hash table data structure, utilizes a binary query to quickly locate when actual properties of components are obtained, stores component types by using a hash table, and avoids tedious operations such as multiple inputs by cooperation of the two, so that efficiency and accuracy are improved. According to an attribute linkage mechanism, when a component type is deleted, all room conditions are checked and linkage operations are performed to ensure that the attributes are consistent and accurate, and when attributes are copied, the target floor room conditions can be automatically processed, manual errors and omissions are reduced. The application scheme is to aggregate all attributes first, then create rooms and automatically generate components meeting the conditions, so that the operation steps and time are greatly reduced. Performance is guaranteed by combination of data structure and algorithm optimization, efficient data structure is adopted in combination with an optimization algorithm, system resources are reasonably utilized, software lag and slow response are avoided, operation logic flow is optimized, unnecessary data reading and writing and calculation are reduced, and therefore modeling efficiency and accuracy are greatly improved.

Description

TECHNICAL FIELD

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

[0002] BIM (Building Information Modeling) is a comprehensive management system based on a digital three-dimensional model, which integrates various information of a building project from planning, design, construction to operation and maintenance throughout the life cycle. BIM civil quantity calculation is an application for calculating the quantities of civil engineering (such as the foundation, structure, wall, floor, etc. of a building) on the BIM technology platform.

[0003] In related technologies, civil quantity calculation software cannot achieve one-key creation, real-time updating and deletion when processing room properties, and requires multiple input, deletion or addition operations and repeated refreshing to achieve the expected property state, which is complex and time-consuming. Most software does not configure one-key property operation function to avoid performance problems such as software freezing and slow response, and cannot provide efficient and convenient property processing capability while ensuring performance.

[0004] In summary, due to the shortcomings of the property operation method, the overall modeling efficiency is not high, and the accuracy is difficult to guarantee in the prior art. Although the final result may be the same, the process is time-consuming and laborious. SUMMARY

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

[0006] In a first aspect, the embodiments of the present application provide a method for quickly creating decoration contents in a building model, applied to BIM civil quantity calculation software, the method comprising:

[0007] receiving a component selection instruction input by a user, selecting multiple component types, and obtaining actual properties corresponding to the component types from cache data of components, wherein the cache data adopts a red-black tree data structure;

[0008] determining association information between the multiple component types according to the outer envelopes of the component types, and creating component entities of the multiple types in the room according to the component actual properties and the association information;

[0009] In the case of receiving a deletion instruction, deleting part of the component types from the room through a property linkage mechanism.

[0010] In some embodiments, the deleting the component type by the attribute linkage mechanism in the case of receiving the deleting instruction comprises:

[0011] According to the outer envelope and the engineering envelope of the room, detecting all components in the room;

[0012] Obtaining the information of the component to be deleted, traversing all components in the room, judging whether there is a related component matching the information of the component to be deleted, and if so, deleting the related component.

[0013] In some embodiments, judging whether there is a related component matching the component type to be deleted comprises:

[0014] According to the attribute information of the component to be deleted, comparing types in the cache data of all components in the room;

[0015] According to the result of the type comparison, determining the related component and deleting the related component, and removing the visual representation of the related component in the front-end user interface.

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

[0017] Judging whether the component type to be deleted is a type contained in the room attribute, if so, traversing the data set of all component types of the room to obtain whether the component type to be deleted is contained in other rooms, wherein the data set is stored in a hash table data structure;

[0018] If so, setting the attribute corresponding to the component to be deleted to be empty, and deleting the entity of the related component, wherein the cache data adopts a red-black tree structure, and in the case of failure to obtain the component attribute, a prompt information is generated and displayed in the front-end user interface.

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

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

[0021] If so, adjusting the attribute corresponding to the component type to be deleted in other rooms to the value modified by the user, and updating the component entity corresponding to the component type in the room.

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

[0023] Judging whether there is a matching component with the same component name by a string table comparison algorithm,

[0024] If yes, the actual attribute of the component is obtained from the cache data of the matched component through a binary query algorithm;

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

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

[0027] Obtaining edge information by obtaining top profiles of all components, and obtaining material information and edge source information of all components;

[0028] Obtaining a room profile based on a maximum outer profile of all edge information, or obtaining a corresponding wall thickness according to the edge source information, and moving relevant edge information to an inner edge of the wall according to the wall thickness to obtain the room profile;

[0029] Based on the room profile, creating a plurality of types of component entities in the room according to the actual attribute information of the components 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 configured to receive a component selection instruction input by a user, select a plurality of component types, and obtain actual attributes corresponding to the component types from cache data of the components, wherein the cache data adopts a red-black tree data structure;

[0032] The creating module is configured to determine association information between the plurality of component types according to outer envelopes of the component types, and create a plurality of types of component entities in a room according to the actual attributes of the components and the association information;

[0033] The deleting module is configured to delete part of the component types from the room through an attribute linkage mechanism when a deletion instruction is received.

[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 of the first aspect when executing the computer program.

[0035] In a fourth aspect, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to implement the method in the first aspect.

[0036] Compared with the related art, the method for quickly creating decoration content in a building model provided by the embodiments of the present application uses the red-black tree and hash table data structure, uses binary search to quickly locate when the actual attribute of a component is obtained, on the other hand, uses a hash table to store the component type, and both of them cooperate to avoid tedious operations such as multiple inputs, thereby improving the efficiency and accuracy. In addition, relying on the attribute linkage mechanism, when a component type is deleted, all room conditions are checked and linked to ensure the consistency and accuracy of the attributes, and when the attributes are copied, the target floor room conditions can be automatically processed, reducing manual errors and omissions. Finally, unlike other software that manually arranges aggregated components, in the embodiments, all attributes are aggregated first, then rooms are created, and components that meet the conditions are automatically generated, greatly reducing the operation steps and time. Through the combination of data structure and algorithm optimization, the performance is guaranteed, the efficient data structure is used, and the optimized algorithm is combined, the system resources are reasonably used, the software is prevented from being slow in response and lagging, the operation logic flow is optimized, and unnecessary data reading and writing and calculation are reduced, thereby greatly improving the modeling efficiency and accuracy. BRIEF DESCRIPTION OF DRAWINGS

[0037] The accompanying drawings, which are included to provide a further understanding of the present application, constitute a part of the present application, and the illustrative embodiments of the present application and their description serve to explain the present application, and do not constitute improper limitations on the present application. In the drawings:

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

[0039] Figure 2 is a schematic diagram of a split judgment for different material positions according to an embodiment of the present application;

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

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

[0042] Figure 5 is a schematic diagram of a room contour 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 room according to an embodiment of the present application;

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

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

[0046] Figure 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;

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

[0048] In order to make the objects, technical solutions and advantages of the present application clearer, the present application is described and explained below in connection with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and should not be used to limit the present application. Based on the embodiments provided in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of the present application.

[0049] Obviously, the drawings in the following description are only some examples or embodiments of the present application, and for those of ordinary skill in the art, the present application can be applied to other similar scenarios without creative labor on the basis of these drawings. In addition, it can be understood that although the efforts made in this development process can be complex and lengthy, for those of ordinary skill in the art related to the content disclosed in the present application, some design, manufacture or production changes based on the technical content disclosed in the present application are only routine technical means and should not be understood as insufficient disclosure of the present application.

[0050] In the present application, "embodiments" means that the specific features, structures or characteristics described in connection with the embodiments can be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily mean the same embodiment, nor is it an independent or alternative embodiment to other embodiments. It is explicitly and implicitly understood by those of ordinary skill in the art that the embodiments described in the present application can be combined with other embodiments without conflict.

[0051] Unless otherwise defined, technical terms and scientific terms used in the present application shall have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terms "a", "an", "one", "this", and the like, as used in the present application, do not denote a limitation of quantity and can be used in the sense of "one or more". The terms "including", "containing", "having", and the like, as used in the present application, are meant to be inclusive, unless otherwise noted. For example, a process, method, system, product, or apparatus that comprises a list of steps or modules (units) is not limited to those steps or units which are recited, but can also include additional steps or units that are not expressly listed or can include additional steps or units that are inherent to the process, method, product, or apparatus. The terms "connected", "coupled", and the like, as used in the present application, are not limited to direct or physical connections, but can include electrical connections, whether direct or indirect. The term "plurality" means two or more. The term "and / or" describes association between name objects, and means that there can be three types of relationships between the objects, for example, "A and / or B" can mean that A exists alone, A and B exist together, or B exists alone. The character " / " generally means that the associated objects are in an "or" relationship. The terms "first", "second", "third", and the like, as used in the present application, are merely used to distinguish similar objects, and do not represent a specific order of the objects.

[0052] Current civil engineering calculation software has many problems. First, for the setting of the properties of each component in the room, such as the floor, wall, ceiling, etc., it is necessary to manually input the relevant information one by one. For example, to set the properties of the wall of a room, it may be necessary to input multiple parameters such as wall material (latex paint, wallpaper, or ceramic tile, etc.), color, texture, etc. in turn, and each parameter needs to be accurately input. If there are multiple types of walls in the room (such as walls with different functional areas requiring different wall properties), the input process needs to be repeated multiple times, consuming a lot of time and effort.

[0053] Secondly, when the properties of the room need to be adjusted, for example, if it is found that the floor material of a room is selected incorrectly, the original floor property setting needs to be deleted and the correct floor property needs to be added again. This process not only involves the operation of finding and deleting the incorrect property, but also requires the selection or input of new property content. Moreover, when adding a new property, it is necessary to check again whether the associated properties need to be adjusted, such as the change of floor material may affect the setting of properties such as skirting and wall skirt adjacent to the floor.

[0054] In addition, due to the inability to see the operation results in real time, users often need to repeat the input, deletion, addition, and refresh process multiple times to achieve the desired property state.

[0055] Most software does not configure one-key attribute operation function to avoid software lag and slow reaction and other performance problems, and cannot provide efficient and convenient attribute processing capability while ensuring performance. The existing software usually needs to manually arrange and aggregate the components in the room one by one, which is time-consuming and inefficient. In view of the above factors, the existing technology has low overall modeling efficiency and poor accuracy due to the deficiency of the attribute operation and component arrangement aggregation method in the modeling process, although the final result may be the same, but the process is time-consuming and laborious.

[0056] Therefore, the embodiments of the present application provide a method for quickly creating decoration content in a building model, Figure 1 is a flowchart of a method for quickly creating decoration content in a building model according to an embodiment of the present application, as shown in Figure 1 The flowchart includes the following steps:

[0057] S101, receiving a component selection instruction input by a user, selecting a plurality of component types, and obtaining actual attributes of components from cache data of the component types;

[0058] Receiving a component selection instruction input by a user, creating different types of components in a room, wherein the component types include but are not limited to floor, wall (concrete), wall (brick), skirting, wall skirt, ceiling, suspended ceiling and column surface, etc.

[0059] In the embodiment, the component type corresponds to the attribute of the room, which is mainly used to describe the characteristics of different types of components in the room. For wall components, the attributes include type differentiation such as wall (concrete) or wall (brick), and also involve material (such as concrete material or brick material), decoration attributes (such as the setting of skirting line, wall skirt, etc.). The attributes 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 attributes selected by the user or the default configuration

[0060] When the user selects the corresponding component type in the room, the actual attributes of the component of the type are obtained through a specific data structure and retrieval method. Specifically, in the embodiment, a red-black tree data structure is used, and a binary search tree node is used for operation. It should be noted that the red-black tree is a self-balancing binary search tree, which has good search performance, and the average search time complexity is O (log n), where n is the number of nodes in the tree. Through this method, even when facing a large amount of component cache data, the required data can be quickly located from the cache data, so that the actual attributes of the component can be efficiently obtained.

[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 all the component types of the room, which can determine whether there is the component type to be deleted in other rooms in a relatively short time, thereby improving the search efficiency.

[0062] Further, after obtaining the actual attributes of the selected component of the user through the red-black tree data structure and the like, the related components such as columns, walls and beams in the room are judged as a whole. The purpose of this step is to determine the relationship between the selected component and other key components (columns, walls and beams) in the room, so as to more accurately perform subsequent modeling operations.

[0063] S102, determining the association information between the plurality of component types according to the outer envelopes of the component types, and creating a plurality of types of component entities in the room according to the actual attribute information of the components and the association information;

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

[0065] It can be understood that the above association judgment has an auxiliary effect on the subsequent generation of entity components, avoiding the problems of component error overlap and the like.

[0066] In addition, if the user does not select the corresponding component type, but manually inputs a new component name, additional detection operation is needed. By traversing the existing component types and using the string comparison algorithm to judge 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 no same name is found, it means that there is no component type with the same name. This detection method can more accurately determine whether the newly input 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 completing the association judgment between the components, different component entities are created according to the above actual attributes and association information according to the component generation logic. It should be noted that the component generation logic is determined based on the building design specification, the structure requirement and the previously obtained component actual attributes and the like.

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

[0069] In addition, if it is detected that there is no same component type, the system will generate a component of this type according to the local default configuration. This ensures that in the case where the user manually inputs a new component name and there is no same name conflict, an initial form of the component that meets the basic specifications and requirements can still be provided for subsequent further improvement and adjustment of the properties of the component.

[0070] Figure 3 is a schematic diagram of a generated room content according to an embodiment of the present application, as Figure 3 As shown, through the above step S102, technical means is provided for how to make association judgment after obtaining the actual properties of the component, handle the manual input of the component name, and create the component entity according to the judgment result. Through one-time editing, all properties in the room can be generated, and a distributed accurate and reasonable building model component entity can be generated.

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

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

[0073] S103, in the case of receiving a deletion instruction, part of the component types in the room are deleted through the attribute linkage mechanism.

[0074] This step mainly includes two key steps: first, detect and obtain all the components of the room, and on this basis, traverse these components, judge and delete the related components matching the to-be-deleted component information.

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

[0076] The outer envelope of the room refers to the outer boundary, contour and other related concepts of the room, and the engineering envelope is a general definition of the relevant scope or space from the engineering point of view, involving comprehensive consideration of space 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 in this range can be determined comprehensively, so as to realize the detection and acquisition of all components in the room.

[0078] Step 2, obtain the to-be-deleted component information, traverse all the components in the room, and judge whether there are related components matching the to-be-deleted component information, if so, delete the related components.

[0079] Wherein, before starting to process the components in the room, the specific information of the to-be-deleted component needs to be determined first, which may include the type, attribute, size and other aspects of the component, so as to accurately find the related components matching it in the numerous components later.

[0080] Further, after obtaining all the components of the room, the components are traversed. In the traversal process, the information of each component is compared with the to-be-deleted component information to judge whether there are related components matching it. The matching judgment here is based on the standard set by the to-be-deleted component information.

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

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

[0083] In addition, based on the above attribute linkage mechanism, the processing of other associated rooms can also be realized, which specifically includes:

[0084] Step 1: Determine whether the component type to be deleted is a type contained in the room attributes. If so, use a binary search to traverse all room component types to find out whether other rooms contain the component type to be deleted. The component types are stored using a hash table data structure.

[0085] After determining that the component type to be deleted is a type contained in the room's attributes, iterate through the component types of all rooms to check whether other rooms contain the component type to be deleted.

[0086] In this embodiment, the component types are stored using a hash table data structure. The hash table uses a specific hash function to map the key (in this case, the component type) to the corresponding storage location, enabling fast access and retrieval. In this embodiment, using a hash table to store component types can be further combined with a binary search method, allowing for a faster and more accurate determination of whether a component type to be deleted exists when traversing and searching for component types in other rooms.

[0087] Step 2: If yes, set the attribute corresponding to the component to be deleted to empty and delete the entity of the related component. The cached data adopts a red-black tree structure. If the component attribute retrieval fails, a prompt message is generated and displayed on the front-end user interface.

[0088] If the search reveals that other rooms do indeed contain the component type to be deleted, the properties corresponding to the component to be deleted will first be set to empty. Simultaneously, the entity containing the relevant component will also be deleted. This is a more thorough approach, directly removing the component type from the room's physical structure. This ensures that the actual structure of the room matches the property settings, avoiding errors such as properties pointing to non-existent entities, and guaranteeing the consistency and accuracy of the overall room data.

[0089] In addition, if component attribute retrieval fails, a prompt message will be generated and displayed on the front-end user interface. This is to inform users in a timely manner that a problem has occurred during the operation and the required component attributes cannot be obtained, so that users can take appropriate measures, such as checking whether the data is complete or whether the system has malfunctioned. It also avoids subsequent processing errors caused by attribute retrieval failures, ensuring the standardization and accuracy of the entire operation process.

[0090] Based on the above attribute association mechanism, global adjustments to attributes can also be achieved, specifically including:

[0091] Step 1: When a user modifies the component type in a room, iterate through all the component types in all rooms to determine whether other rooms contain the component type to be deleted.

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

[0093] also, Figure 4 This is a schematic diagram illustrating an editing operation of room interior components according to an embodiment of this application, such as... Figure 4 As shown, this application solution allows users to add, modify, and delete drawing areas for the room's acoustic measurement data.

[0094] When a user modifies a component type in a room's properties, a hash table is used to check all components in the room to confirm if the corresponding type exists, and then the modification is applied accordingly. If the modification pertains to a type already present in the room's properties, all room types are checked to determine if the component type is included in the room's properties. If it exists, the property is adjusted to the user-modified value, and the corresponding type entity in the room's entity is updated.

[0095] in addition, Figure 5 This is a schematic diagram of the room outline according to an embodiment of this application, such as... Figure 5 As shown, this application's solution supports the differentiated generation of concrete, masonry, beams, and columns at different locations. The top outlines of concrete walls, brick walls, beams, and columns are acquired and recorded as edge information, along with material information and edge source information. After summarizing all edges, the system takes the largest outer contour as the room outline.

[0096] Additionally, if the inner wall edge generation option is selected, the system will obtain the corresponding wall thickness based on the recorded source information and offset the corresponding edge to the inner wall edge, while simultaneously connecting the surrounding edges. After generating the room outline, the system will generate walls, baseboards, wainscoting, and columns of corresponding materials for each edge based on the room's attribute settings. The generation of floors, ceilings, and suspended ceilings will be based on the room outline. It is particularly important to note that floor generation will be based on the bottom outline of the components to avoid errors when the top and bottom surfaces of the components differ.

[0097] Furthermore, this application also supports a convenient attribute copying function, which allows specific attributes to be quickly applied to other floors. When performing an attribute copying operation, if the target floor does not have a corresponding room, a room with attributes completely identical to the original room will be automatically generated on the target floor. Subsequently, the various attributes within the room will be thoroughly examined. If other types of component attributes exist, their existence will be carefully checked recursively; if they do not exist, the same type of component attribute with the same configuration 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, its attributes will be accurately copied to the target floor, and the attributes of the room on the target floor will then be checked. If other types of component attributes are found, the system will completely copy the configuration of that type to the target floor; if they do not exist, the system will create a version of that type with the same configuration. At the same time, the system will comprehensively check all rooms and components that use this type and seamlessly apply this configuration to the corresponding components on other floors, thereby effectively ensuring the consistency and coordination of the attributes of the entire building model across 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 This is a schematic diagram of the user interface for creating a new room according to an embodiment of this application;

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

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

[0103] Step 4: Modify and delete attributes; Figure 8 This is a schematic diagram of the operation interface for editing attributes according to an embodiment of this application.

[0104] Through steps S101 to S103 above, red-black trees and hash tables are used to quickly locate components by binary search when obtaining their actual attributes, with an average time complexity of O(logn). Hash tables store component types, and ideally, the lookup time is close to O(1). The two work together to avoid tedious operations such as multiple inputs, improving efficiency and accuracy. In addition, relying on the attribute linkage mechanism, when deleting a component type, all room conditions are checked and linked operations are performed to ensure consistent and accurate attributes. When copying attributes, the system can automatically handle the situation according to the target floor and room conditions, reducing manual errors and omissions. Finally, unlike other software that manually arranges and aggregates components, this embodiment first aggregates all attributes and then creates rooms and automatically generates components that meet the conditions, greatly reducing operation steps and time. Performance is guaranteed by combining data structure and algorithm optimization. Efficient data structures are used in combination with optimized algorithms to make reasonable use of system resources, avoid software lag and slow response, and optimize the operation logic flow to reduce unnecessary data reading, writing and calculation, thereby achieving a balance between function and performance and greatly improving modeling efficiency and accuracy.

[0105] It should be noted that the steps shown in the above process or in the flowchart of the accompanying figures 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 may be executed in a different order than that shown here.

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

[0107] The receiving module 90 is used to receive the component selection instruction input by the user, select multiple component types, and obtain the actual attributes corresponding to the component type from the component's cache data, 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 based on the outer envelope of each component type, and to create multiple types of component entities in the room based on the actual attributes and association information of the components.

[0109] The deletion module 92 is used to delete certain component types from the room through an attribute linkage mechanism when a deletion command is received.

[0110] This system utilizes red-black trees and hash tables to quickly locate components by using binary search when obtaining their actual attributes. Ideally, the search should be close enough for the correct location. The two methods work together to avoid tedious operations such as multiple inputs, improving efficiency and accuracy. Furthermore, relying on an attribute linkage mechanism, deleting a component type checks all room conditions and performs linked operations to ensure consistent and accurate attributes. Attribute copying is automatically handled based on the target floor and room conditions, reducing manual errors and omissions. Finally, unlike other software that manually arranges and aggregates components, this embodiment first aggregates all attributes, then creates rooms and automatically generates components that meet the conditions, significantly reducing operation steps and time. Performance is ensured through a combination of data structure and algorithm optimization. Highly efficient data structures combined with optimized algorithms are used to rationally utilize system resources, avoiding software lag and slow response. Simultaneously, the operation logic flow is optimized to reduce unnecessary data reading, writing, and calculations, achieving a balance between functionality and performance, thereby significantly improving modeling efficiency and accuracy.

[0111] In one embodiment, Figure 10 This is a schematic diagram of the internal structure of an electronic device according to an embodiment of this application, such as... Figure 10 As shown, an electronic device is provided, which can be a server, and its internal structure diagram can be as follows. Figure 10As shown, the electronic device includes a processor, a network interface, internal memory, and non-volatile memory connected via an internal bus. The non-volatile memory stores the operating system, computer programs, and a database. The processor provides computing and control capabilities, the network interface communicates with external terminals via a network connection, the internal memory provides an environment for the operation of the operating system and computer programs, the computer programs are executed by the processor to implement a system for rapidly creating interior decoration content in an architectural model, and the database stores data.

[0112] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which 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 different component arrangements.

[0113] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

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

Claims

1. A method for rapidly creating interior decoration content in a building model, characterized in that, The method, applied to BIM civil engineering quantity calculation software, includes: The system receives a component selection instruction from the user, selects multiple component types, and retrieves the actual attributes corresponding to the component types from the component's cached data, wherein the cached data adopts a red-black tree data structure. The association information between multiple component types is determined based on the outer envelope of each component type, and multiple component entities of multiple types are created in the room based on the actual attributes of the components and the association information. Upon receiving a deletion command, the system uses an attribute linkage mechanism to delete certain component types from the room, including: detecting and obtaining all components of the room based on the room's outer envelope and engineering envelope; Obtain the information of the component to be deleted, traverse all components in the room, determine whether there are any related components that match the information of the component to be deleted, and if so, delete the related component; The method further includes: Determine whether the component type to be deleted is a type contained in the room attributes. If so, iterate through the dataset of component types of all rooms to obtain whether the component type to be deleted is contained in other rooms. The dataset is stored using a hash table data structure. If so, set the attribute corresponding to the component to be deleted to empty, and delete the entity of the related component. The cached data adopts a red-black tree structure. If the component attribute retrieval fails, a prompt message is generated and displayed on the front-end user interface. When the component selection instruction is a component name entered by the user, the method further includes: The string table comparison algorithm is used to determine whether there is a matching component with the same name as the component. If so, the actual attributes of the component are obtained from the cached data of the matching component using a binary search algorithm; If not, generate a component that matches the component name according to the local default configuration. When the component is a component of a different material with additional distinctions, generate a component entity of the corresponding material according to the wall type to which the component is attached.

2. The method according to claim 1, characterized in that, Determining whether there are related components that match the type of component to be deleted includes: Based on the attribute information of the component to be deleted, a type comparison is performed in the cached data of all components in the room; Based on the results of the type comparison, the relevant components are identified and deleted, and the visual representation of the relevant components is removed from the front-end user interface.

3. The method according to claim 1, characterized in that, The method further includes: When a user modifies the component type in the room, the component types of all rooms are traversed to determine whether the component type to be deleted is contained in other rooms. If so, adjust the attributes of other rooms corresponding to the component type to be deleted to the values ​​modified by the user, and update the component entities corresponding to the component type in the room.

4. The method according to claim 1, characterized in that, Before selecting multiple component types, the method further includes: Obtain the top outline of all components to get edge information, and obtain the material information and edge source information of all components; The room outline is obtained based on the maximum outer contour of all edge information, 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 outline. Based on the room outline, multiple types of component entities are created in the room according to the actual attribute information of the components and the association information.

5. A system for rapidly creating interior decoration content in a building model, characterized in that, The system includes: a receiving module, a creating module, and a deleting module, wherein: The receiving module is used to receive a component selection instruction input by the user, select multiple component types, and obtain the actual attributes corresponding to the component type from the component's cached data, wherein the cached data adopts a red-black tree data structure; when the component selection instruction is a component name input by the user, The string table comparison algorithm is used to determine whether there is a matching component with the same name as the component. If so, the actual attributes of the component are obtained from the cached data of the matching component using a binary search algorithm; If not, generate a component matching the component name according to the local default configuration. When the component is a component of different materials with additional distinctions, generate a component entity of the corresponding material according to the wall type to which the component is attached. The creation module is used to determine the association information between multiple component types based on the outer envelope of each component type, and to create multiple types of component entities in the room based on the actual attributes of the components and the association information. The deletion module is used to delete certain component types from the room through an attribute linkage mechanism when a deletion instruction is received, including: detecting and obtaining all components of the room based on the room's outer envelope and engineering envelope; Obtain the information of the component to be deleted, traverse all components in the room, determine whether there are any related components that match the information of the component to be deleted, and if so, delete the related component; Determine whether the component type to be deleted is a type contained in the room attributes. If so, iterate through the dataset of component types of all rooms to obtain whether the component type to be deleted is contained in other rooms. The dataset is stored using a hash table data structure. If so, set the attribute corresponding to the component to be deleted to null and delete the entity of the related component. The cached data adopts a red-black tree structure. If the component attribute retrieval fails, a prompt message is generated and displayed on the front-end user interface.

6. 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, it implements the method as described in any one of claims 1 to 4.

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

Images