An assembled trestle intelligent parameterized design platform

Abstract

The application discloses an assembled trestle intelligent parameterized design platform, and particularly relates to the field of assembled trestle parameterized design and edge calculation, which comprises the following steps: reading the support position, truss span and elevation in Excel, forming column distribution according to the support position, writing adjacent columns as a trestle section, calling a standardized component library by Rhino and Grasshopper to generate a structure geometric model, and forming a component record number according to the order of the trestle section and the order of components in the section; reading two end connecting points according to the component record number, writing the same Grasshopper connecting point as the same Midas Gen node, forming a Midas Gen unit by the two end nodes of the component, and writing the load and boundary conditions in Excel into corresponding units and nodes respectively to form a finite element model; and continuously transmitting the Excel parameter modification to structure modeling, finite element analysis, calculation book, construction drawing and deepening model along the parameter reference relationship by means of the component record number through Rhino, Midas Gen and Tekla.

Description

Technical Field

[0001] This invention relates to the field of parametric design and edge computing technology for prefabricated trestle bridges, and more specifically, to an intelligent parametric design platform for prefabricated trestle bridges. Background Technology

[0002] Prefabricated trestle design typically involves using Excel to organize the support positions, truss spans, elevations, loads, and boundary conditions, then using Rhino and Grasshopper to complete parametric modeling, using Midas Gen for structural analysis, and continuing to complete detailed modeling and construction drawing results in Tekla. Meanwhile, edge computing nodes handle the design parameters and data processed at each stage. During the design process of adjusting the span of the trestle bridge, changing the position of the support, or adding or deleting components, the structural geometric model, finite element model, calculation results, construction drawings, and detailed model need to be continuously updated along with the same design parameters. Each software saves components, nodes, and analysis results separately. After the parameters are modified, it is easy for Rhino components to be updated while Midas Gen elements, loads, or boundary conditions still correspond to the original model, or for calculation sheets, node details, and Tekla detailed components to still reference the original component data. Designers can only find the affected components again and modify them one by one, which not only involves a lot of repetitive operations, but also easily leads to the interruption of the correspondence between different design results. The technical problem this application aims to solve is: how to ensure that modifications to Excel parameters can be continuously transmitted along the component correspondence to the structural geometric model, finite element analysis, calculation sheets, construction drawings, and detailed models during the parametric design process of prefabricated trestle bridges based on edge computing, while maintaining consistency of design data at each stage. Summary of the Invention

[0003] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide an intelligent parametric design platform for prefabricated trestle bridges. By connecting Rhino, Midas Gen, and Tekla with component record numbers and continuously transmitting Excel parameter modifications to structural modeling, finite element analysis, calculation sheets, construction drawings, and detailed models along parameter reference relationships, the platform solves the problems mentioned in the background art.

[0004] To achieve the above objectives, the present invention provides the following technical solution: an intelligent parametric design platform for prefabricated trestle bridges, comprising: The parametric modeling module is used to read the support positions, truss spans and elevations from Excel, form the column distribution according to the support positions, write adjacent columns as trestle segments, and use Rhino and Grasshopper to call the standardized component library to generate the structural geometric model, and form component record numbers according to the trestle segment sequence and the sequence of components within the segment. The data analysis interface module is used to read the connection points at both ends according to the component record number, write the same Grasshopper connection point as the same Midas Gen node, form Midas Gen elements with the nodes at both ends of the component, and write the loads and boundary conditions in Excel into the corresponding elements and nodes respectively to form a finite element model. The optimization calculation module is used to send the finite element model into Midas Gen to perform structural analysis, read the stress ratio, slenderness ratio and deflection according to the Midas Gen element, and return to Rhino according to the component record number to generate structural index results, calculation report and component table; The drawing generation module is used to generate plan views, elevation views and section views based on the structural geometric model, generate detailed node drawings according to the node connection components and structural index results, and perform node verification to generate construction drawings; The data collaboration module is used to connect Rhino components, Midas Gen units, and Tekla components according to component record numbers to form a detailed model. After the Excel parameters are modified, the structural geometric model is regenerated according to the component record numbers referenced by the parameters, and finite element analysis is performed. Then, the structural index results, calculation sheets, component tables, construction drawings, and detailed models are rewritten.

[0005] In a preferred embodiment, the parametric modeling module includes: Read the total pillars field from the pillar parameter file, write the integer in the field as the total number of pillar records, and then read from the first record according to the record order in the pillars field. Write the name field of each record as the pillar name, the distance from start field as the distance from the starting point, the distance from previous field as the distance from the previous pillar, and the height field as the vertical dimension value. The column parameter file refers to a parameter file created with a prefabricated trestle as a data object. The file header has a total pillars field to record the number of columns, and the columns are continuously saved in the order from the start to the end of the trestle under the pillars field. Each column record includes four fixed fields: name, distance from start, distance from previous, and height, so that each record corresponds to a specific column. The `total pillars` field is an integer field that stores the number of pillar records in the pillar parameter file. Its value is the actual number of pillar records stored in the `pillars` field. The field value is incremented by one when a new pillar record is added, and decremented by one when a pillar record is deleted. The pillars field refers to the data segment in the pillar parameter file that stores pillar records sequentially. The first record corresponds to the first pillar on the starting side of the trestle, and the next record corresponds to the next pillar immediately following the previous pillar along the direction from the starting point to the end point of the trestle. The name field is a character field that stores the name of the column in each column record. One column record in the same column parameter file corresponds to one name field value. The name field value is used to distinguish different columns and index the position data and vertical dimension data in the same record. The "distance from start" field refers to the numerical field that measures the distance from the starting point of the trestle along the longitudinal axis of Rhino to the current position of the pillar. The zero point of the value is taken from the starting point of the trestle, and the positive direction is taken from the starting point of the trestle to the end point of the trestle. The field value uses the current Rhino's unified length unit. The "distance from previous" field refers to the numerical field representing the distance from the previous column position to the current column position measured along the Rhino longitudinal axis. For the second and subsequent column records, the distance from previous column positions is obtained by subtracting the distance from start field value from the current column's distance from start field value. The height field refers to the vertical dimension value of the current column along the vertical direction of Rhino. The field value uses the same length unit as the current Rhino column and is stored in the same column record as the name field of the current column. For the first column record, the column position is obtained by taking the distance from start field value as the distance along the Rhino longitudinal axis from the starting point of the trestle; for the next column record, the current column position is formed by adding the distance from previous field value in the current record to the previous column position, and the current column position is checked against the distance from start field value in the current record item by item. If the two values ​​match, the current record is retained; if the two values ​​do not match, the distance from start field value is written to the current column position, and the distance from previous field value is subtracted from the current column position and rewritten. A pillar record refers to a data record in the pillars field, which consists of a name field, a distance from start field, a distance from previous field, and a height field, and its reading order is determined by its storage order in the pillars field. Rhino longitudinal axis measurement refers to taking the starting point of the trestle as the zero point of distance, taking the direction of the line connecting the starting point of the trestle to the end point of the trestle as the positive direction of the Rhino longitudinal axis, reading the position of the target column in this direction, and subtracting the starting point position of the trestle from the position of the target column to obtain the distance value. Field values ​​refer to the data content stored in a specific field. The total pillars field stores integers, the name field stores character content, and the distance from start, distance from previous, and height fields store length values. The field name determines the meaning of the data, and the field value records the corresponding data content. After each pillar record is written, the reading sequence number is incremented by one. The reading ends when the reading sequence number equals the integer in the total pillars field. The pillar positions are then connected according to the reading sequence number to output the pillar distribution record.

