Seismic data preprocessing method and device, storage medium and electronic equipment

Abstract

The invention relates to a seismic data preprocessing method and device, a storage medium and electronic equipment, and the method comprises the steps: carrying out the division based on a target operation task, obtaining a plurality of sub-tasks, distributing corresponding seismic sub-data, carrying out the parallel preprocessing, and obtaining a sub-task information list displayed by an interface; displaying the sub-task information of the target sub-task on the current interface, and obtaining the state information of the target sub-task from the displayed sub-task information; according to the state information of the target sub-task, processing the target sub-task of which the state information is abnormal, and storing a preprocessing result of the sub-task of which the state information is in a complete state to a result library set for the target job task; the current interface is refreshed, the subtask displayed by the refreshed interface is the subtask displayed by the interface before refreshing, and the position of the corresponding interface is not changed; and determining that the parallel preprocessing of the target operation task is completed, merging the preprocessing results corresponding to the sub-tasks in the result library, and generating seismic preprocessing data. The data preprocessing efficiency can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of geophysical exploration, and in particular to a seismic data preprocessing method and device, a storage medium and an electronic device. BACKGROUND

[0002] With the continuous development of geophysical exploration technology, the amount of seismic data collected is rapidly increasing, and therefore, efficient preprocessing of massive seismic data has become the focus of current research, such as denoising, filtering and abnormal processing of massive seismic data collected. In related technologies, a seismic data preprocessing system can perform large-scale data processing using parallel jobs. Specifically, by dividing a job task into multiple subtasks, a subtask queue is constructed, and the divided subtasks are respectively distributed to corresponding multiple nodes for parallel execution of seismic data, which can significantly improve the processing efficiency of seismic data. However, for each subtask of the parallel job, after being distributed to the corresponding node for processing, the processing result of the subtask is waited for by the node, and it is difficult to monitor the execution state of each subtask in real time, so that once an abnormal situation occurs in the subtask, the processing of the subtask is confirmed to be abnormal only after the corresponding node runs the subtask for more than a pre-set abnormal time threshold, and the abnormal subtask is re-placed in the subtask processing queue for re-preprocessing, resulting in low efficiency of seismic data preprocessing. SUMMARY

[0003] Therefore, the present application provides a seismic data preprocessing method, device, storage medium and electronic device.

[0004] Specifically, the present application is realized by the following technical solutions: According to a first aspect of the present application, a seismic data preprocessing method is provided, which comprises: Collecting seismic data of a target job task, dividing the target job task into multiple subtasks, assigning corresponding seismic sub-data to each subtask for parallel preprocessing, and obtaining a subtask information list corresponding to the multiple subtasks divided based on the target job task for interface display; In response to a subtask state acquisition request, the subtask information of a target subtask corresponding to the subtask state acquisition request is displayed on the current interface, and the state information of the target subtask is acquired from the displayed subtask information; According to the acquired state information of the target subtask, the target subtask with abnormal state information is processed, and the preprocessing result of the subtask with a completed state is stored in a result library set for the target job task; According to the preset refresh strategy, the current interface is refreshed, and the subtasks displayed by the refreshed interface are the subtasks displayed by the interface before the refreshing and the corresponding interface positions are unchanged, so as to monitor parallel preprocessing of the multiple subtasks divided from the target job task; After determining that the parallel preprocessing of the multiple subtasks corresponding to the target job task is completed, the preprocessing results corresponding to the subtasks in the result library are merged to generate the seismic preprocessing data.

[0005] Optionally, the subtask information of the target subtask corresponding to the subtask state acquisition request is displayed on the current interface in response to the subtask state acquisition request, and the method further includes: In response to the subtask state acquisition request, it is determined whether the subtask identifier is carried in the subtask state acquisition request; In response to the subtask identifier carried in the subtask state acquisition request, the target subtask corresponding to the subtask identifier is acquired, the subtask information of the target subtask is extracted from the real-time maintained subtask information list, and is displayed on the current interface; In response to the subtask state acquisition request without carrying the subtask identifier, the real-time maintained subtask information list is displayed on the current interface.

[0006] Optionally, the method further includes: In response to the subtask viewing request of the user, the subtask auxiliary information of the subtask corresponding to the subtask viewing request is displayed.

[0007] Optionally, the method further includes: In response to the subtask information reordering request triggered on the current interface, the subtask information displayed on the current interface is reordered.

