Flood routing simulation method and device for multilayer underground building

Abstract

The invention discloses a flood routing simulation method and device for a multilayer underground building. The flood routing simulation method comprises the following steps: constructing a logical topology network structure of a multilayer underground building, wherein single-layer two-dimensional plane geometric information comprises height distribution of floors of floors; based on the constructed logical topology network structure, aiming at each floor in the multi-floor underground building, executing the following contents: determining configuration data of the floor; associating boundary data with the determined configuration data; calling a two-dimensional hydrodynamic numerical simulation engine based on the determined configuration data, and determining floor submerging process data; judging whether the floor is the last floor of the multi-floor underground building or not; under the condition that the floor is not the last floor of the multi-floor underground building, inflow boundary data of the next floor corresponding to the floor are determined, and the inflow boundary data indicate the change condition of flood flowing into the next floor from the floor along with time. Therefore, the flood routing simulation of the multi-layer underground building is realized.

Description

Technical Field

[0001] This application relates to the interdisciplinary fields of architectural engineering, water conservancy engineering and computer simulation, and more specifically, to a method and apparatus for simulating flood evolution in multi-story underground buildings. Background Technology

[0002] With the intensification of global climate change and the increasing frequency of extreme rainfall events, the risk of urban flooding is becoming increasingly prominent. Multi-story underground structures, characterized by their complex structures, dense populations, and difficulties in rescue efforts, are particularly vulnerable to significant property damage and casualties should floodwaters infiltrate them, making them a top priority for urban flood control. Therefore, accurate flood evolution simulation of such facilities is a prerequisite for scientific and effective disaster prevention and mitigation.

[0003] Simulating flood evolution in multi-story underground structures presents profound and irreconcilable technical contradictions, primarily including the following: 1) The "planar limitations" of two-dimensional models and the "three-dimensional conflict" with the application scenario. Two-dimensional shallow water equation models and their derivative methods (such as efficient models based on cellular automata) are currently the mainstream technologies in the field of flood simulation. They achieve rapid simulation of large-scale surface runoff by solving the water flow equations on a single, continuous digital elevation model (DEM). However, their core assumption is the "planarity" of the computational object. The essential characteristics of multi-story underground structures are "three-dimensional layering" and "vertical discontinuity." It consists of multiple independent floors that overlap vertically in space but are strictly separated by physical entities such as floor slabs and ceilings. If such a three-dimensional structure is forcibly input into a two-dimensional model, the model will fail to recognize the internal multi-layer topological relationships, leading to computational logic collapse and the inability to obtain any meaningful results. This is a fundamental "application object mismatch." 2) The "model gap" in the vertical hydraulic transmission mechanism. In real flood disasters, the propagation of water within multi-story buildings is primarily driven by gravity flow from top to bottom, achieved through various vertical connecting components (such as open stairwells, elevator shafts, atriums, ventilation shafts, and drainage pipes). This vertical hydraulic transfer process across floors is the core physical mechanism determining the order, speed, and extent of flooding throughout the building. However, two-dimensional models, in their theoretical framework and mathematical expression, completely lack a description of this vertical flow. They are designed to simulate horizontal flow, resulting in a "model mechanism gap" when dealing with vertical water flow that "penetrates" the floor slabs. 3) The "high precision, high cost" dilemma of three-dimensional models. As a theoretically perfect solution, three-dimensional computational fluid dynamics (CFD) models (such as solvers based on the Navier-Stokes equations) can precisely characterize arbitrarily complex three-dimensional flow fields within buildings. However, this high precision comes at the cost of extremely high computational costs. For a large-scale underground complex, constructing a three-dimensional computational mesh capable of capturing key flow details often requires hundreds of millions or even more meshes. This not only demands extremely high professional skills from modelers, but also results in a single simulation taking days or weeks to compute, requiring the support of high-performance computing clusters. This characteristic of "high precision, high cost, and low timeliness" makes it virtually unusable in engineering practices requiring multi-solution comparisons, rapid risk assessments, or emergency response decisions. 4) The "inefficiency, subjectivity, and unreliability" of manual layered coupling. To find a compromise between efficiency and accuracy, engineers sometimes try a "manual layering" compromise. That is, each layer is calculated as a separate two-dimensional model, and then a connection is artificially established between the two calculations.This process is usually as follows: First, manually run the simulation of the upper layer (such as B1F); then, in the complex output data, painstakingly find the water depth change data at locations such as the stairwell by eye or script tools; next, estimate a flow rate value for entering the next layer (B2F) based on highly simplified empirical formulas or even subjective guesswork; finally, use this estimated value as a boundary condition to manually configure and start the simulation of B2F. This process has fatal flaws. (1) Inefficiency. The whole process is highly dependent on manual operation, which is time-consuming and laborious, and cannot be used for batch and automated analysis. (2) High subjectivity. The method of estimating the flow rate between layers lacks a unified standard and physical basis, and different engineers may get completely different results, resulting in subjective and unreliable simulation conclusions. (3) Dynamic distortion. Usually, only a constant or segmented flow rate can be estimated, which cannot truly reflect the real-time and nonlinear impact of the dynamic fluctuation of the upper layer water depth on the inflow of the lower layer, resulting in serious distortion of the physical process. (4) Error accumulation. The manual handling process between each floor may introduce new errors, which will be passed on and amplified layer by layer, eventually leading to a situation where the simulation results of the flooding process of the entire building are completely different from the actual situation.

[0004] Therefore, simulating flood evolution in multi-story underground structures presents significant technical challenges. Currently, there is a lack of an effective methodology that can scientifically, rigorously, and automatically combine the efficient computational capabilities of two-dimensional flood models with the three-dimensional structural characteristics of multi-story underground structures to achieve flood evolution simulation.

[0005] Therefore, how to simulate the flood evolution of multi-story underground buildings has become a technical problem that needs to be solved in this field. Summary of the Invention

[0006] In view of this, this application proposes a method and apparatus for simulating flood evolution in multi-story underground buildings, so as to realize the simulation of flood evolution in multi-story underground buildings.