[0006] In a preferred embodiment, the parametric modeling module further includes: Starting from the first record of the column distribution, read two adjacent columns, take the current column as the starting column of a trestle segment, take the next column as the ending column of the same trestle segment, and write the trestle segment order in ascending order of integers starting from the starting point of the trestle. After Grasshopper reads the starting column position and the ending column position, it generates the upper longitudinal beam and the lower longitudinal beam respectively along the longitudinal connection direction between the two columns. Then, it generates the cross beam connecting the upper longitudinal beam and the lower longitudinal beam at the starting column position and the ending column position. Finally, it generates the support at the connection point connecting the longitudinal beam and the cross beam in Grasshopper. Grasshopper is a parametric modeling program that runs in Rhino. It consists of a data input terminal, a parameter processing component, a geometry operation component, and a geometry output terminal in order of connection. The data input terminal reads column positions, truss spans, elevations, and component data from the standardized component library. The parameter processing component transmits values ​​according to the connection relationship. The geometry operation component generates lines, points, or component geometry based on the input values. The geometry output terminal writes the generated results into Rhino to form Rhino components. When the support falls into the current trestle segment, the support record is read from the standardized component library and written to the support position. When two components share the Grasshopper connection point, the node record is read and written to the connection point. When the support is connected to the main structure of the trestle, the support record is read and written to the connection position. The standardized component library saves component records according to existing class standard components and retains the component parameters in the called component record when generating components. The bracket position refers to the position value of the bracket along the longitudinal axis of the trestle, measured from the starting point of the trestle to the ending point of the trestle with the starting point of the trestle as the zero point; when the bracket position is between the distance from start field values ​​of two adjacent column records, the bracket will be written into the trestle segment formed by these two column records. A standardized component library is a data set that stores component generation data according to component categories. Each component record corresponds to a specific component form and stores the component category, geometric dimension field, and data that Grasshopper needs to read when generating Rhino components. When calling the library, the record is first located by component category, and then the field values ​​in the record are read to generate the corresponding Rhino component. A support record is a component record in the standardized component library whose component category is support. The record content is used to determine the geometry and size of the support in Rhino, and the generation position is determined by the support position. Grasshopper connection points refer to the same geometric point object referenced by two or more components during Grasshopper parametric modeling. A connection point has a set of defined Rhino engineering coordinates and corresponds to a Midas Gen node number during finite element transformation. A node record refers to a data record in a standardized component library used to store a node. The record stores the node type, the component relationship connected to the node, and the data read when generating node details and performing node verification. The connection point of the main structure of the trestle refers to the geometric position where the upper end of the support connects to the main structure of the trestle. In Rhino, it is represented by a Grasshopper connection point and is referenced by both the support components and the main structure of the trestle. A support record refers to a component record in the standardized component library whose component category is support. Its generation location is taken from the connection position of the main structure of the trestle. The component parameters in the record are used to generate the support component between the support frame and the main structure of the trestle. Component parameters refer to the numeric and category fields within a component record in the standardized component library that Grasshopper reads when generating Rhino components; the numeric fields are used to determine the component's geometric dimensions, and the category fields are used to determine the component record being called. Write the component order within the current trestle segment according to the order in which Grasshopper generates the components, starting from the beginning. Write the trestle segment order first and the component order within the segment last to form a component record number, and output the structural geometric model with the component record number.

[0007] In a preferred embodiment, the parametric modeling module further includes: For each component record number in the structural geometry model, the Excel field name read when generating the current component and the component record number are written on the same line to form a parameter reference record. When a component reads more than two Excel fields, corresponding parameter reference records are created respectively. All parameter reference records are collected by field name to form a parameter reference table. The Excel field name refers to the data name used in Excel to identify a design parameter. Each field name corresponds to a specific data column or fixed data location. The parameter reference table uses the Excel field name as the lookup field and the component record number that references this field as the lookup result. When performing local adjustments, the parameter reference table is searched row by row by the input Excel field name. The component record number of each row with the same field name is written into the reconstruction priority. Then, the corresponding Grasshopper component generation process is re-executed according to the reconstruction priority, and the Rhino component corresponding to the original component record number is replaced with the newly formed Rhino component. When adding a component, add a component order to the component order of the last segment of the specified stack segment, and form a new component record number with the same stack segment order; when deleting a component, locate the Rhino component with the component record number and delete it, and delete all records in the parameter reference table that have the same component record number. For regenerated, added, or retained components, the corresponding component record number will continue to be used, so that the component position in the scheme model, the corresponding component in the finite element model, and the corresponding component in the detailed model are transmitted using the same component record number; The scheme model refers to the structural geometric model generated in Rhino by the parametric modeling module. It consists of Rhino components with component record numbers and saves the position of each Rhino component, the connection points at both ends, and the connection relationships between components for subsequent finite element model generation and construction drawing generation.

[0008] In a preferred embodiment, the analytical data interface module includes: Read Rhino components sequentially according to their component record numbers. For each Rhino component read, obtain the first and last connection points used when Grasshopper generates the component. Use Grasshopper connection points as the basis for node merging. When a connection point appears for the first time, write the Midas Gen node number from the beginning. When a subsequent component uses the same Grasshopper connection point that has already been written with the Midas Gen node number, directly read the existing Midas Gen node number. The first and last connection points refer to the two connection points used by a Rhino component during Grasshopper generation. The first end that appears along the direction from the start to the end of the bridge is written as the first connection point, and the other end is written as the last connection point. For transverse components and supports, the first and last connection points are determined according to the connection order of the Grasshopper input ends. After obtaining the Midas Gen node number for both the first and last connection points of the current Rhino component, the two node numbers are written into a Midas Gen unit record in the order of first and last connection points. The Midas Gen unit number is then written in ascending order from the first to the last component record number. Finally, the component record number and the Midas Gen unit number are written on the same line to form a corresponding unit record. When reading load records from Excel, the Midas Gen element number is obtained from the corresponding element record based on the component record number pointed to by the load record. Then, the load direction and load value are written into the corresponding Midas Gen element. When reading boundary conditions, the Midas Gen node number is obtained from the Grasshopper connection point pointed to by the boundary conditions. Then, the constraint values ​​are written one by one according to the original order of the Midas Gen node degrees of freedom. A value of 1 indicates a constraint, and a value of 0 indicates a release. The finite element model with the load and boundary conditions written is output. Excel refers to the data table file used to save the current design data of the prefabricated trestle bridge. The design parameters are located by field name, and the support position, truss span and elevation are provided to the parametric modeling process, and the load record and boundary condition record are provided to the finite element assignment process. Load records refer to the data records in Excel corresponding to a single Midas Gen unit load. A load record includes at least one component record number, one load direction field, and one load value field. After obtaining the Midas Gen unit number from the corresponding unit record using the component record number, the load direction and load value are written to the corresponding unit. The load direction is a field that determines the direction of the load in the Midas Gen coordinate system, and the load value is the value stored in the same load record; both are written into the load data of the corresponding Midas Gen element along with the same component record number. Boundary conditions refer to a node constraint record used to limit the degrees of freedom of motion of a Midas Gen node. The corresponding Midas Gen node number is located by the Grasshopper connection point, and then a constraint value is written for each degree of freedom according to the order of the node's degrees of freedom. The degree of freedom refers to the six motion components of a Midas Gen spatial node, which are fixed in the order of translation along the X-axis, translation along the Y-axis, translation along the Z-axis, rotation around the X-axis, rotation around the Y-axis, and rotation around the Z-axis. The constraint value is a binary data corresponding one-to-one with a node's degree of freedom. A value of 1 indicates that the corresponding translation or rotation is restricted, and a value of 0 indicates that the corresponding translation or rotation is released. A Midas Gen node is written with six constraint values ​​according to the order of its six degrees of freedom.

[0009] In a preferred embodiment, the optimization calculation module includes: After the finite element model is sent into Midas Gen, a structural analysis command is sent, and the analysis round number is written starting from an integer. The subsequent structural analysis command is based on the previous analysis round number plus one. Midas Gen refers to a software program that receives Midas Gen nodes, Midas Gen elements, load records, and boundary condition records and performs structural analysis. After a structural analysis is completed, it provides stress ratio, slenderness ratio, and deflection results corresponding to each element according to the Midas Gen element number. The execution process of the structural analysis command is as follows: First, write the Midas Gen node records and Midas Gen element records in the current finite element model into the Midas Gen project; then write the load records into the corresponding Midas Gen elements and the boundary condition records into the corresponding Midas Gen nodes; after completing the writing of the four types of data, send the structural analysis execution command, wait for MidasGen to return the analysis completion status, and then read the corresponding analysis results according to the Midas Gen element number sequence. After Midas Gen completes the current analysis cycle, it reads the stress ratio formed by each element in the order of Midas Gen element number, then reads the slenderness ratio and deflection formed by the same element, and finds the corresponding record of the element by Midas Gen element number to obtain the component record number. The analysis cycle, component record number, stress ratio, slenderness ratio and deflection are written on the same line to form a structural index record. The process of generating stress ratio, slenderness ratio and deflection is as follows: After Midas Gen completes the current analysis cycle, it reads the result records one by one by Midas Gen unit number, takes the stress ratio field value, slenderness ratio field value and deflection field value from the result record of the same unit, and then finds the corresponding record of the unit by Midas Gen unit number to obtain the component record number, and writes the three values ​​into the structural index record corresponding to this component record number. When returning analysis results to Rhino, the Rhino component is located by the component record number, and the stress ratio, slenderness ratio and deflection corresponding to the current analysis round are written into the data record of the Rhino component. When the Excel parameters are modified and resubmitted, the component record number referenced by the modified field is obtained from the parameter reference table, the corresponding Rhino component is regenerated, the finite element model is formed again, and the next analysis round is sent. Excel parameters refer to data fields read from Excel and used in the generation of structural geometric models or assignment of finite element models during the current parametric design process. These include support locations, truss spans, elevations, load records, and boundary condition records. Each Excel parameter consists of a fixed field name and the current field value. Upon receiving the parameter confirmation instruction for this round, stop creating analysis rounds and write the stress ratio, slenderness ratio, and deflection corresponding to the record number of each component in this round as structural index results; The parameter confirmation instruction refers to the confirmation data that the designer writes to the platform after the current analysis round ends. When the confirmation data is written as 1, the creation of new parameter modification records for the current analysis round is stopped, and the structural index record of the current analysis round is written as the structural index result. When the confirmation data is not written as 1, the current structural index record is retained and waits for the next Excel parameter writing.