[0008] Optionally, the subtask information displayed on the current interface is reordered in response to the subtask information reordering request triggered on the current interface, and the method further includes: In response to the subtask identifier sorting request, the subtask information sorted according to the subtask identifier is displayed on the current interface, and the subtask identifier sorting request is generated in response to the monitoring of the user clicking the subtask identifier column in the displayed subtask information list; In response to the job task name sorting request, the subtask information sorted according to the job task name is displayed on the current interface; In response to the running state sorting request, the subtask information sorted according to the running state is displayed on the current interface; In response to the running node sorting request, the subtask information sorted according to the running node is displayed on the current interface; In response to the failure number sorting request, the subtask information sorted according to the failure number of the subtask is displayed on the current interface; In response to the start time sorting request, the subtask information sorted according to the start time of the subtask is displayed on the current interface; In response to the end time sorting request, the subtask information sorted according to the end time of the subtask is displayed on the current interface; In response to the running time sorting request, the subtask information sorted according to the running time of the subtask is displayed on the current interface; In response to the running progress sorting request, the subtask information sorted according to the current running percentage of the subtask is displayed on the current interface.

[0009] Optionally, the target subtask with the abnormal processing state information comprises: In response to the state information of the subtask being the preparation state, the subtask is run, and the state information of the subtask is updated to the running state; In response to the state information of the subtask being the cancellation state, the subtask is run, and the state information of the subtask is updated to the running state; In response to the state information of the subtask being the failure state and the number of failures not exceeding a pre-set number threshold, the subtask is run, and the state information of the subtask is updated to the running state.

[0010] Optionally, the method further comprises: In response to the re-running request of the subtask with the state information being the completion state, the running result of which does not satisfy a pre-set result strategy, the subtask is run, and the state information of the subtask is updated to the running state; In response to the cancellation request of the subtask with the state information being the running state or the preparation state, the running of the subtask is interrupted, and the state information of the subtask is updated to the cancellation state.

[0011] The seismic data preprocessing method in the technical solution comprises the following steps: collecting seismic data of a target operation task, dividing the target operation task into multiple subtasks, assigning corresponding seismic sub-data to each subtask for parallel preprocessing, and obtaining a subtask information list corresponding to the multiple subtasks divided based on the target operation task and displayed on an interface; in response to a subtask state acquisition request, obtaining subtask information of a target subtask corresponding to the subtask state acquisition request from the displayed subtask information, and obtaining state information of the target subtask from the displayed subtask information; according to the obtained state information of the target subtask, processing the target subtask with abnormal state information, storing the preprocessing result of the subtask with a completed state in a result library set for the target operation task, refreshing the current interface according to a pre-set refreshing strategy, and displaying the subtask on the refreshed interface, which is the same as the subtask displayed on the interface before refreshing and has an unchanged corresponding interface position, so as to monitor the parallel preprocessing of the multiple subtasks divided based on the target operation task; determining that the parallel preprocessing of the multiple subtasks corresponding to the target operation task has been completed, merging the preprocessing results of the subtasks in the result library, and generating seismic preprocessing data. In this way, the execution state of each subtask is monitored in real time by using a visual interface, the subtask can be processed in time when an exception occurs, the efficiency of seismic data preprocessing is improved, the preprocessing result of the subtask with a completed state is stored in the result library set for the target operation task, the preprocessing results of the subtasks corresponding to the target operation task can be merged, and the integrity of seismic data processing is ensured.

[0012] According to a second aspect of the present application, a seismic data preprocessing device is provided, which comprises: a list display module configured to collect seismic data of a target operation task, divide the target operation task into multiple subtasks, assign corresponding seismic sub-data to each subtask for parallel preprocessing, and obtain a subtask information list corresponding to the multiple subtasks divided based on the target operation task and displayed on an interface; a state query module configured to, in response to a subtask state acquisition request, obtain subtask information of a target subtask corresponding to the subtask state acquisition request from the displayed subtask information, and obtain state information of the target subtask from the displayed subtask information; an exception processing module configured to, according to the obtained state information of the target subtask, process the target subtask with abnormal state information, and store the preprocessing result of the subtask with a completed state in a result library set for the target operation task; The refreshing monitoring module is configured to refresh the current interface according to a preset refreshing strategy, and the sub-tasks displayed on the refreshed interface are the sub-tasks displayed on the interface before refreshing and the corresponding interface positions are unchanged, so as to monitor the parallel preprocessing of the multiple sub-tasks divided from the target job task. The result merging module is configured to determine that the parallel preprocessing of the multiple sub-tasks corresponding to the target job task has been completed, merge the preprocessing results corresponding to the sub-tasks in the result library, and generate the seismic preprocessing data.

[0013] According to a third aspect of the present application, a storage medium is provided, which stores a computer program, and the program is executed by a processor to implement the steps of the seismic data preprocessing method in any possible implementation manner of the first aspect.

[0014] According to a fourth aspect of the present application, an electronic device is provided, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the seismic data preprocessing method in any possible implementation manner of the first aspect when executing the program. BRIEF DESCRIPTION OF DRAWINGS

[0015] The accompanying drawings, which are incorporated herein and constitute part of the specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or the related description will be briefly introduced. Obviously, for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

