Method and system for converting PDS model data into S3D model data, readable medium and S3D model construction method

Abstract

The invention provides a method and system for converting PDS model data into S3D model data, a readable medium and an S3D model construction method, and relates to the technical field of data conversion. The method for converting the PDS model data into the S3D model data comprises the following steps that the PDS model data are obtained through PDS software, and the PDS model data comprise a plurality of RectangularSolid nodes and a plurality of Cylinder nodes; and respectively replacing each RectangularSolid node and each Cylinder node with a corresponding newParametric node, so as to obtain the S3D model data corresponding to the PDS model data. According to the method for converting the PDS model data into the S3D model data, the PDS model data of the non-parametric equipment can be efficiently and accurately converted into the S3D model data.

Description

Methods, systems, and readable media for converting PDS model data into S3D model data, as well as methods for constructing S3D models. Technical Field

[0001] This application mainly relates to the field of data conversion technology, and in particular to a method, system, and readable medium for converting PDS model data into S3D model data, as well as an S3D model construction method. Background Technology

[0002] PDS (Plant Design System) software, a long-established computer-aided design and engineering application, has been widely used in design projects by owners, operators, engineering procurement and construction companies, and their suppliers worldwide since the 1980s. PDS's multidisciplinary collaboration capabilities allow users to work simultaneously on projects, effectively improving the efficiency of 3D plant modeling and design review. However, over time, PDS's interface has become outdated, and its data processing and digital integration capabilities have struggled to keep pace with the demands of the global market.

[0003] Correspondingly, there are still a large number of onshore processes and power plants whose model data are still in the older PDS format due to their age. With the rapid decline in PDS expertise and the cessation of support for PDS by its developer Hexgon, if these old power plants need to be renovated or built-up, it is necessary to consider converting the existing PDS model data into other formats, whether from the perspective of product performance or economic benefits.

[0004] Furthermore, even when converted to other formats, the PDS model data corresponding to non-parametric devices still suffers from fragmented data information, hindering subsequent model use and adjustments. Non-parametric devices refer to those constructed using basic elements such as cubes and cylinders when a suitable physical form is unavailable.

[0005] Therefore, there is an urgent need for a method to convert PDS model data into S3D model data, so as to efficiently and accurately convert PDS model data of non-parametric devices into S3D model data corresponding to parametric devices. Summary of the Invention

[0006] The technical problem to be solved by this application is to provide a method for converting PDS model data into S3D model data, which can efficiently and accurately convert PDS model data of non-parametric devices into S3D model data of parametric devices.

[0007] To address the aforementioned technical issues, this application provides a method for converting PDS model data into S3D model data, comprising the following steps: acquiring PDS model data using PDS software, wherein the PDS model data includes multiple RectangularSolid nodes and Cylinder nodes; replacing each RectangularSolid node and Cylinder node with the corresponding newParametric node to obtain the S3D model data corresponding to the PDS model data.

[0008] Optionally, the PDS model data corresponds to a target device model. The PDS model data is in XML format and contains a unique identification tag associated with the corresponding target device model.

[0009] Optionally, the PDS model data includes a DesignEquipment node, under which there are multiple EquipmentItems nodes, and each EquipmentItems node has a RectangularSolid node or a Cylinder node. The step of replacing each RectangularSolid node and Cylinder node with the corresponding newParametric node to obtain the S3D model data corresponding to the PDS model data further includes: replacing each RectangularSolid node with the corresponding newParametric node; replacing each Cylinder node with the corresponding newParametric node; determining whether each EquipmentItems node has a DatumPoint node, and if the determination result is yes, deleting the DatumPoint node under the EquipmentItems node.

[0010] Optionally, the step of replacing each RectangularSolid node with the corresponding newParametric node further includes: for each RectangularSolid node, constructing a newParametric node under the corresponding EquipmentItems node, and writing the data in the RectangularSolid node into the newParametric node; for each RectangularSolid node, creating a HoleShape attribute in the newParametric node corresponding to the RectangularSolid node, and writing a first preset value to the HoleShape attribute; and deleting all RectangularSolid nodes.

[0011] Optionally, the data in the RectangularSolid node includes the values ​​corresponding to the Length_1 attribute, the Length_2 attribute, and the Length_3 attribute.

