Method, device, equipment and medium for controlling weather forecast process

Abstract

A weather forecast process control method, device, equipment and medium are disclosed. Whether to execute a job submission task in a job process is determined according to a start condition judgment result in a start process corresponding to a weather forecast branch service; if the job submission task in the job process is executed, whether to execute a subsequent task process is determined according to a running check result of a job running check task in the job process; wherein the subsequent task process includes an extended job process or a job execution result feedback process determined according to a service process of the weather forecast branch service; if the subsequent task process is not executed, a process execution node is controlled to backtrack to the job submission task for re-execution. Through the determination of the start process, the job process and the subsequent task process in the branch service, the stable operation of each process in the weather forecast branch service is ensured, the occurrence frequency of forecast accidents is reduced, and the efficiency of the optimization and upgrade of the service-oriented weather forecast process is improved.

Description

Technical Field

[0001] This invention relates to the field of weather forecasting technology, and in particular to a control method, apparatus, equipment and medium for a weather forecasting process. Background Technology

[0002] An operational weather forecasting system not only needs to be able to automate daily weather forecasting and operate stably while meeting timeliness requirements, and be able to cope with various sudden and abnormal situations, but also needs to be able to expand and upgrade its operations according to changing forecasting needs.

[0003] Current weather forecast products suffer from high development costs and limited computing resources. When facing business expansion and upgrades, the entire weather forecast product needs to be redeveloped. Furthermore, various abnormal situations may lead to forecast timeouts or the inability to publish forecasts, resulting in forecast accidents. Summary of the Invention

[0004] This invention provides a method, apparatus, equipment, and medium for controlling weather forecasting processes, in order to improve the scalability of operational weather forecasting processes and the stability of overall process operation.

[0005] According to one aspect of the present invention, a method for controlling a weather forecasting process is provided, comprising:

[0006] Whether to execute the job submission task in the job workflow is determined based on the start condition judgment result in the start process corresponding to the weather forecast branch service; wherein, the weather forecast branch service is determined according to the overall weather forecast process;

[0007] If a job submission task is executed in the job workflow, the execution of subsequent task workflows is determined based on the execution check results of the job execution check task in the job workflow; wherein, subsequent task workflows include extended job workflows or job execution result feedback workflows determined based on the business workflow of the weather forecast branch business.

[0008] If the subsequent task process is not executed, the control process execution node will backtrack to the job submission task for re-execution.

[0009] Optionally, the decision on whether to execute subsequent task flows can be determined based on the results of the job execution check tasks in the work process, including:

[0010] Determine the operation check result of the operation check task; wherein, the operation check result includes operation abnormality, operation normal and operation not completed or operation completed;

[0011] If the result of the operation check is an operation error, the subsequent task process will not be executed;

[0012] If the operation is running normally and has not yet ended, continue to execute the job operation check task.

[0013] If the process has ended, the subsequent task flow will be executed.

[0014] The above technical solution ensures that specific operations in each weather forecasting branch can run stably under various execution conditions by setting corresponding execution strategies based on the operation inspection results of the operation inspection tasks, thereby improving the stability of the overall weather forecasting process.

[0015] Optionally, the weather forecast branch service is a data preparation service. The startup conditions for the startup process corresponding to the data preparation service include startup time conditions and target data source access result conditions. The job submission task is a target data source download job submission task, the job execution check task is a check of the job status of the target data source download job, and the subsequent task process is a data preprocessing extended job process determined according to the business process of the data preparation service.

[0016] Accordingly, the subsequent task process includes:

[0017] The extended job submission task and extended job execution check task in the data preprocessing extended job process are executed; wherein, the second job is a data preprocessing job;

[0018] Whether to proceed with the extended job execution result feedback process is determined based on the results of the extended job execution check task.

[0019] The above technical solution enables the smooth download of data sources by setting the start conditions, job submission tasks, job execution check tasks, extended job submission tasks, and extended job execution check tasks in the data preparation business. It also determines the response strategies for various abnormal situations that may occur during the download process, ensuring the stable operation of the download process.

[0020] Optionally, the weather forecast branch service is a numerical forecast service, and the start conditions of the start process corresponding to the numerical forecast service include the execution result judgment conditions of the data preparation service corresponding to the target data source. The job submission task is to send the data preprocessing result of the target data source to the target forecast system for numerical forecasting task. The job operation check task is to determine the forecast status of the target forecast system. The subsequent task process is the job execution result feedback process.

[0021] Accordingly, the control flow execution node is traced back to the job submission task for re-execution, including:

[0022] The previous operation check result in the operation check task is determined to be the target forecast time node corresponding to the forecast that is normal.

[0023] Using the target forecast time node as the backtracking node of the process execution node, the job submission task continues to be executed.

[0024] The aforementioned technical solution enables numerical weather prediction of data sources by setting up initiation conditions, job submission tasks, job execution check tasks, and subsequent task flows in numerical weather prediction operations. It also establishes strategies for handling various anomalies that may occur during the prediction process, ensuring the stable operation of the prediction workflow. Furthermore, by controlling the backtracking nodes, it improves the efficiency of restarting numerical weather prediction tasks and reduces the runtime of numerical weather prediction operations.

[0025] Optionally, the weather forecast branch service is a data service service, and the start conditions of the start process corresponding to the data service service include the execution result judgment conditions of the numerical forecast service corresponding to the target forecast system, the job submission task is the post-processing task of the numerical forecast result of the target forecast system, the job operation check task is to determine the processing status of the post-processing, and the subsequent task process is the job execution result feedback process.

[0026] The above technical solution enables the post-processing and release of forecast data by setting the start conditions, job submission tasks, job operation check tasks and subsequent task processes in the data service business. It also determines the response strategies for various abnormal situations that may occur during the processing and release process, thus ensuring the stable operation of the forecast process.

[0027] Optionally, the method further includes:

[0028] A request to add a weather forecast branch service was received;

[0029] Based on the newly added weather forecast branch service, determine the corresponding startup conditions in the startup process, the job submission task and job operation check task in the operation process, and the subsequent task process.

[0030] Based on the startup conditions in the startup process, the job submission task and job operation check task in the job process, and the subsequent task process, a corresponding weather forecast branch process is created for the newly added weather forecast branch service.