[0017] Figure 1 A flowchart of a seismic data preprocessing method provided by an embodiment of the present application; Figure 2 A conversion diagram of state information in a seismic data preprocessing method provided by an embodiment of the present application; Figure 3 A schematic diagram of a seismic data preprocessing device provided by an embodiment of the present application; Figure 4 A structural schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0018] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort belong to the scope of protection of the present application.

[0019] In the related art, a seismic data processing system performing parallel jobs constructs a subtask queue by dividing a job task into multiple subtasks, allocates seismic data corresponding to each subtask to a corresponding node for parallel execution, so as to improve the processing efficiency of seismic data and meet the processing demand of massive seismic data. However, for each subtask of parallel jobs, since the execution state of the subtask processed by the corresponding node is no longer monitored after being allocated to the node for processing, the node is in a state of waiting for the processing result of the subtask, and thus, once the processing of the subtask is abnormal, the abnormal processing of the subtask can be confirmed only after the corresponding node runs the subtask for more than a pre-set abnormal time threshold, and the abnormal subtask is re-placed in the subtask processing queue for re-processing, so that the processing efficiency of seismic data is low. Further, since it is parallel processing, the processing results of parallel processing need to be merged, and if the normal processing result corresponding to the abnormal subtask is missing or the abnormal processing result of the abnormal subtask is merged after the abnormality of the subtask, the entire job task processing may fail, thereby affecting the stability and efficiency of seismic data processing.

[0020] Further, for a subtask in a failed or canceled state, the seismic data processing system needs to wait for more than an abnormal time threshold to confirm the abnormal processing of the subtask and re-place the abnormal subtask in the subtask processing queue for re-processing, lacks a real-time re-sending function, and for a subtask in a running or preparing state, lacks a cancel function based on some strategy changes, so that the execution state and effect of the subtask cannot be adjusted in time, thereby reducing the running efficiency and success rate of parallel jobs. Meanwhile, after re-processing the abnormal subtask, since the processing results of all subtasks are not obtained at one time, the function of merging the processing results of all subtasks is lacked, so that it is difficult to obtain complete seismic data processing results, and further affect subsequent seismic data interpretation and other work.

[0021] The embodiment provides a seismic data processing method, which can improve the stability and efficiency of parallel processing of seismic data by dynamically visualizing management of parallel job subtasks, monitoring the execution state of the job subtasks in real time, and providing a function of changing the execution state of the subtasks.

[0022] The seismic data processing method provided by the embodiment can improve the stability and efficiency of parallel processing of seismic data by dynamically visualizing management of parallel job subtasks, monitoring the execution state of the job subtasks in real time, and providing a function of changing the execution state of the subtasks. Meanwhile, the user can query and display subtask information and monitor and manage in a personalized manner, and the operation efficiency and use experience of the user are improved. Furthermore, the node running state can be changed according to the actual running state of the subtask, and the running efficiency of parallel seismic jobs is improved.

[0023] Referring to Figure 1 The embodiment provided by the present application provides a seismic data preprocessing method, which can include the following steps: S101, collecting seismic data of a target job task, dividing the target job task to obtain a plurality of subtasks, assigning corresponding seismic subdata to each subtask for parallel preprocessing, and obtaining a subtask information list corresponding to the plurality of subtasks divided based on the target job task for interface display; In the embodiment, after collecting the seismic data of the target job task, a parallel processing mode is used to improve the seismic data preprocessing efficiency. As an optional embodiment, the plurality of subtasks are independent of each other, and after assigning corresponding seismic subdata to each subtask for parallel processing, a subtask information list of all subtasks performing parallel seismic jobs is obtained. For example, when a seismic data processing system executes a target job task, the target job task is divided into 10 subtasks, and the subtask information of the 10 subtasks constitutes a subtask information list.

[0024] As an optional embodiment in the embodiment, the subtask information list includes but is not limited to a subtask identifier (id), a job task name (subtask name), a running state, a running node, a failure number, a start time, an end time, a running duration, and a current running percentage. The running node is a node running the subtask.

[0025] S102, in response to a subtask state acquisition request, displaying subtask information of a target subtask corresponding to the subtask state acquisition request on a current interface, and acquiring state information of the target subtask from the displayed subtask information; In this embodiment, when the user needs to monitor the running state of each subtask, a subtask state acquisition request is initiated. As an optional embodiment, the subtask state acquisition request can be a request to acquire the state information of all subtasks, or a request to acquire the state information of a specific subtask, for example, by carrying the subtask identifiers of the subtasks that need to be acquired in the subtask state acquisition request, indicating that the state information of the subtask corresponding to the subtask identifier needs to be acquired, and if no subtask identifier is carried in the subtask state acquisition request, it indicates that the state information of all subtasks needs to be acquired. Thus, as an optional embodiment, in response to the subtask state acquisition request, the subtask information of the target subtask corresponding to the subtask state acquisition request is displayed on the current interface, including: A11, in response to the subtask state acquisition request, determining whether the subtask state acquisition request carries a subtask identifier; A12, in response to the subtask state acquisition request carrying a subtask identifier, acquiring the target subtask corresponding to the subtask identifier, extracting the subtask information of the target subtask from the real-time maintained subtask information list, and displaying it on the current interface; A13, in response to the subtask state acquisition request not carrying a subtask identifier, displaying the real-time maintained subtask information list on the current interface.