[0010] In a preferred embodiment, the optimization calculation module further includes: When generating the calculation sheet, the field names are read sequentially from the first write position of the calculation sheet template. If the field name matches the field name in Excel, the current field value in Excel is written to the corresponding position. If the field name is stress ratio, slenderness ratio, or deflection, the component record number bound to the current write position is read first, and then the structural index record is searched using the component record number and the current analysis round. The structural index value with the same name is written to the corresponding position until all write positions of the calculation sheet template are completed. The calculation template refers to a document data structure consisting of fixed text positions and data writing positions. Each data writing position stores at least one field name. The data position for writing structural indicators also stores a component record number, so that the field name determines the type of data being written and the component record number determines the data object being written. Structural index values ​​refer to the numerical data in the structural index record that are located by a component record number and an analysis round. They include stress ratio, slenderness ratio and deflection values, respectively. The same component record number corresponds to the three structural index values ​​in the same analysis round. When generating the component table, the component table records are created row by row according to the component record number in the structural geometry model. Each row first writes the component record number, then reads the standardized component library record used by the current Rhino component from the component record number, and writes the corresponding component parameters according to the original field order of the component library. Then, the structural index record is obtained with the same component record number and the current analysis round, and the stress ratio, slenderness ratio and deflection are written in the same row. After writing all component record numbers in the current structural geometric model, output the calculation sheet and component table corresponding to the current analysis round.

[0011] In a preferred embodiment, the drawing generation module includes: Read the position of the first and last pillar in the pillar distribution record. Take the direction of the line connecting the two pillar positions as the longitudinal direction of the trestle, take the Rhino vertical direction as the vertical direction of the trestle, and take the direction that is perpendicular to both the longitudinal and vertical directions of the trestle as the lateral direction of the trestle. When generating a plan view, each Rhino component in the structural geometry model is read and projected onto the plane formed by the longitudinal and transverse directions of the trestle; when generating an elevation view, identical Rhino components are projected onto the plane formed by the longitudinal and vertical directions of the trestle; when generating a section view, the sectioning position is read from the standard drawing template, and each Rhino component is checked to see if it intersects with the sectioning position. The intersecting Rhino components are then projected onto the plane formed by the transverse and vertical directions of the trestle. When generating node details, the Midas Gen elements connected to the current node are read by the Midas Gen node number, and the component record number is obtained from the corresponding record of the element. The node data is then read according to the standard component record corresponding to each component record number. The analysis results corresponding to the components connected to the current node in the current analysis round are written to the node verification input position. The node verification process saved in the standard node record is executed. The returned results are written to the node details corresponding to the current node, and the construction drawings are output. Node data refers to the data record content corresponding to a node, including the node's connection position in Rhino, the component record number connected to this node, and the record fields read when generating node details and performing node verification; the node's connection component is determined by the Midas Gen node number and the Midas Gen unit connected to it. A standard component record is an independent component data record in the standardized component library. Each record corresponds to a specific component form and stores the component category and the component parameters that need to be read to generate a Rhino component. Rhino components establish a one-to-one correspondence with the standardized component library by calling the standard component record. The node verification process stored in the standard node record is as follows: First, obtain all Midas Gen unit numbers connected to the node using the current Midas Gen node number. Then, obtain the component record number corresponding to each Midas Gen unit through the unit corresponding record. Read the corresponding analysis results according to the component record number and the current analysis round. Write the analysis results item by item according to the fixed order of the node verification input position. After all input positions are written, execute the verification operation stored in the node record. Then, read the result value in the verification output position and write the result value to the verification result position corresponding to the current node detail drawing.

[0012] In a preferred embodiment, the data collaboration module includes: Component transfer records are created sequentially according to component record number. For each component record number processed, the start and end positions of the corresponding component are first read from Rhino, then the corresponding Midas Gen unit number, start Midas Gen node number, and end Midas Gen node number are read from the corresponding unit record, and then the standardized component library record used by the current Rhino component is read. Write the component record number to the beginning of the component transfer record, and then write the first end position, the last end position, the Midas Gen unit number, the first end Midas Gen node number, the last end Midas Gen node number, and the standardized component library record according to the reading order. After completing a component transfer record, send it to Tekla. Tekla generates corresponding detailed components according to the component transfer record and returns the Tekla component number. The returned Tekla component number and the component record number are written on the same line to form a detailed corresponding record. The next component continues to perform the same transfer process according to the component record number sequence. After all components are completed, the detailed model is output. The Tekla component number refers to a unique character or integer field value returned by Tekla after receiving a component transfer record and generating a refined component; a Tekla component number is written to only one refined corresponding record and corresponds to a component record number in the same refined corresponding record; A refined component refers to a single component object generated by Tekla based on a component transfer record. The component record number in the component transfer record determines the component's identity, the start and end positions determine the component's spatial position, the Midas Gen element number and the node numbers at both ends determine the finite element correspondence, and the standardized component library record determines the component type and component parameters. Multiple refined components are arranged in order of component record number to form a refined model.

[0013] In a preferred embodiment, the data collaboration module further includes: After each parametric design is completed, the field values ​​are saved in order of Excel field names. The next time the Excel is read, the current field value is read item by item according to the same field name and subtracted from the saved field value. If the difference is not zero, the corresponding field name is written to the changed field record. If the difference is zero, the next field is read. The parametric design process refers to a series of parametric design execution processes that start by reading the field values ​​of an Excel spreadsheet, and then sequentially complete the following steps: forming column distribution records, generating structural geometric models, generating finite element models, performing structural analysis, writing structural index results, generating calculation sheets, generating component tables, generating construction drawings, and generating detailed models. The process ends after all output data is saved. The parameter reference table is searched sequentially according to the field names in the changed field records. The component record numbers with the same field names are written into the reconstruction record according to the original component order. The parametric modeling module re-executes the corresponding Grasshopper component generation process according to the reconstruction record, replaces the original Rhino component corresponding to the same component record number with the regenerated Rhino component, and then the analysis data interface module re-forms the corresponding Midas Gen nodes and Midas Gen elements, and re-writes the loads and boundary conditions. The optimization calculation module establishes the next analysis round and re-executes the structural analysis. The resulting structural index results are returned to Rhino according to the component record number. Then, the same component record number is used to rewrite the calculation sheet, component table, and construction drawings. Subsequently, the component transfer record is regenerated according to the reconstructed component record number and sent to Tekla. The component number returned by Tekla replaces the original Tekla component number in the corresponding detailed record. After all the components corresponding to the changed fields have been processed, the current Excel field values ​​will replace the saved field values, and the structural geometric model, finite element model, structural index results, calculation sheet, component table, construction drawings and detailed model after the parameter modification will be output.

[0014] The technical effects and advantages of this invention are as follows: 1. This solution connects Rhino, Midas Gen, and Tekla through edge computing nodes and component record numbers, and transmits Excel modifications through parameter reference tables, so that the model, analysis, drawings, and detailed results are updated synchronously, reducing cross-software data mismatch. 2. Divide adjacent columns into trestle segments and use Grasshopper to call the standardized component library to generate Rhino components, so that the support position, truss span and elevation directly participate in the modeling, reducing repetitive modeling operations; 3. Merge Midas Gen nodes with Grasshopper connection points, and then form Midas Gen elements with the nodes at both ends of the component. This allows the component connection relationship in Rhino to be continued in the finite element model, reducing node correspondence errors. 4. The stress ratio, slenderness ratio and deflection are read from the edge calculation nodes according to the Midas Gen element, and returned to Rhino according to the component record number, so that the analysis results can continue to be written into the calculation sheet and component table, improving the traceability of structural results; 5. Generate plan views, elevation views, and section views based on the structural geometric model, and generate detailed node drawings by combining node connection components and structural index results, so that the construction drawings are consistent with the current model and analysis results. Attached Figure Description

[0015] Figure 1 This is a platform system diagram of the present invention; Figure 2 This is a schematic diagram of the column parameter file for the present invention; Figure 3 This is a schematic diagram of Grasshopper parameter processing according to the present invention. Detailed Implementation