[0031] The above technical solution expands the overall weather forecast process by adding a new weather forecast branch service. It does not restrict the specific business functions of the new weather forecast branch service, and only the corresponding startup process, operation process and subsequent process need to be determined when expanding. There is no need to re-plan the process, which improves the efficiency of expanding the weather forecast process and facilitates the optimization and upgrading of operational weather forecasts.

[0032] Optionally, after executing the job submission task in the job workflow, the method further includes:

[0033] Get the current runtime of the target process;

[0034] If the current runtime exceeds a preset target process runtime threshold, an alarm message will be issued, and / or

[0035] The warning information and corresponding warning type are determined based on the target task status and the corresponding task type; the warning type includes a first type and a second type.

[0036] If a first preset number of first-type warning messages or a second preset number of second-type warning messages are received, an alarm message is issued; wherein the first preset number is greater than the second preset number.

[0037] The above technical solution improves the monitoring of the weather forecast process by identifying alarm information, ensuring the stable operation of the overall weather forecast process, so as to ensure that the process control device can complete the operational weather forecast task in a timely and efficient manner.

[0038] According to another aspect of the present invention, a control device for a weather forecasting process is provided, comprising:

[0039] The job submission judgment module is used to determine whether to execute the job submission task in the job process based on the judgment result of the start condition in the start process corresponding to the weather forecast branch service; wherein, the weather forecast branch service is determined according to the overall weather forecast process;

[0040] The job execution check module is used to determine whether to execute subsequent task processes based on the execution check results of the job execution check task in the job process if the job submission task in the job process is executed; wherein, the subsequent task processes include extended job processes or job execution result feedback processes determined according to the business processes of the weather forecast branch business.

[0041] The job submission backtracking module is used to control the execution node of the process to backtrack to the job submission task for re-execution if the subsequent task process is not executed.

[0042] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0043] At least one processor; and

[0044] A memory communicatively connected to the at least one processor; wherein,

[0045] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the control method for the weather forecast process according to any embodiment of the present invention.

[0046] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the control method for the weather forecasting process described in any embodiment of the present invention.

[0047] This embodiment analyzes and defines the weather forecasting sub-services in the operational weather forecasting process. By defining the initiation process, operation process, and subsequent task process, it improves the efficiency of handling abnormal situations, ensures the stable operation of each process in the weather forecasting sub-services, and reduces the frequency of forecast accidents. Furthermore, it enhances the expansion of the weather forecasting sub-services and facilitates the optimization and upgrading of the operational weather forecasting process.

[0048] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

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

[0050] Figure 1 This is a flowchart of a weather forecasting process control method provided in Embodiment 1 of the present invention;

[0051] Figure 2 This is a flowchart of a weather forecasting process control method provided by an embodiment of the present invention;

[0052] Figure 3 This is a flowchart of a weather forecasting process control method provided in Embodiment 2 of the present invention;

[0053] Figure 4 This is a flowchart of a weather forecasting process control method provided in Embodiment 3 of the present invention;

[0054] Figure 5 This is a flowchart of a weather forecasting process control method provided in Embodiment 4 of the present invention;

[0055] Figure 6 This is a flowchart of a weather forecasting process control method provided in Embodiment 5 of the present invention;

[0056] Figure 7 This is a schematic diagram of the structure of a weather forecasting process control device provided in Embodiment Six of the present invention;

[0057] Figure 8 This is a schematic diagram of the structure of an electronic device that implements the control method for the weather forecast process in Embodiment 7 of the present invention. Detailed Implementation

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

[0059] It should be noted that the terms "candidate," "target," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0060] Example 1

[0061] Figure 1 This invention provides a flowchart of a weather forecast process control method according to Embodiment 1. This embodiment is applicable to controlling the process of operational weather forecasting. The method can be executed by a weather forecast process control device, which can be implemented in hardware and / or software. This control device can be configured in an electronic device with data processing capabilities, such as a server. Figure 1 As shown, the method includes:

[0062] S110. Determine whether to execute the job submission task in the job process based on the start-up condition judgment result in the start-up process corresponding to the weather forecast branch business; wherein, the weather forecast branch business is determined according to the overall weather forecast process.

[0063] The overall weather forecast process refers to the complete forecasting workflow of operational weather forecasting. This complete workflow can be modified and updated according to actual forecasting needs. Weather forecasting sub-services refer to branch services extracted from the overall weather forecast process based on their functionalities. The corresponding processes for these sub-services are part of the overall weather forecast process. For example, if the overall weather forecast process involves first downloading the raw data source, then performing numerical forecasts based on the downloaded data, and finally providing corresponding data services based on the forecasted values, then the weather forecasting sub-service could be the data source download service (data preparation), the numerical forecast service, or the data service service. It could also be a further subdivision of the process. For instance, when downloading data sources, including downloading from different sources, the weather forecasting sub-service could be the data source A download service or the data source B download service, etc. Similarly, when performing numerical forecasts, different forecasting systems can be used, so the weather forecasting sub-service could be the system A numerical forecast service or the system B data forecast service, etc. Alternatively, when providing numerical services, the services can be tailored to the different characteristics of each region. In this case, the weather forecast branch service could be a numerical service service for region A or a numerical service service for region B, etc.

[0064] The startup process is used to determine the startup timing of the workflow corresponding to the weather forecast branch service. This process includes a startup condition judgment process; by determining the result of this judgment, the startup timing of the corresponding work workflow for that weather forecast branch service is determined. The work workflow is used to perform specific tasks within that weather forecast branch service. For example, in the data source download service, the corresponding work workflow is to download the data source. In this embodiment of the invention, the control of the weather forecast process only controls the overall weather forecast process. Specific job execution is scheduled by the scheduling system to the background for execution by the corresponding execution system. The job submission task is used to submit specific jobs within the work workflow to the scheduling system, which then schedules them to the corresponding execution system for execution. The scheduling system distinguishes between the weather forecast process and the job execution system, facilitating the management of the weather forecast process and the modification and updating of the job execution system, thereby improving the control efficiency of the weather forecast process.