[0026] In this embodiment, the subtask information corresponding to the subtask state acquisition request is displayed on the current interface. As an optional embodiment, the subtask information is the column parameter value in the subtask information list, that is, the display parameter, and the display parameter includes but is not limited to: subtask identifier, job task name, running state, running node, failure times, start time, end time, running time, current running percentage. For example, for the subtask identifier, start from 001 and increment by 1.

[0027] In this embodiment, as an optional embodiment, the method further includes: In response to the user's subtask viewing request, the subtask auxiliary information of the subtask corresponding to the subtask viewing request is displayed.

[0028] In this embodiment, as an optional embodiment, when the subtask viewing request triggered by the user selecting a certain subtask is received, the subtask viewing request is responded to. For example, by triggering the direct display of subtask auxiliary information or triggering the right-click menu to display subtask auxiliary information, the real-time auxiliary display parameters of the subtask can be viewed, such as subtask log (log) information, so that the information in the running process of the subtask can be grasped in real time.

[0029] In this embodiment, as another optional embodiment, the method further includes: In response to the running node acquisition request, state information of the running node running the subtask is displayed.

[0030] In this embodiment, the state information of the running node running the subtask can be displayed according to the request of the user. As an optional embodiment, the displayed state information of the running node includes but is not limited to the running node name, the running state, the maximum number of subtasks, and the running subtask information.

[0031] S103, according to the acquired state information of the target subtask, processing the target subtask with abnormal state information, storing the preprocessing result of the subtask with completed state information to the result library set for the target job task; In this embodiment, as an optional embodiment, the user can set and view the state information of the subtask through personalization, and can intuitively understand the running information of each subtask. As an optional embodiment, the state information includes but is not limited to the preparation state, the running state, the completion state, the failure state, and the cancellation state.

[0032] In this embodiment, the state information displayed on the interface through personalization set by the user includes but is not limited to: viewing all state subtask information; viewing preparation state subtask information; viewing running state subtask information; viewing completion state subtask information; viewing failure state subtask information; viewing cancellation state subtask information.

[0033] In this embodiment, for the case of displaying the subtask information list, the number of subtasks obtained by dividing the target job task can be large, in order to quickly locate the required subtask, as an optional embodiment, the method further includes: In response to the subtask information reordering request triggered in the current interface, reordering the subtask information displayed in the current interface.

[0034] In this embodiment, the user can set and view the sorting and displaying of the subtask information through personalization, as an optional embodiment, in response to the subtask information reordering request triggered in the current interface, reordering the subtask information displayed in the current interface, including: in response to the subtask identifier sorting request, displaying the subtask information sorted according to the subtask identifier in the current interface, the subtask identifier sorting request being generated by monitoring the user clicking the subtask identifier column in the displayed subtask information list; in response to the job task name sorting request, displaying the subtask information sorted according to the job task name in the current interface; In response to the running state sorting request, the subtask information sorted according to the running state is displayed on the current interface. In response to the running node sorting request, the subtask information sorted according to the running node is displayed on the current interface. In response to the failure number sorting request, the subtask information sorted according to the failure number of the subtask is displayed on the current interface. In response to the start time sorting request, the subtask information sorted according to the start time of the subtask is displayed on the current interface. In response to the end time sorting request, the subtask information sorted according to the end time of the subtask is displayed on the current interface. In response to the running time sorting request, the subtask information sorted according to the running time of the subtask is displayed on the current interface. In response to the running progress sorting request, the subtask information sorted according to the current running percentage of the subtask is displayed on the current interface.

[0035] In this embodiment, the subtask information is sorted and viewed through the subtask identifier, the job task name, the running state, the running node, the failure number, the start time, the end time, the running time, and the current running percentage.

[0036] In this embodiment, as an optional embodiment, the abnormal state information includes but is not limited to the preparation state, the failure state, and the cancellation state. The target subtask with abnormal state information is processed, including: In response to the state information of the subtask being the preparation state, the subtask is run, and the state information of the subtask is updated to the running state. In response to the state information of the subtask being the cancellation state, the subtask is run, and the state information of the subtask is updated to the running state. In response to the state information of the subtask being the failure state and the failure number not exceeding the pre-set number threshold, the subtask is run, and the state information of the subtask is updated to the running state.