[0007] Firstly, this application proposes a flood evolution simulation method for multi-story underground buildings. This flood evolution simulation method includes: constructing a logical topology network structure for the multi-story underground building, following a floor-to-floor order, using the single-layer two-dimensional planar geometric information of a single floor as nodes and the vertical connection component data between adjacent floors as directed edges. The single-layer two-dimensional planar geometric information includes the floor height distribution. Based on the constructed logical topology network structure, for each floor in the multi-story underground building, the following is performed: determining the configuration data of the floor, wherein the configuration data includes the single-layer two-dimensional planar geometric information of the floor, simulation start time, simulation end time, simulation calculation step size, and so on. The method describes the ground roughness coefficient and output parameters of the floor, including the output path and output frequency of the simulation results; it associates boundary data with the determined configuration data, wherein the boundary data indicates the change of floodwater received by the floor over time; based on the determined configuration data, it calls a two-dimensional hydrodynamic numerical simulation engine to determine the inundation process data of the floor; it determines whether the floor is the last floor of the multi-story underground building; if the floor is not the last floor of the multi-story underground building, it determines the inflow boundary data of the next floor corresponding to the floor, wherein the inflow boundary data indicates the change of floodwater flowing from the floor to the next floor over time.

[0008] Optionally, for each floor in the multi-story underground building, the determined configuration data is associated with boundary data, including: determining whether the floor is the top floor of the multi-story underground building; if the floor is the top floor of the multi-story underground building, determining the boundary condition type of the floor as rainfall, and associating the determined configuration data with rainfall boundary data, wherein the rainfall boundary data indicates the change of rainfall intensity over time; if the floor is not the top floor of the multi-story underground building, determining the boundary condition type of the floor as inflow, and associating the determined configuration data with the inflow boundary data of the floor.

[0009] Optionally, for each floor, if the floor is not the last floor of the multi-story underground building, the inflow boundary data of the next floor corresponding to the floor is determined, including: parsing the determined flooding process data to obtain the temporal water depth data at each outflow monitoring point of the floor; for each outflow monitoring point, the following is performed to determine the inflow boundary data: based on the constructed logical topology network structure, the geometric attributes of the inflow area corresponding to the outflow monitoring point are determined on the next floor corresponding to the floor, wherein the geometric attributes include the area of ​​the cross-section of the water flow; based on the temporal water depth data at the outflow monitoring point and the determined geometric attributes, the temporal flow rate data of the inflow area corresponding to the outflow monitoring point is determined.

[0010] Secondly, this application also provides a flood evolution simulation device for a multi-story underground building. The flood evolution simulation device includes: a first processing module, configured to construct a logical topology network structure of the multi-story underground building according to the order of floors from high to low, using the single-layer two-dimensional planar geometric information of a single floor as nodes and the vertical connection component data between adjacent floors as directed edges, wherein the single-layer two-dimensional planar geometric information includes the floor height distribution; and a second processing module, configured to, based on the constructed logical topology network structure, perform the following for each floor in the multi-story underground building: determine the configuration data of the floor, wherein the configuration data includes the single-layer two-dimensional planar geometric information of the floor, the simulation start time, and the simulation end time. The simulation process includes: calculating the step size, the ground roughness coefficient of the floor, and output parameters, including the output path and output frequency of the simulation results; associating boundary data with the determined configuration data, wherein the boundary data indicates the change of floodwater received by the floor over time; based on the determined configuration data, calling a two-dimensional hydrodynamic numerical simulation engine to determine the inundation process data of the floor; determining whether the floor is the last floor of the multi-story underground building; if the floor is not the last floor of the multi-story underground building, determining the inflow boundary data of the next floor corresponding to the floor, wherein the inflow boundary data indicates the change of floodwater flowing from the floor to the next floor over time.

[0011] Optionally, the second processing module associates boundary data with the determined configuration data for each floor in the multi-story underground building, including: determining whether the floor is the top floor of the multi-story underground building; if the floor is the top floor of the multi-story underground building, determining the boundary condition type of the floor as rainfall, and associating the determined configuration data with rainfall boundary data, wherein the rainfall boundary data indicates the change of rainfall intensity over time; if the floor is not the top floor of the multi-story underground building, determining the boundary condition type of the floor as inflow, and associating the determined configuration data with the inflow boundary data of the floor.

[0012] Optionally, for each floor, if the floor is not the last floor of the multi-story underground building, the second processing module determines the inflow boundary data of the next floor corresponding to the floor, including: parsing the determined flooding process data to obtain the temporal water depth data at each outflow monitoring point of the floor; for each outflow monitoring point, performing the following to determine the inflow boundary data: based on the constructed logical topology network structure, determining the geometric attributes of the inflow area corresponding to the outflow monitoring point on the next floor corresponding to the floor, wherein the geometric attributes include the area of ​​the cross-section of the water flow; based on the temporal water depth data at the outflow monitoring point and the determined geometric attributes, determining the temporal flow rate data of the inflow area corresponding to the outflow monitoring point.

[0013] Thirdly, this application also provides a machine-readable storage medium storing instructions that cause a machine to execute the flood evolution simulation method described above.

[0014] Fourthly, this application also provides an electronic device comprising: a processor; a memory for storing executable instructions of the processor; the processor being configured to read the executable instructions from the memory and execute the executable instructions to implement the flood evolution simulation method described above.

[0015] According to the technical solution of this application, a logical topology network structure for a multi-story underground building is constructed. Based on the constructed logical topology network structure, configuration data is determined for each floor in descending order of floor height, and the flooding process data for that floor is obtained by calling a two-dimensional dynamic numerical simulation engine. In this way, flood evolution simulation of a multi-story underground building is realized. Furthermore, in the process of realizing flood evolution simulation of a multi-story underground building, the two-dimensional dynamic numerical simulation engine is scientifically and rigorously combined with the multi-story underground building, and it is fully automated without human intervention.

[0016] Other features and advantages of this application will be described in detail in the following detailed description section. Attached Figure Description