[0065] Specifically, the process begins by initiating the startup process for each weather forecast branch. The startup condition judgment result is then determined. If the startup condition judgment result meets the preset result for the corresponding weather forecast branch, the corresponding work process for that weather forecast branch continues execution, i.e., the job submission task is executed through the job submission backend. If the startup condition judgment result does not meet the preset result, the startup process continues until the preset result is met, or the execution of the corresponding process for that weather forecast branch is exited, and execution continues after a preset time interval.

[0066] For example, in the data source download service, the startup time judgment result in the startup process is determined to see if the preset startup time has been reached. If it has, the data source download job submission task in the job process is executed. If it has not been reached, the process execution is exited, and the startup time judgment result in the startup process is determined again after a preset time interval.

[0067] By controlling the startup process, the startup timing of each weather forecasting branch can be precisely controlled, ensuring the stable execution of the overall weather forecasting process.

[0068] S120. If the job submission task in the job workflow is executed, the execution of subsequent task workflows shall be determined based on the execution check results of the job execution check task in the job workflow. The subsequent task workflows include extended job workflows or job execution result feedback workflows determined based on the business workflows of the weather forecast branch business.

[0069] The job execution check task is a task that checks the execution status of the job submission task in the job workflow. For example, it determines the background download status of the data source, including checking whether the download is normal and whether the download is complete.

[0070] Specifically, after submitting the job in the workflow, a job execution check is performed, and the results are determined. These results include checks on whether the job is running normally and whether it has finished, used to assess the job's execution status, promptly identify any anomalies in the background job, and improve the control efficiency of the weather forecast workflow. Based on the execution check results, it is determined whether to execute subsequent task flows. These subsequent task flows are determined according to the specific business of this weather forecast branch. For example, in the data source download business, the business is not finished after the data source download is complete; the downloaded data still needs preprocessing, so the extended workflow becomes a data preprocessing workflow. In the numerical forecast business, the entire business is completed after numerical forecasting based on the data is finished, so the subsequent task flow is a job execution result feedback workflow, i.e., feeding back the numerical forecast results.

[0071] By checking the results of the operation of the task, the execution of subsequent tasks can be controlled, thereby improving the control efficiency of the weather forecast process. It also facilitates the understanding of the process execution, timely detection of fault nodes in the process, and ensures the stable execution of the process.

[0072] In one feasible embodiment, determining whether to execute subsequent task flows based on the execution check results of the task execution check in the job flow includes:

[0073] Determine the operation inspection results of the task; the operation inspection results include operation abnormality, operation normal and operation not completed or operation completed;

[0074] If the runtime check result is abnormal, the subsequent task process will not be executed;

[0075] If the operation is running normally and has not yet ended, continue to perform the job operation check task;

[0076] If the process has ended, the subsequent task flow will be executed.

[0077] The job execution check tasks include checking whether the job is running normally and checking whether the job has finished. The execution check results include execution abnormality, execution normality and not finished, or execution finished. Execution abnormality means that there was an error in the job submission task in the job process, that is, the job submitted to the background for execution encountered an error during execution; execution normality and not finished means that the job submission task in the job process is executing normally in the background, but has not yet finished; execution finished means that the job submission task in the job process has been successfully completed in the background.

[0078] Specifically, if the operation check result of the operation check task is abnormal, it means that there is an error in the operation submission, and the previously submitted operation needs to be re-executed to ensure the smooth execution of the forecast process; if the operation is normal and the operation has not ended, continue to wait until it is completed and then execute the subsequent task process, and continue to execute the operation check task during the waiting process; if the operation has ended, then execute the subsequent task process to ensure the stable execution of the weather forecast process.

[0079] In this embodiment, by setting corresponding execution strategies for the operation inspection results of the operation inspection task, it is ensured that the specific operations in each weather forecast branch can run stably under various execution conditions, thereby improving the stability of the overall weather forecast process.

[0080] S130. If the subsequent task process is not executed, the control process execution node will be traced back to the job submission task for re-execution.

[0081] If the job execution check result is abnormal, it indicates that the job submission was abnormal and the previously submitted job needs to be re-executed. This means the job in the workflow needs to be resubmitted to the background for execution. This ensures stable operation even in the event of workflow abnormalities, preventing subsequent forecasting processes from failing due to background job execution system malfunctions, and enabling the weather forecasting process to handle abnormal situations that occur during job execution.

[0082] In one feasible embodiment, the method further includes:

[0083] A request to add a weather forecast branch service was received;

[0084] Based on the newly added weather forecast branch business, determine the corresponding startup conditions in the startup process, the job submission task and job operation check task in the operation process, as well as the subsequent task process;

[0085] Based on the startup conditions in the startup process, the job submission tasks and job operation check tasks in the job process, and the subsequent task processes, create a corresponding weather forecast branch process for the newly added weather forecast branch business.

[0086] Among them, the newly added weather forecast branch service can be a service added after receiving new forecast requests after the weather forecast process has been running stably. The newly added weather forecast branch service can be an extension of the existing branch service, or a branch service that performs different business from the current existing branch service. For example, the newly added weather forecast branch service can be a new data source download service, or a new forecast system numerical forecast service, or a new regional data service service, or a new data post-processing service. The data post-processing service can be a subsequent extension of the data service service. The specific business information can be extended according to the actual situation and is not restricted here. Similarly, the newly added weather forecast branch service can be located at any position in the overall weather forecast process.

[0087] Specifically, based on the specific business requirements of the newly added weather forecast branch service, determine its corresponding start conditions, job submission tasks, job operation check tasks, and subsequent task processes, and create the corresponding weather forecast branch service according to the determined process tasks.

[0088] In this embodiment, the addition of a new weather forecast branch service expands the overall weather forecast process. There are no restrictions on the specific business functions of the new weather forecast branch service. When expanding, only the corresponding startup process, operation process and subsequent process need to be determined. There is no need to re-plan the process, which improves the efficiency of expanding the weather forecast process and facilitates the optimization and upgrading of operational weather forecasts.

[0089] After the job submission task is executed in the job workflow, the method also includes:

[0090] Get the current runtime of the target process;

[0091] If the current runtime exceeds the preset target process runtime threshold, an alarm message will be issued, and / or

[0092] The warning information and corresponding warning type are determined based on the target task status and the corresponding task type; the warning type includes a first type and a second type.

[0093] If a first preset number of first-type warning messages or a second preset number of second-type warning messages are received, an alarm message is issued; wherein the first preset number is greater than the second preset number.