[0037] In this embodiment, as an optional embodiment, the running time threshold is set by predicting the time required for the subtask to be preprocessed, and the running time threshold is compared with the real-time updated running time. If the running time exceeds the running time threshold, the state information of the subtask is updated to the failure state, and the running of the subtask is terminated.

[0038] In this embodiment, as an optional embodiment, the method further includes: Confirming that the running result of the subtask with the completion state information does not satisfy the pre-set result strategy, and in response to the re-running request of the subtask, running the subtask and updating the state information of the subtask to the running state. In response to the cancel request of the subtask in the running state or the preparation state, the running of the subtask is interrupted, and the state information of the subtask is updated to the cancel state.

[0039] In this embodiment, the state of the subtask running on the running node is adjusted in response to the state adjustment request. As an optional embodiment, the state of the subtask can be automatically adjusted according to the state information (actual running state) of the subtask, including but not limited to: for the subtask with unsatisfactory processing result, the subtask in the completed, failed or canceled state can be resent; for the subtask running abnormally, the subtask in the running or preparation state can be canceled. As another optional embodiment, if it is confirmed that the running node is abnormal, the state of the running node can be set to the disabled (unavailable) state, and the subtask running on the running node can be migrated to a normal running node; if it is confirmed that the running node is normal, the state of the running node can be set to the running state.

[0040] In this embodiment, the subtask in the completed, failed or canceled state can be resent, and the subtask in the running or preparation state can be canceled. Thus, after being assigned to the corresponding node for preprocessing, the execution state information of the subtask is monitored by using the visual interface, so that the subtask can be timely regulated once the processing of the subtask is abnormal, and the preprocessing efficiency of the seismic data is effectively improved, and the running efficiency and success rate of the overall parallel job are improved.

[0041] Figure 2 A conversion diagram of state information in a seismic data preprocessing method provided by the embodiment of the present application is shown in FIG. 1. Figure 2 As an optional embodiment, the state information includes but is not limited to: the preparation state, the running state, the completed state, the failed state and the canceled state. In the processing process of the subtask, the subtask starts running from the preparation state and is converted to the running state. After the running of the subtask in the running state is completed, the subtask is converted to the completed state. If the subtask in the running state fails in the running, the subtask is converted to the failed state. In this embodiment, for the subtask in the preparation state, the subtask can be converted to the canceled state according to the actual situation to stop running. For the subtask in the failed state, the subtask can be restarted to run, so as to be converted to the running state. For the subtask in the running state, the subtask can be converted to the canceled state according to the actual situation to stop running. Thus, the subtask in the completed, failed or canceled state can be resent, and the subtask in the running or preparation state can be canceled, so that corresponding measures can be taken in time when the subtask is abnormal, and the overall running efficiency and stability of the parallel job are improved.

[0042] S104, refreshing the current interface according to the pre-set refresh strategy, the sub-tasks displayed by the refreshed interface being the sub-tasks displayed by the interface before refreshing and the corresponding interface positions being unchanged, so as to monitor the parallel preprocessing of the multiple sub-tasks divided from the target job task; In this embodiment, the sub-task information corresponding to each sub-task can be dynamically displayed, for example, the interface is automatically refreshed every half minute or is refreshed in response to a user refresh request, and the sub-task information is dynamically and real-timely displayed to monitor each sub-task, so as to reduce the situation of occupying resources due to abnormalities. After the interface is refreshed, the personalized settings before refreshing are retained, and the scroll bar position of the sub-task information table is kept unchanged, that is, after the interface is refreshed, the state sorting and information sorting before refreshing are retained, that is, the display interface is kept unchanged, but the content in the display interface is dynamically updated, which facilitates continuous monitoring and viewing of the sub-task information.

[0043] S105, determining that the parallel preprocessing of the multiple sub-tasks corresponding to the target job task has been completed, merging the preprocessing results of each sub-task in the result library, and generating seismic preprocessing data.

[0044] In this embodiment, the preprocessing results of each sub-task are merged to generate complete seismic preprocessing data, so that the seismic preprocessing data is data obtained by preprocessing the entire seismic data, thereby improving the accuracy of subsequent seismic data interpretation and the like. Further, the preprocessing result of the sub-task with the state information in the completed state is stored in the result library set for the target job task, so that the normal processing result corresponding to the sub-task that has occurred an abnormality can be waited for after the abnormality is eliminated, thereby the preprocessing results of each sub-task corresponding to the target job task can be merged, and the integrity of the seismic data processing is ensured.

