CN114896792B - Space topological relation analysis and topological network model establishment method for S3D air duct model - Google Patents
Space topological relation analysis and topological network model establishment method for S3D air duct model Download PDFInfo
- Publication number
- CN114896792B CN114896792B CN202210530181.3A CN202210530181A CN114896792B CN 114896792 B CN114896792 B CN 114896792B CN 202210530181 A CN202210530181 A CN 202210530181A CN 114896792 B CN114896792 B CN 114896792B
- Authority
- CN
- China
- Prior art keywords
- current
- feature
- connection
- udpitem
- air duct
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000004458 analytical method Methods 0.000 title claims abstract description 21
- 238000013461 design Methods 0.000 claims abstract description 41
- 238000010276 construction Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 8
- 238000003012 network analysis Methods 0.000 claims description 6
- 238000007670 refining Methods 0.000 claims description 3
- 238000004364 calculation method Methods 0.000 description 10
- 238000007689 inspection Methods 0.000 description 2
- 239000013598 vector Substances 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000010438 heat treatment Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000009423 ventilation Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F30/00—Computer-aided design [CAD]
- G06F30/20—Design optimisation, verification or simulation
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Evolutionary Computation (AREA)
- Geometry (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a space topological relation analysis and topology network model building method for an S3D air duct model, and relates to the technical field of space topology. The S3D air duct model space topological relation analysis and topological network model establishment method provided by the invention provides a method for automatically analyzing the space topological connection relation of the internal elements according to the air duct design model, so that the work of analyzing the space topological connection relation of the elements by an analyzer through observing the design model is avoided, and the working efficiency and the quality are greatly improved.
Description
Technical Field
The invention relates to the technical field of space topology, in particular to a space topology relation analysis and topology network model building method for an S3D air duct model.
Background
S3D is widely used three-dimensional design software; the S3D software is used as integrated multi-specialty participated three-dimensional factory modeling software, can quickly help each specialty designer to carry out three-dimensional modeling and design inspection, and greatly improves the working efficiency and design quality; in the chemical and energy industries, S3D software is widely used and has been the case of numerous successes;
After the design model modeling is completed, a designer in the heating and ventilation profession needs to carry out safety analysis on the designed wind pipe model in a mechanical angle through mechanical analysis and calculation so as to ensure the rationality of the whole design model, and in the process, a corresponding analysis and calculation model needs to be built to carry out development of corresponding work; the analysis calculation model needs to be matched with the actual design model so as to ensure that the calculation result can truly reflect into the design model, so that a large number of original design parameters and space topological structures of the reference design model are needed in the creation process;
S3D software does not provide a mature and available topological relation analysis program for the air duct specialty, so in order to complete the creation of a mechanical analysis calculation model, a designer must manually perform the creation work of a topological relation network of the whole air duct design model according to the design model, and a great deal of working time of related personnel is consumed, and meanwhile, the introduction of human errors is very easy to cause so as to influence the accuracy of analysis results.
Disclosure of Invention
The invention aims to provide a space topological relation analysis and topological network model building method for an S3D air duct model, which aims to solve the problems that the building of a topological relation network in the background technology consumes time and is easy to cause errors.
In order to achieve the above purpose, the present invention provides the following technical solutions:
a method for establishing a topological network model of an S3D air duct model comprises the following steps:
S1, acquiring all air pipes in a project, storing the air pipes into a custom air pipe set HVACRuns, and entering S2 after finishing the operation;
s2, creating an air duct set existRuns to store the air duct objects which have been traversed, and entering S3 after the completion;
s3, creating an air pipe set object errorRuns to store an air pipe object with an error in design, and entering S4 after finishing;
s4, creating an air duct set object extraRuns to store other air ducts connected with the current air duct, and entering S5 after finishing;
S5, creating a custom object UDPItem for storing a topological relation structure of the air duct element, wherein the structure comprises a current element or feature object, coordinate information of the current object and a connection unit set, creating UDPItem an object set ProjectUDPItemList for storing topological relation structures of all air duct objects in the whole project, and entering S6 after the completion of the construction;
S6, circularly traversing all the air pipes, entering S18 if the traversing is completed, and entering S7 if the traversing is not completed;
S7, checking whether the current air pipe is calculated, returning to S6 after calculation is completed, and entering S8 after calculation is not completed;
S8, checking whether a problem exists in the current air pipe, returning to the S6 when the problem exists, and entering the S9 when the problem does not exist;
s9, creating a set UDPItemList for storing the topology network structure information formed by the current air pipes, and entering S10;
s10, carrying out internal topology network analysis on a current air pipe; if the result is successfully finished and stored UDPItemList, acquiring other air duct sets extraRuns which form a Tuo-pu network together with the current air duct, updating existRuns sets, and entering S11; if the middle report is wrong, updating errorRuns sets and then directly entering S14;
s11, circularly traversing extraRuns the set, entering S15 if traversing is completed, and entering S12 if traversing is not completed;
s12, checking whether the current extraRuns has completed calculation in the previous cycle, if yes, returning to S11, and if not, entering S13;
s13, checking whether the current extraRuns is judged to have a problem or not, if yes, returning to S11, and if not, entering S10;
S14, performing error processing on all air pipes in the current whole topological network, and returning to S6 after finishing the error processing;
s15, emptying extraRuns, putting all objects in UDPItemList into ProjectUDPItemList, emptying UDPItemList, and returning to S6;
S16, projectUDPItemList is the topological relation network model of the wind pipe representing the whole acquired project, and the process is finished.
Preferably, in the step S5, the connection unit set is divided into two types, namely a trunk connection unit and a branch connection unit, and each type of connection unit includes the connection object itself and coordinate information of the connection point.
Preferably, in S14, error processing is performed on all the air pipes in the current entire topology network, including the following steps:
s14.1, all objects in existRuns are put into errorRuns, and S14.2 is entered;
s14.2, all objects in extraRuns are put into errorRuns, and S14.3 is entered;
s14.3, emptying existRuns sets, and entering S14.4;
s14.4, emptying extraRuns the set, and entering S14.5;
S14.5, emptying UDPList the set, and entering S14.6;
S14.6, ending.
Preferably, if the storing UDPItemList of the result is successfully completed, acquiring other air duct sets extraRuns which form the topology network together with the current air duct, updating existRuns sets, and entering into S11; if the intermediate report exits, the set is updated errorRuns and then the process directly goes to S15.
Preferably, the topology network analysis comprises the following steps:
S10.1, acquiring all element object sets partCol in the current air duct, and entering S10.2;
s10.2, circularly traversing partCol the collection, completing the traversal, entering S10.49, and completing the traversal without entering S10.3;
S10.3, judging whether the current element currentPart is DuctStockPart type, if yes, entering S10.4, and if not, entering S10.26;
s10.4, finding all connection element sets cpartCol of the current element, circularly traversing cpartCol, wherein the traversing is completed to S10.8, and the traversing is not completed to S10.5;
S10.5, checking whether the air pipe to which the connecting element belongs is in errorRuns, if so, putting the current air pipe into errorRuns set, and directly entering S10.51; if it is not, S10.6 is entered;
S10.6, checking whether the air pipe to which the connecting element belongs is positioned in existRuns, if not, putting the air pipe into extraRuns, and entering S10.7;
S10.7, if the connecting element is DuctStockPart types, considering the structural complexity of the type, the element needs to be thinned into a feature object at the connecting point and stored into a connecting element set connectpartCol of the current object together with the connecting point coordinate, otherwise, the connecting element is directly stored into connectpartCol together with the connecting point coordinate, and the S10.4 is returned;
s10.8, in consideration of the complex structure of the type, finding all features objects features contained under the current element, constructing a topological connection network by taking features as units, and entering S10.9;
S10.9, circularly traversing the features object, returning to S10.2 after traversing is completed, and entering S10.10 after traversing is not completed;
S10.10, if the current feature is a branch point type, entering S10.11, and if the current feature is not a branch point type, entering S10.16;
s10.11, constructing a new UDPItem node for representing the current branch point feature, and putting the coordinates of the feature and the object of the feature into UDPItem; other features with consistent endpoint coordinates and features are found from features, the features are placed on a trunk connection unit of a UDPItem node, the connection coordinates are the coordinates of the current branch features, and S10.12 is entered;
S10.12, finding a branch connection set offlineFeatures corresponding to the branch point feature according to the offlip relation, and entering S10.13;
S10.13, circularly traversing offlineFeatures, wherein the traversing is completed to S10.15, and the traversing is not completed to S10.14;
S10.14, finding out an element corresponding to the current offlineFeatures, if the element is DuctStockPart, putting the current offlineFeatures on a branch connection unit of the UDPItem node, wherein the connection coordinate is the coordinate of the current branch feature, otherwise, putting the element corresponding to offlineFeatures on a branch connection unit of the UDPItem node, and returning to S10.13, wherein the connection coordinate is still the coordinate of the current branch feature;
S10.15, finishing construction of a UDPItem node of the current branch feature, putting the node into UDPItemList, and returning to S10.9;
s10.16, constructing a new UDPItem node for representing the current feature, and placing the coordinates of the feature and the object of the feature into UDPItem; checking whether there is a feature with the same starting point coordinate or end point coordinate as the starting point coordinate of the current feature in the features set according to the starting point coordinate of the current feature, and if so, entering S10.17; if not, go to S10.18;
S10.17, if the number of the found features is greater than one, checking whether branch point features exist, if so, storing the branch point features on a trunk connection unit of a UDP (user datagram protocol) system node, wherein the connection coordinates are the starting point coordinates of the current features, and entering S10.19; if not, the unreasonable repeated connection is represented, the current design error is judged, the current air pipe is put into errorRuns, and S10.50 is directly carried out; if the number of the features found is exactly one, directly storing the features into a trunk connection unit of the UDPItem nodes, wherein the connection coordinate is the starting point coordinate of the current features, and entering S10.19;
S10.18, searching a connecting element consistent with the starting point coordinate of the current feature in connectpartCol, if the connecting element exists, putting the current element into a trunk connecting unit of UDPItem, wherein the connecting coordinate is the starting point coordinate of the current feature, and entering S10.19; if not, directly entering S10.19;
S10.19, checking whether a feature with a consistent starting point coordinate or an end point coordinate and the end point coordinate of the current feature exists in the features set according to the end point coordinate of the current feature, and if so, entering S10.20; if not, go to S10.21;
S10.20, if the number of the found features is greater than one, checking whether branch point features exist, if so, storing the branch point features on a trunk connection unit of a UDPItem node, wherein the connection coordinates are the end coordinates of the current features, and entering S10.22; if not, the unreasonable repeated connection is represented, the current design error is judged, the current air pipe is put into errorRuns, and S10.51 is directly carried out; if the number of the features found is exactly one, directly storing the features into a trunk connection unit of a UDPItem node, wherein the connection coordinate is the endpoint coordinate of the current feature, and entering S10.22;
s10.21, searching a connecting element consistent with the end point coordinate of the current feature in connectpartCol, if the connecting element exists, putting the current element into a trunk connecting unit of UDPItem, wherein the connecting coordinate is the end point coordinate of the current feature, and entering S10.22; if not, directly entering S10.22;
S10.22, checking whether a surface attachment element exists in the current feature, acquiring a corresponding offlineFeatures through an offlip relation, if so, entering S10.23, and if not, directly entering S10.25;
s10.23, circularly traversing offlineFeatures, wherein the traversing is completed to S10.25, and the traversing is not completed to S10.24;
S10.24, finding a wind pipe element corresponding to the current offlineFeatures, putting the wind pipe element on a branch connecting unit of a UDPItem node, and returning to S10.23, wherein the connecting coordinate is the current offlineFeatures coordinate;
s10.25, finishing construction of UDPItem nodes, putting the nodes into UDPItemList, and returning to S10.9;
S10.26, the current object is an air pipe part ductComponent, a UDPItem node is constructed to store a topological logic relationship taking the current element as a unit, the current element and the own coordinates thereof are put into UDPItem, and S10.27 is entered;
s10.27, acquiring all reference endpoint sets referencePorts of the current element, and entering S10.28;
S10.28, circularly traversing referencePorts, wherein the traversing is completed to S10.30, and the traversing is not completed to S10.29;
S10.29, if index of the current port is 1 or 2, creating UDPItem trunk connection units, if index is 1, putting the trunk connection units into a starting point unit, and if index is 2, putting the trunk connection units into an ending point unit, and storing coordinates of the current port into the trunk connection units; if the index of the port is 3 or 4, creating UDPItem branch connection units, storing the coordinates of the current port into the branch connection units, and returning to S10.28;
S10.30, acquiring all connection point information sets connectionCol of the current element, and entering S10.31;
S10.31, circularly traversing connectionCol the collection, wherein the traversing is completed to enter S10.38, and the traversing is not completed to enter S10.32;
S10.32, obtaining DistributionPort corresponding to the current connection point and a connection object connected through the current connection point, checking whether an air pipe to which the current connection object belongs is in a errorRuns set, if so, representing that the air pipe is connected to the air pipe with the wrong design, and if the air pipe has the error, putting the current air pipe into errorRuns, and directly entering S10.51; otherwise, entering S10.33;
S10.33, checking an air duct to which the connecting element belongs, and if the air duct is not the current air duct object or is not in extraRuns sets, putting extraRuns the air duct as an air duct object needing additional calculation, and entering S10.34; otherwise, directly entering S10.34;
S10.34, checking whether the connection object is DuctStockPart types, if so, refining the connection object into a corresponding feature object, entering S10.35, otherwise, entering S10.37;
S10.35, obtaining all feature set features of the connection object, finding a feature set connectedFeatures with the coordinates of the start point or the end point consistent with the coordinates of the current DistributionPort from the feature set features, and entering S10.36;
S10.36, if a plurality of features exist in connectedFeatures, a branch point feature exists, if the branch point feature does not exist, the current air pipe is placed into errorRuns to directly enter S10.51, wherein the current air pipe is represented as having design errors; if so, finding a connection unit consistent with DistributionPort coordinates from the trunk and branch connection units of UDPItem which are already created before, and storing features into the connection unit; otherwise, if only one feature exists in connectedFeatures, finding a connection unit consistent with DistributionPort coordinates from the trunk and branch connection units of UDPItem which are already created before, storing the feature into the connection unit, and returning to S10.31;
S10.37, finding a connection unit consistent with DistributionPort coordinates from the trunk and branch connection units of UDPItem which are already created before, storing the found connection object into the corresponding connection unit, and returning to S10.31;
s10.38, finding a feature object currentFeature corresponding to currentPart, checking whether the starting and ending points of currentFeature are consistent, if yes, representing the consistency as special ENDLEGPART, adjusting the sequence of a trunk unit and a branch unit, entering S10.39, otherwise, directly entering S10.43;
S10.39, checking whether the current UDPItem connecting units are more than or equal to three, if so, entering S10.40, otherwise, directly entering S10.43 without adjusting the sequences of the trunk and the branch units;
S10.40, if the number of the connecting units is three, entering S10.41, and if the number of the connecting units is four, entering S10.42;
S10.41, finding a port with the largest section width from referencePorts corresponding to the three connection units, if the current port corresponds to a terminal connection unit which is not a trunk connection unit, exchanging positions of the connection unit corresponding to the current port and the terminal connection unit of the trunk connection unit, and entering S10.43;
S10.42, two ends of the trunk connecting unit are necessarily collinear, so if vectors formed by connecting the coordinates of two units of the trunk connecting unit with the coordinates of currentPart are not parallel, the trunk connecting unit and the branch connecting unit are completely exchanged in sequence, and S10.43 is performed after the completion; otherwise, directly entering S10.43;
S10.43, for ductwork components, there may be a potential for adhesion to the ductwork surface, looking through ConnHasPorts relations, if such a set of connection points attacheConnCol exists, proceed to S10.44; otherwise, directly entering S10.48;
S10.44, circularly traversing attachConnCol sets, removing objects of non-surface attachment point types, and forming new attachConnCol sets;
S10.45, only one air pipe is attached to one part instead of the air pipe part, so if attachConnCol is more than 1, representing a design error, putting the current air pipe into errorRuns, and directly entering S10.51; otherwise, enter S10.46;
S10.46, finding a feature object currentFeature corresponding to currentPart, creating a new trunk connection unit, wherein the coordinates are currentFeature coordinates, and entering S10.47;
S10.47, finding out the feature attached to the current feature through the offlineFeatures relation of currentFeature, storing the feature into a trunk connection unit created in the last step, and entering S10.48;
S10.48, finishing construction of UDPItem nodes, putting the nodes into UDPItemList, and returning to S10.2;
s10.49, putting the current air pipe into existRuns sets, and entering S10.50;
S10.50, normally ending;
S10.51, reporting error and exiting.
Preferably, in S10.20, if the number of features found is greater than one, checking whether there is a branch point feature, if so, storing the branch point feature on a trunk connection unit of the UDPItem node, where the connection coordinate is the endpoint coordinate of the current feature, and entering S10.22.
Preferably, if the number of features found is greater than one, if there is no branching point feature, which means that there is unreasonable repeated connection, the current design error is determined, the current air duct is put into errorRuns, and the process goes directly to S10.51.
Preferably, if the number of features found is exactly one, the feature number is directly stored in the trunk connection unit of the UDPItem node, the connection coordinate is the endpoint coordinate of the current feature, and the process goes to S10.22.
Preferably, in S10.36, if there are a plurality of features in connectedFeatures and there is a branch point feature, a connection unit with coordinates consistent with DistributionPort is found from the trunk and branch connection units of UDPItem that have been created previously, and the feature is stored in the connection unit.
Preferably, if a plurality of features exist in connectedFeatures and a branch point feature does not exist, representing that the design error exists in the current air duct, putting the current air duct into errorRuns, and directly entering S10.51;
preferably, if there is only one feature in connectedFeatures, a connection unit consistent with DistributionPort coordinates is found from the trunk and branch connection units of UDPItem that have been created previously, and the feature is stored in the connection unit and returned to S10.31.
Compared with the prior art, the invention has the beneficial effects that:
1. The S3D air duct model space topological relation analysis and topological network model establishment method provided by the invention provides a method for automatically analyzing the space topological connection relation of the internal elements according to the air duct design model, so that the work of analyzing the space topological connection relation of the elements by an analyst through observing the design model is avoided, and the working efficiency and quality are greatly improved;
2. The S3D air duct model space topological relation analysis and topological network model establishment method provided by the invention provides a method for automatically constructing an air duct model topological relation network model according to an air duct design model, so that the work of manually carrying out the topological relation network model by an analyst through observing the design model is avoided, and the working efficiency and quality are greatly improved;
3. The space topological relation analysis and topology network model establishment method of the S3D air duct model provided by the invention has a complete error reporting and exiting mechanism and is strong in robustness; meanwhile, in the process of constructing the Tuo Pu network model, design inspection can be carried out on the design model, and the design quality of the air pipe design model is improved;
4. the S3D air duct model space topological relation analysis method and the topological network model establishment method provide a thought for utilizing the data value of the S3D design model, and lay a foundation of a data layer for deep application of the S3D design model to downstream professions.
Drawings
FIG. 1 is a flow chart of an implementation method of the S3D air duct model space topological relation analysis and topological network model establishment method;
FIG. 2 is a schematic flow chart of DuctStockPart elements in the process of analyzing the internal topology network of the air duct according to the present invention;
FIG. 3 is a schematic flow chart of non-DuctStockPart elements in the process of analyzing the internal topology network of the air duct according to the present invention;
fig. 4 is a schematic flow chart of error handling of all air pipes in the topology network of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Referring to fig. 1-4, the present invention provides a technical solution: as shown in fig. 1, the method for establishing the topological network model of the S3D air duct model comprises the following steps:
S1, acquiring all air pipes in a project, storing the air pipes into a custom air pipe set HVACRuns, and entering S2 after finishing the operation;
s2, creating an air duct set existRuns to store the air duct objects which have been traversed, and entering S3 after the completion;
s3, creating an air pipe set object errorRuns to store an air pipe object with an error in design, and entering S4 after finishing;
s4, creating an air pipe set object extra un to store other air pipes connected with the current air pipe, and entering S5 after finishing;
S5, creating a custom object UDPItem for storing a topological relation structure of the air duct element, wherein the structure comprises a current element or feature object, coordinate information of the current object and a connection unit set, wherein the connection unit set is divided into two types of trunk connection units and branch connection units, and each type of connection unit comprises the coordinate information of the connection object and the coordinate information of a connection point. Simultaneously creating UDPItem object set ProjectUDPItemList to store the topological relation structures of all the air duct objects in the whole project for forming a complete topological relation network, and entering S6 after finishing;
S6, circularly traversing all the air pipes, if the traversing is completed, entering S18, otherwise entering S7;
S7, checking whether the current air pipe is calculated, if so, returning to S6, otherwise, entering S8;
s8, checking whether the current air pipe has a problem or not, if so, directly returning to S6, otherwise, entering S9;
s9, creating a set UDPItemList for storing the topology network structure information formed by the current air pipes, and entering S10;
s10, carrying out internal topology network analysis on a current air pipe; if the result is successfully finished and stored UDPItemList, acquiring other air duct sets extraRuns which form a Tuo-pu network together with the current air duct, updating existRuns sets, and entering S11; if the middle report is wrong, updating errorRuns sets and then directly entering S14;
S11, circularly traversing extraRuns sets, if traversing is completed, entering S15, otherwise entering S12;
s12, checking whether the current extraRun has completed calculation in the previous cycle, if yes, returning to S11, otherwise, entering S13;
s13, checking whether the current extraRun is judged to have a problem, if yes, returning to S11, otherwise, entering S10;
S14, performing error processing on all air pipes in the current whole topological network, and returning to S6 after finishing the error processing;
s15, emptying extraRuns, putting all objects in UDPItemList into ProjectUDPItemList, emptying UDPItemList, and returning to S6;
S16, projectUDPItemList is a topological relation network model of the acquired air pipes of the whole project, and the process is finished;
As shown in fig. 2 and fig. 3, according to the internal topology network analysis of the current air duct in S10, if the result is stored UDPItemList successfully, other air duct sets extraRuns which form a topology network together with the current air duct are obtained, and the existRuns sets are updated at the same time, and then the process enters S11; if the intermediate error is reported, the set is updated errorRuns and then directly enters S14, comprising the following steps:
s10.1, acquiring all element object sets partCol in the current air duct currentRun according to OwnsParts relations, and entering S10.2;
s10.2, circularly traversing partCol sets, finishing the traversing, entering S10.61, otherwise entering S10.3;
S10.3, judging whether the current element currentPart is DuctStockPart type, if yes, entering S10.4, otherwise entering S10.36;
s10.4, a component universal connection unit set conObjCol, wherein a connection unit consists of a connection object and a connection coordinate, all connection point sets connectCol of the current element are found from RelConnectionAndPartOcc relation of currentPart, and S10.5 is entered;
S10.5, checking whether the air pipe to which the connecting element belongs is in errorRuns, if so, putting the current air pipe into errorRuns set, and directly entering S10.51; if it is not, S10.6 is entered;
S10.6, finding out two elements associated with the current connection point through the RelConnectionAndPartOcc relation of connection, excluding currentPart, finding out a corresponding connection object connectpart, and entering S10.7;
S10.7, finding a tuber pipe otherRun to which connectpart belongs, checking whether otherRun is in a errorRuns set, if so, putting currentRun into a errorRuns set, and directly entering S10.63; otherwise, entering S10.8;
s10.8, checking whether otherRun is in existRuns, if not, putting the air pipe into extraRuns, and entering S10.9; otherwise, directly entering S10.9;
S10.9, constructing a universal connection unit conObj, storing the coordinates of the port corresponding to the connection into the coordinates of conObj, and entering S10.10 if connectpart is DuctStockPart type; otherwise, connectpart is also stored in conObj, conObj is then stored in conObjCol, and S10.5 is returned;
S10.10, finding out all feature sets corresponding to connectpart, finding out feature sets connectFeatures with consistent starting point coordinates or end point coordinates and corresponding port coordinates of connection, and entering S10.11;
S10.11, if connectFeatures has only one object, store it in conObj, then store conObj in conObjCol, return to S10.5; otherwise, entering S10.12;
S10.12, finding out a feature with the type AlongLegFeature from connectFeatures, wherein the feature represents a branch point feature, storing the branch point feature in conObj, storing conObj in conObjCol, and returning to S10.5;
S10.13, finding an attachment point set attachConnCol with the type CPReAtttachConnection according to the ConnHasPorts relation of currentPart, and entering S10.14;
S10.14, traversing attachConnCol, wherein the completion of traversing is performed to S10.18, otherwise, the process is performed to S10.15;
S10.15, finding out two elements associated with the current attachment relation according to the ConnHasPorts relation of the current attachConn, removing currentPart, finding out a corresponding attachment element ATTACHPART, and entering S10.16;
s10.16, finding a tuber pipe otherRun to which ATTACHPART belongs, checking whether otherRun is in a errorRuns set, if so, putting currentRun into a errorRuns set, and directly entering S10.63; if it is not, S10.17 is entered;
s10.17, checking whether otherRun is in existRuns, if not, putting the air pipe into extraRuns, and returning to S10.14; otherwise, directly returning to S10.14;
S10.18, finding out all features corresponding to the current currentPart, and entering S10.19;
s10.19, circularly traversing the features object, returning to S10.2 after traversing, otherwise entering S10.20;
S10.20, if the current feature is AlongLegFeature and the coordinates of the starting point and the ending point are consistent, the current feature is represented as a branch point feature, the process goes to S10.21, and otherwise, the process goes to S10.26;
S10.21, constructing a new UDPItem node for representing the current currentFeature topological relation, and placing the coordinate of currentFeature and the object of the coordinate into UDPItem; features with consistent starting and ending point coordinates and currentFeature coordinates are found from features, the features are put on a trunk connection unit of a UDPItem node, the connection coordinates are currentFeature coordinates, and S10.22 is entered;
S10.22, finding a branch connection set offlineFeatures corresponding to the branch point feature from the offlineFeatures relation of currentFeature, and entering S10.23;
S10.23, circularly traversing offlineFeatures, wherein the completion of traversing is performed to S10.25, otherwise, the process is performed to S10.24;
S10.24, finding out an element corresponding to the current offlineFeatures, if the element is DuctStockPart, putting the current offlineFeatures on a branch connection unit of the UDPItem node, wherein the connection coordinate is the coordinate of currentFeature, otherwise, putting the element corresponding to offlineFeatures on the branch connection unit of the UDPItem node, and returning to S10.23, wherein the connection coordinate is still the coordinate of currentFeature;
s10.25, finishing the construction of the UDPItem node of the current currentFeature, putting the UDPItem node into UDPItemList, and returning to S10.19;
S10.26, constructing a new UDPItem node for representing the current currentFeature topological relation, and placing the coordinate of currentFeature and the object of the coordinate into UDPItem; checking whether a feature with the same starting point coordinate or end point coordinate as the current currentFeature exists in the features set according to the current currentFeature starting point coordinate, and if so, entering S10.27; if not, go to S10.28;
S10.27, if the number of the found features is greater than one, checking whether a branch point feature exists, if so, storing the branch point feature on a trunk connection unit of a UDPItem node, wherein the connection coordinate is the starting point coordinate of the current currentFeature, and entering S10.29; if not, the unreasonable repeated connection is represented, the current design error is judged, currentRun is put into errorRuns, and S10.63 is directly carried out; if the number of features found is exactly one, directly storing the feature number into a trunk starting point connecting unit of a UDPItem node, wherein the connecting coordinate is the starting point coordinate of the current feature, and entering S10.29;
s10.28, searching a connecting unit conObj consistent with the starting point coordinate of currentFeature in conObjCol, if the connecting unit exists, placing the element in conObj on a trunk starting point connecting unit of UDPItem, connecting the starting point coordinate with the starting point coordinate of currentFeature, and entering S10.29; if not, directly entering S10.29;
S10.29, checking whether a feature with a consistent starting point coordinate or an end point coordinate and currentFeature end point coordinate exists in the features set according to the end point coordinate of currentFeature, and if so, entering S10.30; if not, go to S10.31;
S10.30, if the number of the found features is greater than one, checking whether a branch point feature exists, if so, storing the branch point feature on a trunk end point connection unit of a UDPItem node, connecting an end point coordinate with a coordinate of currentFeature, and entering S10.32; if not, the unreasonable repeated connection is represented, the current design error is judged, currentRun is put into errorRuns, and S10.63 is directly carried out; if the number of features found is exactly one, directly storing the features into a trunk end point connecting unit of UDPItem nodes, connecting end point coordinates with the coordinates of currentFeature, and entering S10.32;
S10.31, searching a connecting unit conObj consistent with the end point coordinate of currentFeature in conObjCol, if the connecting unit exists, placing the element in conObj on a trunk end point connecting unit of UDPItem, connecting the start point coordinate with the end point coordinate of currentFeature, and entering S10.32; if not, directly entering S10.32;
S10.32, obtaining DistributionPort corresponding to the current connection point and a connection object connected through the current connection point, checking whether an air pipe to which the current connection object belongs is in a errorRuns set, if so, representing that the air pipe is connected to the air pipe with the wrong design, and if the air pipe has the error, putting the current air pipe into errorRuns, and directly entering S10.51; otherwise, entering S10.33;
s10.33, circularly traversing offlineFeatures, wherein the completion of traversing is performed to S10.35, otherwise, the process is performed to S10.34;
S10.34, finding a wind pipe element corresponding to the current offlineFeatures, putting the wind pipe element on a branch connection unit of a UDPItem node, and returning to S10.33, wherein the connection coordinates are those of the current offlineFeatures;
S10.35, finishing construction of UDPItem nodes, putting the nodes into UDPItemList, and returning to S10.19;
S10.36, if a plurality of features exist in connectedFeatures, a branch point feature exists, if the branch point feature does not exist, the current air pipe is placed into errorRuns to directly enter S10.51, wherein the current air pipe is represented as having design errors;
S10.37, acquiring all reference endpoint sets referencePorts of the current element, and entering S10.38;
S10.38, circularly traversing referencePorts, wherein the completion of traversing is performed to S10.40, otherwise, the process is performed to S10.39;
S10.39, if index of the current port is 1 or 2, if index is 1, creating a trunk connection starting point unit, if index is 2, creating a trunk connection ending point unit, and storing coordinates of the current port into the trunk connection ending point unit; if index of the port is 3 or 4, creating UDPItem branch connection units, storing the coordinates of the current port into the branch connection units, and returning to S10.38;
S10.40, acquiring all connection point information sets connectionCol according to the RelConnectionAndPartOcc relation of ductComponent, and entering S10.41;
s10.41, circularly traversing connectionCol the set, wherein the completion of traversing is performed to S10.51, otherwise, the process is performed to S10.42;
S10.42, obtaining DistributionPort corresponding to the current connection point connection, finding out two objects connected by the connection according to the RelConnectionAndPartOcc relation of the connection, obtaining a connection object connectpart after ductComponent is eliminated, and entering S10.43;
S10.43, finding a tuber pipe otherRun to which connectpart belongs, checking whether otherRun is in a errorRuns set, if so, putting currentRun into a errorRuns set, and directly entering S10.63; otherwise, entering S10.44;
S10.44, checking whether otherRun is in existRuns, if not, putting the air pipe into extraRuns, and entering S10.45; otherwise, directly entering S10.45;
S10.45, only one air pipe is attached to one part instead of the air pipe part, so if attachConnCol is more than 1, representing a design error, putting the current air pipe into errorRuns, and directly entering S10.51; otherwise, enter S10.46;
s10.46, obtaining all feature set features of connectpart, finding a feature set connectedFeatures with the coordinates of the start point or the end point consistent with the coordinates of the current DistributionPort from the feature set features, and entering S10.47;
S10.47, if connectedFeatures has a plurality of features, entering S10.48; if there is only one feature, go to S10.49;
S10.48, finding a branch point feature in connectedFeatures, if the branch point feature does not exist, representing that the design error exists in the current air pipe, putting the current air pipe into errorRuns, and directly entering S10.62; if so, finding a connection unit consistent with DistributionPort coordinates from the trunk and branch connection units of UDPItem which are already created before, storing the branch point feature into the connection unit, and returning to S10.41;
S10.49, finding a connection unit consistent with DistributionPort coordinates from the trunk and branch connection units of UDPItem which are already created before, storing the unique feature in connectedFeatures into the connection unit, and returning to S10.41;
S10.50, finding a connection unit consistent with DistributionPort coordinates from the trunk and branch connection units of UDPItem which are already created before, storing connectpart into the corresponding connection unit, and returning to S10.41;
S10.51, finding a feature object currentFeature corresponding to currentPart, checking whether the starting and ending points of currentFeature are consistent, if yes, representing the consistency as special ENDLEGPART, adjusting the sequence of a trunk unit and a branch unit, entering S10.52, otherwise, directly entering S10.56;
s10.52, checking whether the created connection units of the current UDPItem are more than or equal to three, if so, entering S10.53, otherwise, directly entering S10.56 without adjusting the sequence of the trunk and the branch units;
s10.53, if the number of the connecting units is three, entering S10.54, and if the number of the connecting units is four, entering S10.55;
S10.54, finding a port with the largest section width from referencePorts corresponding to the three connection units, if the current port is not a trunk connection terminal unit, exchanging positions of the connection unit corresponding to the current port and the trunk connection terminal unit, and entering S10.56; otherwise, directly entering S10.56;
S10.55, two ends of the trunk connecting unit are necessarily collinear, so if vectors formed by connecting the coordinates of two units of the trunk connecting unit with the coordinates of currentPart are not parallel, the trunk connecting unit and the branch connecting unit are completely exchanged in sequence, and S10.56 is performed after the completion; otherwise, directly entering S10.56;
S10.56, for ductwork components, there may be a possibility of attachment to the ductwork surface, looking up a set attachConnCol of attachment points of the type CPRteAtttachConnection by means of the ConnHasPorts relationship of currentPart, if such a set attachConnCol of attachment points is present, proceeding to S10.57; otherwise, directly entering S10.60;
S10.57, only one air pipe is attached to one part, so if attachConnCol is more than 1, representing a design error, putting the current air pipe into errorRuns, and directly entering S10.63; otherwise, entering S10.58;
S10.58, finding a feature object currentFeature corresponding to currentPart, creating a new trunk connection unit, wherein the coordinates are currentFeature coordinates, and entering S10.59;
s10.59, finding out the feature attached to the current feature through the offlin Features relation of currentFeature, storing the feature into a trunk connection unit created in the last step, and entering S10.60;
s10.60, finishing construction of UDPItem nodes, putting the nodes into UDPItemList, and returning to S10.2;
S10.61, putting the current air pipe into existRuns sets, and entering S10.62;
s10.62, normally ending;
S10.63, reporting error and exiting;
As shown in fig. 3, according to the step S14, performing error processing on all the air pipes in the current entire topology network, including the following steps:
s14.1, all objects in existRuns are put into errorRuns, and S14.2 is entered;
s14.2, all objects in extraRuns are put into errorRuns, and S14.3 is entered;
s14.3, emptying existRuns sets, and entering S14.4;
s14.4, emptying extraRuns the set, and entering S14.5;
S14.5, emptying UDPList the set, and entering S14.6;
S14.6, ending;
According to the invention, through analyzing and analyzing all air pipe elements in the S3D air pipe model, the space topological relation analysis of the air pipe model is automatically carried out, and the topological relation connecting network model which takes the air pipe parts and the smallest units as the smallest units is automatically built, so that the work of manually building the air pipe model topological relation network model by design and analysis staff according to an observation design model is avoided, the working efficiency is greatly improved, and meanwhile, the human error caused by manual analysis can be avoided in the full-automatic generation process, and the quality of related work is further improved.
Although embodiments of the present invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made therein without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (10)
1. A method for establishing a topological network model of an S3D air duct model is characterized by comprising the following steps:
Acquiring all air pipes in the project and storing the air pipes into a custom air pipe set HVACRuns;
creating an air duct set existRuns to store air duct objects;
Creating a custom object UDPItem for storing a topological relation structure of the air duct element, and creating a UDPItem object set ProjectUDPItemList for storing the topological relation structures of all air duct objects in the whole project to form a complete topological relation network;
Circulating all air pipes to check the current air pipe;
creating a set UDPItemList for storing network structure information formed by the current air pipes;
Performing internal topology network analysis on the current air pipe, if the analysis is successfully completed, storing UDPItemList the result, acquiring other air pipe sets extraRuns which form a network together with the current air pipe, and updating existRuns sets; if the middle report is wrong, updating errorRuns sets;
Looping through extraRuns the collection, looking at the current extraRuns;
Performing error processing on all air pipes in the current whole topological network;
Empty extraRuns, put all objects in UDPItem List into ProjectUDPItemList, empty UDPItemList;
ProjectUDPItemList represents an acquired topological relation network model of the air pipes of the whole project.
2. The method for building a topological network model of an S3D air duct model according to claim 1, wherein the topological relation structure comprises a current element or feature object, coordinate information of the current object, and a set of connection units.
3. The method for building a topological network model of an S3D air duct model according to claim 1, wherein the set of connection units is divided into two types, namely a trunk connection unit and a branch connection unit, and each type of connection unit includes coordinate information of a connection object and a connection point.
4. The method for building a topological network model of an S3D air duct model according to claim 1, wherein performing topological network analysis to obtain other air duct sets extraRuns and updating existRuns sets comprises the steps of:
acquiring all connecting element object sets partCol in the current air pipe;
Looping through partCol the collection, the current element being currentPart, determining if the current element currentPart is DuctStockPart type; selecting a feature object for refining the element to a point of connection, refining the element to a feature object at a point of connection, storing the feature object and the point coordinates in a current object's connection element set connectPartCol
Checking whether the air pipe to which the connecting element belongs is in errorRuns, and putting the current air pipe into errorRuns set;
Finding all features objects features contained under the current element; circularly traversing the features object, and judging whether the current feature is a branch point type or not;
constructing a new UDPItem node, and placing the coordinates of feature and the object of feature into UDPItem;
Finding a branch connection set offlineFeatures corresponding to the branch point feature according to the offlip relation; circularly traversing offlineFeatures, finding out an element corresponding to the current offlineFeature, and judging whether the element is DuctStockPart;
The UDPItem node construction of the current branch feature is completed, and the coordinates of the feature and the object of the feature are put into UDPItem;
if the number of features found is greater than one, checking whether there are branch points features in it;
Searching a connection element consistent with the starting point coordinate of the current feature in connectPartCol; checking whether a feature with a consistent starting point coordinate or end point coordinate and the end point coordinate of the current feature exists in the feature set; and checks whether there is a branch point feature;
checking whether a surface attachment element exists in the current feature, and acquiring a corresponding offlienFeatures through an offlip relation;
Finding out an air pipe element corresponding to the current offlineFeature, and circularly traversing offlineFeatures; the current object is an air pipe part ductComponent, a UDPItem node is constructed to store a topological logic relationship taking the current element as a unit, and the current element and the self coordinates thereof are put into UDPItem;
Acquiring all reference endpoint sets referencePorts and all connection point information sets connectionCol of the current element, and circularly traversing referencePorts sets and connectionCol sets;
DistributionPort corresponding to the current connection point and a connection object connected through the current connection point are obtained, and whether the air pipe to which the current connection object belongs is in a errorRuns set or not is checked;
checking the air pipe to which the connecting element belongs; checking whether the connection object is DuctStockPart types;
All feature sets feature of the connection object are acquired, and feature set connectedFeatures whose start or end coordinates agree with the current DistributionPort coordinates is found from them.
5. The method for creating a topological network model of an S3D air duct model according to claim 4, wherein a feature set connectedFeatures having a start point or end point coordinate consistent with the current DistributionPort coordinates is found, and then whether a branch point feature exists is determined if a plurality of features exist in connectedFeatures;
Finding a connection unit consistent with DistributionPort coordinates from the trunk and branch connection units of UDPItem which are already created before, and storing the found connection object into the corresponding connection unit;
finding currentPart a corresponding feature object currentFeature, and checking whether the starting and ending points of currentFeature are consistent; checking whether the current UDPItem connection units are more than or equal to three;
looking through ConnHasPorts relationships, if such a set of connection points attacheConnCol exists;
circularly traversing attachConnCol sets, removing objects of non-surface attachment point types, and forming new attachConnCol sets;
finding currentPart a feature object currentFeature corresponding to the feature object, and creating a new trunk connection unit, wherein the coordinates are currentFeature coordinates;
Finding out the feature attached to the current feature through the OffLineFeatures relation of currentFeature, and storing the feature into the trunk connection unit created in the last step;
The UDPItem node is built and put into UDPItemList.
6. The method for building a topological network model of an S3D air duct model according to claim 4, wherein whether the element is DuctStockPart is determined, if the element is DuctStockPart, the current offlineFeature is put into a branch connection unit of UDPItem nodes, the connection coordinate is the coordinate of the current branch feature, otherwise, the element corresponding to offlineFeature is put into a branch connection unit of UDPItem nodes, and the connection coordinate is still the coordinate of the current branch feature.
7. The method for building the topological network model of the S3D air duct model according to claim 4, wherein if the features are consistent in the features set, the found number is more than one, whether the branch point features exist in the features is checked, if yes, the branch point features are stored in a trunk connection unit of a UDPItem node, and the connection coordinates are the end coordinates of the current features;
If the number of features found is exactly one, the feature number is directly stored in a trunk connection unit of the UDPItem nodes, and the connection coordinates are the end coordinates of the current features.
8. The method for building a topological network model of an S3D air duct model according to claim 7, wherein if the number of features found is greater than one, wherein there is no branching point feature, which means that there is unreasonable repeated connection, the current design error is determined, the current air duct is put into erroRuns, and the process is ended.
9. The method of claim 5, wherein if connectedFeatures has a plurality of features and there is a branch point feature, a connection unit with coordinates consistent with Distribution Port is found from the trunk and branch connection units of UDPItem that have been created before, and the feature is stored in the connection unit.
10. The method for establishing the topological network model of the S3D air duct model according to claim 1, wherein all air ducts in the current whole topological network are subjected to error processing, and the method comprises the following steps:
placing all objects in existRuns into errorRuns;
placing all objects in extraRuns into errorRuns;
clearing existRuns sets;
clearing extraRuns sets;
The UDPList sets were emptied.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210530181.3A CN114896792B (en) | 2022-05-16 | 2022-05-16 | Space topological relation analysis and topological network model establishment method for S3D air duct model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210530181.3A CN114896792B (en) | 2022-05-16 | 2022-05-16 | Space topological relation analysis and topological network model establishment method for S3D air duct model |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114896792A CN114896792A (en) | 2022-08-12 |
| CN114896792B true CN114896792B (en) | 2024-06-21 |
Family
ID=82724554
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210530181.3A Active CN114896792B (en) | 2022-05-16 | 2022-05-16 | Space topological relation analysis and topological network model establishment method for S3D air duct model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114896792B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468353A (en) * | 2014-12-26 | 2015-03-25 | 深圳市新格林耐特通信技术有限公司 | SDN based data center network flow management method |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105468869B (en) * | 2015-12-22 | 2021-03-30 | 上海核工程研究设计院 | Topological relation analysis method of PDS model |
| CN106169749B (en) * | 2016-07-28 | 2019-01-01 | 许继集团有限公司 | The modeling method and system of related information topological analysis in a kind of power distribution network |
| CN107133083B (en) * | 2017-04-13 | 2020-01-17 | 大连理工大学 | Virtual data center resource providing method based on virtualization technology |
| CN107591802A (en) * | 2017-09-15 | 2018-01-16 | 云南电网有限责任公司 | A kind of abstract method of calibration of distribution network model |
| CN110109999B (en) * | 2019-05-24 | 2023-06-20 | 上海核工程研究设计院股份有限公司 | System for converting SMART3D three-dimensional model into FlowMaster model and conversion method |
| CN112182871B (en) * | 2020-09-23 | 2024-04-09 | 上海核工程研究设计院股份有限公司 | System and method for converting three-dimensional pipeline model into MapGIS model |
| CN112165405B (en) * | 2020-10-13 | 2022-04-22 | 中国人民解放军国防科技大学 | Method for testing big data processing capacity of supercomputer based on network topological structure |
-
2022
- 2022-05-16 CN CN202210530181.3A patent/CN114896792B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468353A (en) * | 2014-12-26 | 2015-03-25 | 深圳市新格林耐特通信技术有限公司 | SDN based data center network flow management method |
Non-Patent Citations (1)
| Title |
|---|
| 通风网络拓扑关系的自动建立研究;郝宪杰;魏连江;张宏捷;;煤矿安全;20081110(第11期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114896792A (en) | 2022-08-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110705078B (en) | Simulation model development system and analysis method of nuclear power plant | |
| CN109146711A (en) | A method of comprehensive utilization BIM technology and 3D laser scanning system Optimizing construction | |
| CN111353202B (en) | Partitioning method for underground pipe network general investigation in municipal administration | |
| CN109272571B (en) | System and method for converting PDS three-dimensional data into Flowmaster model | |
| CN115080681B (en) | GIS data checking method and system | |
| CN105468869A (en) | Topological relation analysis method of PDS (Plant Design System) model | |
| CN112712441A (en) | Automatic carding method for topological relation of urban' network river | |
| CN112907026A (en) | Comprehensive evaluation method based on editable mesh index system | |
| CN112651057A (en) | Automatic building system and method for railway concrete filled steel tube tied arch bridge BIM model | |
| CN106777687A (en) | The CAD/CAE integrated approaches and system of a kind of nuclear power plant's support steel structure | |
| CN114896792B (en) | Space topological relation analysis and topological network model establishment method for S3D air duct model | |
| CN112182871A (en) | System and method for converting three-dimensional pipeline model into MapGIS model | |
| CN113946926A (en) | System and implementation method for analyzing breakage influence of S3D high-energy pipeline | |
| CN111553041B (en) | Gas pipe network parameter calibration method, system, terminal and storage medium | |
| CN105045804A (en) | Disassembly sequencing planning (DSP) method for large-size complicated product and DSP system for large-size complicated product | |
| CN109117564B (en) | System and method for converting PDS three-dimensional model into RELAP5 model | |
| CN110795390A (en) | System and method for converting S3D model into RELAP5 model | |
| CN114692495A (en) | Efficient complex system reliability evaluation method based on reliability block diagram | |
| CN111798564A (en) | PDS three-dimensional model conversion system and implementation method thereof | |
| CN112598781A (en) | Modeling method for three-dimensional laser point cloud data of cable work well | |
| Sun et al. | Parallel software testing sequence generation method based on state pruning | |
| CN117312608B (en) | Depth-first search-based river network node degeneracy method | |
| CN117290798B (en) | Method, system and chip for overhauling abnormal data in topology data of gas pipe network | |
| CN111324921B (en) | Grasshopper-based parametric modeling method for spatial circular steel tube intersecting welding nodes | |
| CN115270250B (en) | BIM-based automatic checking method, system and medium for basic large sample detailed diagram |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: No. 29 Hong Cao Road, Xuhui District, Shanghai Applicant after: Shanghai Nuclear Engineering Research and Design Institute Co.,Ltd. Address before: No. 29 Hong Cao Road, Xuhui District, Shanghai Applicant before: SHANGHAI NUCLEAR ENGINEERING RESEARCH & DESIGN INSTITUTE Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant |