Node seismic data indexing method, apparatus, medium, and device

Abstract

The application discloses a node seismic data indexing method, device, medium and equipment, and the method comprises the following steps: obtaining the start offset of required seismic data, and generating a start offset list; arranging the seismic data files in chronological order according to the time of the seismic data files; for each seismic data file after sorting, judging whether the seismic data file contains the required seismic data; when the seismic data file contains the required seismic data, reading each trace of data in the seismic data file in turn; for each trace of data, judging whether the trace of data is the start data of the required data; when the trace of data is the start data of the required data, determining the seismic data file where the end data of the required data is located, and recording the start offset of the required data, the file name and path of the seismic data file where the start data and the end data are located in the intermediate index file. The application solves the problem that the seismic data is repeatedly scanned, and indirectly improves the time of shot gather extraction.

Description

Technical Field

[0001] This invention belongs to the field of seismic exploration, and specifically relates to a method, apparatus, medium and electronic equipment for indexing nodal seismic data. Background Technology

[0002] Rapid economic development and energy shortages have led to increased demand for oil. Under this demand, seismic exploration, as the most effective method for oil exploration, is evolving towards higher precision, higher density, and multi-dimensionality. The resulting large-scale seismic exploration data requires timely storage, analysis, and processing. This data is characterized by small blocks of data processed in large quantities. Conventional disk-based data retrieval methods are slow; therefore, it is necessary not only to improve the underlying storage system of seismic data but also to index the seismic data to improve data location speed.

[0003] Using shot excitation and obtaining seismic data through detectors is a common method in seismic exploration.

[0004] Currently, of the shot-induced seismic data acquired by geophones, only the data from the first 8 seconds after firing is useful to mainstream processing systems; and the indexing method for this 8-second data determines the speed of subsequent data extraction. The commonly used indexing method is to scan the corresponding geophone seismic data only when the shot gather data is needed, and then use this index to extract the seismic data at the specified time. This method repeatedly scans a file for a specific time, thus reducing the time required to build an index for a particular firing time.

[0005] Therefore, an indexing method that can avoid repeated scanning of seismic data is needed. Summary of the Invention

[0006] The purpose of this invention is to propose an indexing method for avoiding repeated scanning of seismic data.

[0007] In a first aspect, the present invention provides a node seismic data indexing method, comprising: obtaining the start offset of the required seismic data based on the content of the shot-firing file, and generating a start offset list; arranging the seismic data files in chronological order according to the time of the seismic data files; for each sorted seismic data file, determining whether the seismic data file contains the required seismic data, and if the seismic data file contains the required seismic data, sequentially reading each trace of data in the seismic data file; for each trace of data, determining whether the trace of data is the starting data of the required data based on the start offset list and the current time of the trace of data, and if the trace of data is the starting data of the required data, determining the seismic data file where the ending data of the required data is located, and recording the start offset of the required data, the filename and path of the seismic data file where the starting data and the ending data are located in the intermediate index file.

[0008] Optionally, the starting offset list is generated by the following steps: obtaining multiple initial blasting times based on the content of each blasting file, rounding each initial blasting time to the second, using the rounded blasting time as the starting offset of the required seismic data, and generating a starting offset list based on the multiple starting offsets.

[0009] Optionally, based on the start offset of the required seismic data and the time of the seismic data file, it can be determined whether the required seismic data is contained in the seismic data file.

[0010] Optionally, the following steps are used to determine whether the track data is the starting data of the required data: determine whether the current time of the track data is equal to the time recorded in the start offset list; if the current time of the track data is equal to the time recorded in the start offset list, determine that the track data is the starting data of the required data; if the current time of the track data is not equal to the time recorded in the start offset list, read the next track data.

[0011] Optionally, the following steps can be used to determine the seismic data file containing the end data of the required data: calculate the sum of the number of traces containing the trace data and the number of traces acquired within a preset time. If the sum is less than or equal to the total number of traces contained in the seismic data file, then the start data and the end data are in the same seismic data file, and the seismic data file containing the trace data is the seismic data file containing the start data and the end data of the required data.

[0012] Optionally, if the sum is greater than the total number of traces contained in the seismic data file, then the start data and the end data are in different seismic data files, the seismic data file containing the trace data is the seismic data file containing the start data, and in the sorted seismic data files, the next seismic data file after the seismic data file containing the trace data is the seismic data file containing the end data.

