JP2006099657A - Analysis program execution program and apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an analysis program execution program and an apparatus for facilitating execution conditions for executing an analysis program constituted of a plurality of programs with mutual relationships. <P>SOLUTION: The analysis program execution program and the apparatus are provided with: an execution control information generation means 2 for generating an execution control sentence file 3 from an execution condition file 1; a processing condition information generation means 4 for generating a processing condition file 5; a processing time calculating means 14; and a re-execution object specifying means 15. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a program and an apparatus for executing an orbit analysis program for an artificial satellite.

In the field of design, operation, and utilization of artificial satellites, various numerical analyzes relating to the orbits of artificial satellites (for example, startup simulation and orbit determination accuracy analysis) are performed.
In these numerical analyses, numerical analysis is performed for a plurality of cases (hereinafter referred to as analysis cases) by changing the execution conditions (processing conditions, etc.) of the analysis program in various ways. At this time, for example, the execution conditions are stored in a plurality of input files having different execution conditions and input to the analysis program.

In general, the analysis program is composed of a plurality of mutually related program groups, and cannot be handled simply so as to execute a single program.
Patent Document 1 discloses a system linkage definition method for defining a data linkage between applications connected to a workflow management system that exchanges data between a plurality of programs (between applications).

FIG. 18 shows the input / output relationship for each execution condition between the programs A, B, and C constituting the analysis program.
Here, in the following description, a case where each program constituting the analysis program operates under a predetermined execution condition is referred to as a program execution case.

  In the figure, since eight execution conditions are given for program A, there are case a1 to case a8. Similarly, since the program B and the program C are given four execution conditions and three execution conditions, respectively, the program execution cases include cases b1 to b4 and cases c1 to c3, respectively.

  For example, in the analysis program shown in the figure, in order to obtain the result of the analysis case 1, the program execution cases a1 and a2 are executed, and the execution result of the a1 and a2 is input and the program execution case b1 is executed. Then, the program execution case c1 is executed with the execution result of b1 as an input.

  As can be seen from the figure, the dependency relationship varies depending on the program execution case. For example, in order to execute the case b1, the execution results of the cases a1 and a2 are required, and in order to execute the case b2, the case b2 The execution results of a1, a3, and a4 are required.

Therefore, even when trying to execute the analysis program for three types of analysis cases using different execution conditions, it can be seen that the program execution condition setting and the startup procedure are considerably complicated.
JP 2002-132503 A

  As mentioned above, because the interrelationships between the programs that make up the analysis program are complex, the execution conditions may be organized for each analysis case by using spreadsheet software, but when the analysis program is actually executed For each analysis case, an execution control statement (for example, a shell script in the case of UNIX (registered trademark)) must be created in consideration of the program execution case.

  In addition, trajectory analysis mainly involves numerical calculations such as matrix calculation and integration, and many CPU time is required. Therefore, when executing an analysis program for a large number of analysis cases, a series of execution control statements are often created and flowed in a batch format, but the processing time of the analysis program depends greatly on the execution conditions, so the processing time The prediction had to rely on the experience of the analysts.

  In addition, since the analysis program consists of multiple programs with mutual relations, even if there are program execution cases that do not end normally when executed for multiple analysis cases, the program execution cases that need to be re-executed can be easily identified. It was difficult to do.

  For example, when an error occurs in the program execution case b1 shown in FIG. 18, the program execution case c1 that requires the execution result of the program execution case b1 naturally needs to be re-executed, but the error of the program execution case b1 When the cause is the program execution case a1, re-execution from the program execution case a1 is required. The program execution case b2 that requires the execution result of the program execution case a1 and the program execution case c2 that requires the execution result of the program execution case b2 also need to be re-executed.

