A method, medium and device for efficiently merging seismic data

Abstract

The present invention discloses a method for efficiently merging seismic data, comprising: receiving storage parameter information about seismic data to be merged from a user; retrieving corresponding seismic data in a database based on the storage parameter information; presenting the file name of the retrieved seismic data to the user and requesting the user to select the file name; transferring the file name selected by the user to a list of seismic data to be merged; requesting the user to name the merged seismic data file as the target seismic data file name, and performing a compliance check on the target seismic data file name; performing a compliance check on the seismic data corresponding to the file name included in the list of seismic data to be merged; after successfully checking the compliance of all seismic data, merging the seismic data. The present invention also provides a computer-readable storage medium and device for storing instructions corresponding to the method. The technology of the present invention effectively improves the efficiency of merging seismic data and optimizes the user experience.

Description

Technical Field

[0001] The present invention relates to the field of seismic data processing in petroleum seismic exploration, and in particular to a method, medium and equipment for efficiently merging seismic data. Background Art

[0002] Seismic data processing is a critical technology in the oil exploration industry. Its purpose is to process and calculate seismic data collected in the field according to specific processing algorithms, thereby generating images of underground geological structures to guide subsequent drilling and oil production. With the continuous application of new exploration and high-precision acquisition technologies in oil exploration, the amount of raw seismic data collected from the field has grown rapidly. Currently, the scale of a single data volume has exceeded the petabyte level, with the number of seismic channels reaching hundreds of billions. Processing massive seismic data at the terabyte and petabyte level places higher demands not only on computer hardware systems for data storage and data reading and writing, but also on software systems and seismic data processing processes.

[0003] In seismic data processing, data sorting and merging are the most basic and common data processing patterns in seismic applications. Therefore, efficient data merging is essential for ensuring the integrity of seismic information and improving data processing efficiency. Using traditional methods for data merging presents the following challenges: low transmission efficiency for massive amounts of seismic data, and cumbersome operations such as data analysis and quality control. Furthermore, operating with large amounts of data increases the error rate, and repetitive operations waste significant time, impacting project cycles.

[0004] Therefore, in order to address the problems existing in the merging and processing of massive seismic data, it is necessary to design an efficient seismic data merging method and equipment that is different from the conventional processing process to improve the efficiency of seismic data merging, optimize the user experience, and accelerate the pace of oil field production. Summary of the Invention

[0005] The present invention provides a method, medium and device for efficiently merging seismic data to solve at least one of the above-mentioned technical problems in the prior art.

[0006] In order to achieve the above technical objectives, the technical solutions adopted by the present invention are as follows:

[0007] According to one aspect of the present invention, a method for efficiently merging seismic data is provided, comprising the following steps:

[0008] Step 1: receiving storage parameter information about the seismic data to be merged from the user;

[0009] Step 2: Retrieving corresponding seismic data in a database based on the stored parameter information;

[0010] Step 3: presenting the retrieved file name of the seismic data to the user and requesting the user to select the file name;

[0011] Step 4: Transfer the file name selected by the user to the earthquake data list to be merged;

[0012] Step 5: Requesting the user to name the merged seismic data file as the target seismic data file name, and performing a compliance check on the target seismic data file name;

[0013] Step 6: performing compliance check on the seismic data corresponding to the file name included in the seismic data list to be merged;

[0014] Step 7: After successfully checking the compliance of all seismic data, proceed directly to the seismic data merging operation.

[0015] According to one embodiment of the present invention, receiving storage parameter information about the seismic data to be merged from the user in step 1 includes displaying options for selecting storage parameter information about the seismic data to the user via a human-computer interaction interface.

[0016] According to one embodiment of the present invention, the storage parameter information of the seismic data includes project parameters, work area parameters, survey line parameters and / or swath bundle parameters of the seismic data.

[0017] According to one embodiment of the present invention, the seismic data is stored in the database in the following manner: multiple databases are managed with projects as the main line, each database manages one or more projects, each project has one or more work areas, each work area has a survey line or swath bundle, wherein the seismic data of the two-dimensional work area are stored in the survey line, and the seismic data of the three-dimensional work area are directly stored under the work area.