[0017] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application, and the illustrative embodiments and descriptions thereof are used to explain this application. In the drawings: Figure 1 This is a flowchart of a flood evolution simulation method for multi-story underground buildings according to a preferred embodiment of this application; Figure 2 This is a flowchart illustrating the project initialization and computational model construction according to a preferred embodiment of this application; Figure 3This is a standardized two-dimensional hydrodynamic simulation packaging flowchart according to a preferred embodiment of this application; Figure 4 This is a flowchart of the interlayer dynamic hydraulic interface according to a preferred embodiment of this application; Figure 5 A flowchart illustrating the automated scheduling engine and job management process according to a preferred embodiment of this application; Figure 6 A general flowchart of a preferred embodiment according to this application; and Figure 7 This is a structural block diagram of a flood evolution simulation device for a multi-story underground building according to a preferred embodiment of this application. Detailed Implementation

[0018] The technical solution of this application will now be described in detail with reference to the accompanying drawings and embodiments.

[0019] This application provides a technical solution that enables flood evolution simulation of multi-story underground buildings, allowing mature "planar" simulation tools to maximize their effectiveness in new "three-dimensional" application scenarios.

[0020] In one aspect, the embodiments of this application provide a method for simulating the flood evolution of multi-story underground buildings.

[0021] Figure 1 This is a flowchart illustrating a flood evolution simulation method for multi-story underground buildings according to a preferred embodiment of this application. Figure 1 As shown, the flood evolution simulation method includes the following contents.

[0022] In step S10, following the order of floors from high to low, the logical topology network structure of the multi-story underground building is constructed using the single-layer two-dimensional planar geometric information of a single floor as nodes and the vertical connection component data between adjacent floors as directed edges. The single-layer two-dimensional planar geometric information includes the height distribution of the floor floors.

[0023] In step S11, based on the constructed logical topology network structure, flood evolution simulation is performed for each floor of the multi-story underground building.

[0024] Specifically, based on the constructed logical topology network structure, the following is performed for each floor of a multi-story underground building.

[0025] The configuration data for each floor is determined. This configuration data includes the single-layer two-dimensional planar geometry of the floor, the simulation start time, the simulation end time, the simulation calculation step size, the floor's surface roughness coefficient, and output parameters. The output parameters include the output path and output frequency of the simulation results. It should be noted that the simulation start time, simulation end time, simulation calculation step size, and output parameters described here are used when the two-dimensional hydrodynamic data simulation engine performs the simulation.

[0026] The determined configuration data is associated with boundary data, which indicates how the floodwater received by the floor changes over time.

[0027] Based on the determined configuration data, a two-dimensional hydrodynamic numerical simulation engine is invoked to determine the inundation process data for each floor. Specifically, for each floor, based on the determined configuration data (i.e., the configuration data after associating boundary data), the flood evolution process is simulated using the two-dimensional hydrodynamic numerical simulation engine to determine the inundation process data. This inundation process data includes four types of data: rasterized time-series water depth data, time-series flow velocity data, time-series flow direction data, and time-series absolute elevation. Each type of data is saved as GIS data (ASC file) with coordinates consistent with the floor data. The absolute elevation is obtained based on the floor height and water depth.

[0028] Determine if the floor is the last floor of a multi-story underground building.

[0029] In cases where the floor is not the last floor of a multi-story underground building, determine the inflow boundary data for the floor below the floor, where the inflow boundary data indicates how the floodwater flowing from the floor to the floor below the floor changes over time.

[0030] Optionally, in embodiments of this application, the logical topology network structure for constructing a multi-story underground building may include the following:

[0031] Obtain the single-floor two-dimensional planar geometry information for all floors. Specifically, obtain it from the data input by the user.

[0032] The single-layer two-dimensional planar geometric information of all floors is sorted, wherein for each floor, the single-layer two-dimensional planar geometric information includes the height distribution of the floor. Furthermore, the sorting is performed in descending order of floor height. Specifically, the corresponding floor can be identified based on the name of the single-layer two-dimensional planar geometric information, and based on the identified floors, the single-layer two-dimensional planar geometric information of all floors is sorted in descending order of height.

[0033] Based on the obtained order, the logical topology network structure of the multi-story underground building is constructed using the single-layer two-dimensional planar geometric information of a single floor as nodes and the vertical connection component data between adjacent floors as directed edges.

[0034] The initialization of the project and the logical construction of the multi-layered spatial computing model, i.e., building the logical topology network structure, is the first part of the technical solution and the starting point for all simulations. Its core task is to transform the user-provided raw data describing the physical structure into a structured, standardized logical computing model that can be recognized and processed by subsequent automated processes. This process is akin to drawing a detailed battle map and action plan for a complex military operation. The following section will combine... Figure 2 The process of constructing a logical topology network structure in the embodiments of this application is described exemplarily.

[0035] 1) Standardization and parsing of input data. This application first requires users to provide a set of standardized input data. This set of input data is a digital representation of the physical building, mainly including layered geometric data, vertical connection component data, external driving force data, and overall project configuration file.

[0036] Layered geometric data includes single-layer two-dimensional planar geometric information for each independent floor within a multi-story underground building. This single-layer two-dimensional planar geometric information typically uses a standard raster data format (such as ASCII Grid). The single-layer two-dimensional planar geometric information for each floor, presented in a grid format, meticulously describes the elevation (or depth) distribution of that floor's floor, including various micro-topography features such as indoor ramps, drainage ditches, and raised equipment foundations; in other words, it describes the height distribution of that floor's floor.

[0037] Vertical connection component data describes key information about the hydraulic connection between floors. This data describes the relevant information for the vertical connection components and their two endpoints. Specifically, the two endpoints of the vertical connection components include outflow monitoring points and inflow zones. Outflow monitoring points (Water Depth Monitoring Points) are defined on the upper floor slab as openings that may leak downwards, such as the upper edge of a stair landing, the edge of a courtyard, or an elevator threshold. Each outflow monitoring point has a unique first ID identifier and precise two-dimensional coordinates. Inflow zones are defined on the lower floor slab as the water inlet locations corresponding to the outflow monitoring points on the upper floor, such as the lower edge of a stair landing or the bottom of a courtyard. Each inflow zone also has a second ID identifier matching the outflow monitoring point on the upper floor and its geometric extent is defined by the coordinates of four vertices.

[0038] External driving force data describes external flood input sources. For top layers directly connected to the surface, it is necessary to provide information on external flood input sources. The most common method is rainfall hydrograph (time-rainfall intensity curve) data, which provides rainfall intensity at different times in the form of a time series.