[0016] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0017] Refer to the instruction manual appendix Figure 1-3 The present invention provides an intelligent parametric design platform for prefabricated trestle bridges, comprising: The parametric modeling module is used to read the support positions, truss spans and elevations from Excel, form the column distribution according to the support positions, write adjacent columns as trestle segments, and use Rhino and Grasshopper to call the standardized component library to generate the structural geometric model, and form component record numbers according to the trestle segment sequence and the sequence of components within the segment. First, a unified data connection relationship is established between Excel parameters, column parameters, and Rhino geometric objects. This allows the support position, truss span, and elevation to enter the column positioning, trestle segment generation, and Grasshopper component generation processes according to the determined data positions. Simultaneously, the reference relationship between the input data and Rhino components is saved for subsequent local adjustments, component additions and deletions, and continued reading by the finite element model and the detailed model. All data uses the same length unit as the current Rhino project, and component identities are uniformly represented by component record numbers. Processing of modified parameters continues along the original component record number. This implementation process includes the following steps: First, the sequential reading of the column parameter file and the consistency processing of the column positions are completed; the parametric modeling module establishes a set of column parameter data with a prefabricated trestle bridge, reads the integer in the total pillars field as the total number of column records, and then counts the records in the pillars field one by one. If the count result matches the value of the total pillars field, the field will be read; if they do not match, an abnormal column count record will be written and the generation of the current structural geometry model will be stopped. For each record in the pillars field, read the name, distance from start, distance from previous, and height fields in sequence. The name is the name of the pillar, the distance from start is the distance from the starting point of the bridge along the positive direction of the Rhino longitudinal axis to the current pillar, the distance from previous is the longitudinal distance of the current pillar relative to the previous pillar, and the height is the vertical dimension value of the current pillar. Rhino's vertical axis uses the starting point of the trestle as the zero point of distance and the direction from the starting point of the trestle to the end point of the trestle as the positive direction. Starting from the second column record, the position of the previous column is added to the current distance from previous field value to form a check position. Then, the current distance from start field value is subtracted from the check position. If the difference is zero, the current two distance fields are retained. If the difference is not zero, the current distance from start field value is written to the current column position, and the current distance from previous field value is rewritten by subtracting the previous column's distance from start field value from the current distance from start field value. In Excel, the positions of the supports are arranged in the order from the start to the end of the trestle and correspond to the column records in the pillars field. The position of the i-th support is written to the arrangement position corresponding to the i-th column record, so that the support positions and column positions use the same vertical coordinate reference. If the number of bracket location records is inconsistent with the total number of column records, the name field is empty, or the numeric field is missing, the sequence number and the name of the missing field will be read and written to the abnormal record and the generation of the current column distribution record will be stopped. After all column records have been processed, the column name, distance from the starting point, distance from the previous column, and vertical dimension value are written in sequence according to the reading sequence number to form a column distribution record for the next process. After the column distribution record is completed, the structural geometric model is generated segment by segment according to the relationship between adjacent columns. The parametric modeling module starts from the first column distribution record, reads the current column and the next adjacent column each time, writes the distance from the starting point of the two column records as the starting position and ending position of the current trestle segment respectively, and increments the trestle segment order from the starting point to the ending point of the trestle according to the processing order from the starting point to the ending point of the trestle. When the support position is between the starting and ending positions of the current trestle segment, the current trestle segment is written. When the support position is consistent with the position of the shared column of two adjacent trestle segments, the next trestle segment with the shared column as the starting column is written. The support corresponding to the position of the ending column is written to the terminating trestle segment. Grasshopper's data input terminal reads the starting column position, ending column position, truss span, elevation, and corresponding component data from the standardized component library for the current trestle segment. The parameter processing component passes the input values ​​according to the existing connection sequence. The geometry calculation component generates the corresponding geometric objects for the upper longitudinal beam, lower longitudinal beam, cross beam, and supports. The geometry output terminal writes the generated results into Rhino to form Rhino components. When two Rhino components reference the same geometric point object in Grasshopper, that geometric point is written as a shared Grasshopper connection point. After the support position is written to the current trestle segment, the support record in the standardized component library is read according to the component category; when the support and the main structure of the trestle share Grasshopper connection points, the node record is read; when the upper end of the support and the main structure of the trestle form a bearing position, the support record is read. When multiple standard component records correspond to the same component category, the record group is first determined by the component category. Then, the component parameters currently input by Grasshopper are compared with the record fields in the group according to the field order. If all field contents are consistent, the corresponding component record is read. If no corresponding record is found, the component category and the current stack segment order are written and the generation of the current component is stopped. For each Rhino component generated, the component sequence within the segment is written from an integer starting with the actual output sequence of the Grasshopper geometry output terminal. Then, the stack segment sequence and the component sequence within the segment are used as two integer fields to form the component record number. After all Rhino components in the current stack segment are processed, the next stack segment is read, ultimately forming a structural geometric model that includes Rhino components, Grasshopper connection points, and component record numbers. As the structural geometry model is formed, the parameter reference relationships are written synchronously with the Rhino components. When the Grasshopper geometry output generates the current Rhino component, the original input positions that actually participated in the generation of the current Rhino component are read back from the corresponding geometry output along the component connection relationship to the data input. The data location from Excel records the worksheet name, row number, and column number. The worksheet name, row number, and column number are used together to locate a specific input location. Then, this input location and the current component record number are written into a parameter reference record. When a Rhino component references multiple input locations, multiple parameter reference records are created. When the same input location participates in the generation of multiple Rhino components, the corresponding component record number is written. The parameter reference table is composed of all parameter reference records. When performing local adjustments, first obtain the changed Excel input location using the worksheet name, row number, and column number, and then read all corresponding component record numbers from the parameter reference table; when multiple changed input locations point to the same component record number, retain the record of the first occurrence of that component record number, and form the reconstruction sequence according to the component sequence in the original structural geometric model; The changed field values ​​are then sent back to the corresponding Grasshopper data input, and parameter processing and geometric operations are re-executed along the original component connection relationship. The original Rhino component corresponding to the same component record number is replaced with the newly generated Rhino component. When a component is added, one is added to the last position of the existing component sequence in the specified bridge segment to form the new component sequence. This new component sequence is then combined with the current bridge segment sequence to form the new component record number. At the same time, the parameter reference record corresponding to the new component is written. When deleting a component, locate the Rhino component by its component record number and delete it. Then delete all parameter reference records in the parameter reference table that have the same component record number. If no geometric output is generated after Grasshopper is re-executed, the original Rhino component is retained, and the component record number and the corresponding Grasshopper output are written to the reconstruction exception record. The regenerated, added, and retained Rhino components continue to use their respective component record numbers. Subsequent Midas Gen elements and Tekla components are all established according to the same component record number, and the updated structural geometry model and parameter reference table are output. The overall execution process is illustrated using three consecutive column records. The distance from start, distance from previous, and height fields corresponding to columns 1, 2, and 3 are read sequentially according to the pillars field. The distance of column 2 from the previous column is obtained by subtracting the distance from start field value of column 1 from the distance from start field value of column 2. Column 3 is processed according to the same rules. Then, the position of the previous column is added to the current distance from previous field value to form the verification position. After the position verification of the three column records is completed, they are written into the column distribution record according to the reading order. Subsequently, the first trestle segment is formed by column 1 and column 2, and the second trestle segment is formed by column 2 and column 3. Grasshopper reads the starting column position, ending column position, truss span, elevation, and standardized component library records of the two trestle segments to generate Rhino components. Each Rhino component is synchronously written with a component record number composed of the trestle segment order and the order of components within the segment, and the Excel input position participating in the generation of the current component is registered in reverse along the Grasshopper connection relationship. When any support position, truss span, or elevation changes, the change input position is located according to the worksheet name, row number, and column number. Then, the affected component record number is obtained from the parameter reference table. The corresponding Grasshopper component chain is re-executed according to the reconstruction order, and the component record number is kept in continuous use. This allows the updated structural geometry model to be directly used for finite element model generation, construction drawing generation, and detailed model transfer for continued reading.