Such a determination can only be left to a person who is familiar with the analysis program, and it is difficult for an operator who is only in charge of program execution to make a determination.
The present invention has been made in view of the above-described problems, and a problem to be solved is analysis program execution for facilitating an execution condition for executing an analysis program configured by a plurality of programs having mutual relationships. Program and apparatus are provided.

  In order to solve the above problems, an analysis program execution program according to the present invention is an analysis program composed of a plurality of programs having mutual relations, and an analysis for causing an information processing apparatus to execute analysis processing in a plurality of cases In the program, an execution condition table storage in which an execution condition table in which a part or all of the changeable execution conditions required by the plurality of programs having relations for each case is summarized in a predetermined format is stored An execution condition table reading process for reading the execution condition table from the means, an input / output file name necessary for each program in the analysis process of each case from the execution condition table, and an input / output that is identification information of the input / output file name An execution control information generation process for generating an execution control statement having file identification; and Processing condition information generation processing for generating a processing condition file including input data necessary for each program and input data identification which is identification information of the input data in the analysis processing of each case from the table, and the input / output for each case And a program start control process for starting each program using the file and the input data.

  As a result, an execution control statement is generated from the execution condition table by the execution control information generation process, and a processing condition file is generated by the processing condition information generation process. By performing the operation, it is possible to easily set execution conditions for executing an analysis program composed of a plurality of mutually related programs in various cases.

  Further, in the execution control information generating process according to the present invention, a designated input / output file which is identification information of the designated input / output file name and the designated input / output file name required for each program in the analysis process of each case from the execution condition table An input / output file identification generating process for generating identification, a default input / output file name required by each program in the analysis process of each case, and a default input / output file identification which is identification information of the default input / output file name If the execution control statement template reading process for reading the prepared execution control statement template from the execution control statement template storage means matches the specified input / output file identification with the default input / output file identification, the execution control statement template Default I / O file corresponding to the default I / O file identification for control statement template Is replaced with a specified input / output file name corresponding to the specified input / output file identification, and an execution control statement file generation process is generated to generate an execution control statement, and the processing condition information generation process is performed from the execution condition table. Input data identification generation processing for generating designated input data necessary for each program in the analysis processing of each case and designated input data identification that is identification information of the designated input data, and each program required in the analysis processing of each case A processing condition file template reading process for reading a processing condition file template having a predetermined input data and a default input data identification which is identification information of the default input data from the processing condition file template storage means; and the designated input data identification And the default input data identification A condition file template includes processing condition file generation processing for generating a processing condition file by replacing predetermined input data corresponding to the predetermined input data identification with specified input data corresponding to the specified input data identification. May be.

  Further, according to the present invention, when the input data identification is executed under predetermined conditions, key data identification that is a determining factor of processing time for each program, key data corresponding to the key data identification, and the key data are executed. A model condition processing time table reading process for reading a model condition processing time table comprising model condition processing time from a model execution condition processing time table storage means, and input data and key that match the input data identification and the key data identification And a processing time calculation process for calculating the processing time of the analysis program using the data.

  Thereby, among the input data identification of the processing condition file generated from the processing condition table by the processing condition information generation process, the input data that matches the key data identification of the model execution condition processing time table, and the key data at this time Since it is possible to calculate the processing time of the analysis program from the model condition processing time, an analysis program composed of a plurality of mutually related programs set by operating the execution condition table by an operator or the like It is possible to easily predict the processing time for various cases.

  Further, the determination factor of the processing time includes at least one of a calculation period and an integration step size to be analyzed, and the processing time calculation process uses the input data and the processing time of the analysis program and the processing time The processing time of the analysis program may be calculated using a proportional inverse relationship with the model condition processing time when key data is used.

  Further, the program activation control process further determines whether or not the program in each case is normally completed, stores the determination result in an execution result table, and identifies the input / output file generated by the execution control statement file generation process A case relation table generating process for generating a case relation table that is related information of each program in each case, and based on the case relation table so that a case of abnormal termination can be identified from the execution result table. By execution result display processing for displaying the mutual relationship between the programs, and re-execution instruction means for instructing a case to be re-executed with respect to related information of each program in each case displayed by the execution result display processing Information on the case subject to re-execution instructed is stored in the execution result table. An execution result table changing process to be added, and a re-execution process for executing only the case including the abnormally terminated program and the program to be re-executed by the program start control process. .

  As a result of the program activation control process, the determination result as to whether each program has been normally completed is stored in an execution result table. From the execution result table and the case related table, the mutual relationship and abnormality of each program in each case Since completed cases are displayed, it is possible to easily identify cases that need to be re-executed.

  In addition, the execution result table change process allows information on the program to be reexecuted specified by the operator or the like to be stored in the execution result table, including the abnormally terminated program and the program to be reexecuted. Only the case can be easily re-executed.

  Furthermore, the present invention is an analysis program composed of a plurality of programs having mutual relations, and in the information processing apparatus for performing analysis processing in a plurality of cases, the plurality of programs having the relations for each case An execution condition table in which a part or all of the changeable execution conditions required for the analysis process are collected in a predetermined format, and input / output file names necessary for each program in the analysis process of each case from the execution condition table Execution control information generating means for generating an execution control statement having input / output file identification which is identification information of the input / output file name, input data necessary for each program in the analysis processing of each case from the execution condition table; Processing condition information for generating a processing condition file having input data identification that is identification information of the input data An information processing apparatus for orbital analysis of an artificial satellite, comprising: generating means; and program activation control means for activating each program using the input / output file and the input data for each case Also good.

  As described above, according to the present invention, it is possible to provide an analysis program execution program and apparatus that facilitates execution conditions for executing an analysis program configured by a plurality of mutually related programs.

Hereinafter, embodiments of the present invention will be described with reference to FIGS.
FIG. 1 is a block diagram showing the configuration of an analysis program execution program according to the present invention.

  In the block diagram of the analysis program execution program shown in the figure, the execution control information generating means 2 for generating the execution control statement file 3 from the execution condition file 1 and the processing condition for generating the processing condition file 5 from the execution condition file 1 are shown. And at least information generation means 4.

  The execution condition file 1 is one of execution conditions necessary for executing the analysis program for various cases (for example, input / output files required for each program execution case, parameters required for numerical analysis, etc.). A part or all of them are collected in a predetermined format.

  The execution control information generation unit 2 includes an input / output file identification generation unit 6 and an execution control statement generation unit 7. The input / output file identification generation unit 6 generates an input / output file identification file 8 from the execution condition file 1. The execution control statement generation unit 7 generates the execution control statement file 3 from the input / output file identification file 8 and the execution control statement template 9.

  Here, the input / output file identification file 8 is identification information of an input / output file required by each program (hereinafter referred to as “configuration program”) constituting the analysis program for each program execution case from the execution condition file 1. The input / output file identification (hereinafter referred to as “designated input / output file identification”) and the input / output file name (hereinafter referred to as “designated input / output file name”) are extracted.

  The execution control statement template 9 includes file identification (hereinafter referred to as “default input / output file identification”) and input / output file names (hereinafter referred to as “default input / output file identification”) necessary for the configuration program to execute the analysis program. "Default input / output file name") is stored.

  Therefore, the execution control statement generation means 7 specifies the default input / output file name of the default input / output file identification that matches the specified input / output file identification specified by the input / output file identification file 8 based on the execution control statement template 9. By changing the input / output file name, an execution control statement file 3 corresponding to each program execution case set in the execution condition file 1 is generated.

  The processing condition information generation unit 4 includes an input data list generation unit 10 and a processing condition file generation unit 11. The input data list generation unit 10 generates an input data list file 12 from the execution condition file 1, and the processing conditions The file generation unit 11 generates the processing condition file 5 from the input data list file 12 and the processing condition template 13.

  Here, the input data list file 12 includes input data identification (hereinafter referred to as “designated input data identification”) and input data (hereinafter, referred to as “designated input data identification”) that are required for the configuration program for each case from the execution condition file 1. In the following, “designated input data”) is extracted.

  The execution condition template 13 includes input data identification (hereinafter referred to as “default input data identification”) and input data (hereinafter referred to as “default input data”) necessary for the configuration program to execute the analysis program. Is stored).

  Therefore, the processing condition file generation unit 11 changes the default input data of the default input data identification that matches the specified input data specified by the specified input data identification based on the processing condition template 13 to the specified input data. A processing condition file 5 corresponding to each program execution case set in the execution condition file 1 is generated.

The analysis program execution program according to the present embodiment further includes a processing time calculation unit 14 and a re-execution target specifying unit 15.
Here, the model condition processing time table 16 includes a processing time when the configuration program is executed under a predetermined execution condition (hereinafter referred to as “model condition”) and setting conditions (inputs) that affect the processing time of each configuration program. Part or all of the designated input data of the data list file 12 (hereinafter referred to as “key data”), and key data identification that is key data identification information.

  Therefore, the processing time calculation means 14 uses the proportional / inverse proportional relationship between the key data of the model condition processing time table 16 and the input data of the input data list file 12 that matches the key data identification in the execution condition file 1. The processing time of the configuration program for each set program execution case and the processing time of the analysis program in each analysis case are calculated.

  The re-execution target specifying unit 15 includes a program start control unit 17, a case relation table generation unit 18, and an execution result table change unit 19. The program start control unit 17 includes an input / output file of the execution control statement file 3, The analysis program is started for each program execution case using the input data of the processing condition file 5, and the execution result (whether it is normal end) is stored in the execution result table 20.

  The case relation table generation means 18 generates a case relation table 21 in which the interrelationships between the constituent programs in each program execution case are tabulated from the input / output file identification file 8, and the execution result table change means 19 includes an execution result table 20. The execution result of the configuration program stored in is stored in the case relation table 21 and displayed on a display unit (not shown).