[0039] The overall project configuration file is a top-level configuration file (e.g., in XML format) used to organize and associate all the above data, defining metadata such as simulation operating condition names and data storage paths.

[0040] 2) Establishment of the calculation sequence and solidification of gravity flow logic.

[0041] Upon receiving input data, the automated scheduling and execution engine first uses a floor identification and sorting submodule to logically sort all floors. This submodule has a built-in set of rules that understand building naming conventions (e.g., "1F" for ground floor, "B1F" and "B2F" for basement floors). The floor identification and sorting submodule identifies the name of the single-layer two-dimensional planar geometric information of each floor to determine the corresponding floor. Then, it sorts all the single-layer two-dimensional planar geometric information in descending order of floor height.

[0042] The floor identification and sorting submodule rigorously sorts the single-floor two-dimensional planar geometric information of all floors according to their physical elevation from high to low, generating a unidirectional and irreversible calculation sequence (e.g., [1F, B1F, B2F, B3F,...]). This sequence not only determines the execution order of subsequent calculation tasks, but more importantly, it logically solidifies the unique, gravity-driven, top-down propagation path of the flood within the building. This is a crucial step in transforming physical laws into computational logic.

[0043] 3) Construct the internal logical topology network structure.

[0044] Based on the above data, the system constructs a clear computational topology network in memory. In this network, the single-layer two-dimensional planar geometry of each floor is regarded as a "computation node," and each vertical connecting component data is regarded as a "directed edge" connecting two adjacent computation nodes. The direction of the directed edge strictly points from the higher floor to the lower floor. The data flowing on the "directed edge" is precisely the amount of water transferred between floors.

[0045] Thus, a complex physical building has been successfully and losslessly transformed into a directed acyclic graph (DAG) composed of nodes and directed edges, which can be understood and manipulated by a computer program. The establishment of this logical model is the theoretical foundation for realizing the subsequent fully automated process.

[0046] Optionally, in this embodiment of the application, for each floor in a multi-story underground building, the boundary data associated with the determined configuration data may include the following:

[0047] Determine whether the floor is the top floor of a multi-story underground building.

[0048] In the case where the floor is the top floor of a multi-story underground building, the boundary condition type of the floor is determined to be rainfall, and the determined configuration data is associated with rainfall boundary data, wherein the rainfall boundary data indicates the change of rainfall intensity over time. The rainfall boundary data is the external driving force data described in the embodiments of this application.

[0049] When a floor is not the top floor of a multi-story underground building, the floor's boundary condition type is determined as inflow, and the determined configuration data is associated with the floor's inflow boundary data. For any non-top floor, the inflow boundary data indicates the time-varying nature of the floodwater flowing into this floor from the previous floor, specifically including the temporal flow data of the inflow area corresponding to each outflow monitoring point on the previous floor.

[0050] Optionally, in this embodiment, determining the configuration data can be done by generating a configuration file. The following is in conjunction with... Figure 3 The determination of configuration data and the flood evolution simulation based on the determined configuration data in the embodiments of this application are illustrated by way of example. Figure 3 The document illustrates a standardized two-dimensional hydrodynamic simulation encapsulation for a single computing node. This standardized two-dimensional hydrodynamic simulation encapsulation for a single computing node constitutes the second part of this application. Its core task is to encapsulate the flood inundation simulation of any independent floor into a standardized, reusable "computational task unit." This computational task unit has clear input and output interfaces and can be flexibly invoked by the upper-level automated scheduling engine.

[0051] 1) Dynamic parameterization configuration of computation tasks.

[0052] When the scheduling engine decides to simulate a specific floor (e.g., B1F) in the computation sequence, a dynamic simulation configuration module is activated. This module acts like a "staff headquarters," automatically generating a dedicated, complete configuration file for the upcoming B1F computation task. It precisely fills in all the necessary simulation parameters, including geometric, temporal, physical, and boundary condition parameters.

[0053] The geometric parameters specify the use of the terrain raster file corresponding to B1F, that is, the single-layer two-dimensional planar geometric information of the B1F layer.

[0054] The time parameters are used to set the simulation start time, simulation end time, and simulation calculation step size.

[0055] Physical parameters, setting the roughness coefficient of the floor surface (used to describe water flow resistance).

[0056] Boundary condition parameters are the most critical configuration. This module determines the type of boundary conditions based on the attributes of the current floor. If the current floor is the top floor (1F), the boundary condition type is set to "Rainfall," and the configuration file is associated with the corresponding rainfall boundary file, i.e., associated rainfall boundary data. Specifically, it reads the raw rainfall data, i.e., the external driving force data, and generates the rainfall boundary file. If the current floor is a lower floor (B1F and below), the boundary condition type is set to "Inflow," and the configuration file is associated with one or more inflow boundary files that will be generated by the inter-floor dynamic hydraulic interface module, i.e., associated inflow boundary data.

[0057] The output parameters specify the output path and frequency of the simulation results, and specifically instruct the external numerical simulation engine (i.e., the two-dimensional hydrodynamic numerical simulation engine) to record and output the water depth time series of all "outflow monitoring points" located on B1F as defined in Part 1, that is, the time-series water depth data of all outflow monitoring points.

[0058] 2) Isolation of external numerical simulation engine calls and processes.

[0059] Once the configuration file is generated, the scheduling engine launches an external, independent two-dimensional hydrodynamic numerical simulation engine (e.g., a mature open-source or commercial computing program) through a standard operating system interface. Upon startup, the newly generated configuration file is passed to the engine as input parameters. This approach separates "scheduling" from "computation." The main control process is only responsible for organization and issuing commands, while the heavy numerical computation is handled by a separate, optimized specialized process. This process isolation design ensures the stability and robustness of the entire system.

[0060] 3) Output of standardized results and temporary storage of data.

[0061] After completing the calculation, the two-dimensional hydrodynamic numerical simulation engine generates a series of result files in a specified directory. These result files fall into four categories, corresponding to rasterized time-series water depth data, time-series velocity data, time-series flow direction data, and time-series absolute elevation data. For the methodology of this application, one result file is crucial: a detailed data report recording the dynamic changes in water depth values ​​at all outlets (outflow monitoring points) leading to the next floor over the simulation period. This data represents the time-series water depth data at all outflow monitoring points connected to the next floor. This result serves as the sole data bridge connecting the past (current floor simulation) and the future (next floor simulation) and will be temporarily stored, awaiting retrieval by the inter-floor dynamic hydraulic interface module.