[0094] Alarm and warning information are used to alert users to abnormal situations during the weather forecasting process. Alarm information has higher priority than warning information; for example, alarm information indicates an error in a task that is critical to the process. Warning type is used to characterize the importance of the abnormal task corresponding to the warning information. Tasks corresponding to the first type of warning information are more important in the weather forecasting process than tasks corresponding to the second type of warning information.

[0095] The overall operation of operational weather forecasting also includes an alarm process. Specifically, this includes two types of alarm information. One type is an alarm monitoring the runtime of each process. The theoretical maximum runtime of each process is preset as the runtime threshold for that process, and the current runtime of each process is determined. If the current runtime of a target process exceeds the corresponding target process runtime threshold, it is determined that the process may have encountered an abnormal situation that has caused it to not finish for a long time, and an alarm message is issued to remind the operation and maintenance personnel to check the operation of the process.

[0096] Another type of alarm is for abnormal task execution within the process. Specifically, each task in the process has a corresponding abnormal situation execution strategy. For example, if the job execution check task results in an abnormality, it indicates an error in the job submission, requiring re-execution. Simultaneously, an alarm message needs to be issued for this abnormality. The type of alarm message is pre-determined based on the task type. For instance, the alarm type is determined by the task's impact on the overall weather forecast process; tasks with low impact receive a general alarm, while tasks with high impact receive a critical alarm. Upon receiving a first preset number of general alarm messages or a second preset number of critical alarm messages, an alarm message is issued to remind maintenance personnel to check, preventing excessive re-executions from affecting the stability of the overall weather forecast process. Furthermore, the alarm message type allows for rapid problem localization, improving maintenance efficiency.

[0097] In this embodiment, by determining the alarm information, the monitoring of the weather forecast process is improved, ensuring the stable operation of the overall weather forecast process, so as to ensure that the process control device can complete the operational weather forecast task in a timely and efficient manner.

[0098] like Figure 2 A flowchart of a weather forecasting process control method provided in an embodiment of the present invention is shown below. Figure 2 As shown, the method includes: a main program Framework flow corresponding to the weather forecast branch service, and a corresponding branch process Stage flow. The main program performs system settings and checks, and determines the current execution flow within the branch process. After obtaining the current execution flow, it enters the target flow within the branch process based on conditional judgment. For example, each weather forecast branch service in the overall weather forecast process can share a single main flow or have its own dedicated main flow; this is not a limitation.

[0099] The main program first performs parameter settings, including creating the software runtime environment and setting environment parameters, such as data reading dependencies. Then, it executes system checks, including checking if the file system can read files normally, if the task scheduling system's resource requests are submitted correctly, and other system environment checks. After the parameter settings and system checks are completed, the `Get_stage` function retrieves the current execution flow, and then the `case` instruction determines which branch to enter. The branch flow is divided into a startup flow, a job flow, and a subsequent job flow. The startup flow is stage 0, the job flow is stage 1, the job submission task in the job flow corresponds to stage 1, and the job execution check task is stage 1. Stage 1 checks include whether the execution is normal and whether it has finished. The subsequent job flow is stage 2. If the subsequent job flow is an extended job flow, the job submission task in the extended job flow corresponds to stage 2, and the job execution check task is stage 2.

[0100] The number of extended job processes is developed and set according to the specific forecast task. For example, one extended job process is listed for detailed explanation. When starting a weather forecast branch service forecast task, the execution process defaults to stage0. The process branch of stage0 is entered to execute the startup process, mainly checking the startup conditions. If the startup conditions are not met, the main program exits directly, and after a period of hibernation, it restarts. If the startup conditions are met, the current execution process is updated to stage1, and the process branch of stage1 is entered. When the execution process enters stage1, the stage1 task is executed via job submission and background execution. Once the job is submitted, the stage1 task is completed, and the main program can exit directly. When the main program restarts after a period of hibernation, the Get_stage function retrieves the current execution process as stage1, enters stage1 to check the task, and performs checks to ensure the task runs correctly and has completed. If an execution error is detected, the process will re-enter stage 1 to run the task. If the job execution is normal, it will continue to check if execution has finished. If the job submission task in stage 1 is still running in the background (i.e., the job execution has not finished), the main program will exit directly. If the job submission task in stage 1 has finished, the process will be updated to stage 2, and then the process branch of stage 2 will be entered. When the execution process enters stage 2, the stage 2 running task will be executed, also submitted to run in the background, and then the main program will exit. The job execution check task in stage 2 is similar to that in stage 1. After the main program completes all stage process tasks, the job execution result feedback process will be executed last.

[0101] Figure 2 This paper provides an optimization method for controlling weather forecasting sub-services within the operational weather forecasting process. Different weather forecasting sub-services are configured according to their specific operational needs. Figure 2 The specific task information in stage0, stage1 and stage2 is set to meet the expansion of weather forecast branch services. At the same time, the specific task execution branches can be adjusted according to the actual situation, which is not restricted here.

[0102] The design of the main process framework and each process branch ensures the stable execution of operational weather forecasting tasks. Furthermore, this control method can automatically handle general anomalies, respond automatically, and repair them in a timely manner, further improving the stability of the weather forecasting process.

[0103] This embodiment analyzes and defines the weather forecasting sub-services in the operational weather forecasting process. By defining the initiation process, operation process, and subsequent task process, it improves the efficiency of handling abnormal situations, ensures the stable operation of each process in the weather forecasting sub-services, and reduces the frequency of forecast accidents. Furthermore, it enhances the expansion of the weather forecasting sub-services and facilitates the optimization and upgrading of the operational weather forecasting process.

[0104] Example 2

[0105] Figure 3 This is a flowchart of a weather forecast process control method provided in Embodiment 2 of the present invention. This embodiment further details the weather forecast branch service in the above embodiments and determines the specific tasks corresponding to this branch service. The weather forecast branch service is a data preparation service. The startup conditions for the data preparation service include startup time conditions and target data source access result conditions. The job submission task is a target data source download job submission task, and the job execution check task is to check the job status of the target data source download job. The subsequent task process is a data preprocessing extended job process determined according to the data preparation service's business process. Executing the subsequent task process includes: executing the extended job submission task and the extended job execution check task in the data preprocessing extended job process; wherein, the second job is a data preprocessing job; and determining whether to perform the extended job execution result feedback process based on the execution check result of the extended job execution check task.