[0012] Optionally, the step of replacing each Cylinder node with the corresponding newParametric node further includes: for each Cylinder node, constructing a newParametric node under the corresponding EquipmentItems node, and writing the data in the Cylinder node into the newParametric node; for each Cylinder node, creating a HoleShape attribute in the newParametric node corresponding to the Cylinder node, and writing a second preset value to the HoleShape attribute; and deleting all Cylinder nodes.

[0013] Optionally, the data in the Cylinder node includes the values ​​corresponding to the Diameter attribute and the Length attribute.

[0014] Optionally, before replacing each RectangularSolid node and Cylinder node with the corresponding newParametric node to obtain the S3D model data corresponding to the PDS model data, the method further includes: for each RectangularSolid node, determining whether the data in the RectangularSolid node is missing; if the determination result is yes, then the RectangularSolid node is taken as the RectangularSolid node to be completed; for each RectangularSolid node to be completed, writing multiple real parameter values ​​corresponding to the RectangularSolid node to be completed from the dataset into the RectangularSolid node to be completed.

[0015] Optionally, the PDS model data corresponds to a target device model. The step of completing the data in all the RectangularSolid nodes to be completed based on the database corresponding to the PDS software further includes: obtaining the model number name of the target device model in the PDS software and the node ID corresponding to each RectangularSolid node to be completed; obtaining a data set from the database based on the model number name and node ID, the data set containing multiple real parameter values ​​corresponding to all the RectangularSolid nodes to be completed; and completing the data in each RectangularSolid node to be completed based on the data set.

[0016] Optionally, the database includes the SQL Server database bound to the PDS software.

[0017] To address the aforementioned technical problems, this application provides an S3D model construction method, comprising the following steps: obtaining S3D model data according to the method described above for converting PDS model data into S3D model data; and constructing the corresponding S3D model in S3D software based on the S3D model data.

[0018] To address the aforementioned technical problems, this application provides a system for converting PDS model data into S3D model data, comprising: a memory for storing instructions executable by a processor; and a processor for executing the instructions to implement the aforementioned method for converting PDS model data into S3D model data.

[0019] To address the aforementioned technical problems, this application provides a computer-readable medium storing computer program code, which, when executed by a processor, implements the method for converting PDS model data into S3D model data.

[0020] Compared with the prior art, this application has the following advantages: by replacing each RectangularSolid node and Cylinder node in the PDS model data with the corresponding newParametric node, the data stored in the scattered RectangularSolid nodes and Cylinder nodes in the PDS model data corresponding to the non-parametric device can be stored in the corresponding newParametric node in the S3D model data. This enables the S3D software to convert the non-parametric device into the corresponding parametric device when running the S3D model data, which facilitates the subsequent use and adjustment of the corresponding model. Attached Figure Description

[0021] The accompanying drawings are included to provide a further understanding of this application. They are incorporated into and constitute a part of this application. The drawings illustrate embodiments of this application and, together with this specification, serve to explain the principles of this application. In the drawings: Figure 1 is a flowchart illustrating a method for converting PDS model data into S3D model data according to an embodiment of this application; Figure 2 is a flowchart illustrating a sub-step of step S13 in Figure 1; Figure 3 is a flowchart illustrating a sub-step of step S14 in Figure 1; Figure 4 is a flowchart illustrating a sub-step of step S141 in Figure 3; Figure 5 is a flowchart illustrating a sub-step of step S142 in Figure 3; Figure 6 is a flowchart illustrating an S3D model construction method according to an embodiment of this application; and Figure 7 is a block diagram of a system for converting PDS model data into S3D model data according to an embodiment of this application. Detailed Implementation

[0022] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are merely some examples or embodiments of this application. For those skilled in the art, these drawings can be applied to other similar scenarios without creative effort. Unless obvious from the context or otherwise specified, the same reference numerals in the drawings represent the same structures or operations.

[0023] As indicated in this application and claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" are not specifically singular and may include plural forms. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of explicitly identified steps and elements, which do not constitute an exclusive list, and the method or apparatus may also include other steps or elements.