[0018] According to an embodiment of the present invention, the human-computer interaction interface displays options for selecting a project, a work area, a survey line and / or a swath harness to the user.

[0019] According to one embodiment of the present invention, a search option is provided to the user, all seismic data containing the search string are searched based on the seismic data name entered by the user in the search option, and the names of all found seismic data files are displayed in a search result list so that the user can make batch selections.

[0020] According to one embodiment of the present invention, the names of all found seismic data files are displayed in the search result list, including only loading the seismic data files created by the user in the search result list, filtering out other redundant data, and not displaying incomplete seismic data that has not yet been generated. If the seismic data job is still running, the user updates the seismic data list in real time through the refresh option set on the human-computer interaction interface.

[0021] According to an embodiment of the present invention, the option of storing the parameter information is displayed to the user based on the management authority of the user.

[0022] According to one embodiment of the present invention, the seismic data to be merged and the merged seismic data need to be located in the same project, work area and survey line.

[0023] According to one embodiment of the present invention, requesting the user to name the merged seismic data file in step 5 includes requesting the user to input the name of the merged seismic data file in a seismic data name input box.

[0024] According to one embodiment of the present invention, the compliance check of the target seismic data file name in step 5 includes: if the target seismic data file name has the same name as the file name in the seismic data list to be merged, the user is prompted to modify it; if there is a data file with the same name under the project / work area / survey line where the target seismic data is located, the user is prompted whether to overwrite it. If the user chooses to overwrite, the original data file with the same name will be replaced by the target seismic data. If the user chooses to keep the original seismic data file with the same name, the user is prompted to modify the target seismic data file name.

[0025] According to one embodiment of the present invention, step 6 includes: taking the first seismic data in the list of seismic data to be merged as a reference, checking in turn whether the volume header and / or trace header description files of all seismic data to be merged are completely consistent; if the volume header and / or trace header formats of all seismic data to be merged are consistent, the data are directly merged after the check is completed; otherwise, the user is prompted with the name of the seismic data that is different from the volume header and / or trace header description files of the first seismic data in the list of seismic data to be merged; the user adjusts the list of seismic data to be merged as required and determines that the volume header and / or trace header description files of all seismic data to be merged are completely consistent before executing the data merge.

[0026] According to one embodiment of the present invention, the seismic data merging operation in step 7 includes:

[0027] Generate target data file: Generate the merged seismic data file in the seismic directory according to the project, work area and survey line where the seismic data file to be merged is located;

[0028] Merging the seismic data files to be merged: merging the volume headers of each sub-data in the seismic data list to be merged, writing the merged seismic data volume header into the data file, taking out a trace header description file of one of the sub-data, writing the merged seismic data trace header description file into the data file, and renaming the trace header files and data body files of each sub-data in the merging order, and renaming them as the trace header and data body components of the merged seismic data;

[0029] Generate a history file of the merged data: copy the history file of the first sub-data in the seismic data list to be merged as the main history file of the merged seismic data, and then write the path information of each sub-data into this file;

[0030] Delete source data files: After the seismic data file merging is completed, the local file directories of all sub-data under the seismic data list to be merged will be deleted from the database, and the seismic data merging process is completed.

[0031] According to one embodiment of the present invention, the method further includes fault tolerance processing, wherein the fault tolerance processing includes:

[0032] During the merging process of seismic data, a configuration file is simultaneously generated under the generated target seismic data file, wherein the configuration file records the original file path of the seismic sub-data involved in the merging, the original data trace header file, the data body file name, the merged target seismic data file path, and the renamed trace header file and / or data body file name;

[0033] If an uncontrollable abnormal situation occurs during the seismic data merging process, the user should restart the program and make the database, project, work area, survey line and merged seismic data file names consistent with the interface at the time of abnormal exit. Then, reset the merged file to the original location through the seismic data recovery option and re-merge the data. When choosing to recover seismic data, according to the configuration file record information under the target seismic data file, the files in the seismic data are restored to their original locations in turn, and the modified data file name is reset according to the original file path and file name.