[0106] The data preparation service involves downloading the raw data sources required for weather forecasting and performing corresponding preprocessing work.

[0107] like Figure 3 As shown, the method includes:

[0108] S310, Determining startup time conditions.

[0109] The start time condition judgment task is part of the start process in the data preparation business. The data preparation business is the first process module executed in the overall weather forecast process. The start time is used as the start condition for the overall weather forecast process. If the start time judgment is not met, the process execution will be terminated, that is, the main program will be terminated, and the start time condition judgment task will be re-executed after a period of dormancy.

[0110] S320, Data access judgment.

[0111] Since the data preparation process involves downloading data sources, if the startup time condition is met, the data access check is initiated, determining whether the corresponding data source resource can be accessed normally. If data access fails, step S330 is executed; if data access succeeds, step S350 is executed.

[0112] S330, Data access timeout judgment.

[0113] If data access fails, check if the data access time exceeds the access time threshold. If it does, execute S340 to determine the data status of the data source as failed, i.e., display False. If the time threshold is not exceeded, repeat the data access judgment task.

[0114] S340, The data status is determined to be a failure.

[0115] If data access fails and times out, the data status is determined to be failed. This ensures that subsequent weather forecasting services can promptly process the data based on its status.

[0116] S350, data download.

[0117] Once data access is successful, execute the data download task. This involves submitting the data source download task to the backend.

[0118] S360, data download check.

[0119] After submitting the data source download task to the backend, a data download check is performed, including checking whether the data source download is normal and whether the data source download has finished. If the data download is abnormal, the data download task is re-executed; if the data download is normal but not finished, the data download check task continues; if the data download is normal and finished, the extended task process is entered to perform data preprocessing.

[0120] S370, Data Preprocessing.

[0121] Since the data obtained by downloading from the data source is raw data, it needs to be preprocessed during numerical weather prediction. This preprocessing includes checking for missing or abnormal data. Data preprocessing is a task submission task within the extended workflow of data preparation.

[0122] S380, Perform normal judgment.

[0123] Specifically, the startup conditions for the startup process include the judgment conditions in S310, S320, and S330, which are related to the data access timeout judgment conditions. The job submission task corresponds to the data download task in S350. The job execution check task corresponds to the data download check in S360. The extended job submission task in the subsequent task process corresponds to the data preprocessing task in S370. The extended job execution check task corresponds to the execution normal judgment in S380.

[0124] After a data preprocessing task is submitted, a preprocessing job check task is initiated to determine the preprocessing execution status, including whether the preprocessing execution is abnormal, whether it is running normally but not yet completed, or whether it is running normally and completed. If an execution abnormality occurs, the data preprocessing flow is re-entered; if the execution is running normally but not yet completed, the execution status is further determined; if the execution is running normally and completed, a data status of success is returned, displaying True.

[0125] S390, Determine the data status.

[0126] If data preprocessing is successful and completes, the data status is determined to be successful. This allows subsequent weather forecasting operations to promptly process the data based on its status from this data source.

[0127] Specifically, the data preparation service includes at least two data sources. Each data source is configured with a corresponding data preparation service so that the execution processes of each data source can be executed simultaneously without affecting each other. Once the data download and preprocessing tasks are completed, the data status of each data source will be returned. The data status will control the start of subsequent numerical weather prediction service processes.

[0128] This embodiment achieves smooth downloading of data sources by setting the start conditions, job submission tasks, job execution check tasks, extended job submission tasks, and extended job execution check tasks in the data preparation business, and determines the response strategies for various abnormal situations that may occur during the download process, thus ensuring the stable operation of the download process.

[0129] Example 3

[0130] Figure 4This is a flowchart of a weather forecasting process control method provided in Embodiment 3 of the present invention. This embodiment further details the weather forecasting branch service in the above embodiments and determines the specific tasks corresponding to the branch service. The weather forecasting branch service is a numerical weather prediction service. The start-up conditions of the numerical weather prediction service include the execution result judgment conditions of the data preparation service corresponding to the target data source. The job submission task is to send the data preprocessing results of the target data source to the target forecasting system for numerical weather prediction. The job operation check task is to determine the forecast status of the target forecasting system. The subsequent task flow is the job execution result feedback flow.

[0131] Among them, numerical weather prediction services are used to perform numerical calculations of future weather based on downloaded data source information.

[0132] like Figure 4 As shown, the method includes:

[0133] S410, Determining the end of the data preparation process.

[0134] Numerical weather forecasting services need to be executed after the corresponding data preparation service is completed. Therefore, the conditions for starting a numerical weather forecasting service include determining whether the data preparation process for the data source required by the numerical weather forecasting service has been completed.

[0135] Specifically, whether the data preparation process is completed is used as the start condition in the numerical weather prediction service startup process. If the data preparation process is not completed, the main program exits and re-executes the judgment after a period of hibernation.

[0136] S420, Data status determination.

[0137] After the data preparation process is completed, the data status of the data source required for the numerical weather prediction service is determined to establish the corresponding forecasting strategy. If the data status of any set of data in the required data source is False, then S430 is executed; if the data status of all data is False, then the numerical weather prediction service is terminated, and the forecast results of other numerical weather prediction services are used as the forecast results of this numerical weather prediction service to ensure the integrity of the numerical weather prediction results.

[0138] S430, Activate the backup forecasting plan.

[0139] If any data set in the data source required for this numerical weather prediction service has a data status of False, then the remaining data with a status of True will be used to make the forecast according to the backup forecasting scheme.

[0140] S440, Numerical Prediction Mission in Progress.

[0141] If the data preparation process is complete and all required data are in the True state, then the numerical forecast task corresponding to this numerical forecast service will be initiated. This means the numerical forecast task will be submitted to the backend, and the corresponding forecast system will perform the numerical forecast based on the required data.

[0142] S450, Judgment of forecast mission operation check.

[0143] After a numerical weather prediction mission is submitted, it enters a mission execution check process, which includes checking whether the mission is running normally and whether it has finished. If the mission completes normally, S470 is executed, returning the prediction status to True. If the mission malfunctions, S460 is executed to determine the number of mission failures; if the mission runs normally and has not yet finished, the execution check continues; if the mission runs normally and has finished, S470 is executed.

