A method and related apparatus for generating boundary conditions

Abstract

The application discloses a method and related device for generating boundary conditions, which comprises: based on the setting information of a wind resource simulation platform, acquiring general configuration parameters, boundary condition types and solver types for generating boundary conditions; automatically generating a boundary condition configuration file through the general configuration parameters, boundary condition types and solver types, and the file format of the boundary condition configuration file is determined based on the boundary condition types and the solver types; and automatically generating boundary conditions corresponding to grid information corresponding to the general configuration parameters based on the boundary condition configuration file. On the basis of the general configuration parameters, the boundary condition types and the solver types are added, a boundary condition configuration file corresponding to a file format determined by the boundary condition types and the solver types is automatically generated, and then the boundary conditions are automatically generated in combination with the grid information. In this way, the boundary condition types and the solver types are set by a user, and therefore, the boundary condition generation method is expandable.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method and related apparatus for generating boundary conditions. Background Technology

[0002] Wind resource simulation of wind farms requires the provision of boundary conditions. Currently, based on the characteristic that boundary conditions need to conform to the physical distribution laws of the atmospheric boundary layer, boundary conditions are automatically generated by the user through a small number of general configuration parameters set on the wind resource simulation platform, and wind resource simulation of wind farms is performed using these boundary conditions.

[0003] Wind resource simulation of wind farms typically involves setting up multiple sectors, which require more diverse boundary conditions. Research has found that different types of boundary conditions and solvers are crucial for generating diverse boundary conditions.

[0004] However, when automatically generating boundary conditions using a limited number of general configuration parameters, the method relies solely on the single, fixed boundary condition type and solver type provided by the wind resource simulation platform by default. Therefore, this approach lacks scalability and cannot meet the diverse needs of boundary condition generation. Summary of the Invention

[0005] In view of this, embodiments of this application provide a method and related apparatus for generating boundary conditions, which are scalable to meet diverse needs for boundary conditions.

[0006] In a first aspect, embodiments of this application provide a method for generating boundary conditions, the method comprising:

[0007] Obtain the general configuration parameters, boundary condition types, and solver types used to generate boundary conditions from the settings information of the wind resource simulation platform;

[0008] A boundary condition configuration file is automatically generated based on the general configuration parameters, the boundary condition type, and the solver type; the file format of the boundary condition configuration file is determined based on the boundary condition type and the solver type.

[0009] Based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters, the boundary conditions corresponding to the mesh information are automatically generated.

[0010] Optionally, the general configuration parameters include wind farm location, sector wind direction, stability, and reference wind speed.

[0011] Optionally, the step of automatically generating a boundary condition configuration file based on the general configuration parameters, the boundary condition type, and the solver type includes:

[0012] Generate a configuration file that satisfies the file format corresponding to the boundary condition type and the solver type;

[0013] The boundary condition configuration file is obtained based on the general configuration parameters, the boundary condition type, the solver type, and the configuration file.

[0014] Optionally, obtaining the boundary condition configuration file based on the general configuration parameters, the boundary condition type, the solver type, and the configuration file includes:

[0015] Based on the general configuration parameters, the boundary condition type, and the solver type, other configuration parameters for generating the boundary conditions are obtained;

[0016] Write the general configuration parameters, the other configuration parameters, the boundary condition type, and the solver type into the configuration file to obtain the boundary condition configuration file.

[0017] Optionally, the step of automatically generating boundary conditions corresponding to the mesh information based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters includes:

[0018] Determine the first boundary condition generation algorithm corresponding to the boundary condition type and the solver type;

[0019] The boundary conditions are automatically generated based on the boundary condition configuration file, the mesh information, and the first boundary condition generation algorithm.

[0020] Optionally, the method further includes:

[0021] The first boundary condition generation algorithm is optimized into a second boundary condition generation algorithm;

[0022] The automatic generation of boundary conditions corresponding to the mesh information based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters includes:

[0023] The boundary conditions are automatically generated based on the boundary condition configuration file, the mesh information, and the second boundary condition generation algorithm.

[0024] Optionally, the method further includes:

[0025] Wind resource simulation of the wind farm is performed based on the aforementioned boundary conditions.

[0026] Secondly, embodiments of this application provide an apparatus for generating boundary conditions, the apparatus comprising: an acquisition unit and a generation unit;