[0024] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of this application. It should also be understood that, for ease of description, the dimensions of the various parts shown in the drawings are not drawn to actual scale. Techniques, methods, and devices known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and devices should be considered part of the specification. In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters in the following drawings denote similar items; therefore, once an item is defined in one drawing, it need not be further discussed in subsequent drawings.

[0025] In the description of this application, it should be understood that the orientation or positional relationship indicated by directional terms such as "front, back, up, down, left, right", "horizontal, vertical, horizontal" and "top, bottom" is usually based on the orientation or positional relationship shown in the accompanying drawings, and is only for the convenience of describing this application and simplifying the description. Unless otherwise stated, these directional terms do not indicate or imply that the device or element referred to must have a specific orientation or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation on the scope of protection of this application; the directional terms "inner" and "outer" refer to the inner and outer contours relative to the outline of each component itself.

[0026] For ease of description, spatial relative terms such as "above," "on top of," "on the upper surface of," "above," etc., are used herein to describe the spatial positional relationship of a device or feature as shown in the figures to other devices or features. It should be understood that spatial relative terms are intended to encompass different orientations in use or operation beyond the orientation of the device as described in the figures. For example, if the device in the figures were inverted, a device described as "above" or "on top of" other devices or structures would subsequently be positioned as "below" or "under" other devices or structures. Thus, the exemplary term "above" can include both "above" and "below." The device may also be positioned in other different ways (rotated 90 degrees or in other orientations), and the spatial relative descriptions used herein will be interpreted accordingly.

[0027] Furthermore, it should be noted that the use of terms such as "first" and "second" to define components is merely for the purpose of distinguishing the corresponding components. Unless otherwise stated, these terms have no special meaning and therefore should not be construed as limiting the scope of protection of this application. In addition, although the terminology used in this application is selected from commonly known and used terms, some terms mentioned in this application's specification may have been chosen by the applicant according to his or her judgment, and their detailed meanings are explained in the relevant sections of this description. Moreover, this application should be understood not only through the actual terms used, but also through the meaning implied by each term.

[0028] It should be understood that when a component is referred to as "on another component," "connected to another component," "coupled to another component," or "in contact with another component," it can be directly on, connected to, coupled to, or in contact with that other component, or there may be an intervening component. In contrast, when a component is referred to as "directly on another component," "directly connected to," "directly coupled to," or "directly in contact with" another component, there is no intervening component. Similarly, when a first component is referred to as "electrically contacting" or "electrically coupled to" a second component, there is an electrical path between the first and second components that allows current to flow. This electrical path may include capacitors, coupled inductors, and / or other components that allow current to flow, even if there is no direct contact between the conductive components.

[0029] Flowcharts are used in this application to illustrate the operations performed by the system according to embodiments of this application. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, various steps can be processed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more steps may be removed from these processes.

[0030] Referring to Figure 1, an embodiment of this application proposes a method 100 for converting PDS model data into S3D model data (hereinafter referred to as conversion method 100). In this embodiment, the PDS model data corresponds to a target device model, and the target device model is a non-parametric device. In this embodiment, conversion method 100 can convert the PDS model data corresponding to the target device model into S3D model data, and the S3D model data can generate an S3D model corresponding to the target device model in S3D software. It should be noted that the non-parametric device uses multiple cube elements and cylinder elements to construct its corresponding shape in the PDS software. Accordingly, in this embodiment, the PDS model data includes a DesignEquipment node, under which there are multiple EquipmentItems nodes, and each EquipmentItems node has a RectangularSolid node or a Cylinder node. Each RectangularSolid node corresponds to a cube element, and each Cylinder node corresponds to a cylinder element. It should be noted that, through research, the applicant determined that S3D (Smart 3D) software offers better flexibility, interconnectivity, and scalability compared to other software. Furthermore, the intelligent features and open secondary development interfaces of S3D software, combined with its excellent automation programs and data interfaces, not only reduce human design errors but also significantly shorten the design cycle, reportedly improving production efficiency by at least 30%. In addition, since the model interfaces between existing PDS software and existing S3D software are not yet interoperable, for non-standardized parametric devices (i.e., non-parametric devices), existing technologies still require manual modeling to convert the PDS model data of non-parametric devices into the corresponding S3D model data of parametric devices. To address this, the conversion method 100 of this application can efficiently and automatically convert the PDS model data of non-parametric devices into the S3D model data of parametric devices, thereby enabling existing PDS model data to be better used and processed after being converted into other format model data. Here, the parametric device is a single complex entity containing all the parameters of the corresponding non-parametric device, without containing the multiple basic elements of the non-parametric device, thus possessing better completeness.