In the above description, the input data list file 12 is used for calculation of the processing time by the processing time calculation means 14, but the processing condition file 5 may be used.
Further, although the input / output file identification file 8 is used for the generation process of the case relation table 21 by the case relation table generation means 18, the execution control statement file 3 may be used.

FIG. 2 shows an outline of processing of the execution control information generation unit 2 and the processing condition information generation unit 4 mainly.
In order to simplify the following description, the analysis program shown in FIGS. 2 to 5 will be described as being configured by two configuration programs A and B. However, the present invention is not limited to this.

  First, the operator 22 creates an execution condition file (for example, a CSV file) using the spreadsheet software 23 or the like. On the other hand, the operator 22 creates a processing flow definition file 25 by defining the processing procedure of the configuration program constituting the analysis program, that is, the processing flow, in the analysis program execution device 24.

When the operator 22 activates the analysis program execution program in the analysis program execution device 24, the execution condition file 1 is read into the analysis program execution device 24, and the input / output file identification generation unit 6 performs the input / output file identification file 8.
Is generated, and the input data list file 12 is generated by the input data list generation means 10.

  Further, the execution control statement generation unit 7 generates the execution control statement file 3 for each of the configuration programs A and B from the input / output file identification file 8 and the execution control statement template 9.

  Also, the processing condition file 5 for each of the configuration programs A and B is generated from the input data list file 12 and the processing condition template 13 by the processing condition file generation means 11.

  When the processing flow definition file 25, the execution control statement file 3, and the processing condition file 5 are generated by the above processing, the operator 22 instructs the analysis program execution device 24 to execute the analysis program, and controls the program activation. Means 17 are executed.

  Then, according to the process flow definition file 25, the program activation control unit 17 sequentially executes the configuration programs in the order of the configuration program A and the configuration program B together with the execution control statement file 3 and the processing condition file 5 for each configuration program that have been generated. It will be activated.

  In the above description, it is natural that operations other than the execution condition file creation processing using the spreadsheet software 23 and the processing for starting the analysis program execution program can be automatically performed by batch processing or the like.

With the above processing, it is possible to easily set execution conditions and the like for executing an analysis program composed of a plurality of mutually related programs in various cases.
FIG. 3 shows an outline of the processing of the processing time calculation unit 14 mainly.

  When the analysis program execution program is executed by the operator 22, the analysis program execution device reads the execution condition file 1 and generates the input data list file 12 by the input data list generation means 10.

  Further, the processing time calculation means 14 calculates the processing time for each configuration program in each program execution case and the processing time of each analysis case from the input data list file 12 and the model condition processing time table 16 and displays them on the display unit 28. To do.

  The model condition processing time table 16 shown in the figure is an example in which the configuration data A and B are defined with respect to key data identification affecting the processing time, its unit, model conditions, and calculation conditions.

  For example, the configuration program A defines SPAN (calculation period) and INTEG (integration step) as key data identification, and executes processing in the integration step of 60 seconds for the orbit of the artificial satellite for one day. The time is 6 minutes. The calculation condition “×” indicates that SPAN is proportional to the processing time, and the calculation condition “÷” indicates that INTEG is inversely related to the processing time.

  Similarly, the configuration program B defines SPAN (calculation period), SATC (number of satellites), and STAT (number of satellite base stations) as key data identification, and SATC and STAT are 1 for the calculation period for one day. In this case, the processing time is 1 minute.

  With the above processing, when executing an analysis program composed of a plurality of mutually related programs in various cases, the processing time of the analysis case and the program execution case can be easily determined from the setting of the execution condition (execution condition file 1). It becomes possible to predict.

FIG. 4 shows an outline of processing of the re-execution target specifying unit 15 mainly.
The program start control unit 17 receives the execution control statement file 3 and the process condition file 5 as inputs and sequentially starts the configuration program according to the process flow definition file 25. Then, the execution result of each component program is stored in the execution result table 20.

  Further, the related information of each constituent program in each analysis case is stored in the case related table 21 from the input / output file identification file 8 (not shown), and the related information and the execution result are displayed on the display unit 28.

  The operator 22 designates an analysis case and a program execution case that need to be re-executed for display on the display unit from an input means (not shown). Then, the execution result table changing unit 19 changes the execution result table 20 in accordance with an instruction from the operator 22.

Thereafter, the program activation control means 17 executes again the analysis case and the program execution case that need to be reexecuted in the execution result table 20.
With the above processing, when an analysis program composed of multiple interrelated programs is executed in various cases, re-execution that correlates with program execution cases that do not end normally and program execution cases that do not end normally is necessary. It is possible to easily identify a program execution case.

FIG. 5 shows a flowchart about the outline of the processing described in FIGS.
The operator 22 creates an execution condition in advance using the spreadsheet software 23 or the like (step S500), and activates the analysis program execution program.

  In step S501, when the operator 22 instructs the analysis program execution device 24 to perform the processing procedure (execution order) of the configuration program constituting the analysis program, the analysis program execution device 24 creates the process flow definition file 25, The process proceeds to step S502.

  When the creation of the processing flow definition file 25 is completed, in step S502, the analysis program execution device 24 reads the execution condition file 1 previously created by the operator 22 or the like using spreadsheet software or the like, and the process proceeds to step S503.

  In step S503, the analysis program execution device 24 refers to the processing flow definition file 25, and the input / output file identification generation unit 6 generates the input / output file identification file 8 for each program execution case for each component program. Then, the execution control statement generation means 7 generates the execution control statement file 3 from the generated input / output file identification file 8 and the execution control statement template 9.