[0045] In this embodiment, by respectively viewing the state information (preparation, running, completion, failure, cancellation) of the current different sub-tasks, and sorting and viewing the sub-task information (sub-task identifier, job task name, running state, running node, failure times, start time, end time, running duration), and dynamically displaying the sub-task information through automatic refreshing of the interface, the sub-task information of the parallel job of the seismic data preprocessing is dynamically displayed, and the purpose of visual management of the sub-tasks of the parallel job is achieved.

[0046] The seismic data preprocessing method of this embodiment can dynamically display the sub-task information of the parallel job in the seismic data preprocessing and the running node information of the sub-task preprocessing, achieve more convenient visual management of the sub-tasks of the parallel job, and improve the success rate of the parallel job execution and the preprocessing efficiency of the seismic data. The following beneficial effects are achieved: 1. Dynamic visual management of parallel job subtasks is realized, the execution state of each subtask can be monitored in real time, once an abnormal condition occurs, corresponding measures can be taken in time, the stability and efficiency of seismic data preprocessing are improved; 2. Resending of subtasks in completed, failed or canceled state, and canceling of subtasks in running or preparing state are supported, the execution of subtasks can be adjusted in time, the running efficiency and success rate of parallel job are improved; 3. The processing results of each subtask are supported to be merged, complete seismic preprocessing data can be obtained, and strong support is provided for subsequent processing and interpretation work links; 4. The automation degree of the system is improved, personalized setting and query monitoring subtask information state are realized, and the operation efficiency and use experience are improved.

[0047] 5. The state change of subtask running node is supported, the node running state can be changed according to the actual running condition of the subtask, and the running efficiency and stability of parallel job are improved.

[0048] Based on the same inventive concept, as shown in Figure 3 The embodiment of the present application also provides a seismic data preprocessing device, the device comprises: The list display module 301 is used for collecting seismic data of a target job task, dividing a plurality of subtasks based on the target job task, allocating corresponding seismic subdata to each subtask for parallel preprocessing, and obtaining a subtask information list corresponding to the plurality of subtasks divided based on the target job task for interface display. In the embodiment, the parallel processing mode is adopted, the plurality of subtasks are independent of each other, and after allocating corresponding seismic subdata to each subtask for parallel processing, a subtask information list of all subtasks performing parallel seismic job is obtained.

[0049] The state query module 302 is used for responding to a subtask state acquisition request, displaying subtask information of a target subtask corresponding to the subtask state acquisition request in the current interface, and acquiring state information of the target subtask from the displayed subtask information. In the embodiment, as an optional embodiment, the state query module 302 is specifically used for: Responding to the subtask state acquisition request, determining whether the subtask state acquisition request carries a subtask identifier; In response to the subtask state acquisition request carrying the subtask identifier, acquiring a target subtask corresponding to the subtask identifier, extracting subtask information of the target subtask from the real-time maintained subtask information list, and displaying in the current interface; In response to the subtask state acquisition request not carrying a subtask identifier, a list of real-time maintained subtask information is displayed on the current interface.

[0050] In this embodiment, as another optional embodiment, the state query module 302 is specifically further used for: In response to a subtask viewing request of a user, subtask auxiliary information of a subtask corresponding to the subtask viewing request is displayed.

[0051] In this embodiment, as still another optional embodiment, the state query module 302 is specifically further used for: In response to a subtask information reordering request triggered on the current interface, the subtask information displayed on the current interface is reordered.

[0052] In this embodiment, as an optional embodiment, in response to a subtask information reordering request triggered on the current interface, the subtask information displayed on the current interface is reordered, including: In response to a subtask identifier sorting request, subtask information sorted according to subtask identifiers is displayed on the current interface, the subtask identifier sorting request being generated in response to monitoring that a user clicks a subtask identifier column in a displayed subtask information list; In response to a job task name sorting request, subtask information sorted according to job task names is displayed on the current interface; In response to a running state sorting request, subtask information sorted according to running states is displayed on the current interface; In response to a running node sorting request, subtask information sorted according to running nodes is displayed on the current interface; In response to a failure number sorting request, subtask information sorted according to failure numbers of subtasks is displayed on the current interface; In response to a start time sorting request, subtask information sorted according to start times of subtasks is displayed on the current interface; In response to an end time sorting request, subtask information sorted according to end times of subtasks is displayed on the current interface; In response to a running duration sorting request, subtask information sorted according to running durations of subtasks is displayed on the current interface; In response to a running progress sorting request, subtask information sorted according to current running percentages of subtasks is displayed on the current interface.

[0053] The exception processing module 303 is configured to process a target subtask whose state information is abnormal according to the obtained state information of the target subtask, and store a preprocessing result of a subtask whose state information is a completed state to a result library set for the target job task. In this embodiment, as an optional embodiment, the exception processing module 303 is specifically configured to: in response to the state information of the subtask being the preparation state, running the subtask, and updating the state information of the subtask to the running state; in response to the state information of the subtask being the cancellation state, running the subtask, and updating the state information of the subtask to the running state; in response to the state information of the subtask being the failure state and the number of failures not exceeding a pre-set threshold, running the subtask, and updating the state information of the subtask to the running state.