[0031] Referring again to Figure 1, the conversion method 100 of this embodiment includes the following steps. Step S11 is to obtain PDS model data through PDS software. The PDS model data is in XML format and contains a unique identifier tag associated with the corresponding target device model. It should be noted that in this embodiment, calling the PDS software can generate XML-formatted PDS model data, and XML format is a file format that S3D software can directly recognize. Therefore, the PDS model data generated by calling the PDS software facilitates subsequent recognition by the S3D software. Furthermore, the PDS model data generated by calling the PDS software also includes numerous parameter information other than the RectangularSolid node and Cylinder node. These parameter information are required to generate the target device model in the S3D model. Therefore, the PDS model data generated by calling the PDS software facilitates subsequent conversion into S3D model data that the S3D software can recognize and process. It should also be noted that a power plant model includes multiple target equipment models. Therefore, because the PDS model data in this embodiment contains unique identification tag data, it is possible to combine the corresponding power plant model based on the unique identification tag data after inputting the S3D model data corresponding to the multiple PDS model data associated with the power plant model into the S3D software. However, PDS model data generated in other ways is difficult to retain unique identification tag data, and therefore cannot be used to construct a complete power engineering model from the corresponding multiple target equipment models in the S3D software.

[0032] Referring again to Figure 1, step S12 checks whether any data is missing from each RectangularSolid node. If the result is yes, the RectangularSolid node is designated as a node to be completed; otherwise, step S13 continues. It should be noted that the inventors discovered that when converting PDS model data into corresponding S3D model data, sometimes the S3D model data cannot be used normally in the S3D software. The inventors further discovered that the PDS model data corresponding to the unusable S3D model data contains missing data for some RectangularSolid nodes. For example, some RectangularSolid nodes lack the value corresponding to the Length_1 attribute, some lack the value corresponding to the Length_2 attribute, and some lack the value corresponding to the Length_3 attribute, etc. However, no such missing values ​​were found in the PDS software. Therefore, the inventors found that the PDS software itself has certain defects, which may lead to incomplete data in the generated PDS model data. Therefore, in this embodiment, step S12 is used to verify the integrity of the PDS model data to ensure that the subsequently generated S3D model data can be used normally.

[0033] Referring again to Figure 1, step S13 involves completing the data in all the RectangularSolid nodes to be completed based on the database corresponding to the PDS software. Referring further to Figure 2, step S13 includes the following sub-steps: Step S131 involves obtaining the model number of the target device model in the PDS software and the node ID corresponding to each RectangularSolid node to be completed. The model number is the modelnumber. Step S132 involves retrieving a data set from the database based on the model number and node ID. This data set contains multiple real parameter values ​​corresponding to all the RectangularSolid nodes to be completed. Furthermore, the database includes the SQL Server database bound to the PDS software. It is understandable that since the data obtained from the PDS software may be incomplete, this embodiment directly retrieves the real parameter values ​​related to the RectangularSolid nodes to be completed from the SQL Server database in step S132, thus avoiding the inherent defects of the PDS software itself. Moreover, due to the advantages of using the PDS model data generated by the PDS software mentioned above, this embodiment does not directly generate the PDS model data corresponding to the target device model from the SQL Server database.

[0034] Referring again to Figure 2, step S133 involves writing multiple real parameter values ​​corresponding to the To-be-Completed RectangularSolid node from the dataset into the To-be-Completed RectangularSolid node for each node to be completed. Specifically, in this embodiment, the multiple real parameter values ​​corresponding to each To-be-Completed RectangularSolid node include the real values ​​corresponding to the Length_1 attribute, the Length_2 attribute, and the Length_3 attribute. Therefore, step S133 in this embodiment sets the values ​​of the Length_1, Length_2, and Length_3 attributes in the To-be-Completed RectangularSolid node to their corresponding real values. It should be noted that this application does not limit the specific writing method. In some embodiments, only the attributes with missing values ​​in the To-be-Completed RectangularSolid node are set to their corresponding real values.