In step S503, when the generation of the execution control statement file 3 is completed for all program execution cases in all analysis cases, the process proceeds to step S504.
In step S504, the analysis program execution device 24 refers to the processing flow definition file 25, and the input data list generation unit 10 generates the input data list file 12 for each program execution case for each component program. Then, the processing condition file generation unit 11 generates the processing condition file 5 from the generated input data list file 12 and the processing condition template 13.

  Through the above processing, the input / output file (execution control statement file 3) and input data (processing condition file 5) required by each component program in each program execution case of each analysis case set in the execution condition file 1 are set. Is completed, and the analysis program execution device 24 proceeds to step S505.

  In step S505, the analysis program execution device 24 reads the model condition processing time table 16 by the processing time calculation means 14, and the key data in the model condition processing time table 16 and the input data list file 12 that matches the key data identification. The processing time of the analysis program for each analysis case or each program execution case set in the execution condition file 1 is calculated using a proportional / inverse proportional relationship with the input data.

  When the calculation of the processing time of the analysis program is completed, the analysis program execution device 24 proceeds to step S506, and the program start control unit 17 starts the configuration program sequentially for each analysis case according to the process flow definition file 25. Execute. That is, each component program is executed sequentially for each program execution case. Then, the execution result is stored in the execution result table 20.

  When the execution of the analysis program is completed, in step S507, the analysis program execution device 24 causes the case related table generation means 18 to execute each component program in each program execution case from the input / output file identification file 8 (or execution control statement file 3). Are generated in the case relation table 21.

  Then, the mutual relationship between the program execution cases is displayed on the display unit according to the case relation table 21, and information on the program execution cases that have ended abnormally is also displayed from the execution result table 20.

  When the operator 22 determines from the execution result displayed on the display unit that re-execution is necessary for a program execution case other than abnormal termination, the input means (for example, a mouse or a keyboard) for the analysis program execution device 24 is used. Indicates a program execution case that needs to be re-executed.

  When a program execution case requiring re-execution is instructed by the operator 22 or when there is a case of abnormal termination, the process proceeds to step S509, and the program execution case requiring re-execution instructed by the operator 22 is selected. The result is stored in the execution result table 20. Then, re-execution is performed only for the program execution case that is abnormally terminated and stored in the execution result table 20 and the program execution case that is specified by the operator 22 and needs to be re-executed, and the process is completed.

  In step S508, if the program execution case that needs to be re-executed is not instructed by the operator 22, or if there is no abnormal termination, the analysis program execution process is terminated.

An example in which the analysis program execution program described above is implemented for a more specific analysis program will be described below.
That is, a case where the analysis program execution program according to the present embodiment is used as an analysis program for performing an orbit analysis of an artificial satellite constituted by two configuration programs (ORBGEN, RadINT) will be described.

  The configuration program ORBGEN has six program execution cases (AS, AL, US, UL, MS, and ML), and the configuration program RADINT has four program execution cases ( AUM-S-10, AUM-S-20, AU-L-10, and AM-L-180). 6A and 6B show an example of the execution condition file 1 used in this embodiment.

First, FIG. 6A shows an execution condition file 1 for the configuration program ORBGEN.
The format of the execution condition file 1 shown in the figure is mainly composed of “configuration program name”, “input file setting”, “output file setting”, and “input data setting”.

  The “input file setting” and “output file setting” are each configured by “file name”, “file identification”, and “file identification by program execution case”, and “file identification by program execution case” is each program. It is defined for each execution case.

Here, “file identification” is “designated input / output file identification”, and “file identification by program execution case” corresponds to “designated input / output file name”.
The “input data setting” includes “input data item”, “input data identification”, and “data by program execution case”, and “data by program execution case” is defined for each program execution case.

Here, “input data identification” is “designated input data identification”, and “data by program execution case” corresponds to “designated input data”.
Therefore, in the execution condition file 1 shown in the figure, four input files (input files 1 to 4), one output file (output file 1), and 10 necessary for executing the configuration program ORBGEN are shown. Each piece of input data (satellite name, calculation period, perturbation condition, integration condition) for each program execution case (AS, AL, US, UL, MS, and ML) It can be seen that it can be defined.

  Similarly, in the execution condition file 1 shown in FIG. 6B, four input files (input files 1 to 4), one output file (output file 1), and 15 required for executing the configuration program RadINT. Each program execution case (AUM-S-10, AUM-S-20, AU-L-10, and AM-L-180) for each piece of input data (satellite name, calculation period, ground station information, and interference determination condition) ) Can be defined every time.

  Note that the “input data identification” shown in FIGS. 6A and 6B uses two input data identifications (input data identification 1 and input data identification 2). Furthermore, although classification (categorization) is performed by the input data identification 2, it is not intended to be limited to this. That is, a plurality of “file identification” and “input data identification” may be prepared as necessary, for example, “input data identification”, or only one, such as “file identification”.

  Further, the setting items (“input file setting”, “output file setting”, “input data setting”, etc.) shown in FIG. 6A and FIG. 6B are not limited to the setting items shown in FIG. The number and combination of input file identification, output file identification, input data identification, and program execution case may be determined accordingly.

  From the execution condition file 1 shown above, the input / output file identification file 8 is generated by the input / output file identification generation means 6 provided in the program execution device 24, and the input data list file 12 is generated by the input data list generation means 10. It will be.

  FIG. 7 shows an example of the input / output file identification file 8, and FIG. 8 shows an example of processing for generating the execution control statement file 3 from the input / output file identification file 8. FIG. 9 shows an example of the input data list file 12, and FIG. 10 shows an example of processing for generating the processing condition file 5 from the input data list file 12.

FIG. 7 shows an example of the input / output file identification file 8 generated from the execution condition file 1 shown in FIGS. 6A and 6B by the input / output file identification generation means 6.
In the input / output file identification file 8 shown in the figure, a “configuration program name” (for example, ORBGEN) is stored in the first line. Hereinafter, a “program execution case name” (for example, AS) for each program execution case, “File identification” (for example, FDDB, etc.) and “file identification by program execution case” (for example, * or ALOS) for the input file necessary for executing the configuration program in the program execution case, “file identification” for the output file (For example, SEFW) and “file identification by program execution case” (for example, ALOS) are stored.

  Therefore, the input / output file identification generating means 6 performs processing for extracting the items shown in FIG. In addition, a line beginning with “#” shown in the figure indicates a comment line.