[0027] The acquisition unit is used to acquire, from the setting information of the wind resource simulation platform, the general configuration parameters, boundary condition type and solver type used to generate boundary conditions;

[0028] The generation unit is used to automatically generate a boundary condition configuration file based on the general configuration parameters, the boundary condition type, and the solver type; the file format of the boundary condition configuration file is determined based on the boundary condition type and the solver type.

[0029] The generation unit is also used to automatically generate boundary conditions corresponding to the mesh information based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters.

[0030] Optionally, the general configuration parameters include wind farm location, sector wind direction, stability, and reference wind speed.

[0031] Optionally, the generation unit includes: a first generation subunit and an acquisition subunit;

[0032] The generation subunit is used to generate a configuration file that satisfies the file format corresponding to the boundary condition type and the solver type;

[0033] The obtaining sub-unit is used to obtain the boundary condition configuration file based on the general configuration parameters, the boundary condition type, the solver type, and the configuration file.

[0034] Optionally, the obtaining subunit includes: a first obtaining module and a second obtaining module;

[0035] The first obtaining module is used to obtain other configuration parameters for generating the boundary conditions based on the general configuration parameters, the boundary condition type, and the solver type;

[0036] The second obtaining module is used to write the general configuration parameters, the other configuration parameters, the boundary condition type and the solver type into the configuration file to obtain the boundary condition configuration file.

[0037] Optionally, the generation unit further includes: a determining subunit and a second generation subunit;

[0038] The determining subunit is used to determine the first boundary condition generation algorithm corresponding to the boundary condition type and the solver type;

[0039] The second generation subunit is used to automatically generate the boundary conditions based on the boundary condition configuration file, the mesh information, and the first boundary condition generation algorithm.

[0040] Optionally, the method further includes: an optimization unit;

[0041] The optimization unit is used to optimize the first boundary condition generation algorithm into a second boundary condition generation algorithm;

[0042] The generation unit is further configured to:

[0043] The boundary conditions are automatically generated based on the boundary condition configuration file, the mesh information, and the second boundary condition generation algorithm.

[0044] Optionally, the device further includes: a simulation unit;

[0045] The simulation unit is used to simulate wind resources of the wind farm based on the boundary conditions.

[0046] Thirdly, embodiments of this application provide a computer device, the computer device including a processor and a memory:

[0047] The memory is used to store program code and transmit the program code to the processor;

[0048] The processor is configured to execute the boundary condition generation method described in the first aspect above according to the instructions in the program code.

[0049] Fourthly, embodiments of this application provide a computer-readable storage medium, characterized in that the computer-readable storage medium is used to store program code, the program code being used to execute the boundary condition generation method described in the first aspect above.

[0050] Compared with the prior art, this application has at least the following advantages:

[0051] The technical solution adopted in this application firstly obtains general configuration parameters, boundary condition types, and solver types for generating boundary conditions based on the setting information of the wind resource simulation platform. Then, a boundary condition configuration file is automatically generated using the general configuration parameters, boundary condition types, and solver types. The file format of this boundary condition configuration file is determined based on the boundary condition types and solver types. Finally, the boundary conditions corresponding to the mesh information are automatically generated by combining the boundary condition configuration file with the mesh information corresponding to the general configuration parameters. It can be seen that by adding user-defined boundary condition types and solver types to the general configuration parameters, a boundary condition configuration file with a file format determined by the boundary condition types and solver types is automatically generated. Then, the boundary conditions are automatically generated by combining the mesh information. In this method, the boundary condition types and solver types are user-defined, thus the boundary condition generation method is scalable, thereby meeting diverse needs for boundary conditions. Attached Figure Description

[0052] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0053] Figure 1 This is a schematic diagram of multiple sectors in an embodiment of this application;

[0054] Figure 2 This is a schematic diagram of the system framework involved in one application scenario in the embodiments of this application;

[0055] Figure 3 A flowchart illustrating a method for generating boundary conditions provided in an embodiment of this application;

[0056] Figure 4 This is a schematic diagram of a boundary condition generation device provided in an embodiment of this application. Detailed Implementation

[0057] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0058] Wind resource simulation of a wind farm requires defining boundary conditions. Typically, multiple sectors are set up in a wind resource simulation, such as... Figure 1 The diagram illustrates a multi-sector approach, where multiple sectors require more diverse boundary conditions. However, the inventors discovered that automatically generating boundary conditions using a limited number of general configuration parameters relies solely on the default boundary condition and solver types provided by the wind resource simulation platform. Therefore, this approach lacks scalability and fails to meet the diverse needs of boundary condition generation.