[0054] In this embodiment, as another optional embodiment, the abnormality processing module 303 is specifically further used for: in response to the running result of the subtask with the state information being the completion state not satisfying a pre-set result policy, running the subtask in response to a re-running request of the subtask, and updating the state information of the subtask to the running state; in response to a cancellation request of the subtask with the state information being the running state or the preparation state, interrupting the running of the subtask, and updating the state information of the subtask to the cancellation state.

[0055] The refreshing monitoring module 304 is used for refreshing the current interface according to a pre-set refreshing policy, the subtask displayed on the refreshed interface being the subtask displayed on the interface before refreshing and the corresponding interface position being unchanged, so as to monitor the parallel preprocessing of the multiple subtasks obtained by dividing the target job task. In this embodiment, the subtask information corresponding to each subtask is dynamically displayed, for example, the interface is automatically refreshed every half minute or is refreshed in response to a user refreshing request, the subtask information is dynamically and real-timely displayed to monitor each subtask, and the situation of occupying resources due to an abnormality is reduced.

[0056] The result merging module 305 is used for determining that the parallel preprocessing of the multiple subtasks corresponding to the target job task has been completed, merging the preprocessing results of each subtask in the result library, and generating the seismic preprocessing data.

[0057] In this embodiment, the preprocessing results of each subtask are stored in the result library, so that the situation that the seismic preprocessing data is incomplete due to no preprocessing result for merging because of an abnormality during parallel processing can be avoided, and the merging can be performed after the preprocessing of the abnormal subtask is completed.

[0058] Based on the same inventive concept, the embodiments of the present application also provide a storage medium having a computer program stored thereon, and the program is executed by a processor to implement the steps of the seismic data preprocessing method in any possible implementation manner.

[0059] Optionally, the storage medium can be a non-transitory computer readable storage medium, for example, the non-transitory computer readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk and an optical data storage device, etc.

[0060] Based on the same inventive concept, see Figure 4 The embodiment of the present application also provides an electronic device, which comprises a memory 101 (for example, a non-volatile memory), a processor 102 and a computer program stored in the memory 101 and capable of running on the processor 102, and the processor 102 implements the steps of the seismic data preprocessing method in any possible implementation manner described above when executing the program, which is equivalent to the foregoing seismic data preprocessing device, and of course, the processor can also be used to process other data or operations. The electronic device can be a PC, a server, a terminal or the like.

[0061] As shown in Figure 4 The electronic device generally further comprises a memory 103, a network interface 104 and an internal bus 105. In addition to these components, other hardware can also be included, which will not be described herein.

[0062] It should be noted that the foregoing seismic data preprocessing device can be realized by software, and as a logically meaningful device, it is formed by reading the computer program instructions stored in the non-volatile memory into the memory 103 and running by the processor 102 of the electronic device.

[0063] Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly-embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible non-transitory program carrier to be executed by, or to control the operation of, data processing apparatus. Alternatively or additionally, the program instructions can be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.

[0064] The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit), and / or by a combination of computer hardware and software. Apparatuses can also be implemented as special purpose logic circuitry.

[0065] Suitable computers for the execution of a computer program include, by way of example, general and / or special purpose microprocessors, or any other kind of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory and / or a random access memory. The essential elements of a computer are a central processing unit for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few.

[0066] Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0067] While this specification contains many specifics, these should not be construed as limitations on the scope of any invention or of any claimed

[0068] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring such order nor that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing can be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0069] Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0070] It is noted that, in this document, the terms "first", "second", etc. are used merely as label to distinguish between different entities or operations, and do not necessarily imply a particular order or sequence among those entities or operations, nor do they necessarily imply that these entities or operations exist at different points in time. Moreover, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.

[0071] The above description is that of current embodiments of the application. Various modifications and changes can be made thereto without departing from the spirit and scope of the application as set forth. The scope of the application is not to be limited to the embodi ments disclosed in this release and that extending beyond the contents of this release is naturally presumed.

Claims

1. A method of seismic data preprocessing, characterized in that, The method comprises the following steps: Collecting seismic data of a target operation task, dividing the target operation task into a plurality of subtasks, assigning corresponding seismic subdata to each subtask for parallel preprocessing, and obtaining a subtask information list corresponding to the plurality of subtasks divided based on the target operation task for interface display; In response to a subtask state acquisition request, displaying the subtask information of the target subtask corresponding to the subtask state acquisition request on the current interface, and acquiring the state information of the target subtask from the displayed subtask information; According to the acquired state information of the target subtask, processing the target subtask with abnormal state information, and storing the preprocessing result of the subtask with a completed state in the result library set for the target operation task; According to the pre-set refresh strategy, refreshing the current interface, and displaying the subtasks on the refreshed interface, which are the same as those on the interface before refreshing and have unchanged corresponding interface positions, to monitor the parallel preprocessing of the plurality of subtasks divided from the target operation task; When it is determined that the parallel preprocessing of the plurality of subtasks corresponding to the target operation task has been completed, merging the preprocessing results of the subtasks in the result library, and generating seismic preprocessing data.