[0062] Optionally, in this embodiment of the application, for each floor, if the floor is not the last floor of a multi-story underground building, determining the inflow boundary data of the next floor corresponding to the floor may include the following:

[0063] The determined inundation process data is analyzed to obtain time-series water depth data at each outflow monitoring point on each floor. Specifically, the inundation process data includes rasterized time-series water depth data. For each outflow monitoring point, the corresponding time-series water depth data is obtained from the rasterized time-series water depth data based on the location of the outflow monitoring point.

[0064] For each outflow monitoring point, the following steps are performed to determine the inflow boundary data. Based on the constructed logical topology network structure, the geometric attributes of the inflow region corresponding to the outflow monitoring point are determined on the floor below the corresponding floor. These geometric attributes include the area of ​​the cross-sectional area. Based on the temporal water depth data at the outflow monitoring point and the determined geometric attributes, the temporal flow data of the inflow region corresponding to the outflow monitoring point is determined. Specifically, for each outflow monitoring point, the temporal flow data of the corresponding inflow region can be determined as follows: For each time point in the temporal water depth data, based on hydraulic formulas, combined with the water depth value and the area of ​​the cross-sectional area of ​​the inflow region corresponding to that outflow monitoring point, the flow rate of the corresponding inflow region at that time point is determined. The above steps are performed for each time point to determine the temporal flow data of that outflow monitoring point.

[0065] Specifically, for each floor, assuming it is not the last floor of a multi-story underground building, the inflow boundary data for the next floor can be determined based on the following: (See below for details.) Figure 4 An example is provided on how to determine the inflow boundary data.

[0066] Determining the inflow boundary data is part of the implementation and invocation of the inter-floor dynamic hydraulic interface in this application. This is achieved through the inter-floor dynamic hydraulic interface module and constitutes the third part of this application. This is the core technology of this application and the key to applying a "planar" model to a "three-dimensional" space. The function of the inter-floor dynamic hydraulic interface module is to automatically and in real-time complete data conversion and transmission between computational tasks on two adjacent floors, based on physical principles, thereby perfectly simulating the real cross-floor hydraulic transmission process in computational logic.

[0067] 1) Accurate capture and parsing of upstream status data.

[0068] After the calculation task for one floor (e.g., B1F) is declared complete, the automated scheduling engine does not immediately begin the calculation for the next floor (B2F). Instead, it first invokes the inter-floor dynamic hydraulic interface module. The primary task of this interface module is to act as a "data scout," immediately accessing the results directory of B1F, locating and locking the data report generated by the numerical engine that records the water depth process at all outflow monitoring points. That is, it parses the inundation process data to obtain the time-series water depth data for all outflow monitoring points. It parses this report line by line and point by point with extremely high precision, completely extracting the water depth time series of each monitoring point (e.g., Stair_1_Out) into memory. This process is equivalent to performing a precise "snapshot" and digital extraction of the final dynamic results of the previous floor simulation.

[0069] 2) Translation of the physical mechanism of "state-flux".

[0070] After the data extraction is completed, the "hydraulic translation engine" inside the interlayer dynamic hydraulic interface module begins to work. This is the most innovative part of this application.

[0071] The hydraulic translation engine traverses the water depth sequence of each outflow monitoring point in memory. For each outflow monitoring point, it queries the logical topology network structure established in the first part to find the geometric properties of the corresponding inflow region (Stair_1_In) located in the next layer (B2F), especially the cross-sectional area A of the water passage.

[0072] Next, for each outflow monitoring point, the hydraulic translation engine applies a built-in hydraulic formula based on classical physics (e.g., the widely used weir or orifice outflow formula Q=C) to each time point in the water depth sequence. d A Calculations are performed to determine the flow rate in the inflow region corresponding to a specific outflow monitoring point at a given time. The physical meanings of each parameter in the formula are clear. Specifically, h is the real-time water depth captured from upstream (B1F) at the current moment, i.e., the water depth at the current outflow monitoring point; g is the acceleration due to gravity, the fundamental driving force propelling the water flow downstream; A is the cross-sectional area of ​​the vertical structure through which the water flows, the cross-sectional area of ​​the inflow region corresponding to the current outflow monitoring point; C... d It is the flow coefficient, an empirical parameter that can be calibrated based on the specific shape of the component (such as the slope of the staircase, the presence or absence of obstacles, etc.), which makes this method highly flexible and calibrable in engineering.

[0073] Through the above calculations, the water depth sequence, originally describing the physical "state," was successfully and point-by-point "translated" into a flow rate sequence describing the physical "flux." This step represents a perfect mathematical reproduction in a computer of the core physical phenomenon that "the deeper the water, the faster it drains."

[0074] 3) Formatting and Injection of Downstream Boundary Conditions. The translated flow sequence is processed by a data formatting submodule. This submodule combines the flow sequence with the corresponding time series to generate a standardized inflow boundary condition file (usually in CSV format) that conforms to the input of the downstream numerical simulation engine, thus defining the inflow and outflow boundary data. The inflow boundary condition file is automatically named and precisely placed in a pre-defined inflow subdirectory within the next-level (B2F) working directory. When flood evolution simulation is required for the next level (B2F), the inflow boundary condition file is associated with the next-level (B2F) configuration file, and the inflow boundary condition file is retrieved from the inflow subdirectory.

[0075] Thus, a complete "data transfer-translation-injection" cycle is completed. The calculation results from the previous layer have unknowingly transformed into the driving force for the calculations in the next layer.

[0076] Optionally, in this embodiment, the flood evolution simulation method may further include the following for each floor of a multi-story underground building: When the floor is the last floor of the multi-story underground building, preset result data is determined based on the inundation process data of all floors, and the determined preset result data is stored in a preset final result directory. Optionally, in this embodiment, the preset result data can be determined according to the user's needs.

[0077] The fourth part of this application is the automated scheduling engine and workflow management that drives the overall computational flow. If the inter-layer dynamic hydraulic interface module is the "heart," then the automated scheduling engine is the "brain." The automated scheduling engine is responsible for directing and coordinating all the above modules, ensuring that the entire complex multi-layer simulation process can run automatically, accurately, efficiently, and unattended, like a precise machine. The following section combines... Figure 5 The content of Part IV of this application is described by way of example.