[0013] Secondly, the present invention also provides an electronic device, the electronic device comprising: a memory storing executable instructions; and a processor that executes the executable instructions in the memory to implement the above-described node seismic data indexing method.

[0014] Thirdly, the present invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described node seismic data indexing method.

[0015] Fourthly, the present invention also provides a node seismic data indexing device, comprising: a start offset list generation module, which obtains the start offset of the required seismic data according to the content of the blasting file and generates a start offset list; a file sorting module, which arranges the seismic data files in chronological order according to the time of the seismic data files; a seismic data file judgment module, which judges whether each sorted seismic data file contains the required seismic data, and when the seismic data file contains the required seismic data, reads each data track in the seismic data file sequentially; and an index file recording module, which, for each data track, judges whether the data track is the starting data of the required data according to the start offset list and the current time of the data track, and when the data track is the starting data of the required data, determines the seismic data file where the ending data of the required data is located, and records the file name and path of the seismic data files where the starting data and the ending data are located in the intermediate index file.

[0016] Optionally, the starting offset list is generated by the following steps: obtaining multiple initial blasting times based on the content of each blasting file, rounding each initial blasting time to the second, using the rounded blasting time as the starting offset of the required seismic data, and generating a starting offset list based on the multiple starting offsets.

[0017] Optionally, based on the start offset of the required seismic data and the time of the seismic data file, it can be determined whether the required seismic data is contained in the seismic data file.

[0018] Optionally, the following steps are used to determine whether the track data is the starting data of the required data: determine whether the current time of the track data is equal to the time recorded in the start offset list; if the current time of the track data is equal to the time recorded in the start offset list, determine that the track data is the starting data of the required data; if the current time of the track data is not equal to the time recorded in the start offset list, read the next track data.

[0019] Optionally, the following steps can be used to determine the seismic data file containing the end data of the required data: calculate the sum of the number of traces containing the trace data and the number of traces acquired within a preset time. If the sum is less than or equal to the total number of traces contained in the seismic data file, then the start data and the end data are in the same seismic data file, and the seismic data file containing the trace data is the seismic data file containing the start data and the end data of the required data.

[0020] Optionally, if the sum is greater than the total number of traces contained in the seismic data file, then the start data and the end data are in different seismic data files, the seismic data file containing the trace data is the seismic data file containing the start data, and in the sorted seismic data files, the next seismic data file after the seismic data file containing the trace data is the seismic data file containing the end data.

[0021] The beneficial effects of this invention are as follows: The node seismic data fast indexing technology of this invention achieves the goal of multiple efficient uses with a single scan by scanning the seismic data only once and establishing an efficient index file. This effectively solves the problem of repeated scanning of seismic data and indirectly improves the time for shot gather extraction, providing an efficient indexing method for efficient shot gather extraction at blind sampling nodes in the field.

[0022] The present invention has other features and advantages that will be apparent from or will be set forth in detail in the accompanying drawings and following detailed description, which together serve to explain the particular principles of the invention. Attached Figure Description

[0023] The above and other objects, features and advantages of the present invention will become more apparent from the more detailed description of exemplary embodiments of the invention in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the invention.

[0024] Figure 1 A flowchart of a node seismic data indexing method according to an embodiment of the present invention is shown.

[0025] Figure 2 A structural block diagram of a node seismic data indexing device according to an embodiment of the present invention is shown.

[0026] Explanation of reference numerals in the attached figures

[0027] 102. Start Offset List Generation Module; 104. File Sorting Module; 106. Seismic Data File Judgment Module; 108. Index File Recording Module. Detailed Implementation

[0028] Preferred embodiments of the invention will now be described in more detail. While preferred embodiments of the invention are described below, it should be understood that the invention can be implemented in various forms and should not be limited to the embodiments set forth herein.

[0029] This invention provides a node seismic data indexing method, comprising: obtaining the start offset of the required seismic data based on the content of the shot file, and generating a start offset list; arranging the seismic data files in chronological order according to their time; for each sorted seismic data file, determining whether the seismic data file contains the required seismic data, and if the seismic data file contains the required seismic data, sequentially reading each trace of data in the seismic data file; for each trace of data, determining whether the trace data is the starting data of the required data based on the start offset list and the current time of the trace data, and if the trace data is the starting data of the required data, determining the seismic data file containing the ending data of the required data, and recording the start offset of the required data, the filenames of the starting data and the ending data of the seismic data file containing the ending data in an intermediate index file.