[0018] The data analysis interface module is used to read the connection points at both ends according to the component record number, write the same Grasshopper connection point as the same Midas Gen node, form Midas Gen elements with the nodes at both ends of the component, and write the loads and boundary conditions in Excel into the corresponding elements and nodes respectively to form a finite element model. Before the structural geometric model enters the finite element analysis, the Rhino components, Grasshopper connection points and MidasGen nodes are unified into the same component record number system so that subsequent loads, boundary conditions and analysis results can be located to the specific components. Coordinate data uniformly adopts the current Midas Gen project length unit, and the Rhino project origin and the three coordinate axis directions correspond to the Midas Gen project. This implementation process includes the following steps: After the structural geometric model is formed, the Rhino components are read one by one according to the component record number, and the two connection points used by Grasshopper when generating the current Rhino component are obtained at the same time. When a Grasshopper connection point first appears, the Grasshopper connection point number is generated by incrementing from an integer, and the connection point number and its X-axis, Y-axis, and Z-axis coordinates are written into the connection point record; when a subsequent Rhino component references the same Grasshopper connection point, the existing connection point number is reused directly. Next, generate Midas Gen node numbers according to the order of Grasshopper connector numbers, and write the connector numbers, Midas Gen node numbers, and the three converted coordinate values ​​into the corresponding node records; If the connection point coordinates are missing or the unit conversion is incomplete, record the current component record number and stop the finite element conversion of the current Rhino component; After the component endpoints are numbered, the first connection point that appears along the direction from the start to the end of the trestle is written as the first connection point of the longitudinal component, and the next connection point is written as the last connection point; the first and last points of the beams and supports are determined according to the input order of the two connection points when Grasshopper is generated. Find the corresponding records of the nodes by the first connection point number and the last connection point number respectively, obtain two Midas Gen node numbers, and then generate Midas Gen unit numbers by starting from the integer first according to the component record number. Write the component record number, Midas Gen unit number, first node number and last node number into the same Midas Gen unit record, and form a unit corresponding record with the component record number and the Midas Gen unit number. After the finite element element correspondence is established, the Excel load records are read one by one; for each load record, the corresponding element record is located by the component record number and the Midas Gen element number is obtained, and then the load direction and load value in the same record are read. The load direction is written according to the coordinate direction used in the current project in Midas Gen, and the load value is converted into the load unit used in the current project and then written into the corresponding Midas Gen unit. When there are multiple load records for the same component record number, write them one by one according to the order of the Excel records; when the component record number, load direction or load value is missing, write the Excel row number and the missing field to the load exception record, and stop writing to the current load record. During the node constraint writing phase, the corresponding record of the node is found by using the Grasshopper connection point number in the boundary condition record and the Midas Gen node number is obtained. Then, the six constraint values ​​are read in the order of translation along the X-axis, translation along the Y-axis, translation along the Z-axis, rotation around the X-axis, rotation around the Y-axis, and rotation around the Z-axis. Each digit is written with either an integer zero or an integer one. A value of one is written to the constraint state of the corresponding degree of freedom, and a value of zero is written to the release state. After completing the six digits, the Grasshopper connector number, the Midas Gen node number, and the six-digit constraint value are written to the node constraint record. If the connection point number does not have a Midas Gen node number, the constraint value is missing, or a value other than zero or one appears, write a boundary condition exception record and stop writing the current node constraint. Once all node records, Midas Gen element records, load records, and node constraint records are completed, a finite element model is formed for structural analysis. Let's take two Rhino components that share a Grasshopper connection point as an example. After the first Rhino component reads the shared connection point, it generates a Grasshopper connection point number and a corresponding Midas Gen node number. When the second Rhino component reads the connection point again, it directly reuses the same number. Two Rhino components form Midas Gen elements with their respective first and last node numbers. The Excel load is then written into the corresponding element by the component record number, and the six-bit boundary conditions are written into the shared node by the Grasshopper connection point number. This establishes a continuous correspondence between component record number, Grasshopper connection point number, Midas Gen node number, and Midas Gen unit number, which can be directly read in the subsequent structural analysis process.

[0019] The optimization calculation module is used to send the finite element model into Midas Gen to perform structural analysis, read the stress ratio, slenderness ratio and deflection according to the Midas Gen element, and return to Rhino according to the component record number to generate structural index results, calculation report and component table; After the finite element model completes the writing of nodes, elements, loads and boundary conditions, the analysis process uses the Midas Gen element number as the index for reading structural results and uses the component record number to inherit the Rhino component, so that each structural analysis forms an independent analysis cycle, and the analysis results can continue to enter Rhino write-back, parameter modification, calculation sheet and component table generation. When the location of the support structure, the span of the truss, and the elevation change, the structural geometry model and finite element model are regenerated. When the load record or boundary conditions change, the corresponding finite element data is directly rewritten. All modifications are included in the next analysis cycle. This implementation process includes the following steps: When entering the structural analysis phase, the Midas Gen node records and Midas Gen element records in the current finite element model are written into the Midas Gen project. Then, the load records are written according to the element correspondence between the component record number and the Midas Gen element number, and the boundary condition records are written according to the node correspondence between the Grasshopper connection point and the Midas Gen node number. After the four types of records are written, the current analysis cycle is established. The first analysis writes the integer 1, and the subsequent analysis adds 1 to the previous analysis cycle. Then, a structural analysis execution command is sent to Midas Gen, and the analysis round and the current finite element model are written into an analysis execution record. After Midas Gen returns the analysis completion status, it proceeds to result reading. If it does not return the analysis completion status, the current analysis execution record is retained, and the structural indicators of the current round are not read. After the analysis is completed and the status is written, the result record of the current element is obtained one by one according to the Midas Gen element number. The stress ratio, slenderness ratio and deflection are read from the same result record. Then, the component record number is obtained by looking up the corresponding record of the element by the Midas Gen element number. For each Midas Gen element processed, the analysis round and component record number are written at the beginning of the structural index record, followed by the stress ratio, slenderness ratio and deflection, so that one component record number corresponds to one structural index record in one analysis round. If no structural index returns a value, the analysis round, Midas Gen unit number, and missing index name are written to the missing results record. The current component is not written to the structural index results of this round, and the next Midas Gen unit continues to be read. After all Midas Gen units have been read, the analysis results of the current round are composed of complete structural index records. When the results are passed to Rhino, the component record number in the structural index record is used to find the Rhino component with the same number in the structural geometry model. The current analysis round is written into the data record of the Rhino component, and then the stress ratio, slenderness ratio and deflection are written in order of fixed fields. If the component record number does not correspond to a Rhino component, the component record number and analysis round are written into the write-back exception record, and the current results are not written to other Rhino components. When the support position, truss span, or elevation in Excel is modified, the component record number referencing the corresponding input position is obtained from the parameter reference table, the corresponding Grasshopper component generation process is re-executed, and the finite element model is re-formed. When load records are modified, the Rhino components remain unchanged. The Midas Gen element is located by the component record number, and the corresponding load record is overwritten. When boundary conditions are modified, the Rhino components remain unchanged. The Midas Gen node number is obtained by the Grasshopper connection point, and the corresponding six-bit constraint value is overwritten. After the three types of modifications are processed, the next analysis cycle is established and the structural analysis execution command is resent. After all structural metrics for the current analysis round have been written back to Rhino, the platform receives a parameter confirmation instruction. The parameter confirmation command uses a single confirmation data. After the designer confirms the current parameters and the current analysis results, the confirmation data is changed from zero to one, and the current analysis round is saved at the same time. When the confirmation data remains zero, the current structural indicator record continues to be saved, and the platform accepts the next Excel parameter modification and establishes the next analysis round. Confirm that the data is temporarily stopped and a new analysis cycle is established based on the current design results. The structural indices with complete stress ratio, slenderness ratio and deflection in the current analysis cycle are recorded as structural index results, and this analysis cycle is used as the data reading cycle for the calculation sheet and component table. Once the structural index results are determined, the field names are read sequentially from the first data entry position in the calculation template. When the field name corresponds to an Excel parameter, the current field value is obtained according to the field name and its fixed data position and written to the current data writing position; when the field name is stress ratio, slenderness ratio or deflection, the component record number bound to the current data writing position is read, and then the unique structural index record is found by using the component record number and the confirmed analysis round, and the corresponding structural index value is written to the current position. After writing one data entry position, proceed to the next position until all data entry positions in the template have been assigned values. If the corresponding field value is not obtained, record the data entry position and field name and leave the position empty. After writing the remaining positions, form the calculation sheet corresponding to the current analysis round. The component table uses the component record number in the structural geometric model as the basis for writing each row. After creating the current row according to the component record number sequence, the component record number is written into the first field. Then, the component record number is used to locate the Rhino component and read the standardized component library record used by it. The component parameters are written into the current row according to the sequence of the existing fields in the component library record. Subsequently, the structural index records are obtained with the same component record number and the confirmed analysis round, and the stress ratio, slenderness ratio and deflection are written into the current row. After completing one component record number, proceed to the next component record number. When all Rhino component processing is completed, a component table is formed. If a component record number lacks a standardized component library record or structural index record, write the component record number and the name of the missing data into the component table's exception record, and retain the data already obtained in the corresponding row. A series of continuous analysis processes can demonstrate the connection between various data: after the first finite element model is written, analysis cycle one is established. Midas Gen returns the stress ratio, slenderness ratio and deflection according to the element number. Then, the component record number is obtained through the corresponding element record and written back to the corresponding Rhino component. If only one load record is modified, the original Midas Gen element is located by the component record number and the load is rewritten. The Rhino component retains its original record, and then analysis round two is established. If the truss span is modified, the affected component record number is obtained from the parameter reference table, the corresponding Rhino component is regenerated by Grasshopper, and the finite element model is re-formed. Then analysis round three is established. After the third analysis round is confirmed, the structural index records are read together using the third analysis round and the component record number, and written into the calculation sheet and component table respectively, so that the final design results correspond to the same round of parameters and structural analysis results.