[0144] S460, Determining the number of task failures.

[0145] If the forecast mission fails more than a preset threshold, execute S480 and return the forecast status as False; if the forecast mission fails less than the preset threshold, restart the numerical forecast mission. If the forecast mission can complete normally within two restarts, execute S470 and return the forecast status as True.

[0146] In one feasible embodiment, the control flow execution node is traced back to the job submission task for re-execution, including: determining that the previous run check result in the job run check task is the target forecast time node corresponding to the forecast being normal; and continuing the execution of the job submission task with the target forecast time node as the traceback node of the flow execution node.

[0147] Specifically, when restarting a numerical weather prediction task, it does not restart from the forecast start time. Instead, it restarts using a breakpoint resumption method, beginning from the forecast time node corresponding to the last time the run check result indicated a normal forecast. For example, if the numerical weather prediction task includes forecasting daily weather data from the 1st to the 30th, and the current run check result indicates an abnormal run, then the forecast time node corresponding to the last run check is determined to be the 7th. Therefore, the 7th is determined as the target forecast time node, and the numerical weather prediction restart task begins on the 8th, using the 7th as the backtracking node.

[0148] This embodiment improves the efficiency of restarting numerical weather prediction tasks and reduces the running time of numerical weather prediction services by controlling the backtracking nodes.

[0149] S470, Forecast status confirmed as successful.

[0150] If a numerical weather prediction task runs normally and ends within a preset threshold number of failures, the prediction status is determined to be successful.

[0151] S480, Forecast status confirmed as failed.

[0152] If a numerical weather prediction task continues to malfunction after the number of failures exceeds a preset threshold, the prediction status is determined to be failed.

[0153] Specifically, the startup conditions for the startup process include the judgment conditions in S410 and S420; the job submission task corresponds to the data download task in S440; the job operation check task corresponds to the forecast task operation check in S450 and the judgment of the number of task failures in S460; the subsequent task process is the job execution result feedback process, which corresponds to the forecast status determination in S470 and S480.

[0154] This embodiment achieves numerical forecasting of data sources by setting the initiation conditions, job submission tasks, job operation check tasks, and subsequent task processes in numerical weather prediction services. It also determines the response strategies for various abnormal situations that may occur during the forecasting process, ensuring the stable operation of the forecasting process.

[0155] Example 4

[0156] Figure 5 This is a flowchart of a weather forecasting process control method provided in Embodiment 4 of the present invention. This embodiment further details the weather forecasting branch service in the above embodiments and determines the specific tasks corresponding to the branch service. The weather forecasting branch service is a data service service. The start-up conditions of the start-up process corresponding to the data service service include the execution result judgment conditions of the numerical forecasting service corresponding to the target forecasting system, the job submission task is the post-processing task of the numerical forecasting results of the target forecasting system, the job operation check task is to determine the processing status of the post-processing, and the subsequent task process is the job execution result feedback process.

[0157] Among them, the data service business is used to publish the calculated weather forecast values ​​for users to view.

[0158] like Figure 5 As shown, the method includes:

[0159] S510, Judgment of forecast status.

[0160] Data service operations refer to the business process of publishing forecasted data. Therefore, the initiation conditions for data service operations require the forecast status of the required forecast data. This means determining the execution result of the numerical forecast operation corresponding to the target forecast system. If the forecast status is False, it indicates an anomaly in the numerical forecast, and S520 is executed; if the forecast status is True, S530 is executed.

[0161] S520, Determine backup forecast data.

[0162] Among them, the backup forecast data is the reference forecast data that can be determined in advance based on historical data. The determination of the backup forecast data improves the stability of the forecast process and avoids the interruption or error of the process due to abnormal situations.

[0163] S530, Judgment of forecast time nodes.

[0164] In this embodiment of the invention, the data service is performed by post-processing data according to time nodes. For example, the post-processing execution strategy adopts daily execution, that is, the post-processing process is executed once after each day's forecast is completed. When it is determined that a day's forecast is completed, S540 is executed to enter the forecast data processing process; otherwise, the main program exits and re-enters the judgment of the current forecast time node.

[0165] S540, Forecast Data Processing Task.

[0166] Forecast data processing refers to the post-processing of forecast data calculated by numerical weather prediction systems to enable the dissemination of weather forecasts. Post-processing may include accuracy assessment and data processing, such as determining the display effect on the release page based on forecast data.

[0167] S550, judgment of normal data processing.

[0168] After the forecast data processing task is submitted, it enters the inspection task, which includes checking whether the data processing is normal. The judgment of normal data processing refers to the judgment of whether the forecast data processing task is normal. Since the forecast data processing task is scheduled and executed by the background scheduling system, the result of whether the task is processed normally is obtained. If the data processing is abnormal, the forecast data processing task is re-executed; if the data processing is normal, S560 is executed.

[0169] S560, Determination of data processing completion.

[0170] The determination of data processing completion refers to whether the cumulative processing time of the forecast data processing task meets the preset target time node. If it does not meet the target time node, the forecast data processing for subsequent time nodes continues. If it does meet the target time node, S570 is executed to release the forecast data. For example, based on the above example, since the post-processing execution strategy adopts daily execution, that is, the post-processing process is executed once after each day of forecast is completed, and the target time node is 30 days, the data processing is completed after 30 days of forecast data post-processing.

[0171] S570, forecast data released.

[0172] Specifically, the startup conditions for the startup process include the judgment conditions in S510; the job submission task corresponds to the judgment of the forecast time node in S530 and the forecast data processing task in S540; the job operation check task corresponds to the judgment of normal data processing in S550 and the judgment of data processing completion in S560; the subsequent task process is the job execution result feedback process, which corresponds to the forecast data release in S570.

[0173] This embodiment achieves post-processing and publishing of forecast data by setting the start conditions, job submission tasks, job operation check tasks and subsequent task processes in the data service business, and determines the response strategies for various abnormal situations that may occur during processing and publishing, thus ensuring the stable operation of the forecast process.

[0174] Example 5