[0030] Specifically, the blasting time in the blasting file is rounded to the second, and the rounded time is used as the starting offset of the required data to generate a starting offset list. Based on the shot point time and the time of the seismic data file, it is determined whether the sorted seismic data file contains the required seismic data. If it does, each data track in the seismic data file is read sequentially. Based on the current time of the data track and the starting offset list, it is determined whether the data track is the starting data. If it is the starting data, the seismic data file where the ending data is located is determined according to the preset time and starting offset. The starting offset, the file name and path of the seismic data file where the starting data is located, and the file name and path of the seismic data file where the ending data is located are recorded in the intermediate index file.

[0031] According to the exemplary implementation, the node seismic data fast indexing technology achieves the goal of one scan for multiple efficient uses by scanning seismic data only once and creating an efficient index file. This effectively solves the problem of repeated scanning of seismic data and indirectly improves the time for shot gather extraction, providing an efficient indexing method for efficient shot gather extraction at blind sampling nodes in the field.

[0032] As an optional approach, the starting offset list is generated by the following steps: based on the content of each blasting file, multiple initial blasting times are obtained, each initial blasting time is rounded to the second, and the rounded blasting time is used as the starting offset of the required seismic data. A starting offset list is generated based on the multiple starting offsets.

[0033] Specifically, the blasting time in the blasting file is rounded to the second, and the rounded blasting time is used as the starting offset of the required seismic data to generate a list of starting offsets.

[0034] As an alternative, it can be determined whether the required seismic data file contains the required seismic data based on the start offset of the required seismic data and the time of the seismic data file.

[0035] Specifically, find each seismic data file containing the required seismic data from multiple seismic data files.

[0036] As an optional solution, the following steps are used to determine whether the track data is the starting data of the required data: determine whether the current time of the track data is equal to the time recorded in the start offset list; if the current time of the track data is equal to the time recorded in the start offset list, determine that the track data is the starting data of the required data; if the current time of the track data is not equal to the time recorded in the start offset list, read the next track data.

[0037] Specifically, determine whether the current time of the data is in the start offset list. If not, read the next data. If it is, record the start offset of the data in the intermediate index file.

[0038] As an optional approach, the following steps are used to determine the seismic data file containing the end data of the required data: calculate the sum of the number of traces containing the trace data and the number of traces acquired within a preset time. If the sum is less than or equal to the total number of traces contained in the seismic data file, then the start data and end data are in the same seismic data file. The seismic data file containing the trace data is the seismic data file containing the start data and end data of the required data.

[0039] Specifically, the length to be captured by the shot (i.e., the preset time) plus the start offset equals the end offset, which is also the end position. The end offset is used to scan the end position of the seismic data. If this end position does not extend to the next file, the method is to add the number of traces corresponding to the start data and the number of traces acquired at the preset time to a value less than the total number of traces in the seismic data file. This indicates that it has not extended to the next file, and the intermediate index file only records the filename and path of this seismic data file.

[0040] As an alternative, if the sum is greater than the total number of traces contained in the seismic data file, then the start data and the end data are in different seismic data files. The seismic data file containing the trace data is the same as the seismic data file containing the start data. In the sorted seismic data files, the seismic data file next to the seismic data file containing the trace data is the same as the seismic data file containing the end data.

[0041] Specifically, if the sum is greater than the total number of traces contained in the seismic data file, it means that the ending data is not in this seismic data file. The position of the ending data has crossed over to the next file. That is, the seismic data file where the starting data is located is different from the seismic data file where the ending data is located. The intermediate index file records the file name and path of the seismic data where the starting data is located, as well as the file name and path of the next adjacent (immediately adjacent) seismic data.

[0042] Secondly, the present invention also provides an electronic device, comprising: a memory storing executable instructions; and a processor executing the executable instructions in the memory to implement the above-mentioned node seismic data indexing method.

[0043] Thirdly, the present invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described node seismic data indexing method.

[0044] Fourthly, the present invention also provides a node seismic data indexing device, comprising: a start offset list generation module, which obtains the start offset of the required seismic data according to the content of the blasting file and generates a start offset list; a file sorting module, which arranges the seismic data files in chronological order according to the time of the seismic data files; a seismic data file judgment module, which judges whether each sorted seismic data file contains the required seismic data, and when the seismic data file contains the required seismic data, reads each data track in the seismic data file sequentially; and an index file recording module, which, for each data track, judges whether the data track is the starting data of the required data according to the start offset list and the current time of the data track, and when the data track is the starting data of the required data, determines the seismic data file where the ending data of the required data is located, and records the file name and path of the seismic data file where the starting data and the ending data are located in an intermediate index file.