[0020] The drawing generation module is used to generate plan views, elevation views and section views based on the structural geometric model, generate detailed node drawings according to the node connection components and structural index results, and perform node verification to generate construction drawings; The construction drawings are generated using the structural geometric model and the confirmed analysis rounds as the unified data source. First, the longitudinal direction, transverse direction and vertical direction of the trestle are established, and then the plan view, elevation view and section view are generated according to the standard drawing template. The node detail drawing continues to obtain the connecting components and the results of the current analysis round along the Midas Gen node number, Midas Gen element number, and component record number, and writes the node verification results into the corresponding node detail drawing, so that the component positions, node relationships, and analysis results in the drawing correspond to the current structural geometric model; this implementation process includes the following steps: In the drawing output stage, three drawing directions are first determined; the column position with the first position and the column position with the last position are read from the column distribution record, and the direction of the line connecting the two positions from the first column to the last column is written as the longitudinal direction of the trestle. Read the vertical direction directly from the Rhino engineering coordinates and write it as the vertical direction of the trestle. Then, take the direction perpendicular to the longitudinal direction of the trestle in the Rhino horizontal plane and write it as the transverse direction of the trestle. After writing the three directions into the current drawing generation record, read the Rhino components in the structural geometry model one by one. When creating the plan view, project the geometric points on the Rhino components orthogonally along the vertical direction of the trestle onto the plane formed by the longitudinal and transverse directions of the trestle, and connect the projected points according to the original connection sequence of the Rhino components. When creating the elevation view, the geometric points on the same Rhino component are orthographically projected along the transverse direction of the trestle to the plane formed by the longitudinal and vertical directions of the trestle, while keeping the original component record number written to the corresponding projection object. When a Rhino component lacks a component record number or the geometry object is empty, the component record number reading location and exception type are written into the drawing generation record, and the current Rhino component is not included in the current projection round. When generating the section view, the sectioning records are read one by one from the standard drawing template. Each sectioning record determines the sectioning plane with a sectioning point and a sectioning direction. The sectioning point is saved using Rhino engineering coordinates, and the sectioning direction is the longitudinal direction of the trestle or the sectioning direction already saved in the template. Read Rhino components sequentially according to component record number, and perform an intersection check between the component geometry and the cutting plane; if an intersection point exists, write the current Rhino component into the current cutting record, and project the intersecting part along the normal of the cutting plane onto the drawing plane formed by the horizontal and vertical directions of the trestle; if no intersection point exists, continue reading the next Rhino component. After one sectioning record is processed, the current section drawing is saved in the order of the sectioning records, and then the next sectioning record is read, until all sectioning records in the standard drawing template are completed. When a sectioning record is missing a sectioning point or sectioning direction, write the template location and the name of the missing field and stop generating the current section view; After entering the node detail processing, the current Midas Gen node number is used as the starting point for node reading. The Midas Gen unit records are traversed, and the Midas Gen unit number that is consistent with the current Midas Gen node number at the beginning or end is written into the node connection record. Then, the component record number is obtained by looking up the corresponding record of each Midas Gen unit number, and the node record used by the corresponding Rhino component is read by the component record number; The node record uniformly stores the connection position of the node in Rhino, the component record number of the connected node, and the node detail reading field; the component record numbers with the same Midas Gen node number are written to the current node connection record according to the unit reading order, and then written to the corresponding position of the node detail according to the detail data stored in the node record. When a node record is missing or a corresponding Rhino component is not obtained for a component record number, the Midas Gen node number and the missing object are written to the node detail diagram exception record, and the current node does not output a node detail diagram. The node verification continues to read the structural analysis results that have been formed along the current analysis cycle; first, the node connection record is obtained according to the current MidasGen node number, and then the corresponding structural index record is obtained one by one according to the component record number and the current analysis cycle. The data corresponding to the defined verification input position in the node record is written in a fixed input order. After all the input data is written, the node verification content already saved in the node record is called to perform the verification, and the return value is read from its result position. The return value, together with the Midas Gen node number and the current analysis round, is written into the node verification result, and then written into the verification result position of the current node detail diagram. When no corresponding data is obtained at a certain verification input position, the Midas Gen node number, input position and missing data name are written to the node verification exception record, and the current node verification does not generate a result; Finally, the template positions of the plan view, elevation view, section view and node detail view are written into the current drawing file in sequence, and the Rhino component is kept in correspondence with the drawing object by component record number, the node detail view is kept in correspondence with the finite element node by Midas Gen node number, and the node verification result is kept in correspondence with the structural index result by the current analysis cycle. Taking a structural geometric model containing three column records and two trestle sections as an example, the longitudinal direction of the trestle is first determined by the position of the first column and the position of the last column, and then the plan view and elevation view are generated; the corresponding sectional view is generated after reading the section record in the standard drawing template. For a Midas Gen node located at the connection between two components, the Midas Gen element connected to the node is read and the corresponding component record number is obtained. Then, the node verification input data is read by the current analysis cycle and node details and node verification results are generated. Finally, construction drawings consistent with the current structural geometric model and the current analysis cycle are output.

[0021] The data collaboration module is used to connect Rhino components, Midas Gen units, and Tekla components according to component record numbers to form a detailed model; after the Excel parameters are modified, the structural geometric model is regenerated according to the component record numbers referenced by the parameters and finite element analysis is performed, and then the structural index results, calculation sheets, component tables, construction drawings, and detailed models are rewritten. Data transfer between Rhino, Midas Gen and Tekla uses the component record number as a continuous index. The spatial position of the components adopts the same engineering coordinate benchmark, and the length is converted according to their respective engineering units before being written into different software. The structural geometric model, finite element model, and detailed model are associated with each other through component record number, Midas Gen element number, and Tekla component number; After the Excel parameters change, the scope of geometric reconstruction or finite metadata rewriting is determined based on the parameter type, and then analysis results and design outcomes consistent with the current parameters are regenerated. This implementation process includes the following steps: Entering the in-depth data organization stage, Rhino components are read one by one according to the component record number; for each Rhino component processed, the start position, end position and the current geometric direction of the Rhino component are read, and the Midas Gen unit number, start Midas Gen node number and end Midas Gen node number are obtained from the corresponding unit record, and the component category and existing component parameters in the corresponding standardized component library record are read. The first and last positions are represented using Rhino engineering coordinates. Before writing them into Tekla, the length units used in Tekla engineering are converted, and the coordinate axis direction is kept consistent with that of Rhino engineering. After the conversion is completed, the component record number, the positions of both ends, the Midas Gen unit number, the Midas Gen node numbers of both ends, and the standardized component library record are written into a component transfer record according to the fixed field order. If any component lacks a corresponding unit record, endpoint data, or standardized component library record, the component record number and missing item are written into the transmission exception record, and the current component transmission is stopped; after the component transmission record is formed, it is sent to Tekla in order of component record number. Tekla reads the start and end positions to determine the layout of the detailed components, then reads the component category and component parameters from the standardized component library record to create the corresponding detailed components. After generation, it returns the Tekla component number. The Tekla component number and the component record number are written to the same detailed corresponding record, so that a component record number obtains a currently valid Tekla component number. Subsequent components are processed in the same order until all components are transferred and a detailed model is formed; if Tekla does not return a component number, the current component transfer record and component record number are saved, but no corresponding detailed record is created. Parameter modification judgment starts from the saved results of the previous round of parametric design; after each completion of the structural geometric model, finite element model, structural index results, calculation sheet, component table, construction drawings and detailed model, the field values ​​are saved according to the worksheet name, row number, column number and field name in Excel. The next time the Excel file is read, the current field value is read from the same data position; after the numeric field is unified to the corresponding engineering unit, the current field value is subtracted from the saved field value, and if the difference is not zero, it is written to the change field record; the character field is compared character by character in order, and if there are different characters, it is also written to the change field record. When multiple change fields correspond to the same component record number, only one component reconstruction record is retained to avoid duplicate generation of the same Rhino component. After the change field is generated, it is processed according to the location of the data. When the position of the support, the span of the truss and the elevation change, the parameter reference table is searched by worksheet name, row number, column number and field name to obtain all the record numbers of the affected components. The corresponding Grasshopper component chain is re-executed according to the original component order, and the original Rhino component with the same component record number is replaced with the newly generated Rhino component. When adding or deleting columns, the subsequent trestle segment sequence and component record number are re-established starting from the position of the column that has changed, and the original component records that have lost their corresponding relationship are deleted. When the load record changes, keep the Rhino component unchanged, obtain the Midas Gen element number from the component record number and rewrite the corresponding load; when the boundary conditions change, obtain the Midas Gen node number from the Grasshopper connection point number and rewrite the six-bit constraint value. After the geometric components are rebuilt, the Midas Gen node records and Midas Gen unit records for the current round are regenerated based on the updated complete structural geometric model. Then, the loads and boundary conditions are written so that the shared Grasshopper connection points continue to correspond to the same Midas Gen node. Once the limited metadata update is complete, the next analysis cycle is established, the Midas Gen structural analysis is re-executed, and the stress ratio, slenderness ratio and deflection are read according to the Midas Gen element number. Then, the results are written back to Rhino along the component record number to form new structural index results. The calculation sheet rereads the Excel field values ​​and structural index values ​​according to the confirmed analysis round; the component table is rewritten with component parameters and three structural indices according to the current component record number; the construction drawings continue to read the current structural geometric model, where the plan view, elevation view and section view are generated based on the updated Rhino components, and the node details are written with the node verification results corresponding to the current analysis round, thus ensuring that the calculation sheet, component table and construction drawings use the same round of parameters and structural analysis data; The model refinement update continues along the new component record number; for components that already have a refinement record, the original Tekla component number is saved first, and then the newly generated component transfer record is sent; after Tekla successfully forms a new refinement component and returns a new Tekla component number, the original refinement component is located and deleted using the original Tekla component number, and then the new Tekla component number is overwritten into the refinement record. When a new component is added, a new detail record is created directly. When a component is deleted, the corresponding detail component is deleted based on the original Tekla component number, and the corresponding detail record is deleted simultaneously. If a new component is not created or Tekla does not return a new component number, the original detailed record remains unchanged, and the current component record number is written to the detailed update exception record. A single continuous modification process can reflect the update relationship of the entire data chain: after the truss span changes, the affected component record number is obtained from the parameter reference table and the corresponding Rhino component is regenerated. Then, the Midas Gen node and Midas Gen element are re-formed based on the current complete structural geometry model. When only the load value changes, the load record of the corresponding Midas Gen element is directly rewritten. After the new structural analysis is completed, the same component record number continues to carry over the structural index results, calculation sheets, component tables and construction drawings, and a new component transfer record is generated and sent to Tekla; After all the changed fields have been processed, the current Excel field values ​​will overwrite the field values ​​saved in the previous round, and finally the structural geometric model, finite element model, structural index results, calculation sheets, component tables, construction drawings and detailed models of this round will be saved.