[0035] Referring again to Figure 1, step S14 involves replacing each RectangularSolid node and Cylinder node with its corresponding newParametric node to obtain the S3D model data corresponding to the PDS model data. Referring further to Figure 3, step S14 includes the following sub-steps: Step S141 involves replacing each RectangularSolid node with its corresponding newParametric node. Referring further to Figure 4, step S141 includes the following sub-steps: Step S1411 involves constructing a newParametric node under the corresponding EquipmentItems node for each RectangularSolid node, and writing the data from the RectangularSolid node into the newParametric node. The data in the RectangularSolid node includes the values ​​corresponding to the Length_1 attribute, the Length_2 attribute, and the Length_3 attribute. Specifically, in step S1411, the values ​​corresponding to the Length_1 attribute, the Length_2 attribute, and the Length_3 attribute are all written into the corresponding newParametric nodes, thereby completely converting the information of the RectangularSolid node into a newParametric node for storage, so that it can be effectively recognized by the S3D software in the future.

[0036] Referring again to Figure 4, step S1412 involves creating a HoleShape attribute in the corresponding newParametric node for each RectangularSolid node and writing a first preset value to the HoleShape attribute. Specifically, in this embodiment, the first preset value is 10002. It is understood that constructing the HoleShape attribute and writing the first preset value is to facilitate effective recognition by the S3D software. Step S1413 involves deleting all RectangularSolid nodes. It is understood that the S3D software cannot recognize RectangularSolid nodes, therefore all RectangularSolid nodes are deleted. Through the above step S141, all cube element-related data in the original PDS model data is transformed into a data format that the S3D software can recognize.

[0037] Referring again to Figure 3, step S142 involves replacing each Cylinder node with its corresponding newParametric node. Referring further to Figure 5, step S142 includes the following sub-steps: Step S1421: For each Cylinder node, construct a newParametric node under the corresponding EquipmentItems node, and write the data from the Cylinder node into the newParametric node. The data in the Cylinder node includes the values ​​corresponding to the Diameter and Length attributes. Step S1422: For each Cylinder node, create a new HoleShape attribute in the corresponding newParametric node, and write a second preset value to the HoleShape attribute. Step S1423: Delete all Cylinder nodes. It is understood that in this embodiment, step S142 is similar to step S141 above, enabling all data related to cylindrical elements in the original PDS model data to be converted into a data format recognizable by the S3D software. Referring again to Figure 3, step S143 determines whether each EquipmentItems node has a DatumPoint node. If the result is yes, the DatumPoint node under the EquipmentItems node is deleted. It should be noted that the S3D software cannot effectively recognize the data corresponding to the DatumPoint node. Therefore, deleting the DatumPoint node in the PDS model data can avoid the problem of the S3D software being unable to recognize it.

[0038] In summary, the conversion method 100 of this embodiment can efficiently and accurately convert PDS model data into S3D model data that can be effectively recognized by S3D software through the above steps S11 to S14. This allows for the subsequent generation of an S3D model corresponding to the target device model in the S3D software. Specifically, for PDS model data of non-parametric devices, the converted S3D model data corresponds to parametric devices, thereby improving the convenience of subsequent S3D model use and processing, and enhancing the data quality of the S3D model. Specifically, the PDS model data corresponding to non-parametric devices contains multiple RectangularSolid nodes and Cylinder nodes, requiring adjustments to the shape and material information of each RectangularSolid node and Cylinder node to modify the entire non-parametric device model. In contrast, through the processing of conversion method 100, the data corresponding to each RectangularSolid node and Cylinder node is converted into a unified newParametric node, thus forming the S3D model data corresponding to the parametric device. Subsequently, after reading the S3D model data through the S3D software, attribute information can be input in batches through the official API interface of the S3D software or by reading and writing SQL databases, thereby improving the model data quality of the target device model and achieving efficient and convenient processing of the target device model.

[0039] Referring to Figure 6, an embodiment of this application also proposes an S3D model construction method 200. As shown in Figure 6, the S3D model construction method 200 includes the following steps: Step S21 is to obtain S3D model data according to the above-mentioned method 100 for converting PDS model data into S3D model data. Step S22 is to construct the corresponding S3D model in S3D software based on the S3D model data. Specifically, in step S22, inputting the S3D model data into the S3D software yields the corresponding S3D model. In this embodiment, steps S21 to S22 can efficiently and accurately construct the S3D model corresponding to the parametric device in the S3D software based on the PDS model data corresponding to the non-parametric device in the PDS software.