[0045] Specifically, the blasting time in the blasting file is rounded to the second, and the rounded time is used as the starting offset of the required data to generate a starting offset list. Based on the shot point time and the time of the seismic data file, it is determined whether the sorted seismic data file contains the required seismic data. If it does, each data track in the seismic data file is read sequentially. Based on the current time of the data track and the starting offset list, it is determined whether the data track is the starting data. If it is the starting data, the seismic data file where the ending data is located is determined according to the preset time and starting offset. The starting offset, the file name and path of the seismic data file where the starting data is located, and the file name and path of the seismic data file where the ending data is located are recorded in the intermediate index file.

[0046] According to the exemplary implementation, the node seismic data fast indexing technology achieves the goal of one scan for multiple efficient uses by scanning seismic data only once and creating an efficient index file. This effectively solves the problem of repeated scanning of seismic data and indirectly improves the time for shot gather extraction, providing an efficient indexing method for efficient shot gather extraction at blind sampling nodes in the field.

[0047] As an optional approach, the starting offset list is generated by the following steps: based on the content of each blasting file, multiple initial blasting times are obtained, each initial blasting time is rounded to the second, and the rounded blasting time is used as the starting offset of the required seismic data. A starting offset list is generated based on the multiple starting offsets.

[0048] Specifically, the blasting time in the blasting file is rounded to the second, and the rounded blasting time is used as the starting offset of the required seismic data to generate a list of starting offsets.

[0049] As an alternative, it can be determined whether the required seismic data file contains the required seismic data based on the start offset of the required seismic data and the time of the seismic data file.

[0050] Specifically, find each seismic data file containing the required seismic data from multiple seismic data files.

[0051] As an optional solution, the following steps are used to determine whether the track data is the starting data of the required data: determine whether the current time of the track data is equal to the time recorded in the start offset list; if the current time of the track data is equal to the time recorded in the start offset list, determine that the track data is the starting data of the required data; if the current time of the track data is not equal to the time recorded in the start offset list, read the next track data.

[0052] Specifically, determine whether the current time of the data is in the start offset list. If not, read the next data. If it is, record the start offset of the data in the intermediate index file.

[0053] As an optional approach, the following steps are used to determine the seismic data file containing the end data of the required data: calculate the sum of the number of traces containing the trace data and the number of traces acquired within a preset time. If the sum is less than or equal to the total number of traces contained in the seismic data file, then the start data and end data are in the same seismic data file. The seismic data file containing the trace data is the seismic data file containing the start data and end data of the required data.

[0054] Specifically, the length to be captured by the shot (i.e., the preset time) plus the start offset equals the end offset, which is also the end position. The end offset is used to scan the end position of the seismic data. If this end position does not extend to the next file, the method is to add the number of traces corresponding to the start data and the number of traces acquired at the preset time to a value less than the total number of traces in the seismic data file. This indicates that it has not extended to the next file, and the intermediate index file only records the filename and path of this seismic data file.

[0055] As an alternative, if the sum is greater than the total number of traces contained in the seismic data file, then the start data and the end data are in different seismic data files. The seismic data file containing the trace data is the same as the seismic data file containing the start data. In the sorted seismic data files, the seismic data file next to the seismic data file containing the trace data is the same as the seismic data file containing the end data.

[0056] Specifically, if the sum is greater than the total number of traces contained in the seismic data file, it means that the ending data is not in this seismic data file. The position of the ending data has crossed over to the next file. That is, the seismic data file where the starting data is located is different from the seismic data file where the ending data is located. The intermediate index file records the file name and path of the seismic data where the starting data is located, as well as the file name and path of the next adjacent (immediately adjacent) seismic data.

[0057] Example 1

[0058] Figure 1 A flowchart of a node seismic data indexing method according to an embodiment of the present invention is shown.

[0059] Combination Figure 1 The method for indexing seismic data at this node includes:

[0060] Step 1: Based on the contents of the blasting file, obtain the starting offset of the required seismic data and generate a list of starting offsets;

[0061] Step 2: Arrange the earthquake data files in chronological order according to their time.