[0059] To address this issue, in this embodiment, based on the settings information of the wind resource simulation platform, general configuration parameters, boundary condition types, and solver types for generating boundary conditions are obtained. A boundary condition configuration file is automatically generated using these parameters. The file format of this configuration file is determined based on the boundary condition type and solver type. The boundary condition configuration file is then combined with the mesh information corresponding to the general configuration parameters to automatically generate the boundary conditions corresponding to the mesh information. Therefore, by adding user-defined boundary condition types and solver types to the general configuration parameters, a boundary condition configuration file with the determined file format is automatically generated. This, combined with the mesh information, automatically generates the boundary conditions. Since the boundary condition type and solver type are user-defined, the boundary condition generation method is scalable, thus meeting diverse boundary condition requirements.

[0060] For example, one scenario in the embodiments of this application can be applied to, such as Figure 2 The scenario shown includes a wind resource simulation platform 201 and a corresponding processor 202. The processor 202 processes relevant data from the wind resource simulation platform 201 to perform wind resource simulation. Users can set general configuration parameters, boundary condition types, and solver types for generating boundary conditions on the wind resource simulation platform 201 to obtain setting information. The processor 102 uses the implementation method provided in this application embodiment to generate boundary conditions so as to perform wind resource simulation of the wind farm based on the generated boundary conditions.

[0061] First, in the above application scenarios, although the action descriptions of the implementation methods provided in this application are executed by the processor 102, the implementation methods of this application are not limited in terms of the execution subject, as long as the actions disclosed in the implementation methods provided in this application are executed.

[0062] Secondly, the above scenario is only one example provided by the embodiments of this application, and the embodiments of this application are not limited to this scenario.

[0063] The following description, in conjunction with the accompanying drawings, details the specific implementation of the method and apparatus for generating boundary conditions in the embodiments of this application.

[0064] Exemplary methods

[0065] See Figure 3 The diagram illustrates a flowchart of a method for generating boundary conditions according to an embodiment of this application. In this embodiment, the method may include, for example, the following steps:

[0066] Step 301: Obtain the general configuration parameters, boundary condition type, and solver type used to generate boundary conditions from the settings information of the wind resource simulation platform.

[0067] Given that different boundary condition types and solver types are crucial for generating diverse boundary conditions, related technologies, when automatically generating boundary conditions through a small number of general configuration parameters, rely solely on the single, fixed boundary condition type and solver type provided by the wind resource simulation platform by default. This approach results in a lack of scalability in boundary condition generation, failing to meet the diverse needs of boundary conditions.

[0068] In this embodiment, to address the need for more diverse boundary conditions across multiple sectors in wind resource simulation, the wind resource simulation platform provides users with various boundary condition types and solver types. This allows users to set different boundary condition types and solver types in addition to a few general configuration parameters, thus obtaining the configuration information used to generate boundary conditions. Based on this, the general configuration parameters, boundary condition types, and solver types used to generate boundary conditions can be obtained from the configuration information of the wind resource simulation platform.

[0069] For different sectors generating different boundary conditions, the common configuration parameters can be wind farm location, sector wind direction, stability, and reference wind speed. Therefore, in an optional embodiment of this application, the common configuration parameters include wind farm location, sector wind direction, stability, and reference wind speed.

[0070] Step 302: Automatically generate a boundary condition configuration file based on the general configuration parameters, the boundary condition type, and the solver type; the file format of the boundary condition configuration file is determined based on the boundary condition type and the solver type.

[0071] In this embodiment, after obtaining the user-set general configuration parameters, boundary condition type, and solver type for generating boundary conditions in step 301, a boundary condition configuration file needs to be automatically generated using the general configuration parameters, boundary condition type, and solver type so that boundary conditions can be automatically generated subsequently based on this boundary condition configuration file. The boundary condition type and solver type are used to determine the file format of the boundary condition configuration file.

[0072] In the specific implementation of step 302, based on determining different file formats for boundary condition configuration files under different boundary condition types and solver types, firstly, the file format needs to be determined by the boundary condition type and solver type, and a configuration file that meets that file format needs to be automatically generated; then, the boundary condition configuration file can be obtained by combining the general configuration parameters, boundary condition type, and solver type with the generated configuration file. Therefore, in an optional embodiment of this application, step 302 may include, for example, the following steps A-B:

[0073] Step A: Generate a configuration file that satisfies the file format corresponding to the boundary condition type and the solver type.

[0074] As an example, the boundary condition type is boundary condition type 1, the solver type is OpenFOAM simpleFoam solver, and a configuration file that satisfies the file format corresponding to boundary condition type 1 and OpenFOAM simpleFoam solver is generated.

[0075] Step B: Obtain the boundary condition configuration file based on the general configuration parameters, the boundary condition type, the solver type, and the configuration file.

[0076] Specifically, in step B, firstly, for the general configuration parameters, combining the boundary condition type and the solver type, other configuration parameters for generating boundary conditions can be obtained besides the general configuration parameters; then, the general configuration parameters, other configuration parameters, boundary condition type, and solver type are written into the configuration file to obtain the boundary condition configuration file. Therefore, in an optional embodiment of this application, step B may include, for example, the following steps B1-B2:

[0077] Step B1: Based on the general configuration parameters, the boundary condition type, and the solver type, obtain other configuration parameters for generating the boundary conditions.

[0078] Step B2: Write the general configuration parameters, the other configuration parameters, the boundary condition type, and the solver type into the configuration file to obtain the boundary condition configuration file.

[0079] Step 303: Based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters, automatically generate the boundary conditions corresponding to the mesh information.

[0080] In this embodiment of the application, after the boundary condition configuration file is automatically generated in step 302, the boundary conditions corresponding to the grid information are automatically generated based on the boundary condition configuration file and the grid information corresponding to the sector. Since the sector corresponds to the general configuration parameters, the boundary conditions corresponding to the grid information are automatically generated based on the grid information corresponding to the general configuration parameters.

[0081] In the specific implementation of step 303, based on determining different boundary condition generation algorithms for different boundary condition types and solver types, firstly, the boundary condition generation algorithm corresponding to the boundary condition type and solver type needs to be used as the first boundary condition generation algorithm; then, according to the first boundary condition generation algorithm, the boundary condition configuration file and mesh information are calculated to automatically generate boundary conditions. Therefore, in an optional embodiment of this application, step 303 may include, for example, the following steps C-D:

[0082] Step C: Determine the first boundary condition generation algorithm corresponding to the boundary condition type and the solver type.

[0083] Step D: Automatically generate the boundary conditions based on the boundary condition configuration file, the mesh information, and the first boundary condition generation algorithm.

[0084] It is important to note that the sector wind direction included in the general configuration parameters of the boundary condition configuration file needs to be converted into a vector in Cartesian coordinates in order to calculate the boundary condition configuration file and mesh information according to the first boundary condition generation algorithm and automatically generate the boundary conditions.

[0085] Furthermore, in this embodiment, the first boundary condition generation algorithm corresponding to the boundary condition type and solver type can be optimized to obtain a second boundary condition generation algorithm corresponding to the boundary condition type and solver type. This allows for the automatic generation of boundary conditions by calculating the boundary condition configuration file and mesh information according to the second boundary condition generation algorithm during step 303. Therefore, in an optional embodiment of this application, the method may further include step E: optimizing the first boundary condition generation algorithm into a second boundary condition generation algorithm; step 303 may include, for example, automatically generating the boundary conditions based on the boundary condition configuration file, the mesh information, and the second boundary condition generation algorithm.

[0086] The method described above, which optimizes the first boundary condition generation algorithm corresponding to the boundary condition type and solver type to obtain the second boundary condition generation algorithm, allows for changes to boundary conditions without altering the existing boundary condition configuration file. Only the boundary condition generation algorithm needs optimization to change the boundary conditions. This approach, focusing solely on optimizing the boundary condition generation algorithm, improves the development efficiency and robustness of the wind resource simulation platform.

[0087] Furthermore, in this embodiment of the application, after automatically generating boundary conditions, wind resource simulation of the wind farm can be performed according to these boundary conditions to achieve wind resource simulation of the wind farm. Therefore, in an optional implementation of this embodiment, the method may further include step F: performing wind resource simulation of the wind farm based on the boundary conditions.