[0034] According to one embodiment of the present invention, when the compliance check is performed on the seismic data, the check progress is displayed in real time in a progress bar of the human-computer interaction interface.

[0035] According to one embodiment of the present invention, when the seismic data are merged, the merging progress is displayed in real time in a progress bar of the human-computer interaction interface.

[0036] According to one embodiment of the present invention, if an error occurs during the seismic data merging process, the human-computer interaction interface is used to prompt the user with corresponding error information.

[0037] According to one embodiment of the present invention, the method further comprises providing the user with an option to remove files from the list of seismic data to be merged.

[0038] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described above are performed.

[0039] According to another aspect of the present invention, there is provided a computer device comprising:

[0040] at least one processor; and

[0041] A memory stores a computer program that can be run on the processor, and the processor performs the steps of the method described above when executing the program.

[0042] Due to the adoption of the above technical solution, the method, medium and device provided by the present invention have at least one of the following beneficial effects compared with the prior art:

[0043] (1) Retrieve and merge seismic data to be merged based on storage parameter information, which can significantly improve the efficiency of seismic data loading and merging compared with traditional methods;

[0044] (2) Using the search function to quickly select the list of earthquake data to be merged;

[0045] (3) When merging seismic data, the progress and error information of seismic data compliance check and seismic data merging are prompted in real time, so that users can better understand the operation progress;

[0046] (4) If power outages, program crashes, or other abnormal situations occur during the data merging process, the original data recovery function is provided to avoid wasting time due to repeated operations;

[0047] (5) According to the specified database, project, work area, and survey line, load all complete seismic data created by the current user and filter out other redundant data. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the following detailed description, they are used to explain the present invention but do not constitute a limitation of the present invention. In the accompanying drawings:

[0049] Figure 1A schematic diagram showing a human-computer interaction interface when loading data in a method for efficiently merging seismic data according to an embodiment of the present invention is shown;

[0050] Figure 2 A schematic diagram showing a flow chart of a method for efficiently merging seismic data according to an embodiment of the present invention when performing data merging is shown;

[0051] Figure 3 A schematic diagram showing the efficiency comparison between the efficient seismic data merging method according to an embodiment of the present invention and a conventional seismic data merging processing flow is shown. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below in conjunction with specific embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0053] In one embodiment of the present invention, a method for efficiently merging seismic data is provided. The method generally comprises the following steps:

[0054] Step 1: receiving storage parameter information about the seismic data to be merged from the user;

[0055] Step 2: Retrieve corresponding earthquake data from the database based on the stored parameter information;

[0056] Step 3: presenting the retrieved file name of the seismic data to the user and requesting the user to select the file name;

[0057] Step 4: Transfer the file name selected by the user to the earthquake data list to be merged;

[0058] Step 5: Requesting the user to name the merged seismic data file as the target seismic data file name, and performing a compliance check on the target seismic data file name;

[0059] Step 6: performing compliance check on the seismic data corresponding to the file name included in the seismic data list to be merged;

[0060] Step 7: After successfully checking the compliance of all seismic data, proceed directly to the seismic data merging operation.

[0061] Each step is described in detail below with reference to the accompanying drawings and examples.

[0062] In step 1, storage parameter information about the seismic data to be merged is received from a user. The storage parameter information of the seismic data includes project parameters, work area parameters, survey line parameters and / or swath bundle parameters of the seismic data.

[0063] Receiving storage parameter information about the seismic data to be merged from a user includes displaying an option for selecting the storage parameter information about the seismic data to the user via a human-computer interaction interface. Figure 1 FIG2 shows a schematic diagram of a human-computer interaction interface when loading data in a method for efficiently merging seismic data according to an embodiment of the present invention. Figure 1 As shown, the human-computer interaction interface may include relevant options for selecting a database (Database), a project (Project), a work area (Survey) and a survey line (Line). The interface also includes an area DataList that displays the names of data files related to the input information and a list of seismic data to be merged SelectedData that displays the names of seismic data files to be merged selected by the user.