[0062] Step 3: For each sorted seismic data file, determine whether the seismic data file contains the required seismic data. If the seismic data file contains the required seismic data, read each data track in the seismic data file in sequence.

[0063] Step 4: For each trace, based on the start offset list and the current time of the trace data, determine whether the trace data is the starting data of the required data. If the trace data is the starting data of the required data, determine the seismic data file where the ending data of the required data is located, and record the start offset, the file name and path of the seismic data file where the starting data and the ending data are located in the intermediate index file.

[0064] The starting offset list is generated through the following steps: Based on the content of each blasting file, multiple initial blasting times are obtained, each initial blasting time is rounded to the second, and the rounded blasting time is used as the starting offset of the required seismic data. A starting offset list is generated based on multiple starting offsets.

[0065] Specifically, based on the start offset of the required seismic data and the time of the seismic data file, it is determined whether the required seismic data is contained in the seismic data file.

[0066] The following steps are used to determine whether the track data is the starting data of the required data: determine whether the current time of the track data is equal to the time recorded in the start offset list. If the current time of the track data is equal to the time recorded in the start offset list, determine that the track data is the starting data of the required data; if the current time of the track data is not equal to the time recorded in the start offset list, read the next track data.

[0067] The following steps are used to determine the seismic data file containing the end data of the required data: calculate the sum of the number of traces containing the trace data and the number of traces acquired within a preset time. If the sum is less than or equal to the total number of traces contained in the seismic data file, then the start data and the end data are in the same seismic data file. The seismic data file containing the trace data is the seismic data file containing the start data and the end data of the required data.

[0068] If the sum is greater than the total number of traces contained in the seismic data file, then the start data and the end data are in different seismic data files. The seismic data file containing the trace data is the same as the seismic data file containing the start data. In the sorted seismic data files, the seismic data file next to the seismic data file containing the trace data is the same as the seismic data file containing the end data.

[0069] Specifically, the workflow of the seismic data indexing method in this application is explained from the perspective of program operation:

[0070] The first step is to read the OB file.

[0071] The blasting information is read into memory.

[0072] The second step is to obtain the list of node files.

[0073] For 1->N / / From the first node's data root directory to the Nth / / Multi-threaded parallelism

[0074] [1]. Get the 'line' directory list

[0075] [2]. If there is a 'line' whitelist, filter out the 'line' directory list that is not in the whitelist.

[0076] [3]. Get a list of 'devices' directories for all 'line' directories.

[0077] [4]. Traverse all 'device' directories, obtain the BIN file names, and store them according to the 'device' category.

[0078] [5]. If there is a 'device' whitelist, filter for devices that are not in the whitelist.

[0079] [6]. Categorize devices by disk (to improve speed in subsequent concurrent processing of multiple hard drives).

[0080] [7]. Sort all BIN files by time (the original data file list is sorted in chronological order to solve the problem of cross-file shooting data).

[0081] / / Step 3: Parse the BIN files in the file list and generate: "DeviceID.sgri" (Note: One file is generated for each device)

[0082] For 1->N / / From the BIN file of the first disk to the Nth / / Multi-threaded parallel processing

[0083] For 1->M / / From the first device (BIN file) to the Mth device / / The processing of each device is placed in a thread pool.

[0084] [1]. Parse the BIN file in the device and extract the seismic data of each shot point according to the OB information and put it into memory.

[0085] [2]. After all the data in all the BIN files of a device has been extracted into memory, the data in memory is written into an intermediate file (deviceID.sgri).

[0086] / / Step 4: Sort the intermediate files according to the same fffid order.

[0087] For 1->N / / From the first intermediate file to the Nth file

[0088] [1]. Retrieve data from an intermediate file and store it in a memory variable according to the file number.

[0089] [2]. Write the memory variables categorized by file number back to the file.

[0090] / / Step 5: Parse the intermediate file and generate: ele_rawdata_ffidstart-ffidend.json

[0091] For 1->N / / From the first intermediate file to the Nth file

[0092] [1]. Retrieve the data from the intermediate file and store it in memory according to the file number and device number.

[0093] [2]. After an intermediate file is parsed, the data read into memory is written to the file 'ele_rawdata_ffidstart-ffidend.json'.

[0094] Because memory data is stored by file number, JSON files are also saved by file number for easy extraction and use.

[0095] The intermediate index file is output in the following format:

[0096] Node number, file number, Offset (qint32), flag (1 / empty), path