[0078] 1) Top-level workflow orchestration based on computational sequences The entire simulation process is driven by the top-level loop of the automated scheduling engine. This loop iterates strictly according to the top-down floor calculation sequence ([1F, B1F, B2F, ...]) generated in Part 1.

[0079] For each floor in the floor calculation sequence, the automated scheduling engine strictly executes a fixed "three-step" operation mode: 1) Call the "computation task encapsulation module" to prepare all the parameters and boundary conditions required for the current floor (if it is the top floor, prepare the rainfall boundary; if it is the lower floor, the inflow boundary file generated by the inter-floor dynamic hydraulic interface module is already in place); 2) Execute "standardized two-dimensional hydrodynamic simulation", start the external numerical engine, complete the flooding calculation of the current floor, and obtain its "outflow status" data to the next floor; 3) Call the "inter-floor dynamic hydraulic interface module" to generate "inflow boundary" data in real time for the next floor in the sequence based on the "outflow status" just obtained.

[0080] This chain reaction of "configuration -> calculation -> interface -> configuration -> calculation -> interface -> ..." constitutes the core logic of the automated operation of this application.

[0081] 2) Status monitoring and process control During operation, the automated scheduling engine monitors the status of each step in real time. It knows which floor is currently being calculated, which floor's calculation has been successfully completed, and which interface file has been successfully generated.

[0082] This fine-grained process control ensures data consistency and logical correctness of calculations. At the same time, a robust automated scheduling engine should also include error handling mechanisms, such as the ability to interrupt the process and report clear error messages to the user when a calculation at a certain level fails or a required file is missing.

[0083] 3) Aggregation and visualization of global results: Once the simulation of the last floor in the computation sequence is complete, the top-level loop of the scheduling engine ends.

[0084] At this point, a results integration module will be invoked. This module will automatically inspect the results catalog of all floors, extract the most valuable final results for the user (such as the maximum flood depth distribution map of each floor, the flooding process animation of the entire building, the water level change curve of a specific location, etc.), and summarize them into a top-level final results catalog named after the project conditions.

[0085] This automated post-processing greatly facilitates users' global and systematic analysis of the flooding situation of the entire multi-story building.

[0086] This application provides a systematic method for applying standard two-dimensional hydrodynamic models to the simulation of flood evolution in multi-story underground buildings. Its core technology lies in its approach: instead of directly processing physically complete but computationally challenging three-dimensional building models, it first deconstructs and reorganizes the three-dimensional space at a logical level, transforming it into an ordered computational topology network composed of multiple independent two-dimensional computational layers and dynamic hydraulic interfaces connecting them. Subsequently, an automated scheduling engine drives data and control flows through this network according to a pre-defined physical logic (i.e., the direction of gravity flow), thereby reproducing the entire top-down inundation process of the building in a computationally efficient and physically realistic manner.

[0087] The specific implementation of this application strictly follows a meticulously designed, modular, automated workflow. This workflow can be clearly divided into four core process modules, which are interconnected and work collaboratively to form the complete technical system of this application, such as... Figure 6 As shown. Through the precise coordination of the above four major process modules, this application is no longer a simple program, but rather a complete, self-consistent, and efficient "methodology and automated implementation framework for flood simulation of multi-story buildings". It successfully and creatively "grafts" the two-dimensional hydrodynamic model, which is widely used in open surface environments, onto the new and highly challenging engineering scenario of multi-story underground buildings with complex structures and unique physical processes, providing unprecedented and powerful technical support for improving the safety and resilience of urban underground spaces.

[0088] This application belongs to the interdisciplinary field of architectural engineering, hydraulic engineering, and computer simulation. Specifically, it relates to a methodological framework for successfully applying a mature two-dimensional surface flood numerical model to the simulation of flood evolution in multi-story underground structures with complex three-dimensional structures and vertical connectivity. The core of this application lies in proposing and implementing a complete spatial deconstruction, dynamic coupling, and automated scheduling strategy, aiming to solve the fundamental applicability problems of existing two-dimensional hydrodynamic models when facing such discontinuous, hierarchical, artificially enclosed environments. This application is mainly applied to flood disaster risk assessment, flood control and drainage engineering design optimization, emergency plan formulation, and effectiveness verification for key infrastructure such as subway transfer hubs, underground commercial complexes, large transportation tunnels, multi-story underground parking lots, and deeply buried civil defense projects in modern cities. It has significant theoretical value and broad engineering application prospects.

[0089] The fundamental purpose of this application is to propose a groundbreaking methodology that successfully "transplants" and adapts mature and efficient two-dimensional hydrodynamic numerical models from their traditional open surface applications to multi-story underground structures with unique structures and enclosed environments. This application does not seek to improve the hydrodynamic calculation algorithms themselves, but rather focuses on creating a completely new systematic framework for "organizing, scheduling, and linking" existing computational tools, thereby achieving a leapfrog expansion of application scenarios. Specifically, it aims to achieve the following objectives.

[0090] 1) Expanding the applicability of 2D models to 3D space. The primary goal of this application is to break the limitation that 2D models can only be used for "planar" calculations. Through a novel "spatial deconstruction and logical reorganization" strategy, a physically complete but computationally incompatible 3D building is transformed into an ordered sequence of computational tasks that a 2D model can understand and process, thereby fundamentally solving the problem of "application object mismatch".

[0091] 2) Constructing a physically realistic automated cross-layer hydraulic coupling mechanism. Addressing the various drawbacks of manual coupling, this application aims to establish a fully automated "inter-layer dynamic hydraulic interface" based on physical principles. This interface can replace manual intervention, simulating the transmission process of water flow through vertical components in real time and with high precision. It automatically "translates" the dynamic submersion state (water depth) of the upper calculation layer into the inflow boundary conditions (flow rate) of the lower calculation layer, thereby constructing a continuous, dynamic, and physically realistic "vertical hydraulic transmission logic chain" throughout the entire building model.