FIG. 8 shows an example of processing for generating the execution control statement file 3 from the input / output file identification file 8 and the execution control statement template 9.
In step S801, the analysis program execution device 24 reads the input / output file identification file 8 and acquires the program name of the configuration program. When the configuration program name is acquired, the process proceeds to step S802, and the execution control statement template 9 for the configuration program is acquired using the acquired configuration program name as a key.

  When the reading process of the input / output file identification file 8 and the execution control statement template 9 is completed, the processes of steps S803 to S814 are executed for all the program execution cases described in the input / output file identification file 8.

  First, in step S804, the program execution case name is read from the input / output file identification file 8, and further, the file identification and the file identification for each program execution case for the read program execution case are read (step S806).

  If the file identification is “*” in step S807, the default settings described in the execution control statement template 9 are used, so the processing in steps S808 and S809 is not performed.

  If it is determined in step S807 that the file identification is not “*”, the process proceeds to step S808, and the file identification in the input file matching the input / output file identification file 8 and the execution control statement template 9 is extracted and extracted. Get the path name of the file using the file identification and file name as keys.

  Here, for the file path, a general method (for example, a command WHERE in the UNIX (registered trademark) environment or the like may be used, or a correspondence list of file names and path names is created in advance. The list may be referred to), and the description thereof will be omitted.

  When the path name of the corresponding file is acquired, the process proceeds to step S809, and the path name of the corresponding file identification in the execution control statement template 9 is rewritten with the path name acquired in step S808.

  When the processes in steps S805 to S809 described above are executed for all input files in the program execution case described in the input / output file identification file 8, the analysis program execution device 24 shifts the process to step S810 and outputs it. Do the same for the file.

  First, the analysis program execution device 24 reads the file identification of the output file and the file identification for each program execution case for the program execution case read in step S804 (step S811).

  Then, the process proceeds to step S812, where the file identification in the output file that matches between the input / output file identification file 8 and the execution control statement template 9 is extracted, and the path of the file is extracted using the extracted file identification and file name as a key. Get the name.

  When the path name of the corresponding file is acquired, the process proceeds to step S812, and the path name of the corresponding file identification in the execution control statement template 9 is rewritten with the path name acquired in step S812.

  Since the execution control statement file 3 is generated by executing the processing of the above steps S810 to S813 for all output files in the program execution case described in the input / output file identification file 8, the program execution case Save the file with a name (step S814).

Then, the process proceeds to step S803, and the same process is repeated for the next program execution case.
FIG. 9 shows an example of the input data list file 12 generated from the execution condition file 1 shown in FIGS. 6A and 6B by the input data list generation means 10.

  In the input data list file 12 shown in the figure, the “configuration program name” (for example, ORBGEN) is stored in the first line. Hereinafter, the “program execution case name” (for example, AS) for each program execution case, “Input Data Identification 1” (for example, SPAN) and “Input Data Identification 2” (for example, TS) and “Input Data Value” (for example, 2004/10) for input data necessary for executing the configuration program in the program execution case. / 1 0:00) is stored.

  Therefore, similarly to the input / output file identification generation unit 6, the input data list generation unit 10 performs a process of extracting the items shown in FIG. Also, a line beginning with “#” shown in FIG.

FIG. 10 shows an example of processing for generating the processing condition file 5 from the input data list file 12 and the processing condition template 13.
In step S1001, the analysis program execution device 24 reads the input data list file 12 and acquires the program name of the configuration program. When the configuration program name is acquired, the process proceeds to step S1002, and the processing condition template 13 for the configuration program is acquired using the acquired configuration program name as a key.

  When the reading process of the input data list file 12 and the processing condition template 13 is completed, the processes of steps S1003 to S1009 are executed for all program execution cases described in the input data list file 12.

  First, in step S1004, a program execution case name is read from the input data list file 12, and further, input data identification (input data identification 1ID1 and input data identification 2ID2) and data for each program execution case regarding the read program execution case. DD is read (step S1006).

  In step S1007, input data identification and input data identification 2 that match both the input data list file 12 and the processing condition template 13 (in this embodiment, both input data identification 1ID1 and input data identification 2ID2 match). ).

  In step S1008, the input data for identifying the input data in the processing condition template 13 is rewritten to the input data DD for identifying the input data in the input data list file 12.

  The processing condition file 5 generated by the above processing is stored with a program execution case name (step S1009), and the same processing is repeated from step S1003 for the next program execution case.

Next, a specific example of the processing time calculation unit 14 will be described with reference to FIGS.
FIG. 11 shows a configuration example of the model condition processing time table 16 used by the processing time calculation means 14.

  The model condition processing time table 16 shown in the figure includes a “configuration program name” (for example, ORBGEN), “number of key data”, “processing time for model conditions”, “key data identification” (for example, SPAN), and “ “Model conditions” and “calculation flags” are defined for each configuration program.

  For example, for the configuration program ORBGEN shown in the figure, two key data identifications having a calculation period of 1 day (key data identification SPAN) and an integration step of 60 seconds (key data identification STEP) are defined as model conditions. It is shown that the model condition processing time when the configuration program ORBGEN is executed under the conditions is 6 minutes.

  An operation flag for key data identification (for example, “×” corresponding to “SPAN” in the model condition processing time table 16) indicates a proportional inverse relationship between the key data and the model condition processing time.

  For example, the calculation flag for “SPAN” in the model condition processing time table 16 is “x”, which indicates that the model condition processing time is proportional. That is, assuming that the calculation time is 2 days, the execution time of the configuration program ORBGEN in this case can be calculated as 12 minutes, which is twice the model condition processing time.

  Similarly, since the calculation flag for “STEP” is “÷”, it indicates that it is inversely proportional to the model condition processing time. That is, assuming that the integration step is 120 seconds, the execution time of the configuration program ORBGEN in this case can be calculated as 3 minutes, which is 1/2 of the model condition processing time.

  FIG. 12 shows a flowchart of processing for calculating the execution time of the analysis program under the execution conditions set in the execution condition file 1 by the processing time calculation means 14 from the input data list file 12 and the model condition processing time table 16.

  In step S1201, the analysis program execution device 24 reads the input data list file 12 and acquires the configuration program name. When the configuration program name is acquired, the process proceeds to step S1202, and the model condition processing time table 16 for the configuration program is searched using the acquired configuration program name as a key.

  The number N of key data and the model condition processing time T are read for each constituent program from the model condition processing time table 16 specified in step S1202, the process proceeds to step S1204, and the following steps S1205 to S1205 are performed for each program execution case. The process of step S1212 is repeated.

  First, in step S1205, the program execution case name is read from the input data list file 12, and the following steps S1207 to S1211 are performed for the program execution case by the number of key data acquired in the process of step S1203.

  In step S1207, the key data identification KEYi, the model condition MDDi, and the calculation flag IFLGi are read from the model condition processing time table 16, and the process proceeds to step S1208.

  In step S1208, the input data list file 12 is read out to search for input data identification (in this embodiment, input data identification 1 or input data identification 2) that matches the key data identification KEYi, and the matched input data identification. Is substituted into the variable DD.