[0040] An embodiment of this application also proposes a system 300 (hereinafter referred to as conversion system 300) for converting PDS model data to S3D model data, as shown in FIG7. According to FIG7, the conversion system 300 may include an internal communication bus 31, a processor 32, a read-only memory (ROM) 33, a random access memory (RAM) 34, and a communication port 35. When applied to a personal computer, the conversion system 300 may also include a hard disk 36.

[0041] The internal communication bus 31 enables data communication between components of the conversion system 300. The processor 32 can perform judgments and issue prompts. In some embodiments, the processor 32 may consist of one or more processors. The communication port 35 enables data communication between the conversion system 300 and external systems. In some embodiments, the conversion system 300 can send and receive information and data from a network via the communication port 35.

[0042] The conversion system 300 may also include different types of program storage units and data storage units, such as a hard disk 36, a read-only memory (ROM) 33, and a random access memory (RAM) 34, capable of storing various data files used for computer processing and / or communication, as well as possible program instructions executed by the processor 32. The processor 32 executes these instructions to implement the main part of the method. The results processed by the processor 32 are transmitted to the user equipment via a communication port and displayed on the user interface.

[0043] In addition, this application also proposes a computer-readable medium storing computer program code, which, when executed by a processor, implements the method 100 for converting the PDS model data into S3D model data as described above.

[0044] The basic concepts have been described above. Obviously, for those skilled in the art, the above disclosure is merely illustrative and does not constitute a limitation of this application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and corrections to this application. Such modifications, improvements, and corrections are suggested in this application, and therefore remain within the spirit and scope of the exemplary embodiments of this application.

[0045] Furthermore, this application uses specific terms to describe embodiments of the application. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic related to at least one embodiment of the application. Therefore, it should be emphasized and noted that "an embodiment," "one embodiment," or "an alternative embodiment" mentioned twice or more in different locations in this specification do not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of the application can be appropriately combined.

[0046] Similarly, it should be noted that, in order to simplify the description of the present application and thus aid in the understanding of one or more embodiments, the foregoing description of the embodiments of the present application sometimes combines multiple features into a single embodiment, drawing, or description thereof. However, this disclosure method does not imply that the subject matter of the present application requires more features than those mentioned in the claims. In fact, the embodiments contain fewer features than all the features of the single embodiments disclosed above.

[0047] Some aspects of this application can be executed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The aforementioned hardware or software may be referred to as a "data block," "module," "engine," "unit," "component," or "system." The processor may be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. Furthermore, aspects of this application may manifest as computer products residing in one or more computer-readable media, including computer-readable program code. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes, etc.), optical discs (e.g., compressed CDs, digital multifunction DVDs, etc.), smart cards, and flash memory devices (e.g., cards, sticks, key drives, etc.).

[0048] A computer-readable medium may contain a propagated data signal containing computer program code, for example, on baseband or as part of a carrier wave. This propagated signal may take various forms, including electromagnetic, optical, and so on, or suitable combinations thereof. A computer-readable medium can be any computer-readable medium other than a computer-readable storage medium, which can be connected to an instruction execution system, apparatus, or device to enable communication, propagation, or transmission of a program for use. The program code located on the computer-readable medium can be propagated through any suitable medium, including radio, cable, fiber optic cable, radio frequency signals, or similar media, or any combination of the above media.

[0049] Although this application has been described with reference to specific embodiments, those skilled in the art should recognize that the above embodiments are only used to illustrate this application, and various equivalent changes or substitutions can be made without departing from the spirit of this application. Therefore, any changes or modifications to the above embodiments within the essential spirit of this application will fall within the scope of the claims of this application.

Claims

1. A method for converting PDS model data into S3D model data, characterized in that, The process includes the following steps: acquiring PDS model data through PDS software, wherein the PDS model data includes multiple RectangularSolid nodes and Cylinder nodes; replacing each RectangularSolid node and Cylinder node with a corresponding newParametric node to obtain S3D model data corresponding to the PDS model data.