[0092] 3) Providing a highly efficient paradigm for solving 3D problems. Faced with the high computational cost of 3D models, this application aims to provide an innovative, "quasi-3D" or "2.5D" efficient solution paradigm. Through a technical approach of "breaking down the whole into parts (spatial layering), tackling layer by layer (2D computation), and dynamic linking (interface coupling)," a computationally unsustainable 3D flooding problem is reduced in dimension to a series of computationally easy 2D simulation tasks. This aims to achieve an ideal balance, obtaining physical realism far exceeding that of traditional 2D models (due to the consideration of core vertical flow) while maintaining near-2D computational efficiency.

[0093] 4) Develop a standardized and engineered simulation analysis workflow. The ultimate goal of this application is to solidify the above ideas into an end-to-end, "black-box" automated simulation platform. Users (such as architects and flood control engineers) do not need to worry about complex intermediate data processing and model calling processes. They only need to provide the building's geometry and connection data according to standardized specifications, and the system can automatically complete the entire process from task decomposition, layer-by-layer calculation, dynamic coupling to result aggregation, producing intuitive and reliable simulation results. This aims to transform multi-story building flood simulation from a complex technology mastered by a few researchers into a standardized engineering analysis tool that can be easily used by a wide range of engineers, greatly enhancing its application value in practical engineering.

[0094] This application combines a mature two-dimensional hydrodynamic model with an innovative layer-by-layer coupling framework, and has been successfully applied to the field of flood simulation for large-scale underground buildings and transportation hubs in cities. It has achieved remarkable technical results and perfectly solved the contradiction between efficiency and accuracy in existing technologies.

[0095] Taking a multi-level underground transportation hub comprising a commercial level, a transfer level, and a platform level as an example, the effectiveness of applying this application for flood control assessment is reflected in a complete and efficient automated workflow. First, through its spatial deconstruction and logical modeling capabilities, this method clearly transforms the physically complex hub structure into a top-down, ordered sequence of computational tasks.

[0096] After the simulation begins, the system automatically simulates the inundation process of ground rainfall or floodwater flowing back into the top floor (commercial floor) of the hub through the entrances and exits. When water accumulates on the top floor and begins to spread to lower floors through staircases, escalator shafts, or atriums, the core "inter-floor dynamic hydraulic interface" of this application plays a crucial role. It can capture the water depth changes at key openings on the upper floor in real time and, based on physical principles, accurately "translate" them dynamically into inflow rates to the lower floor (transfer floor). This flow rate is then automatically injected into the two-dimensional model of the next floor as a precise boundary condition, driving the inundation calculation for that floor.

[0097] This chain-like process of "computation-coupling-recomputation" is automatically passed down layer by layer to the bottom platform level, thus completely reproducing the entire propagation of floodwaters throughout the three-dimensional space of the hub. Ultimately, users can obtain detailed inundation process data, maximum inundation depth, and water level changes in key channels for all floors of the entire hub within hours. The results combine the physical realism of three-dimensional simulation (especially in vertical transmission) with the high computational efficiency of two-dimensional models, providing rapid, reliable, and quantitative decision-making basis for the hub's flood control design (such as floodgate installation), drainage system optimization, and emergency plan development. It has extremely high engineering practical value and promising prospects for widespread application.

[0098] Secondly, this application also provides a flood evolution simulation device for multi-story underground buildings.

[0099] Figure 7 This is a structural block diagram of a flood evolution simulation device for a multi-story underground building according to a preferred embodiment of this application. Figure 7 As shown, the flood evolution simulation device includes a first processing module 10 and a second processing module 20.

[0100] The first processing module 10 is used to construct a logical topology network structure for a multi-story underground building, following the order of floors from high to low, using the single-layer two-dimensional planar geometric information of each floor as nodes and the vertical connection component data between adjacent floors as directed edges. The single-layer two-dimensional planar geometric information includes the floor height distribution. The second processing module 20, based on the constructed logical topology network structure, performs the following operations for each floor in the multi-story underground building: determining the floor's configuration data, including the single-layer two-dimensional planar geometric information, simulation start time, simulation end time, simulation calculation step size, floor surface roughness coefficient, and output parameters, including the output path and output frequency of the simulation results; associating boundary data with the determined configuration data, where the boundary data indicates the change in floodwater received by the floor over time; based on the determined configuration data, calling a two-dimensional hydrodynamic numerical simulation engine to determine the floor's inundation process data; determining whether the floor is the last floor of the multi-story underground building; and if the floor is not the last floor, determining the inflow boundary data of the next floor corresponding to the floor, where the inflow boundary data indicates the change in floodwater flowing from the floor to the next floor over time.

[0101] Optionally, the second processing module 20 associates boundary data with the determined configuration data for each floor in the multi-story underground building, including: determining whether the floor is the top floor of the multi-story underground building; if the floor is the top floor of the multi-story underground building, determining the boundary condition type of the floor as rainfall, and associating the determined configuration data with rainfall boundary data, wherein the rainfall boundary data indicates the change of rainfall intensity over time; if the floor is not the top floor of the multi-story underground building, determining the boundary condition type of the floor as inflow, and associating the determined configuration data with the inflow boundary data of the floor.

[0102] Optionally, for each floor, if the floor is not the last floor of a multi-story underground building, the second processing module 20 determines the inflow boundary data of the next floor corresponding to the floor, including: parsing the determined flooding process data to obtain the temporal water depth data at each outflow monitoring point of the floor; for each outflow monitoring point, performing the following to determine the inflow boundary data: based on the constructed logical topology network structure, determining the geometric attributes of the inflow area corresponding to the outflow monitoring point on the next floor corresponding to the floor, wherein the geometric attributes include the area of ​​the cross-section of the water flow; based on the temporal water depth data at the outflow monitoring point and the determined geometric attributes, determining the temporal flow data of the inflow area corresponding to the outflow monitoring point.

[0103] Optionally, the second processing module 20 is further configured to: for each floor in a multi-story underground building, in the case that the floor is the last floor of the multi-story underground building, determine preset result data based on the flooding process data of all floors, and store the determined preset result data in a preset final result directory.

[0104] The specific working principle and benefits of the flood evolution simulation device provided in this application are similar to those of the flood evolution simulation method provided in this application, and will not be repeated here.

[0105] Thirdly, this application also provides a machine-readable storage medium storing instructions that cause a machine to execute the flood evolution simulation method described above.