[0022] exist Figure 1 It should be noted that the system sequentially enters the parametric modeling module, analysis data interface module, optimization calculation module, drawing generation module, and data collaboration module from Excel design parameters, respectively completing the generation of structural geometric model, finite element model conversion, structural analysis, construction drawing generation, and Tekla detailed model formation; solid arrows indicate the data transfer direction in the normal design process, while dashed arrows indicate the update path after Excel parameters are modified, i.e., returning to the parametric modeling module according to component record number and parameter reference relationship, and continuing to update subsequent analysis, drawings, and detailed models; Figure 2 The data organization of the column parameter file is shown in the figure. The file records the total number of column records in the "total pillars" field, which is 16 in the figure. The column records are saved sequentially according to their order in the "pillars" field. Each column record includes the fields "name", "distance from start", "distance from previous", and "height". "Name" records the name of the column, "distance from start" records the distance of the current column from the starting point of the trestle, "distance from previous" records the distance of the current column from the previous column, and "height" records the vertical dimension value of the current column. For example, the distance from the starting point of column 1 is 27000, column 2 is 54000, and column 3 is 81000. The column records are read sequentially according to their order in the file, thus forming the column position and vertical dimension data used for subsequent parametric modeling. Figure 3The diagram illustrates the Grasshopper process of reading and transmitting input data. The sampledata area on the left provides the data to be processed and its corresponding extended information. The data enters the encodedFile and extension components, and then is sent to the central data processing component along the Grasshopper connection. After receiving the input data and extended information, the processing component generates the output result and continues to pass it to subsequent components. The display area on the right is used to view the currently processed data content and status. The lines between the components in the diagram represent the direction of data transmission, reflecting the execution process of Grasshopper transmitting parameters sequentially from the data input end, parameter processing component, and output end, providing parameterized data for the subsequent generation of Rhino components.

[0023] Overall Execution and Implementation: This scheme first uses edge computing nodes to read the support locations, truss spans, elevations, loads, and boundary conditions from Excel. Rhino and Grasshopper then generate a geometric model of the trestle structure, which is then converted into a Midas Gen finite element model for structural analysis. The stress ratio, slenderness ratio, and deflection are obtained, and calculation sheets, component lists, and construction drawings are generated accordingly. Subsequently, the corresponding components are transferred to Tekla to form a detailed model. Each stage is connected through component record numbers. After parameter modifications, the edge computing nodes update the affected components and subsequent results along the parameter reference relationships. For example, after adjusting the truss span of a certain trestle, the edge computing node first triggers the platform to regenerate the corresponding Rhino component, then updates the Midas Gen unit and recalculates the structural parameters, and then synchronously updates the calculation sheet, component table, construction drawings and Tekla detailed components, so that the modified parameters can be continuously transmitted to the final design results.

[0024] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. An intelligent parametric design platform for prefabricated trestle bridges, characterized in that, include: The parametric modeling module is used to read the support positions, truss spans and elevations from Excel, form the column distribution according to the support positions, write adjacent columns as trestle segments, and use Rhino and Grasshopper to call the standardized component library to generate the structural geometric model, and form component record numbers according to the trestle segment sequence and the sequence of components within the segment. The data interface module is used to read the connection points at both ends of the component according to the component record number, write the same Grasshopper connection point as the same Midas Gen node, form Midas Gen elements with the nodes at both ends of the component, and write the loads and boundary conditions in Excel into the corresponding elements and nodes respectively to form a finite element model. The optimization calculation module is used to send the finite element model into Midas Gen to perform structural analysis, read the stress ratio, slenderness ratio and deflection according to the Midas Gen element, and return to Rhino according to the component record number to generate structural index results, calculation report and component table; The drawing generation module is used to generate plan views, elevation views and section views based on the structural geometric model, generate detailed node drawings according to the node connection components and structural index results, and perform node verification to generate construction drawings; The data collaboration module is used to connect Rhino components, Midas Gen units, and Tekla components according to component record numbers to form a detailed model. After the Excel parameters are modified, the structural geometric model is regenerated according to the component record numbers referenced by the parameters, and finite element analysis is performed. Then, the structural index results, calculation sheets, component tables, construction drawings, and detailed models are rewritten.

2. The intelligent parametric design platform for prefabricated trestle bridges according to claim 1, characterized in that: The parametric modeling module includes: Read the total pillars field from the pillar parameter file, write the integer in the field as the total number of pillar records, and then read from the first record according to the record order in the pillars field. Write the name field of each record as the pillar name, the distance from start field as the distance from the starting point, the distance from previous field as the distance from the previous pillar, and the height field as the vertical dimension value. For the first column record, the column position is obtained by taking the distance from start field value as the distance along the Rhino longitudinal axis from the starting point of the trestle; for the next column record, the current column position is formed by adding the distance from previous field value in the current record to the previous column position, and the current column position is checked against the distance from start field value in the current record item by item. If the two values ​​match, the current record is retained; if the two values ​​do not match, the distance from start field value is written to the current column position, and the distance from previous field value is subtracted from the current column position and rewritten. After each pillar record is written, the reading sequence number is incremented by one. The reading ends when the reading sequence number equals the integer in the total pillars field. The pillar positions are then connected according to the reading sequence number to output the pillar distribution record.

3. The intelligent parametric design platform for prefabricated trestle bridges according to claim 2, characterized in that: The parametric modeling module also includes: Starting from the first record of the column distribution, read two adjacent columns, take the current column as the starting column of a trestle segment, take the next column as the ending column of the same trestle segment, and write the trestle segment order in ascending order of integers starting from the starting point of the trestle. After Grasshopper reads the starting column position and the ending column position, it generates the upper longitudinal beam and the lower longitudinal beam respectively along the longitudinal connection direction between the two columns. Then, it generates the cross beam connecting the upper longitudinal beam and the lower longitudinal beam at the starting column position and the ending column position. Finally, it generates the support at the connection point connecting the longitudinal beam and the cross beam in Grasshopper. When the support falls into the current trestle segment, the support record is read from the standardized component library and written to the support position. When two components share the Grasshopper connection point, the node record is read and written to the connection point. When the support is connected to the main structure of the trestle, the support record is read and written to the connection position. The standardized component library saves component records according to existing class standard components and retains the component parameters in the called component record when generating components. Write the component order within the current trestle segment according to the order in which Grasshopper generates the components, starting from the beginning. Write the trestle segment order first and the component order within the segment last to form a component record number, and output the structural geometric model with the component record number.