[0064] In step 2, the corresponding seismic data is retrieved from the database based on the stored parameter information. To improve the software's speed and streamline data management, seismic data is stored in the database as follows: multiple databases are managed based on projects. Each database manages one or more projects, each project has one or more work areas, and each work area has survey lines or swaths. Seismic data for two-dimensional work areas is stored within the survey lines, while seismic data for three-dimensional work areas is stored directly within the work area.

[0065] In step 3, the file names of the retrieved seismic data are presented to the user and the user is requested to select a file name.

[0066] In the Database selection drop-down box, you can list the names of all databases that the user has permission to access, and the user can select the database containing the seismic data to be merged as needed. After the database is selected, the Project selection drop-down box will list all projects under the database that the user has permission to access, and the user can select the project containing the seismic data to be merged as needed. After the project is selected, the Survey work area selection drop-down box will list all work areas that the user has permission to access under the project, and the user can select the work area containing the seismic data to be merged as needed. If the seismic data that the user needs to merge is the seismic data of a three-dimensional work area, then after the work area is selected, all the seismic data under the work area will be displayed under the DataList data tree. If the seismic data that the user needs to merge is the seismic data of a two-dimensional work area, then after the work area is selected, the user needs to select the survey line where the seismic data to be merged is located in the Line survey line selection drop-down box, and then all the seismic data under the survey line will be listed under the DataList data tree.

[0067] Regarding the earthquake data under the DataList data tree, in order to facilitate the user's subsequent data selection, in some embodiments, the loaded data may only be the complete earthquake data created by the user himself, and the earthquake data created by other users that is not needed is filtered.

[0068] In some implementations, if the user is loading data and there is seismic data that is in the process of being generated but is not displayed under the data tree, the user can update the seismic data list under the DataList data tree in real time through the Reload refresh option set on the interface without changing the project-work area-survey line.

[0069] In step 4, the file name selected by the user is transferred to the list of seismic data to be merged, SelectedData. The user needs to select the seismic data to be merged from all the seismic data loaded in the work area / surface line and store them separately in the SelectedData data tree for subsequent data merging. The steps for selecting seismic data are as follows:

[0070] Step 4.1: The user selects the earthquake data to be merged from the earthquake data file name loaded in the DataList data tree. Figure 1 The “=>” transfer button shown transfers the seismic data to the SelectedData data tree. The seismic data list stored in the SelectedData data tree is the final seismic data to be merged.

[0071] Step 4.2: Since the seismic data to be merged are often generated by the same seismic operation, their file names may have similar prefixes. To facilitate quick seismic data selection, the DataList tree provides a string sorting function, allowing users to search by the first letter of the data file name. The human-computer interface also provides a search option. If the user enters the corresponding seismic data file name in the Filter search box, the DataList tree will display only those seismic data containing the search string.

[0072] Step 4.3: You can select and drag data in batches to save operation time.

[0073] Step 4.4: If the user finds that unnecessary data is placed under the final earthquake data list SelectedData to be merged, the user can Figure 1 The “<=” button shown is used to adjust the data and move the mistakenly selected data from the data to be merged back to the DataList data list.

[0074] In step 5, the user is requested to name the merged seismic data file as the target seismic data file name, and a compliance check is performed on the target seismic data file name.

[0075] Before merging seismic data, users need to name the merged seismic data and check the compliance of the target seismic data file name.

[0076] Step 5.1: Enter the name of the merged seismic data file in the Dataname input box. In some embodiments, to meet the requirements of the subsequent seismic data processing flow, the input file name needs to be within 256 characters.

[0077] Step 5.2: If the file name you need to enter has a similar prefix to the file name of some data in the earthquake data list, the user can select a similar earthquake data name, copy it, and paste it into the Dataname input box, and then modify and adjust the merged earthquake data file name based on this.

[0078] Step 5.3: Seismic data file names must be unique within the same project / work area / surface. If the target seismic data file has the same name as data in the list of data to be merged, the user will be prompted to modify it. If the target seismic data file has the same name as other data files in the same work area / surface, the user will be prompted to overwrite it.

[0079] Step 5.4: If the user chooses to overwrite, that is, the user selects the Override check box, the original data file with the same name will be replaced by the target seismic data. If the user chooses to keep the original seismic data file with the same name, the target seismic data name needs to be modified.