[0175] Figure 6 This is a schematic diagram of the structure of a weather forecasting process control system provided in Embodiment 5 of the present invention. Figure 6 As shown, the system includes:

[0176] The weather forecasting system includes a data preparation module, a numerical forecasting module, and a data service module. The process control method for the data preparation module is described in Example 2, the process control method for the numerical forecasting module is described in Example 3, and the process control method for the data service module is described in Example 4. These will not be elaborated upon here.

[0177] The data preparation module of the weather forecasting system in this embodiment includes download and data preprocessing processes for at least two data sources, such as data source 1, data source 2, data source 3, and data source 4. The numerical forecasting module includes numerical forecasting processes for at least two forecasting systems, such as M1 forecast, M2 forecast, N1 forecast, and N2 forecast. M1 and M2 (or N1 and N2) represent different areas covered by the weather forecasts and have different spatial resolutions. The M forecast represents a forward forecasting system using assimilation techniques, and the N forecast represents a backward forecasting system using a better initial field. The data service model includes data post-processing processes for at least two services, such as website services, site services, and regional services. The process control of each module supports functional scalability, facilitating the collaborative execution of multiple forecasting tasks. The data preparation module supports parallel processing of multiple data sources, the numerical forecasting module supports the simultaneous operation of multiple sub-forecasting systems, and the data service module allows for simultaneous execution of various data service functions and supports different data product services from multiple sites and regions.

[0178] For example, the data download module includes data download business processes corresponding to four data sources, which are executed simultaneously, and the data status of each data source is fed back according to the execution status. The numerical weather prediction module starts after the data preparation module process is completed. The data sources used by the pre-prediction systems M1 and M2 and the post-prediction systems N1 and N2 are different. Specifically, the M1 and M2 forecasts require data 1, data 2, and data 3 as input data, while the N1 and N2 forecasts require data 3 and data 4 as input data. That is, the data sources required by the M1 and M2 forecasts are the same, but different data processing methods are executed in the data preprocessing process to generate the corresponding input data required by M1 and M2. Therefore, the data preprocessing process in the data download business can be extended accordingly. The data sources of N1 and N2 are the same, and the process is similar to that of M1 and M2. Each forecast subsystem executes the process corresponding to the numerical weather prediction business as described in Example 3, and each forecast subsystem is relatively independent. The data service module begins after the data forecast module process is completed. The website service part needs to execute four sets of post-processing processes for forecast data. The site service and regional service specify the processes and forecast data according to the actual business needs.

[0179] This embodiment provides a weather forecast process control system that enables stable and efficient operation of operational weather forecasts, as well as automatic execution of forecast tasks, automatic response to abnormal situations, and can meet different operational forecasting needs, while improving the efficiency of business expansion.

[0180] Example 6

[0181] Figure 7 This is a schematic diagram of the control device for a weather forecasting process provided in Embodiment Six of the present invention. Figure 7 As shown, the device includes:

[0182] The job submission judgment module 710 is used to determine whether to execute the job submission task in the job process based on the judgment result of the start condition in the start process corresponding to the weather forecast branch business; wherein, the weather forecast branch business is determined according to the overall weather forecast process;

[0183] The job execution check module 720 is used to determine whether to execute subsequent task processes based on the execution check results of the job execution check task in the job process if the job submission task in the job process is executed; wherein, the subsequent task processes include extended job processes or job execution result feedback processes determined according to the business processes of the weather forecast branch business.

[0184] The job submission backtracking module 730 is used to control the execution node of the process to backtrack to the job submission task for re-execution if the subsequent task process is not executed.

[0185] Optionally, the job execution check module includes:

[0186] Subsequent task flow includes:

[0187] Determine the operation inspection results of the task; the operation inspection results include operation abnormality, operation normal and operation not completed or operation completed;

[0188] If the runtime check result is abnormal, the subsequent task process will not be executed;

[0189] If the operation is running normally and has not yet ended, continue to perform the job operation check task;

[0190] If the process has ended, the subsequent task flow will be executed.

[0191] Optionally, the weather forecast branch is a data preparation business. The startup conditions for the data preparation business include startup time conditions and target data source access result conditions. The job submission task is the target data source download job submission task, the job execution check task is the job status check of the target data source download job, and the subsequent task flow is the data preprocessing extended job flow determined according to the data preparation business flow.

[0192] Accordingly, the device also includes a subsequent task flow execution module, used for:

[0193] The extended job submission task and extended job execution check task are executed in the data preprocessing extended job workflow; the second job is the data preprocessing job.

[0194] Whether to proceed with the extended job execution result feedback process is determined based on the results of the extended job execution check task.

[0195] Optionally, the weather forecast branch service is a numerical forecast service. The start conditions for the start process of the numerical forecast service include the execution result judgment conditions of the data preparation service corresponding to the target data source. The job submission task is to send the data preprocessing results of the target data source to the target forecast system for numerical forecasting tasks. The job operation check task is to determine the forecast status of the target forecast system. The subsequent task process is the job execution result feedback process.

[0196] Correspondingly, the job submission backtracking module includes:

[0197] Determine the target forecast time node corresponding to the previous operation and inspection result in the operation and inspection task when the forecast is normal;

[0198] The task submission continues to be executed by using the target forecast time node as the backtracking node of the process execution node.

[0199] Optionally, the weather forecast branch service is a data service service. The start-up conditions for the data service service include the execution result judgment conditions of the numerical forecast service corresponding to the target forecast system, the job submission task is the post-processing task of the numerical forecast results of the target forecast system, the job operation check task is to determine the processing status of the post-processing, and the subsequent task process is the job execution result feedback process.

[0200] Optionally, the device also includes a process addition module for:

[0201] A request to add a weather forecast branch service was received;

[0202] Based on the newly added weather forecast branch business, determine the corresponding startup conditions in the startup process, the job submission task and job operation check task in the operation process, as well as the subsequent task process;

[0203] Based on the startup conditions in the startup process, the job submission tasks and job operation check tasks in the job process, and the subsequent task processes, create a corresponding weather forecast branch process for the newly added weather forecast branch business.

[0204] Optionally, the device also includes an alarm module for obtaining the current runtime of the target process after the job submission task is executed in the job process;

[0205] If the current runtime exceeds the preset target process runtime threshold, an alarm message will be issued, and / or