2. The method for converting PDS model data into S3D model data as described in claim 1, characterized in that, The PDS model data corresponds to a target device model. The PDS model data is in XML format and contains a unique identification tag associated with the corresponding target device model.

3. The method for converting PDS model data into S3D model data as described in claim 1, characterized in that, The PDS model data includes a DesignEquipment node, under which there are multiple EquipmentItems nodes. Each EquipmentItems node has one RectangularSolid node or one Cylinder node. The step of replacing each RectangularSolid node and Cylinder node with a corresponding newParametric node to obtain the S3D model data corresponding to the PDS model data further includes: replacing each RectangularSolid node with a corresponding newParametric node; replacing each Cylinder node with a corresponding newParametric node; determining whether each EquipmentItems node has a DatumPoint node. If the determination result is yes, then deleting the DatumPoint node under the EquipmentItems node.

4. The method for converting PDS model data into S3D model data as described in claim 3, characterized in that, The step of replacing each RectangularSolid node with the corresponding newParametric node further includes: for each RectangularSolid node, constructing the newParametric node under the corresponding EquipmentItems node, and writing the data in the RectangularSolid node into the newParametric node; for each RectangularSolid node, creating a HoleShape attribute in the newParametric node corresponding to the RectangularSolid node, and writing a first preset value into the HoleShape attribute; and deleting all RectangularSolid nodes.

5. The method for converting PDS model data into S3D model data as described in claim 4, characterized in that, The data in the RectangularSolid node includes the values ​​corresponding to the Length_1 attribute, the Length_2 attribute, and the Length_3 attribute.

6. The method for converting PDS model data into S3D model data as described in claim 3, characterized in that, The step of replacing each Cylinder node with the corresponding newParametric node further includes: for each Cylinder node, constructing the newParametric node under the corresponding EquipmentItems node, and writing the data in the Cylinder node into the newParametric node; for each Cylinder node, creating a HoleShape attribute in the newParametric node corresponding to the Cylinder node, and writing a second preset value into the HoleShape attribute; and deleting all Cylinder nodes.

7. The method for converting PDS model data into S3D model data as described in claim 6, characterized in that, The data in the Cylinder node includes the values ​​corresponding to the Diameter attribute and the Length attribute.

8. The method for converting PDS model data into S3D model data as described in any one of claims 1 to 7, characterized in that, Before the step of replacing each RectangularSolid node and Cylinder node with the corresponding newParametric node to obtain the S3D model data corresponding to the PDS model data, the method further includes: for each RectangularSolid node, determining whether the data in the RectangularSolid node is missing; if the determination result is yes, then the RectangularSolid node is taken as a RectangularSolid node to be completed; and completing the data in all the RectangularSolid nodes to be completed according to the database corresponding to the PDS software.

9. The method for converting PDS model data into S3D model data as described in claim 8, characterized in that, The step of completing the data in all the RectangularSolid nodes to be completed according to the database corresponding to the PDS software, where the PDS model data corresponds to a target device model, further includes: obtaining the model number name of the target device model in the PDS software and the node ID corresponding to each RectangularSolid node to be completed; obtaining a data set from the database according to the model number name and the node ID, the data set containing multiple real parameter values ​​corresponding to all the RectangularSolid nodes to be completed; and for each RectangularSolid node to be completed, writing the multiple real parameter values ​​corresponding to the RectangularSolid node to be completed from the data set into the RectangularSolid node to be completed.

10. The method for converting PDS model data into S3D model data as described in claim 8, characterized in that, The database includes the SQL Server database bound to the PDS software.

11. A method for constructing an S3D model, characterized in that, The method includes the following steps: obtaining S3D model data using the method for converting PDS model data to S3D model data according to any one of claims 1 to 10; and constructing a corresponding S3D model in S3D software based on the S3D model data.

12. A system for converting PDS model data into S3D model data, comprising: Memory is used to store instructions that can be executed by the processor; And a processor for executing the instructions to implement the method for converting PDS model data into S3D model data as described in any one of claims 1-10.

13. A computer-readable medium storing computer program code, which, when executed by a processor, implements the method for converting PDS model data into S3D model data as described in any one of claims 1-10.

Images