In step S1209, whether IFLGi is “x” or “÷” is determined. If “x”, the process proceeds to step S1210, and the calculation of equation (1) is performed.
T = T * (DD / MDDi) (1)
If it is determined in step S1209 that IFLGi is “÷”, the process proceeds to step S1211, and the calculation of Expression (2) is performed.

T = T / (DD / MDDi) (2)
The processing time T in one program execution case is calculated by the processing in steps S1206 to S1211 described above, the program execution case name and the processing time T are displayed on the display unit, and the same processing is repeated for the next program execution case. Do.

FIG. 13 shows an example of processing time for each program execution case calculated by the processing of FIG.
The processing time shown in the figure is the processing time of each program execution case calculated by the processing of FIG. 12 for the configuration programs ORBGEN and RadINT shown in FIGS. 6A and 6B.

  The configuration program ORBGEN defines SPAN (calculation time) and STEP (integration step) as key data identification in the model condition processing time table 16 shown in FIG. 11, and is proportional to and inversely proportional to the model condition processing time, respectively. It is defined to be.

  Therefore, for example, when the program execution case is AS, SPAN is 0.5 days, STEP is 60 seconds, and the SPAN model condition in the model condition processing time table 16 shown in FIG. Since the STEP model condition is 60 seconds, considering that the model condition processing time is 6 minutes, a processing time of 3 minutes (= 6 * (0.5 / 1) * (60/60)) is obtained. Can be calculated.

Next, a specific example of the re-execution target specifying unit 15 will be described with reference to FIGS.
FIG. 14 shows an example of the execution result file 20 of the analysis program generated by the program activation control means 17.

  The execution result file 20 shown in the figure includes an execution result flag (0 for normal termination, 1 for abnormal termination) and a re-execution flag (0 for no re-execution) for each program execution case for each component program. When re-execution is performed, 1) is stored.

  For example, since the execution result flag of the program execution case ML in the configuration program ORBGEN is “1”, it indicates that the program has ended abnormally. In this case, the re-execution flag is also set to “1” because of abnormal termination.

FIG. 15 shows an example of the case relation table 21 generated by the case relation table generation means 18.
The case relation table 21 shown in the figure shows the interrelationships between the configuration programs in each program execution case. The output file in the program execution case of one configuration program and the output file required as an input file It shows the relationship with the program execution case of the component program.

  For example, the output file in the program execution case A-S of the configuration program ORBGEN indicates that it is required as an input file of the program execution cases AUM-S-10 and AUM-S-20 of the configuration program RADINT.

  Further, the case relation table 21 shown in the figure includes a re-execution flag for each program execution case. When the re-execution flag is “0”, the re-execution flag is “1”. "Indicates re-execution.

  FIG. 16 shows an example in which the interrelationships between the constituent programs and the execution results in each program execution case are displayed on the display unit based on the execution result table 20 and the case relation table 21.

  In the execution result display screen shown in the figure, the relationship between the output file in each program execution case of the configuration program ORBGEN and the input file in each program execution case of the configuration program RADIUS is indicated by arrows according to the case relation table 21.

  For example, the program execution case AUM-S-10 of the configuration program RADINT indicates that the output files of the program execution cases A-S, US, and MS of the configuration program ORBGEN are input by the direction of the arrow. ing.

A program execution case surrounded by a thick line in accordance with the execution result table 20 represents a case of abnormal termination.
Further, when there is a program execution case that the operator 22 has determined that restart is necessary, the case is selected by clicking the corresponding case with an input means (for example, a mouse) provided in the analysis program execution device 24. A black circle (●) appears in the program execution case.

In the example shown in the figure, it is shown that the program execution cases A-S and AUM-S-10 are selected as re-execution targets by the operator 22.
Note that the program execution cases (ML, AUM-S-20, and AM-L-180) are abnormally terminated and need to be re-executed, so the black circle (without being selected by the operator 22). ●) is displayed.

  Further, when the operator 22 presses the re-execution button, the analysis program execution device 24 causes the re-execution target program execution case designated by the operator 22 (a program execution case that has been normally completed, and the operator 22 needs to re-execute). The program execution cases, for example, A-S and AUM-S-10 with black circles among the program execution cases surrounded by the broken line in FIG.