[0097] 12345678 123456 234567 1 absolute path / rawdata filename1 | absolute path / rawdata filename2 (the latter part of the data)

[0098] 12345678 123456 234567 absolute path / rawdata filename 1

[0099] The ele_rawdata_ffidstart-ffidend.json file has the following format:

[0100]

[0101]

[0102] Example 2

[0103] Figure 2 A structural block diagram of a node seismic data indexing device according to an embodiment of the present invention is shown.

[0104] like Figure 2 As shown, the seismic data indexing device for this node includes:

[0105] The start offset list generation module 102 obtains the start offset of the required seismic data based on the contents of the blasting file and generates a start offset list.

[0106] The file sorting module 104 arranges the earthquake data files in chronological order according to their time.

[0107] The earthquake data file judgment module 106 determines whether each sorted earthquake data file contains the required earthquake data. When the earthquake data file contains the required earthquake data, it reads each data track in the earthquake data file in sequence.

[0108] The index file recording module 108, for each data trace, determines whether the trace data is the starting data of the required data based on the start offset list and the current time of the trace data. When the trace data is the starting data of the required data, it determines the seismic data file where the ending data of the required data is located, and records the file name and path of the seismic data file where the starting data and the ending data are located in the intermediate index file.

[0109] The starting offset list is generated through the following steps: Based on the content of each blasting file, multiple initial blasting times are obtained, each initial blasting time is rounded to the second, and the rounded blasting time is used as the starting offset of the required seismic data. A starting offset list is generated based on multiple starting offsets.

[0110] Specifically, based on the start offset of the required seismic data and the time of the seismic data file, it is determined whether the required seismic data is contained in the seismic data file.

[0111] The following steps are used to determine whether the track data is the starting data of the required data: determine whether the current time of the track data is equal to the time recorded in the start offset list. If the current time of the track data is equal to the time recorded in the start offset list, determine that the track data is the starting data of the required data; if the current time of the track data is not equal to the time recorded in the start offset list, read the next track data.

[0112] The following steps are used to determine the seismic data file containing the end data of the required data: calculate the sum of the number of traces containing the trace data and the number of traces acquired within a preset time. If the sum is less than or equal to the total number of traces contained in the seismic data file, then the start data and the end data are in the same seismic data file. The seismic data file containing the trace data is the seismic data file containing the start data and the end data of the required data.

[0113] If the sum is greater than the total number of traces contained in the seismic data file, then the start data and the end data are in different seismic data files. The seismic data file containing the trace data is the same as the seismic data file containing the start data. In the sorted seismic data files, the seismic data file next to the seismic data file containing the trace data is the same as the seismic data file containing the end data.

[0114] Example 3

[0115] This disclosure provides an electronic device comprising: a memory storing executable instructions; and a processor executing the executable instructions in the memory to implement the aforementioned node seismic data indexing method.

[0116] An electronic device according to an embodiment of the present disclosure includes a memory and a processor.

[0117] This memory is used to store non-transitory computer-readable instructions. Specifically, the memory may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may, for example, include random access memory (RAM) and / or cache memory. The non-volatile memory may, for example, include read-only memory (ROM), hard disk, flash memory, etc.

[0118] The processor may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device to perform desired functions. In one embodiment of this disclosure, the processor is used to execute computer-readable instructions stored in the memory.

[0119] Those skilled in the art should understand that, in order to solve the technical problem of how to obtain a good user experience, this embodiment may also include well-known structures such as communication buses and interfaces, and these well-known structures should also be included within the protection scope of this disclosure.

[0120] For a detailed description of this embodiment, please refer to the corresponding descriptions in the foregoing embodiments, which will not be repeated here.

[0121] Example 4

[0122] This disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described nodal seismic data indexing method.

[0123] A computer-readable storage medium according to embodiments of the present disclosure stores non-transitory computer-readable instructions. When these non-transitory computer-readable instructions are executed by a processor, all or part of the steps of the methods described in the foregoing embodiments of the present disclosure are performed.

[0124] The aforementioned computer-readable storage media include, but are not limited to: optical storage media (e.g., CD-ROM and DVD), magneto-optical storage media (e.g., MO), magnetic storage media (e.g., magnetic tape or portable hard drive), media with built-in rewritable non-volatile memory (e.g., memory card), and media with built-in ROM (e.g., ROM cartridge).