[0206] The warning information and corresponding warning type are determined based on the target task status and the corresponding task type; the warning type includes a first type and a second type.

[0207] If a first preset number of first-type warning messages or a second preset number of second-type warning messages are received, an alarm message is issued; wherein the first preset number is greater than the second preset number.

[0208] The weather forecast process control device provided in the embodiments of the present invention can execute the weather forecast process control method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0209] The acquisition, storage, use, and processing of data in this application comply with relevant national laws and regulations and do not violate public order and good morals.

[0210] Example 7

[0211] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0212] Figure 8 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0213] like Figure 8 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0214] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0215] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the control of a weather forecasting process.

[0216] In some embodiments, the control of the method weather forecasting process can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the control of the method weather forecasting process described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to perform the control of the method weather forecasting process by any other suitable means (e.g., by means of firmware).

[0217] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0218] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0219] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0220] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0221] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0222] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0223] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0224] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A control method for a weather forecasting process, characterized in that, include: The decision on whether to execute the job submission task in the job workflow is based on the start-up condition judgment result in the start-up process corresponding to the weather forecast branch service; wherein, the weather forecast branch service refers to the branch service that is split off from the overall weather forecast process according to the process function; If a job submission task is executed in the job workflow, the execution of subsequent task workflows is determined based on the execution check results of the job execution check task in the job workflow; wherein, subsequent task workflows include extended job workflows or job execution result feedback workflows determined based on the business workflow of the weather forecast branch business. If the subsequent task process is not executed, the control process execution node will be traced back to the job submission task for re-execution; The method further includes: A request to add a weather forecast branch service is received; wherein the added weather forecast branch service is located at any position in the overall weather forecast process, and the added weather forecast branch service is an extension of an existing branch service, or a branch service that performs different services from the existing branch service. Based on the newly added weather forecast branch service, determine the corresponding startup conditions in the startup process, the job submission task and job operation check task in the operation process, and the subsequent task process. Based on the startup conditions in the startup process, the job submission task and job operation check task in the job process, and the subsequent task process, a corresponding weather forecast branch process is created for the newly added weather forecast branch service. The control flow execution node is traced back to the job submission task for re-execution, including: The previous operation check result in the operation check task is determined to be the target forecast time node corresponding to the forecast that is normal. Using the target forecast time node as the backtracking node of the process execution node, the job submission task continues to be executed.

2. The method according to claim 1, characterized in that, Based on the results of the job execution check tasks in the work process, determine whether to execute subsequent task processes, including: Determine the operation check result of the operation check task; wherein, the operation check result includes operation abnormality, operation normal and operation not completed or operation completed; If the result of the operation check is an operation error, the subsequent task process will not be executed; If the operation is running normally and has not yet ended, continue to execute the job operation check task. If the process has ended, the subsequent task flow will be executed.

3. The method according to claim 2, characterized in that, The weather forecast branch service is a data preparation service. The startup conditions for the startup process corresponding to the data preparation service include startup time conditions and target data source access result conditions. The job submission task is the target data source download job submission task, and the job execution check task is the job status check for the target data source download job. The subsequent task process is the data preprocessing extended job process determined according to the business process of the data preparation service. Accordingly, the subsequent task process includes: Execute the extended job submission task and extended job execution check task in the data preprocessing extended job process; wherein, the extended job is a data preprocessing job; Whether to proceed with the extended job execution result feedback process is determined based on the results of the extended job execution check task.

4. The method according to claim 1, characterized in that, The weather forecast branch service is a numerical weather prediction service. The start conditions of the start process corresponding to the numerical weather prediction service include the execution result judgment conditions of the data preparation service corresponding to the target data source. The job submission task is to send the data preprocessing result of the target data source to the target forecast system for numerical weather prediction. The job operation check task is to determine the forecast status of the target forecast system. The subsequent task process is the job execution result feedback process.

5. The method according to claim 1, characterized in that, The weather forecast branch service is a data service service. The start conditions of the start process corresponding to the data service service include the execution result judgment conditions of the numerical forecast service corresponding to the target forecast system. The job submission task is the post-processing task of the numerical forecast result of the target forecast system. The job operation check task is to determine the processing status of the post-processing. The subsequent task process is the job execution result feedback process.

6. The method according to any one of claims 1-5, characterized in that, After the job submission task in the job workflow is executed, the method further includes: Get the current runtime of the target process; If the current runtime exceeds a preset target process runtime threshold, an alarm message will be issued, and / or The warning information and corresponding warning type are determined based on the target task status and the corresponding task type; the warning type includes a first type and a second type. If a first preset number of first-type warning messages or a second preset number of second-type warning messages are received, an alarm message is issued; wherein the first preset number is greater than the second preset number.

7. A control device for a weather forecasting process, characterized in that, include: The job submission judgment module is used to determine whether to execute the job submission task in the job process based on the judgment result of the start condition in the start process corresponding to the weather forecast branch business; wherein, the weather forecast branch business refers to the branch business that is split off from the weather forecast general process according to the process function. The job execution check module is used to determine whether to execute subsequent task processes based on the execution check results of the job execution check task in the job process if the job submission task in the job process is executed; wherein, the subsequent task processes include extended job processes or job execution result feedback processes determined according to the business processes of the weather forecast branch business. The job submission backtracking module is used to control the process execution node to backtrack to the job submission task for re-execution if the subsequent task process is not executed. The device further includes a process addition module, used for: A request to add a weather forecast branch service is received; wherein the added weather forecast branch service is located at any position in the overall weather forecast process, and the added weather forecast branch service is an extension of an existing branch service, or a branch service that performs different services from the existing branch service. Based on the newly added weather forecast branch service, determine the corresponding startup conditions in the startup process, the job submission task and job operation check task in the operation process, and the subsequent task process. Based on the startup conditions in the startup process, the job submission task and job operation check task in the job process, and the subsequent task process, a corresponding weather forecast branch process is created for the newly added weather forecast branch service. The job submission backtracking module is specifically used for: The previous operation check result in the job operation check task is determined to be the target forecast time node corresponding to the forecast being normal; the job submission task is continued to be executed with the target forecast time node as the backtracking node of the process execution node.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the control method for the weather forecast process according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the control method for the weather forecasting process according to any one of claims 1-6.

Images