[0106] Fourthly, this application also provides an electronic device comprising: a processor; a memory for storing executable instructions of the processor; the processor being configured to read the executable instructions from the memory and execute the executable instructions to implement the flood evolution simulation method described above.

[0107] The preferred embodiments of this application have been described in detail above. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solution of this application, and these simple modifications all fall within the protection scope of this application.

[0108] It should also be noted that the various specific technical features described in the above embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, this application will not describe the various possible combinations separately.

[0109] Furthermore, various different implementations of this application can be combined in any way, as long as they do not violate the spirit of this application, they should also be regarded as the content disclosed in this application.

Claims

1. A method for simulating flood evolution in multi-story underground buildings, characterized in that, The flood evolution simulation method includes: Following the order of floors from high to low, the logical topology network structure of the multi-story underground building is constructed using the single-layer two-dimensional planar geometric information of a single floor as nodes and the vertical connection component data between adjacent floors as directed edges. The single-layer two-dimensional planar geometric information includes the height distribution of the floor floors. Based on the constructed logical topology network structure, the following operations are performed for each floor of the multi-story underground building: The configuration data of the floor is determined, wherein the configuration data includes the single-layer two-dimensional planar geometric information of the floor, the simulation start time, the simulation end time, the simulation calculation step size, the ground roughness coefficient of the floor, and the output parameters, wherein the output parameters include the output path and output frequency of the simulation results; The determined configuration data is associated with boundary data, wherein the boundary data indicates the change in the flood received by the floor over time; Based on the determined configuration data, a two-dimensional hydrodynamic numerical simulation engine is invoked to determine the inundation process data of the floor. Determine whether the floor is the last floor of the multi-story underground building; If the floor is not the last floor of the multi-story underground building, determine the inflow boundary data of the next floor corresponding to the floor, wherein the inflow boundary data indicates the change of floodwater flowing from the floor to the next floor over time.

2. The flood evolution simulation method according to claim 1, characterized in that, For each floor of the aforementioned multi-story underground building, the determined configuration data is associated with boundary data, including: Determine whether the floor is the top floor of the multi-story underground building; In the case that the floor is the top floor of the multi-story underground building, the boundary condition type of the floor is determined to be rainfall, and the determined configuration data is associated with rainfall boundary data, wherein the rainfall boundary data indicates the change of rainfall intensity over time; If the floor is not the top floor of the multi-story underground building, the boundary condition type of the floor is determined to be inflow, and the determined configuration data is associated with the inflow boundary data of the floor.

3. The flood evolution simulation method according to claim 1, characterized in that, For each floor, if the floor is not the last floor of the multi-story underground building, determine the inflow boundary data for the next floor corresponding to that floor, including: The determined flooding process data is analyzed to obtain time-series water depth data at each outflow monitoring point of the floor. For each outflow monitoring point, perform the following steps to determine the inflow boundary data: Based on the constructed logical topology network structure, the geometric attributes of the inflow area corresponding to the outflow monitoring point are determined on the floor below the floor corresponding to the floor, wherein the geometric attributes include the area of ​​the water flow cross section; Based on the time-series water depth data at the outflow monitoring point and the determined geometric properties, the time-series flow data of the inflow region corresponding to the outflow monitoring point is determined.

4. A flood evolution simulation device for multi-story underground buildings, characterized in that, The flood evolution simulation device includes: The first processing module is used to construct the logical topology network structure of the multi-story underground building in order from high to low, using the single-layer two-dimensional plane geometric information of a single floor as nodes and the vertical connection component data between adjacent floors as directed edges. The single-layer two-dimensional plane geometric information includes the height distribution of the floor floors. The second processing module is used to perform the following operations for each floor of the multi-story underground building, based on the constructed logical topology network structure: The configuration data of the floor is determined, wherein the configuration data includes the single-layer two-dimensional planar geometric information of the floor, the simulation start time, the simulation end time, the simulation calculation step size, the ground roughness coefficient of the floor, and the output parameters, wherein the output parameters include the output path and output frequency of the simulation results; The determined configuration data is associated with boundary data, wherein the boundary data indicates the change in the flood received by the floor over time; Based on the determined configuration data, a two-dimensional hydrodynamic numerical simulation engine is invoked to determine the inundation process data of the floor. Determine whether the floor is the last floor of the multi-story underground building; If the floor is not the last floor of the multi-story underground building, determine the inflow boundary data of the next floor corresponding to the floor, wherein the inflow boundary data indicates the change of floodwater flowing from the floor to the next floor over time.

5. The flood evolution simulation device according to claim 4, characterized in that, The second processing module, for each floor in the multi-story underground building, associates the determined configuration data with boundary data, including: Determine whether the floor is the top floor of the multi-story underground building; In the case that the floor is the top floor of the multi-story underground building, the boundary condition type of the floor is determined to be rainfall, and the determined configuration data is associated with rainfall boundary data, wherein the rainfall boundary data indicates the change of rainfall intensity over time; If the floor is not the top floor of the multi-story underground building, the boundary condition type of the floor is determined to be inflow, and the determined configuration data is associated with the inflow boundary data of the floor.

6. The flood evolution simulation device according to claim 4, characterized in that, The second processing module, for each floor, if the floor is not the last floor of the multi-story underground building, determines the inflow boundary data of the next floor corresponding to that floor, including: The determined flooding process data is analyzed to obtain time-series water depth data at each outflow monitoring point of the floor. For each outflow monitoring point, perform the following steps to determine the inflow boundary data: Based on the constructed logical topology network structure, the geometric attributes of the inflow area corresponding to the outflow monitoring point are determined on the floor below the floor corresponding to the floor, wherein the geometric attributes include the area of ​​the water flow cross section; Based on the time-series water depth data at the outflow monitoring point and the determined geometric properties, the time-series flow data of the inflow region corresponding to the outflow monitoring point is determined.

7. A machine-readable storage medium, characterized in that, The machine-readable storage medium stores instructions for causing the machine to perform the flood evolution simulation method according to any one of claims 1-3.

8. An electronic device, characterized in that, The electronic device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to read the executable instructions from the memory and execute the executable instructions to implement the flood evolution simulation method according to any one of claims 1-3.

Images