[0088] Through the various implementation methods provided in this embodiment, firstly, based on the setting information of the wind resource simulation platform, general configuration parameters, boundary condition types, and solver types for generating boundary conditions are obtained; then, a boundary condition configuration file is automatically generated using the general configuration parameters, boundary condition types, and solver types; the file format of this boundary condition configuration file is determined based on the boundary condition types and solver types; finally, the boundary conditions corresponding to the mesh information are automatically generated by combining the boundary condition configuration file with the mesh information corresponding to the general configuration parameters. It can be seen that by adding user-defined boundary condition types and solver types to the general configuration parameters, a boundary condition configuration file with a file format determined by the boundary condition types and solver types is automatically generated, and then combined with mesh information, the boundary conditions are automatically generated. In this method, the boundary condition types and solver types are user-defined, thus the boundary condition generation method has scalability, thereby meeting diverse needs for boundary conditions.

[0089] Exemplary device

[0090] See Figure 4 This illustration shows a schematic diagram of a boundary condition generation device according to an embodiment of this application. In this embodiment, the device may specifically include, for example, an acquisition unit and a generation unit;

[0091] The acquisition unit 401 is used to acquire, from the setting information of the wind resource simulation platform, the general configuration parameters, boundary condition type and solver type used to generate boundary conditions;

[0092] The generation unit 402 is used to automatically generate a boundary condition configuration file based on the general configuration parameters, the boundary condition type, and the solver type; the file format of the boundary condition configuration file is determined based on the boundary condition type and the solver type.

[0093] The generation unit 402 is also used to automatically generate boundary conditions corresponding to the mesh information based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters.

[0094] In one optional embodiment of this application, the general configuration parameters include wind farm location, sector wind direction, stability, and reference wind speed.

[0095] In one optional embodiment of this application, the generation unit 402 includes: a first generation subunit and an acquisition subunit;

[0096] The generation subunit is used to generate a configuration file that satisfies the file format corresponding to the boundary condition type and the solver type;

[0097] The obtaining sub-unit is used to obtain the boundary condition configuration file based on the general configuration parameters, the boundary condition type, the solver type, and the configuration file.

[0098] In one optional embodiment of this application, the obtaining subunit includes: a first obtaining module and a second obtaining module;

[0099] The first obtaining module is used to obtain other configuration parameters for generating the boundary conditions based on the general configuration parameters, the boundary condition type, and the solver type;

[0100] The second obtaining module is used to write the general configuration parameters, the other configuration parameters, the boundary condition type and the solver type into the configuration file to obtain the boundary condition configuration file.

[0101] In one optional embodiment of this application, the generation unit 402 further includes: a determining subunit and a second generation subunit;

[0102] The determining subunit is used to determine the first boundary condition generation algorithm corresponding to the boundary condition type and the solver type;

[0103] The second generation subunit is used to automatically generate the boundary conditions based on the boundary condition configuration file, the mesh information, and the first boundary condition generation algorithm.

[0104] In one optional embodiment of this application, the method further includes: an optimization unit;

[0105] The optimization unit is used to optimize the first boundary condition generation algorithm into a second boundary condition generation algorithm;

[0106] The generation unit 402 is further configured to:

[0107] The boundary conditions are automatically generated based on the boundary condition configuration file, the mesh information, and the second boundary condition generation algorithm.

[0108] In one optional embodiment of this application, the device further includes: a simulation unit;

[0109] The simulation unit is used to simulate wind resources of the wind farm based on the boundary conditions.

[0110] Through the various implementation methods provided in this embodiment, firstly, based on the setting information of the wind resource simulation platform, general configuration parameters, boundary condition types, and solver types for generating boundary conditions are obtained; then, a boundary condition configuration file is automatically generated using the general configuration parameters, boundary condition types, and solver types; the file format of this boundary condition configuration file is determined based on the boundary condition types and solver types; finally, the boundary conditions corresponding to the mesh information are automatically generated by combining the boundary condition configuration file with the mesh information corresponding to the general configuration parameters. It can be seen that by adding user-defined boundary condition types and solver types to the general configuration parameters, a boundary condition configuration file with a file format determined by the boundary condition types and solver types is automatically generated, and then combined with mesh information, the boundary conditions are automatically generated. In this method, the boundary condition types and solver types are user-defined, thus the boundary condition generation method has scalability, thereby meeting diverse needs for boundary conditions.

[0111] Furthermore, embodiments of this application also provide a computer device, which includes a processor and a memory:

[0112] The memory is used to store program code and transmit the program code to the processor;

[0113] The processor is used to execute the boundary condition generation method described in the above method embodiments according to the instructions in the program code.