Then, the analysis program execution device 24 reads the execution result table 20 and re-executes only the program execution case whose re-execution flag is “1”.
FIG. 17 shows a flowchart of processing for the re-execution target specifying means.

  In step S170A, when the analysis program is executed by the program activation control means 17 and the execution result table 20 is created, the analysis program execution device 24 reads the input / output file identification file 8 in step S1701, and in each program execution case. The case relation table 21 shown in FIG. 15 is created from the input file identification and the output file identification.

  For example, in the input / output file identification file 8 shown in FIG. 7, the analysis program execution device 24 first specifies the output file identification ALOS for the program execution case A-S of the configuration program ORBGEN, and further about the configuration program RADINT. The program execution case of the configuration program RADINT requiring the output file of the program execution case AS of the configuration program ORBGEN as an input file is searched by searching the program execution case defining the identified ALOS as the input file identification. Identify.

  Then, as shown in FIG. 15, the program execution case A-S of the configuration program ORBGEN, and the program execution cases AUM-S-10 and AUM-S- of the configuration program RADIUS requiring the output file of this AS 20 is stored in the case relation table 21 together with the re-execution flag (initial value is “0”).

  The case-related table 21 shown in FIG. 15 is created by performing the same processing for each program execution case of each configuration program (configuration program ORBGEN and configuration program RADINT in the embodiment).

  When the creation of the case association table 21 is completed by the process of step S1702, the analysis program execution device 24 moves the process to step S1703, reads the execution result table 20, and refers to the execution result flag. Then, the abnormally terminated program execution case (program execution case whose execution result flag is “1”) is detected, and the re-execution flag of the program execution case in the case case relation table 21 is rewritten to “1”.

  For example, the execution result table 20 shown in FIG. 14 indicates that abnormal termination has been detected for the program execution case ML of the configuration program ORBGEN and the program execution cases AUM-S-20 and AM-L-180 of the configuration program RADIUS. (The execution result flag is “1”), the analysis program execution device 24 executes the program execution case ML of the configuration program ORBGEN and the program execution of the configuration program RADIUS in the case relation table 21 shown in FIG. The re-execution flag of cases AUM-S-20 and AM-L-180 is rewritten to “1”.

  When the rewriting process of the case relation table 21 is completed by the process of step S1703, the analysis program execution device 24 moves the process to step S1704, and displays the correlation between the program execution cases in each analysis case according to the case relation table 21. The information about the program execution case that has ended abnormally from the execution result table 20 is also displayed on the unit 28 using a GUI.

  For example, as shown in FIG. 16, the program execution case whose re-execution flag is “1” in the case-related table 21 (abnormally terminated program execution case recorded in the execution result table 20) is surrounded by a bold solid line and abnormally terminated. The executed program execution case is notified to the operator 22 and the program execution case that requires the program execution case and an output file of the program execution case as an input file are connected by an arrow line to display the program execution case that has ended abnormally. The operator 22 is notified of the program execution case correlated with the above.

  When the display process in step S1704 is completed, the analysis program execution device 24 moves the process to step S1705, accepts the re-execution flag setting from the GUI, and performs the process of rewriting the execution result table 20. In other words, when the program execution case that the operator 22 needs to re-execute is specified by an input means such as a mouse in accordance with the display by the processing in step S1704, the analysis program execution device 24 specifies the execution result table 20 in the execution result table 20. The re-execution flag of the executed program execution case is set to “1”.

  For example, in the display example shown in FIG. 16, the re-execution flag of the execution result table 20 is set for the program execution case A-S of the configuration program ORBGEN designated by the operator 22 and the program execution case AUM-S-10 of the configuration program RADIUS. Set to “1”.

  Further, the analysis program execution device 24 shifts the processing to step S1206, reads the execution result table 20, and reflects the re-execution flag changed in step S1706 in the case relation table 21.

  For example, in the example described in step S1705, the re-execution flag of the execution result table 20 for the program execution case A-S of the configuration program ORBGEN and the program execution case AUM-S-10 of the configuration program RADIUS specified by the operator 22 is “ In the case related table 21, the re-execution flag is changed to “1” for the program execution case A-S of the configuration program ORBGEN and the program execution case AUM-S-10 of the configuration program RADIUS. To do.

  When the change process of the case relation table 21 is completed, the analysis program execution device 24 moves the process to step S1707, and the correlation between the program execution cases in each analysis case according to the case relation table 21 by the same process as step S1704. Is also displayed on the GUI, and information on the execution result flag and the program execution case in which the re-execution flag is set to “1” is also displayed (the program execution in which the execution result flag or the re-execution flag is set to “1”). Display the case and the program execution case that requires the output file of this program execution case as an input file by connecting with an arrow line).

  When the operator 22 presses a re-execution button according to a display screen (for example, the screen shown in FIG. 16) (when the analysis program execution device 24 receives a confirmation instruction), the process proceeds to step S1708, and the execution result table 20 is illustrated. To be stored in the storage means provided in the analysis program execution device 24.

  In step S170B, the program start control unit 17 executes the program execution case in which the re-execution flag of the execution result table 20 is set to “1”.

It is a block diagram which shows the structure of the program for analysis program execution which concerns on this invention. It is a figure which shows the outline | summary of the process of the execution control information generation means 2 and the process condition information generation means 4 mainly. It is a figure which shows the outline | summary of the process of the process time calculation means 14 mainly. It is a figure which mainly shows the outline | summary of the process of the re-execution target specific means 15. FIG. It is a flowchart which shows the outline | summary of the process of FIGS. It is a figure which shows the example of the execution condition file used by a present Example. It is a figure which shows the example of the execution condition file used by a present Example. FIG. 7 is a diagram showing an example of an input / output file identification file generated from the execution condition file shown in FIGS. 6A and 6B by the input / output file identification generation means. It is a figure which shows the example of the process which produces | generates an execution control statement file from an input / output file identification file and an execution control statement template. FIG. 7 is a diagram showing an example of an input data list file generated from the execution condition file shown in FIGS. 6A and 6B by the input data list generation means. It is a figure which shows the example of the process which produces | generates a process condition file from an input data list file and a process condition template. It is a figure which shows the structural example of a model condition processing time table. It is a flowchart which shows the process which calculates the execution time of the analysis program in the execution condition set by the execution condition file by the processing time calculation means from the input data list file and the model condition processing time table. It is a figure which shows the example of the processing time for every program execution case calculated by the process of FIG. It is a figure which shows the example of the execution result file of the analysis program produced | generated by the program starting control means. It is a figure which shows the example of the case relevant table produced | generated by the case relevant table production | generation means. It is a figure which shows the example at the time of displaying the mutual relationship between the configuration programs in each program execution case, and an execution result on a display part based on an execution result table and a case relation table. It is a flowchart which shows the process about a re-execution object specific means. It is a figure shown about the input-output relationship for every execution condition between each program A, B, and C which comprises an analysis program.

Explanation of symbols

1 execution condition file 2 execution control information generation means 3 execution control statement file 4 processing condition information generation means 5 processing condition file 6 input / output file identification generation means 7 execution control statement generation means 8 input / output file identification file 9 execution control statement template 10 Input data list generation means 11 Processing condition file generation means 12 Input data list file 13 Processing condition template 14 Processing time calculation bullet 15 Reexecution target identification means 16 Model condition processing time table 17 Program start control means 18 Case relation table generation means 19 Execution result table changing means 20 Execution result table 21 Case-related table 22 Operator 23 Spreadsheet software 24 Analysis program execution device 25 Process flow definition file

Claims (10)