[0080] In step 6, a compliance check is performed on the seismic data corresponding to the file names included in the seismic data list to be merged.

[0081] The system's seismic data files are generally stored in the seismic directory under the user's project, work area, or survey line. Complete seismic data primarily consists of the following components: a volume header definition file, a trace header definition file, a volume header file, a trace header file, and a seismic trace data file. The volume header definition and trace header definition for the seismic data are recorded in XML format, describing the common attribute information for the seismic data and the individual attribute information for the seismic traces, respectively. Each seismic trace has the same trace header word sequence structure (trace header definition), but different trace header word values. The trace header values ​​for all seismic traces are recorded sequentially in binary format. Furthermore, the seismic data records the sample point data for all seismic traces sequentially in binary format. The data recording method is generally described in the volume header.

[0082] The seismic data to be merged must have a consistent volume header / trace header format, that is, the number, type, and offset of volume header / trace header characters must be exactly the same. Therefore, when checking the seismic data to be merged, the first seismic data in the data list is used as the benchmark, and the volume header / trace header description files of the subsequent seismic data to be merged are compared to ensure that they are completely consistent with it.

[0083] In some embodiments, when performing a compliance check on seismic data, the check progress will be displayed in real time in the progress bar of the interactive interface. If the volume header / trace header formats of all seismic data to be merged are consistent, the data will be merged directly after the check is completed.

[0084] If seismic data is found to have different volume header / trace header description files from the first seismic data in the list after inspection, the user will be prompted with the file name of the seismic data. The user needs to adjust the volume header / trace header format of the different seismic data to make it consistent with the volume header / trace header description file of the first seismic data before executing the seismic data merge.

[0085] In step 7, after successfully checking the compliance of all seismic data, proceed directly to the seismic data merging operation. Figure 1 Click the Merge button in the human-computer interaction interface to start merging seismic data.

[0086] The merging process of seismic data is as follows Figure 2 As shown, it is mainly divided into the following steps:

[0087] Step 7.1: Generate the merged target seismic data file in the seismic directory according to the project / work area / survey line.

[0088] Step 7.2: Merge the volume headers of each sub-data in the list of seismic data to be merged, and write them into the data file as the volume headers of the merged seismic data.

[0089] Step 7.3: Take out the trace header description file of one of the sub-data and write it into the data file as the trace header description file of the merged seismic data.

[0090] Step 7.4: Rename the header files (Header.partxxx) and volume files (Volumn.partxxx) of each sub-data in the order of merging, as the part of the merged seismic data.

[0091] Step 7.5: Copy the history file of the first sub-data in the list of seismic data to be merged as the main history file of the merged seismic data. Based on this file, add the merged data source information, that is, the path information of each sub-data.

[0092] Step 7.6: After the seismic data files are merged, the local file directories of all sub-data under the list of seismic data to be merged are deleted from the database.

[0093] Optionally, in some embodiments, a progress bar is displayed on the human-computer interaction interface to prompt the user that the seismic data merging process is completed.

[0094] If there is only one earthquake data in the earthquake data list to be merged, the earthquake data merging process at this time is equivalent to renaming the earthquake data.

[0095] In some embodiments, the method also includes fault-tolerant processing. If an error occurs during the seismic data merging process, the interactive interface will prompt the user with the corresponding error information so that the user can make adjustments. If uncontrollable abnormal conditions occur during the seismic data merging process, such as power outages or program crashes, the program also provides a function for restoring the original data to avoid wasting time by repeatedly generating data. The specific recovery steps are as follows:

[0096] Step A1: Restart the program to ensure that the database, project, work area, survey line and merged seismic data file names are consistent with the interface at the time of abnormal exit.

[0097] Step A2: Press the Recover data recovery button to restore the merged files to their original location (the specific restoration operation will be introduced below), and then merge the data again using the above data merging steps.