4. The intelligent parametric design platform for prefabricated trestle bridges according to claim 3, characterized in that: The parametric modeling module also includes: For each component record number in the structural geometry model, the Excel field name read when generating the current component and the component record number are written on the same line to form a parameter reference record. When a component reads more than two Excel fields, corresponding parameter reference records are created respectively. All parameter reference records are collected by field name to form a parameter reference table. When performing local adjustments, the parameter reference table is searched row by row by the input Excel field name. The component record number of each row with the same field name is written into the reconstruction priority. Then, the corresponding Grasshopper component generation process is re-executed according to the reconstruction priority, and the Rhino component corresponding to the original component record number is replaced with the newly formed Rhino component. When adding a component, add a component order to the component order of the last segment of the specified stack segment, and form a new component record number with the same stack segment order; when deleting a component, locate the Rhino component with the component record number and delete it, and delete all records in the parameter reference table that have the same component record number. For regenerated, added, or retained components, the corresponding component record number will continue to be used.

5. The intelligent parametric design platform for prefabricated trestle bridges according to claim 4, characterized in that: The analytical data interface module includes: Read Rhino components sequentially according to their component record numbers. For each Rhino component read, obtain the first and last connection points used when Grasshopper generates the component. Use Grasshopper connection points as the basis for node merging. When a connection point appears for the first time, write the Midas Gen node number from the beginning. When a subsequent component uses the same Grasshopper connection point that has already been written with the Midas Gen node number, directly read the existing Midas Gen node number. After obtaining the Midas Gen node number for both the first and last connection points of the current Rhino component, the two node numbers are written into a Midas Gen unit record in the order of first and last connection points. The Midas Gen unit number is then written in ascending order from the first to the last component record number. Finally, the component record number and the Midas Gen unit number are written on the same line to form a corresponding unit record. When reading load records from Excel, the Midas Gen element number is obtained from the corresponding element record based on the component record number pointed to by the load record. Then, the load direction and load value are written into the corresponding Midas Gen element. When reading boundary conditions, the Midas Gen node number is obtained from the Grasshopper connection point pointed to by the boundary conditions. Then, the constraint values ​​are written one by one according to the original order of the Midas Gen node degrees of freedom. A value of 1 indicates a constraint, and a value of 0 indicates a release. The finite element model with the loads and boundary conditions written is then output.

6. The intelligent parametric design platform for prefabricated trestle bridges according to claim 5, characterized in that: The optimization calculation module includes: After the finite element model is sent into Midas Gen, a structural analysis command is sent, and the analysis round number is written starting from an integer. The subsequent structural analysis command is based on the previous analysis round number plus one. After Midas Gen completes the current analysis cycle, it reads the stress ratio formed by each element in sequence according to the Midas Gen element number, then reads the slenderness ratio and deflection formed by the same element, and finds the corresponding record of the element by the Midas Gen element number to obtain the component record number. The analysis cycle, component record number, stress ratio, slenderness ratio and deflection are written on the same line to form a structural index record. When returning analysis results to Rhino, the Rhino component is located by the component record number, and the stress ratio, slenderness ratio and deflection corresponding to the current analysis round are written into the data record of the Rhino component. When the Excel parameters are modified and resubmitted, the component record number referenced by the modified field is obtained from the parameter reference table, the corresponding Rhino component is regenerated, the finite element model is formed again, and the next analysis round is sent. Upon receiving the parameter confirmation instruction for this round, the system stops establishing analysis rounds and writes the stress ratio, slenderness ratio, and deflection corresponding to the record number of each component in this round as structural index results.

7. The intelligent parametric design platform for prefabricated trestle bridges according to claim 6, characterized in that: The optimization calculation module also includes: When generating the calculation sheet, the field names are read sequentially from the first write position of the calculation sheet template. If the field name matches the field name in Excel, the current Excel field value is written to the corresponding position. If the field name is stress ratio, slenderness ratio, or deflection, the component record number bound to the current write position is read first, and then the structural index record is searched using the component record number and the current analysis round. The structural index value with the same name is written to the corresponding position until all write positions of the calculation sheet template are completed. When generating the component table, the component table records are created row by row according to the component record number in the structural geometry model. Each row first writes the component record number, then reads the standardized component library record used by the current Rhino component from the component record number, and writes the corresponding component parameters according to the original field order of the component library. Then, the structural index record is obtained with the same component record number and the current analysis round, and the stress ratio, slenderness ratio and deflection are written in the same row. After writing all component record numbers in the current structural geometric model, output the calculation sheet and component table corresponding to the current analysis round.

8. The intelligent parametric design platform for prefabricated trestle bridges according to claim 7, characterized in that: The drawing generation module includes: Read the position of the first and last pillar in the pillar distribution record. Take the direction of the line connecting the two pillar positions as the longitudinal direction of the trestle, take the Rhino vertical direction as the vertical direction of the trestle, and take the direction that is perpendicular to both the longitudinal and vertical directions of the trestle as the lateral direction of the trestle. When generating a plan view, each Rhino component in the structural geometry model is read and projected onto the plane formed by the longitudinal and transverse directions of the trestle; when generating an elevation view, identical Rhino components are projected onto the plane formed by the longitudinal and vertical directions of the trestle; when generating a section view, the sectioning position is read from the standard drawing template, and each Rhino component is checked to see if it intersects with the sectioning position. The intersecting Rhino components are then projected onto the plane formed by the transverse and vertical directions of the trestle. When generating node details, the Midas Gen elements connected to the current node are read by the Midas Gen node number, and the component record number is obtained from the corresponding record of the element. The node data is then read according to the standard component record corresponding to each component record number. The analysis results corresponding to the components connected to the current node in the current analysis round are written to the node verification input position. The node verification process saved in the standard node record is executed, and the returned results are written to the node details corresponding to the current node, and the construction drawings are output.

9. The intelligent parametric design platform for prefabricated trestle bridges according to claim 8, characterized in that: The data collaboration module includes: Component transfer records are created sequentially according to component record number. For each component record number processed, the start and end positions of the corresponding component are first read from Rhino, then the corresponding Midas Gen unit number, start Midas Gen node number, and end Midas Gen node number are read from the corresponding unit record, and then the standardized component library record used by the current Rhino component is read. Write the component record number to the beginning of the component transfer record, and then write the first end position, the last end position, the MidasGen unit number, the first end Midas Gen node number, the last end Midas Gen node number, and the standardized component library record according to the reading order. After completing a component transfer record, send it to Tekla. Tekla generates corresponding detailed components based on the component transfer record and returns the Tekla component number. The returned Tekla component number and the component record number are written on the same line to form a detailed corresponding record. The next component continues to perform the same transfer process according to the component record number sequence. After all components are completed, the detailed model is output.

10. The intelligent parametric design platform for prefabricated trestle bridges according to claim 9, characterized in that: The data collaboration module also includes: After each parametric design is completed, the field values ​​are saved in order of Excel field names. The next time the Excel is read, the current field value is read item by item according to the same field name and subtracted from the saved field value. If the difference is not zero, the corresponding field name is written to the changed field record. If the difference is zero, the next field is read. The parameter reference table is searched sequentially according to the field names in the changed field records. The component record numbers with the same field names are written into the reconstruction record according to the original component order. The parametric modeling module re-executes the corresponding Grasshopper component generation process according to the reconstruction record, replaces the original Rhino component corresponding to the same component record number with the regenerated Rhino component, and then the analysis data interface module re-forms the corresponding Midas Gen nodes and Midas Gen elements, and re-writes the loads and boundary conditions. The optimization calculation module establishes the next analysis round and re-executes the structural analysis. The resulting structural index results are returned to Rhino according to the component record number. Then, the same component record number is used to rewrite the calculation sheet, component table, and construction drawings. Subsequently, the component transfer record is regenerated according to the reconstructed component record number and sent to Tekla. The component number returned by Tekla replaces the original Tekla component number in the corresponding detailed record. After all the components corresponding to the changed fields have been processed, the current Excel field values ​​will replace the saved field values, and the structural geometric model, finite element model, structural index results, calculation sheet, component table, construction drawings and detailed model after the parameter modification will be output.

Images