An analysis program composed of a plurality of programs having mutual relations, in an analysis program for causing an information processing apparatus to execute analysis processing in a plurality of cases,
From the execution condition table storage means in which an execution condition table in which a part or all of the changeable execution conditions required for the analysis process is stored in a predetermined format is stored in a predetermined format for each of the mutually related programs. An execution condition table read process for reading the execution condition table;
Execution control information generation processing for generating an execution control statement having an input / output file name required for each program and an input / output file identification that is identification information of the input / output file name in the analysis processing of each case from the execution condition table When,
A processing condition information generation process for generating a processing condition file including input data necessary for each program and input data identification that is identification information of the input data in the analysis processing of each case from the execution condition table;
Program start control processing for starting each program using the input / output file and the input data for each case;
For executing an orbital analysis program for an artificial satellite, characterized in that the information processing apparatus is executed. The execution control information generation process includes:
An input / output file identification generation process for generating a specified input / output file name necessary for each program in the analysis process of each case from the execution condition table and a specified input / output file identification that is identification information of the specified input / output file name;
An execution control statement template having a default input / output file name required by each program in the analysis processing of each case and a default input / output file identification that is identification information of the default input / output file name is stored in an execution control statement template Execution control statement template reading processing read from the means;
When the specified input / output file identification and the default input / output file identification are compared and matched, for the execution control statement template, the default input / output file name corresponding to the default input / output file identification is Execution control statement file generation processing for generating an execution control statement by replacing with a specified input / output file name corresponding to the output file identification;
With
The processing condition information generation process includes
Input data identification generation processing for generating designated input data necessary for each program in the analysis processing of each case from the execution condition table and designated input data identification that is identification information of the designated input data;
Processing conditions for reading out a processing condition file template having default input data required by each program in the analysis processing of each case and default input data identification that is identification information of the default input data from the processing condition file template storage means File template read processing,
When the specified input data identification and the default input data identification are compared and matched, the default input data corresponding to the default input data identification for the processing condition file template corresponds to the specified input data identification. A processing condition file generation process for generating a processing condition file by replacing with specified input data;
The program for executing an orbit analysis program for an artificial satellite according to claim 1. Among the input data identifications, key data identification that is a determining factor of processing time for each program, key data corresponding to the key data identification, and model condition processing time when the key data is executed under predetermined conditions A model condition processing time table reading process for reading the model condition processing time table provided from the model execution condition processing time table storage means;
A processing time calculation process for calculating a processing time of an analysis program using input data and key data in which the input data identification and the key data identification match;
The program for executing an orbital analysis program for an artificial satellite according to claim 1, wherein the information processing apparatus is further executed. The determination factor of the processing time includes at least one of a calculation period to be analyzed and an integration step size,
The processing time calculation process calculates the processing time of the analysis program using a proportional inverse relationship between the processing time of the analysis program when the input data is used and the model condition processing time when the key data is used. calculate,
The program for executing an orbital analysis program for an artificial satellite according to claim 3. The program activation control process further determines whether or not the program in each case has ended normally, stores the determination result in the execution result table,
A case related table generating process for generating a case related table that is related information of each program in each case from the input / output file identification generated by the execution control statement file generating process;
An execution result display process for displaying the mutual relationship of each program in each case based on the case relation table so that a case of abnormal termination can be identified from the execution result table;
The information on the case to be re-executed instructed by the re-execution instructing means for instructing the case to be re-executed with respect to the relevant information of each program in each case displayed by the execution result display processing is executed. Execution result table change processing to be added to the result table;
A re-execution process that executes only the case including the program that has been abnormally terminated in the execution result table and the program to be re-executed by the program activation control process;
The program for executing an orbital analysis program for an artificial satellite according to claim 1, wherein the information processing apparatus is further executed. An analysis program composed of a plurality of programs having mutual relations, in an information processing apparatus for performing analysis processing in a plurality of cases,
An execution condition table in which a part or all of the changeable execution conditions required for the analysis process by the plurality of programs having the mutual relation for each case are summarized in a predetermined format;
Execution control information generating means for generating an execution control statement having an input / output file name necessary for each program and an input / output file identification that is identification information of the input / output file name in the analysis processing of each case from the execution condition table When,
Processing condition information generating means for generating a processing condition file including input data necessary for each program and input data identification which is identification information of the input data in the analysis processing of each case from the execution condition table;
Program start control means for starting each program using the input / output file and the input data for each case;
An information processing apparatus for orbit analysis of an artificial satellite characterized by comprising: The execution control information generating means
An input / output file identification generating means for generating a specified input / output file name necessary for each program in the analysis processing of each case from the execution condition table and a specified input / output file identification that is identification information of the specified input / output file name;
An execution control statement template comprising a default input / output file name required by each program in the analysis processing of each case and a default input / output file identification which is identification information of the default input / output file name;
When the specified input / output file identification and the default input / output file identification are compared and matched, for the execution control statement template, the default input / output file name corresponding to the default input / output file identification is Execution control statement file generation means for generating an execution control statement by replacing with a specified input / output file name corresponding to the output file identification;
With
The processing condition information generating means
Input data identification generating means for generating designated input data necessary for each program in the analysis process of each case from the execution condition table and designated input data identification that is identification information of the designated input data;
A processing condition file template comprising default input data required by each program in the analysis processing of each case and default input data identification which is identification information of the default input data;
When the specified input data identification and the default input data identification are compared and matched, the default input data corresponding to the default input data identification for the processing condition file template corresponds to the specified input data identification. A processing condition file generating means for generating a processing condition file by replacing with specified input data;
The information processing apparatus for orbital analysis of an artificial satellite according to claim 6. Among the input data identifications, key data identification that is a determining factor of processing time for each program, key data corresponding to the key data identification, and model condition processing time when the key data is executed under predetermined conditions Model condition processing time table with
Processing time calculation means for calculating processing time of an analysis program using designated input data and key data in which the input data identification and the key data identification match;
The information processing apparatus for orbit analysis of an artificial satellite according to claim 6, further comprising: The determination factor of the processing time includes at least one of a calculation period to be analyzed and an integration step size,
The processing time calculation means calculates the processing time of the analysis program using a proportional inverse relationship between the processing time of the analysis program when the input data is used and the model condition processing time when the key data is used. calculate,
The information processing apparatus for orbital analysis of an artificial satellite according to claim 8. The program activation control means further determines whether or not the program in each case has ended normally, stores the determination result in the execution result table,
Case-related table generating means for generating a case-related table that is related information of each program in each case from the input / output file identification generated by the execution control statement file generating means;
Execution result display means for displaying the mutual relationship of each program in each case based on the case relation table so that a case of abnormal termination can be identified from the execution result table;
The information on the case to be reexecuted instructed by the reexecution instructing means for instructing the case to be reexecuted with respect to the related information of each program in each case displayed by the execution result display means An execution result table changing means to be added to the result table;
Re-execution means for executing, by the program activation control means, only a case that includes the abnormally terminated program and the program to be re-executed in the execution result table;
The information processing apparatus for orbit analysis of an artificial satellite according to claim 6, further comprising:

Images