[0098] During the seismic data merging process, a MergedMap configuration file is generated within the target seismic data file. This file contains the original file paths, original data header / data volume file names, merged target seismic data file paths, and renamed header / data volume file names of the seismic data sub-data involved in the merging process. During seismic data recovery, the local file directory for the data is traced back using the database, project, work area, survey line, and seismic data file names provided in Step 1. The files in the seismic data are then restored to their original locations, one by one, based on the information recorded in the configuration file. This means that the file names modified in Step 7.4 are restored to their original file paths and file names.

[0099] In order to verify the effectiveness of the method of the present invention, a merge test was conducted on two-dimensional, three-dimensional, pre-stack, post-stack, same gather, different gathers, and depth domain velocity volume data. In addition, the efficiency comparison test was conducted with the batch input and output module of the conventional processing flow for the cases where the number of data files was 500 and the test data size was 100G, 1T, and 10T respectively, and the test data size was 100G and the number of data files was 5, 100, and 500 respectively. The test results are as follows: Figure 3 As shown in the figure, it can be seen that as the amount of data increases, the method of the present invention can significantly improve the efficiency of seismic data merging.

[0100] The present invention also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the method described above are executed.

[0101] In addition, the present invention also provides a computer device. The device includes at least one processor and a memory. The memory stores a computer program that can be run on the processor, and when the processor executes the program, the steps of the above method are performed.

[0102] Those skilled in the art will also appreciate that, in addition to implementing the controller in pure computer-readable program code, it is entirely possible to implement the same functionality by logically programming the method steps in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, embedded microcontrollers, and the like. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered structures within the hardware component. Alternatively, the devices for implementing various functions can be considered both software modules implementing the method and structures within the hardware component.

[0103] It can be seen from the description of the above embodiments that those skilled in the art can clearly understand that the present application can be implemented by means of software plus the necessary general hardware platform. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product. In a typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. The computer software product may include several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application or certain parts of the embodiments. The computer software product can be stored in a memory, which may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium. Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0104] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the device embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

[0105] The present application can be used in a wide variety of general-purpose or specialized computer system environments or configurations, such as personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments that include any of the above.

[0106] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

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

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

[0109] In addition, the various embodiments of the present invention may be arbitrarily combined, and as long as they do not violate the concept of the present invention, they should also be regarded as the contents disclosed by the present invention.

Claims

1. A method for efficiently merging seismic data, characterized in that: The following steps are involved: Step 1: receiving storage parameter information about the seismic data to be merged from the user; Step 2: Retrieving corresponding seismic data in a database based on the stored parameter information; Step 3: presenting the retrieved file name of the seismic data to the user and requesting the user to select the file name; Step 4: Transfer the file name selected by the user to the earthquake data list to be merged; Step 5: Requesting the user to name the merged seismic data file as the target seismic data file name, and performing a compliance check on the target seismic data file name; Step 6: performing compliance check on the seismic data corresponding to the file name included in the seismic data list to be merged; Step 7: After successfully checking the compliance of all seismic data, proceed directly to the seismic data merging operation; The storage parameter information of the seismic data includes project parameters, work area parameters, survey line parameters and / or swath bundle parameters of the seismic data; In step 6, the first earthquake data in the earthquake data list to be merged is used as a reference, and the volume header and / or trace header description files of all the earthquake data to be merged are checked in turn to see if they are completely consistent. If the volume header and / or trace header formats of all the earthquake data to be merged are consistent, the data are directly merged after the check is completed. Otherwise, the user is prompted with the names of the earthquake data that are different from the volume header and / or trace header description files of the first earthquake data in the earthquake data list to be merged. The user adjusts the earthquake data list to be merged as required and determines that the volume header and / or trace header description files of all the earthquake data to be merged are completely consistent before performing the data merge. Step 7: The seismic data merging operation includes: Generate target data file: Generate the merged seismic data file in the seismic directory according to the project, work area and survey line where the seismic data file to be merged is located; Merging the seismic data files to be merged: merging the volume headers of the sub-data in the seismic data list to be merged, writing the merged seismic data volume header into the data file, taking out the trace header description file of one of the sub-data, writing the merged seismic data trace header description file into the data file, and renaming the trace header files and data body files of the sub-data in the merged order, and using them as the trace header and data body components of the merged seismic data; Generate a history file of the merged data: copy the history file of the first sub-data in the seismic data list to be merged as the main history file of the merged seismic data, and then write the path information of each sub-data into this file; Delete source data files: After the seismic data file merging is completed, the local file directories of all sub-data under the seismic data list to be merged will be deleted from the database, and the seismic data merging process is completed; The method further includes fault tolerance processing, and the fault tolerance processing includes: During the merging process of seismic data, a configuration file is simultaneously generated under the generated target seismic data file, wherein the configuration file records the original file path of the seismic sub-data involved in the merging, the original data trace header file, the data body file name, the merged target seismic data file path, and the renamed trace header file and / or data body file name; If an uncontrollable abnormal situation occurs during the seismic data merging process, the user should restart the program and make the database, project, work area, survey line and merged seismic data file names consistent with the interface at the time of abnormal exit. Then, reset the merged file to the original location through the seismic data recovery option and re-merge the data. When choosing to recover seismic data, according to the configuration file record information under the target seismic data file, the files in the seismic data are restored to their original locations in turn, and the modified data file name is reset according to the original file path and file name.