[0114] This application also provides a computer-readable storage medium for storing program code for executing the boundary condition generation method described in the above method embodiments.

[0115] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0116] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0117] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0118] The above description is merely a preferred embodiment of this application and is not intended to limit the application in any way. Although this application has disclosed preferred embodiments above, it is not intended to limit the application. Any person skilled in the art can make many possible variations and modifications to the technical solutions of this application using the methods and techniques disclosed above, or modify them into equivalent embodiments with equivalent changes, without departing from the scope of the technical solutions of this application. Therefore, any simple modifications, equivalent changes, and modifications made to the above embodiments based on the technical essence of this application without departing from the content of the technical solutions of this application shall still fall within the protection scope of the technical solutions of this application.

Claims

1. A method for generating boundary conditions, characterized in that, include: Obtain the general configuration parameters, boundary condition types, and solver types used to generate boundary conditions from the settings information of the wind resource simulation platform; The wind resource simulation platform provides various boundary condition types and solver types; A boundary condition configuration file is automatically generated based on the general configuration parameters, the boundary condition type, and the solver type. The general configuration parameters include wind farm location, sector wind direction, stability, and reference wind speed. The file format of the boundary condition configuration file is determined based on the boundary condition type and the solver type. Based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters, the boundary conditions corresponding to the mesh information are automatically generated. The step of automatically generating a boundary condition configuration file based on the general configuration parameters, the boundary condition type, and the solver type includes: Generate a configuration file that satisfies the file format corresponding to the boundary condition type and the solver type; The boundary condition configuration file is obtained based on the general configuration parameters, the boundary condition type, the solver type, and the configuration file. The automatic generation of boundary conditions corresponding to the mesh information based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters includes: Determine the first boundary condition generation algorithm corresponding to the boundary condition type and the solver type; The boundary conditions are automatically generated based on the boundary condition configuration file, the mesh information, and the first boundary condition generation algorithm.

2. The method according to claim 1, characterized in that, The step of obtaining the boundary condition configuration file based on the general configuration parameters, the boundary condition type, the solver type, and the configuration file includes: Based on the general configuration parameters, the boundary condition type, and the solver type, other configuration parameters for generating the boundary conditions are obtained; Write the general configuration parameters, the other configuration parameters, the boundary condition type, and the solver type into the configuration file to obtain the boundary condition configuration file.

3. The method according to claim 1, characterized in that, The method further includes: The first boundary condition generation algorithm is optimized into a second boundary condition generation algorithm; The automatic generation of boundary conditions corresponding to the mesh information based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters includes: The boundary conditions are automatically generated based on the boundary condition configuration file, the mesh information, and the second boundary condition generation algorithm.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Wind resource simulation of the wind farm is performed based on the aforementioned boundary conditions.

5. A device for generating boundary conditions, characterized in that, include: Acquisition unit and generation unit; The acquisition unit is used to acquire general configuration parameters, boundary condition types, and solver types for generating boundary conditions from the setting information of the wind resource simulation platform; the wind resource simulation platform provides multiple boundary condition types and solver types. The generation unit is used to automatically generate a boundary condition configuration file based on the general configuration parameters, the boundary condition type, and the solver type; the general configuration parameters include wind farm location, sector wind direction, stability, and reference wind speed, and the file format of the boundary condition configuration file is determined based on the boundary condition type and the solver type; The generation unit is also used to automatically generate boundary conditions corresponding to the mesh information based on the boundary condition configuration file and the mesh information corresponding to the general configuration parameters; The generation unit includes: a first generation subunit and an acquisition subunit; The generation subunit is used to generate a configuration file that satisfies the file format corresponding to the boundary condition type and the solver type; The obtaining subunit is used to obtain the boundary condition configuration file based on the general configuration parameters, the boundary condition type, the solver type, and the configuration file; The generation unit further includes: a determining subunit and a second generation subunit; The determining subunit is used to determine the first boundary condition generation algorithm corresponding to the boundary condition type and the solver type; The second generation subunit is used to automatically generate the boundary conditions based on the boundary condition configuration file, the mesh information, and the first boundary condition generation algorithm.

6. A computer device, characterized in that, The computer device includes a processor and memory: The memory is used to store program code and transmit the program code to the processor; The processor is configured to execute the boundary condition generation method according to any one of claims 1-4 according to the instructions in the program code.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store program code for performing the method for generating boundary conditions according to any one of claims 1-4.

Images