[0125] The various embodiments of the present invention have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments.

Claims

1. A method for indexing nodal seismic data, characterized in that, include: Based on the contents of the blasting file, obtain the starting offset of the required seismic data and generate a list of starting offsets; The earthquake data files are arranged in chronological order according to their time. For each sorted seismic data file, determine whether the seismic data file contains the required seismic data. If the seismic data file contains the required seismic data, read each data track from the seismic data file in sequence. For each data track, based on the start offset list and the current time of the data track, determine whether the data track is the starting data of the required data. If the data track is the starting data of the required data, determine the seismic data file where the ending data of the required data is located. Record the start offset, the file name and path of the seismic data file where the starting data and the ending data of the required data are located in the intermediate index file. The following steps are used to determine whether the data in question is the starting data for the required data: Determine whether the current time of the track data is equal to the time recorded in the start offset list. If the current time of the track data is equal to the time recorded in the start offset list, determine that the track data is the starting data of the required data. If the current time of the data is not equal to the time recorded in the start offset list, read the next data; The following steps are used to determine the seismic data file containing the final data of the required data: Calculate the sum of the number of traces where the trace data is located and the number of traces collected within a preset time. If the sum is less than or equal to the total number of traces contained in the seismic data file, then the start data and the end data are in the same seismic data file, and the seismic data file where the trace data is located is the seismic data file where the start data and end data of the required data are located. If the sum is greater than the total number of traces contained in the seismic data file, then the start data and the end data are in different seismic data files. The seismic data file containing the trace data is the seismic data file containing the start data. In the sorted seismic data files, the next seismic data file after the seismic data file containing the trace data is the seismic data file containing the end data.

2. The node seismic data indexing method according to claim 1, characterized in that, Generate the list of starting offsets using the following steps: Based on the content of each blasting file, multiple initial blasting times are obtained. Each initial blasting time is rounded to the second, and the rounded blasting time is used as the starting offset of the required seismic data. A starting offset list is generated based on the multiple starting offsets.

3. The node seismic data indexing method according to claim 2, characterized in that, Based on the start offset of the required seismic data and the time of the seismic data file, determine whether the required seismic data is contained in the seismic data file.

4. An electronic device, characterized in that, The electronic device includes: Memory, which stores executable instructions; A processor that executes the executable instructions in the memory to implement the node seismic data indexing method according to any one of claims 1-3.

5. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the node seismic data indexing method according to any one of claims 1-3.

6. A nodal seismic data indexing device, characterized in that, include: The start offset list generation module obtains the start offset of the required seismic data based on the contents of the blasting file and generates a start offset list. The file sorting module arranges the earthquake data files in chronological order based on their time. The seismic data file judgment module determines whether each sorted seismic data file contains the required seismic data. If the seismic data file contains the required seismic data, it reads each data track from the seismic data file in sequence. Index file recording module: For each data trace, based on the start offset list and the current time of the trace data, it determines whether the trace data is the starting data of the required data. When the trace data is the starting data of the required data, it determines the seismic data file where the ending data of the required data is located, and records the start offset, the file name and path of the seismic data file where the starting data and the ending data are located in the intermediate index file. The following steps are used to determine whether the data in question is the starting data for the required data: Determine whether the current time of the track data is equal to the time recorded in the start offset list. If the current time of the track data is equal to the time recorded in the start offset list, determine that the track data is the starting data of the required data. If the current time of the data is not equal to the time recorded in the start offset list, read the next data; The following steps are used to determine the seismic data file containing the final data of the required data: Calculate the sum of the number of traces where the trace data is located and the number of traces collected within a preset time. If the sum is less than or equal to the total number of traces contained in the seismic data file, then the start data and the end data are in the same seismic data file, and the seismic data file where the trace data is located is the seismic data file where the start data and end data of the required data are located. If the sum is greater than the total number of traces contained in the seismic data file, then the start data and the end data are in different seismic data files. The seismic data file containing the trace data is the seismic data file containing the start data. In the sorted seismic data files, the next seismic data file after the seismic data file containing the trace data is the seismic data file containing the end data.

7. The node seismic data indexing device according to claim 6, characterized in that, Generate the list of starting offsets using the following steps: Based on the content of each blasting file, multiple initial blasting times are obtained. Each initial blasting time is rounded to the second, and the rounded blasting time is used as the starting offset of the required seismic data. A starting offset list is generated based on the multiple starting offsets.

Images