2. The method according to claim 1, characterized in that Receiving storage parameter information about the seismic data to be merged from the user in step 1 includes displaying options for selecting storage parameter information about the seismic data to the user via a human-computer interaction interface.

3. The method according to claim 2, characterized in that The seismic data is stored in the database in the following manner: multiple databases are managed with projects as the main line, each database manages one or more projects, each project has one or more work areas, each work area has a survey line or swath bundle, among which the seismic data of the two-dimensional work area are stored in the survey line, and the seismic data of the three-dimensional work area are directly stored under the work area.

4. The method according to claim 3, characterized in that The human-computer interaction interface displays options for the user to select a project, a work area, a survey line and / or a swath harness.

5. The method according to claim 3, characterized in that The method includes providing a search option to the user, searching for all earthquake data containing a search string based on the earthquake data name input by the user in the search option, and displaying the names of all found earthquake data files in a search result list so that the user can select in batches.

6. The method according to claim 5, characterized in that The search results list displays the names of all found earthquake data files, including only loading the earthquake data files created by the user in the search results list, filtering out other redundant data, and not displaying incomplete earthquake data that has not yet been generated. If the earthquake data job is still running, the user can update the earthquake data list in real time through the refresh option set on the human-computer interaction interface.

7. The method according to claim 2, characterized in that The option of displaying the storage parameter information to the user is based on the user's management authority.

8. The method according to claim 1, characterized in that The seismic data to be merged and the merged seismic data need to be located in the same project, work area and survey line.

9. The method according to claim 1, characterized in that Requesting the user to name the merged seismic data file in step 5 includes requesting the user to input the name of the merged seismic data file in a seismic data name input box.

10. The method according to claim 1, characterized in that The compliance check of the target seismic data file name in step 5 includes: if the target seismic data file name has the same name as the file name in the seismic data list to be merged, the user is prompted to modify it; if there is a data file with the same name under the project / work area / survey line where the target seismic data is located, the user is prompted whether to overwrite it. If the user chooses to overwrite, the original data file with the same name will be replaced by the target seismic data. If the user chooses to keep the original seismic data file with the same name, the user is prompted to modify the target seismic data file name.

11. The method according to claim 2, characterized in that When the compliance check is performed on the seismic data, the check progress is displayed in real time in the progress bar of the human-computer interaction interface.

12. The method according to claim 2, characterized in that When the seismic data are merged, the merging progress is displayed in real time in the progress bar of the human-computer interaction interface.

13. The method according to claim 2, characterized in that If an error occurs during the seismic data merging process, the human-computer interaction interface is used to prompt the user with corresponding error information.

14. The method according to claim 1, wherein The method also includes providing the user with an option to remove files from the list of seismic data to be merged.

15. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 14 are performed.

16. A computer device comprising: at least one processor; as well as A memory storing a computer program executable on the processor, wherein the processor executes the steps of the method according to any one of claims 1 to 14 when executing the program.

Images