2. The seismic data pre-processing method of claim 1, wherein, The method further comprises the following steps: In response to a subtask state acquisition request, determining whether the subtask identification is carried in the subtask state acquisition request; In response to the subtask identification carried in the subtask state acquisition request, acquiring the target subtask corresponding to the subtask identification, extracting the subtask information of the target subtask from the real-time maintained subtask information list, and displaying the subtask information on the current interface; In response to the subtask state acquisition request, displaying the real-time maintained subtask information list on the current interface.

3. The seismic data pre-processing method of claim 2, wherein, The method further comprises the following steps: In response to a subtask viewing request of a user, displaying the subtask auxiliary information of the subtask corresponding to the subtask viewing request.

4. The seismic data pre-processing method of claim 2, wherein, The method further comprises the following steps: In response to a subtask information reordering request triggered on the current interface, reordering the subtask information displayed on the current interface.

5. The seismic data pre-processing method of claim 4, wherein, The method further comprises the following steps: In response to a subtask identification reordering request triggered on the current interface, reordering the subtask information displayed on the current interface. In response to a subtask identification reordering request triggered on the current interface, reordering the subtask information displayed on the current interface. In response to a subtask identification reordering request triggered on the current interface, reordering the subtask information displayed on the current interface. In response to a subtask identification reordering request triggered on the current interface, reordering the subtask information displayed on the current interface. In response to a subtask identification reordering request triggered on the current interface, reordering the subtask information displayed on the current interface. In response to a subtask identification reordering request triggered on the current interface, reordering the subtask information displayed on the current interface. In response to a subtask identification reordering request triggered on the current interface, reordering the subtask information displayed on the current interface. In response to the end time sorting request, the subtask information sorted by the end time of the subtask is displayed on the current interface; In response to the running time sorting request, the subtask information sorted by the running time of the subtask is displayed on the current interface; In response to the running progress sorting request, the subtask information sorted by the current running percentage of the subtask is displayed on the current interface.

6. The seismic data pre-processing method according to any one of claims 1 to 5, characterized in that, The target subtask with the abnormal state information includes: In response to the state information of the subtask being in the preparation state, the subtask is run, and the state information of the subtask is updated to the running state; In response to the state information of the subtask being in the cancellation state, the subtask is run, and the state information of the subtask is updated to the running state; In response to the state information of the subtask being in the failure state and the number of failures not exceeding a pre-set number threshold, the subtask is run, and the state information of the subtask is updated to the running state.

7. The seismic data pre-processing method of claim 6, wherein, The method further includes: In response to the re-running request of the subtask whose running result does not satisfy the pre-set result strategy, the subtask is run, and the state information of the subtask is updated to the running state; In response to the cancellation request of the subtask whose state information is in the running state or the preparation state, the running of the subtask is interrupted, and the state information of the subtask is updated to the cancellation state.

8. A seismic data pre-processing apparatus, characterized by, The seismic data preprocessing device includes: A list display module is configured to collect seismic data of a target job task, divide the target job task into a plurality of subtasks, assign corresponding seismic sub-data to each subtask for parallel preprocessing, and obtain a subtask information list corresponding to the plurality of subtasks divided based on the target job task for interface display; A state query module is configured to, in response to a subtask state acquisition request, display subtask information of a target subtask corresponding to the subtask state acquisition request on a current interface, and acquire state information of the target subtask from the displayed subtask information; An abnormality processing module is configured to, according to the acquired state information of the target subtask, process the target subtask with abnormal state information, and store a preprocessing result of a subtask with completed state information in a result database set for the target job task; A refresh monitoring module is configured to refresh the current interface according to a pre-set refresh strategy, and display the subtask on the refreshed interface without change in the corresponding interface position, so as to monitor parallel preprocessing of the plurality of subtasks divided from the target job task; A result merging module is configured to determine that parallel preprocessing of the plurality of subtasks corresponding to the target job task has been completed, merge the preprocessing results of the subtasks in the result database, and generate seismic preprocessing data.

9. A storage medium, characterized by A program or instruction is stored on a storage medium, and the program or instruction is run by a processor to implement the steps of the seismic data preprocessing method of any one of claims 1 to 7.

10. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor executes the program to implement the steps of the seismic data preprocessing method of any one of claims 1 to 7.

Images