JP6260445B2 - Simulation device - Google Patents

Description

  The present invention relates to a simulation apparatus.

  2. Description of the Related Art Conventionally, there is known a simulation device that temporarily stops execution of a simulation according to the present scenario (whole scenario) at an arbitrary point in the middle of the simulation and executes a simulation according to a plurality of trial scenarios (partial scenarios) (for example, Patent Document 1) ). In the simulation apparatus, the simulation result by a plurality of trial scenarios at the time of interest is confirmed in advance, and the corresponding part of the scenario is replaced with a desired trial scenario. In other words, among the multiple existing scenarios, the simulation with the common partial scenario (common scenario) is shared by the multiple entire scenarios, and only the simulation with different partial scenarios (difference scenarios) is performed for each of the multiple entire scenarios. The time required to obtain the expected result can be shortened.

JP 2008-027359 A

  However, depending on how the common scenario and the difference scenario are divided, the processing time required for the overhead accompanying the division (for example, data storage of the divided common scenario and difference scenario) may increase. Then, there is a possibility that the overall processing time may be worsened by exceeding the effect of shortening the processing time by sharing the simulation based on the common scenario among a plurality of overall scenarios.

  Therefore, in view of the above problems, a simulation using a common scenario that is common to each of a plurality of overall scenarios to be verified is shared by each overall scenario, and a simulation using a differential scenario corresponding to each overall scenario is executed from the end of the common scenario. In this case, an object of the present invention is to provide a simulation apparatus capable of preventing deterioration of the entire processing time.

In order to solve the above problem, in one embodiment, a simulation apparatus includes:
A simulation device for executing a simulation according to an input scenario,
A first case in which a partial scenario shared by a plurality of input scenarios is shared as a common scenario, and the simulation is performed by each of the plurality of scenarios from the start point of the common scenario without performing the sharing; The simulation by the common scenario is shared by the plurality of scenarios, and the processing time including the simulation execution time in the second case of executing the simulation by the plurality of scenarios from the end point of the common scenario is compared in advance. When the processing time in the second case is not shortened compared to the case of 1, the commonization is canceled, and the simulation with each of the plurality of scenarios is executed from the start point of the common scenario. .

  According to the above embodiment, when a simulation by a common scenario common to each of a plurality of overall scenarios to be verified is shared by each overall scenario, and a simulation by a differential scenario corresponding to each overall scenario is executed from the end of the common scenario In addition, it is possible to provide a simulation apparatus capable of preventing deterioration of the entire processing time.

It is a schematic block diagram which shows an example of a structure of the simulation apparatus which concerns on this embodiment. It is a flowchart which shows an example of the division | segmentation process (process divided | segmented into a common scenario and a difference scenario) of the verification scenario by a scenario division part. It is a figure explaining the method of dividing | segmenting the verification scenario by a scenario division part into a common scenario and a difference scenario. It is a flowchart which shows an example of the simulation execution process by the simulation apparatus which concerns on this embodiment.

  Hereinafter, embodiments for carrying out the invention will be described with reference to the drawings.

  FIG. 1 is a schematic configuration diagram illustrating an example of a configuration of a simulation apparatus 100 according to the present embodiment. The simulation apparatus 100 executes a simulation based on the input verification scenario and outputs a verification result (simulation result). In addition, when a plurality of verification scenarios are input, the simulation apparatus 100 executes a simulation based on each verification scenario and outputs a verification result corresponding to each verification scenario. Hereinafter, the simulation apparatus 100 will be described on the assumption that a plurality of verification scenarios are input.

  The simulation apparatus 100 includes a scenario division unit 30, a division simulation execution management unit 40, a virtual machine 50, a virtual machine storage unit 60, and the like, which are mounted on the computer 20.

  The computer 20 may be a plurality of computers. That is, each function included in the simulation apparatus 100 may be implemented across a plurality of computers.

  The scenario dividing unit 30 divides a plurality of input verification scenarios into a common scenario that is a partial scenario common to each verification scenario and a differential scenario that is a partial scenario different in each verification scenario. Note that the common scenario need not be a partial scenario that is common to all input verification scenarios. Of the multiple verification scenarios that have been input, partial scenarios that are common to at least two verification scenarios are divided as common scenarios. There is a case. The scenario dividing unit 30 outputs the generated common scenario, the difference scenario, and the simulation execution order including the combination of the common scenario and the difference scenario to the divided simulation execution management unit 40 as the execution plan EP. Details of the verification scenario dividing process by the scenario dividing unit 30 will be described later.

  The division simulation execution management unit 40 manages the execution of the simulation based on the execution plan input from the scenario division unit 30.

  Here, a simulation execution procedure by the simulation apparatus 100 will be briefly described.

  As described above, each verification scenario is divided into a common scenario and a difference scenario. Therefore, the verification result by each verification scenario can be obtained by executing the simulation by the differential scenario corresponding to each verification scenario from the end of the simulation by the common scenario corresponding to each verification scenario.

  That is, the simulation based on the common scenario is paused at the end time, and resumed from the time when the simulation based on the differential scenario corresponding to each verification scenario sharing the common scenario is paused. And the simulation result by each difference scenario is output as the simulation result by each verification scenario corresponding.

  As described above, the common scenario does not have to be a partial scenario common to all input verification scenarios, so the verification scenario may be composed of a combination of multiple common scenarios and one differential scenario. is there. For example, when five verification scenarios are input, the verification scenario is composed of a combination of a common scenario common to the five verification scenarios, a common scenario common to the four verification scenarios, and a difference scenario in time series. There is a possibility that.

  In the present embodiment, as will be described later, a simulator 51 that executes simulation is mounted in the virtual machine 50, and the virtual machine 50 in a state where the simulator 51 is temporarily stopped is stored in the virtual machine storage unit 60. That is, the simulator 51 is temporarily stopped at the end of the simulation using the common scenario, and the virtual machine 50 in a state where the simulator 51 is temporarily stopped is stored in the virtual machine storage unit 60. Then, when restarting the simulation based on the common scenario or the difference scenario from the end point of the common scenario, the virtual machine 50 s corresponding to the saved state is loaded from the virtual machine storage unit 60 to the virtual machine 50 and the simulation is restarted.

  The divided simulation execution management unit 40 manages the execution of the simulation by the simulator 51 in the virtual machine 50 in order to execute the simulation according to the execution procedure described above. Specifically, a simulation operation instruction (instruction to execute simulation), a parameter change instruction (instruction to change a time-series parameter in accordance with a scenario), an intermediate storage instruction (the simulator 51 is temporarily stopped, and the virtual machine 50 is virtually An execution instruction EI including an instruction to be stored in the machine storage unit 60 is output to the simulator execution management unit 52 in the virtual machine 50.

  Further, the divided simulation execution management unit 40 outputs an environment preparation command PC to the virtual machine storage unit 60 in order to restart the simulation from the end point of the common scenario. That is, the environment preparation command PC is output to the virtual machine storage unit 60 in order to load the virtual machine 50 s in the saved state corresponding to the scenario (common scenario or differential scenario) to be executed by the simulator 51.

  The virtual machine 50 includes a simulator 51 that specifically executes a simulation, and a simulator execution management unit 52 that directly manages the execution of the simulation by the simulator 51.

  The simulator 51 is a simulation execution unit that specifically executes a simulation, and includes an inspection model 51a, an external input model 51b, and a time series parameter 51c. The inspection model 51a includes a plant model to be controlled and a controller model that controls the control target. For example, when the time series parameter 51c related to the controller model is changed in accordance with the input scenario, the behavior of the control target with respect to the external input corresponding to the external input model 51b is simulated. can do.

  The “scenario” in the present embodiment corresponds to the value of each time series parameter 51c in the simulator at each time and how the value changes with time.

  The simulator execution management unit 52 directly manages the execution of the simulation by the simulator 51 based on the execution instruction EI from the divided simulation execution management unit 40. Specifically, the simulator 51 is caused to execute a simulation based on a simulation operation instruction included in the execution instruction EI. Further, the time-series parameter 51 c is changed along with the passage of time in the simulation by the simulator 51 based on the parameter change instruction included in the execution instruction EI. Further, based on the midway saving instruction included in the execution instruction EI, the simulator 51 is paused, and the virtual machine 50 in a state where the simulator 51 is paused is saved in the virtual machine storage unit 60. When the virtual machine 50 is stored in the virtual machine storage unit 60, the virtual machine 50 is associated with a common scenario (corresponding scenario) corresponding to the virtual machine 50.

  The virtual machine 50 may include a plurality of simulators. That is, the simulator execution management unit 52 may execute a coupled simulation by a plurality of simulators and output simulation results by a plurality of input verification scenarios.

  The virtual machine storage unit 60 is a storage unit that stores the virtual machine 50s in a state where the simulator 51 is temporarily stopped in a database format. As described above, the virtual machine storage unit 60 stores a plurality of virtual machines 50 s including the simulator 51 paused at the end of the simulation by the common scenario in association with the common scenario (corresponding scenario). This is because when the saved virtual machine 50 s is loaded into the virtual machine 50, it is possible to determine which common scenario causes the simulator 51 to be suspended at the end of the simulation.

  In addition, the virtual machine storage unit 60 stores the virtual machine 50s in the storage state including the temporarily stopped simulator 51 corresponding to the scenario to be executed by the simulator 51 based on the environment preparation command PC from the divided simulation execution management unit 40. Load 50.

  Instead of using the virtual machine storage unit 60, for example, storage of the virtual machine 50 and management of the virtual machine 50 in the storage state may be performed by predetermined software.

  Next, verification scenario splitting processing (processing for splitting into a common scenario and a differential scenario) by the scenario splitting unit 30 will be specifically described.

  FIG. 2 is a flowchart illustrating an example of verification scenario division processing (processing to divide into a common scenario and a difference scenario). FIG. 3 is a diagram for explaining a method of dividing the verification scenario by the scenario dividing unit 30 into a common scenario and a difference scenario. Hereinafter, the verification scenario dividing process will be described with reference to each other alternately with reference to FIGS. 2 and 3.

  FIG. 3 shows an example of a verification scenario dividing method when three verification scenarios of the first scenario, the second scenario, and the third scenario are input to the scenario dividing unit 30. In FIG. 3, four parameters P1 to P4 are set for each time as the time series parameter 51c.

<1. Creating a scenario map>
Referring to FIG. 2, when a plurality of verification scenarios to be verified by the simulation apparatus 100 are input to the scenario dividing unit 30, a scenario map is created in step S101.
Specifically, as shown in FIG. 3, scenario maps M1 to M1 corresponding to the respective verification scenarios (first to third scenarios) in a table format in which parameters P1 to P4 are associated with time T in the simulation. M3 is created.
In FIG. 3, five times of times T = 0, 0.1, 0.5, 0.7, and 0.8 are set as times when the parameters P1 to P4 can be changed. The time setting (how to divide the time) is the same for all verification scenarios (first to third scenarios). Further, the absolute values of the numerical values in the scenario maps M1 to M3 have no specific meaning.

<2. Creation of scenario structure tree>
Referring to FIG. 2, in step S102, a scenario structure tree is created.

<2-1. Tree structure>
Specifically, as shown in FIG. 3, first, each time is formed into a tree structure as an individual partial scenario (individual scenario). More specifically, corresponding to the scenario map M1 (first scenario), five times T (= 0, 0.1, 0.5, 0.7,. A structural tree T1 including the individual scenarios 1 to 5 in 8) is created. Corresponding to the scenario map M2 (second scenario), a structural tree T2 composed of the individual scenarios 6 to 10 at the five times T from the earlier (smaller) time T is created. Corresponding to the scenario map M3 (third scenario), a structural tree T3 composed of the individual scenarios 11 to 15 at the five times T from the earlier (smaller) time T is created. The individual scenarios 1 to 15 mean the values of the parameters P1 to P4 at the corresponding time T.

<2-2. Grouping common parts>
Next, in the structural tree corresponding to each verification scenario, those having the same individual scenario (parameters P1 to P4) at the same time are sequentially searched from time T = 0 and are grouped. As shown in FIG. 3, when the individual scenarios 1, 6 and 11 at time T = 0 are compared, the values of the parameters P1 to P4 are all the same, so that the common scenario common to the first to third scenarios Group as A. Further, when the individual scenarios 7 to 9 and the individual scenarios 12 to 14 at the times T = 0.1, 0.5, and 0.7 are compared, the values of the parameters P1 to P4 all match, 2. Grouped as a common scenario B common to the third scenario. As a result, the structural tree T1 of the first scenario is configured in the order of the common scenario A and the individual scenarios 2, 3, 4, and 5. The structural tree T2 of the second scenario is configured in the order of the common scenario A, the common scenario B, and the individual scenario 10. The structural tree T3 of the third scenario is configured in the order of the common scenario A, the common scenario B, and the individual scenario 15.

<2-3. Synthesis of each structural tree>
Next, each of the structural trees T1 to T3 is synthesized to generate a scenario structural tree TC. As shown in FIG. 3, since the common scenario A is common to the first to third scenarios, the common scenario A is used as a base point and corresponds to the individual scenarios 2 to 5 corresponding to the first scenario and the second and third scenarios. A tree structure branches into the common scenario B. Further, since the common scenario B is common to the second and third scenarios, a tree structure that branches from the common scenario B to the individual scenario 10 corresponding to the second scenario and the individual scenario 15 corresponding to the third scenario. To. Moreover, the continuous individual scenarios 2 to 5 are grouped into a difference scenario 2-5.

<3. Scenario tree optimization>
Referring to FIG. 2, in step S103, the scenario structure tree is optimized.

  Specifically, it is determined whether or not there is an effect of each common scenario included in the scenario structure tree TC (an effect of shortening the processing time by sharing the common scenario among a plurality of verification scenarios). If there is no effect, the sharing is canceled and the scenario is divided into differential scenarios corresponding to each verification scenario.

  A determination formula f for determining whether or not there is an effect due to the common scenario is expressed as follows.

f = N · Tcom−Tcom−N · Tover
N is the number of verification scenarios sharing a common scenario, Tcom is a simulation execution time based on the common scenario, and Tober is to execute the common scenario and the differential scenario corresponding to each verification scenario separately. Indicates the accompanying overhead time.

  In the determination formula f, the overhead time associated with the execution of the differential scenario corresponding to each verification scenario divided from the common scenario is reduced from the simulation execution time that is reduced by sharing the common scenario among a plurality of verification scenarios. Is. Therefore, if the determination formula f> 0, it is determined that there is an effect due to the common scenario, and if the determination formula f ≦ 0, it is determined that there is no effect due to the common scenario.

  In other words, when a simulation based on each scenario is shared by each verification scenario, compared to when a simulation based on each verification scenario is executed from the beginning of the common scenario, and a simulation based on each verification scenario is executed from the end of the common scenario. It is determined in advance whether or not the processing time is shortened. If there is no effect and the processing time is not shortened, the sharing is canceled, and the simulation using each verification scenario is executed from the start point of the common scenario.

  As shown in FIG. 3, in this example, it is determined that there is an effect due to the common scenario A, but it is determined that there is no effect due to the common scenario B, and the sharing is canceled and the second and third scenarios are released. It is broken down into corresponding differential scenarios. In FIG. 3, the decomposed difference scenario (individual scenarios 7 to 9) corresponding to the second scenario and the individual scenario 10 are grouped and shown as a difference scenario 7-10. Further, the decomposed difference scenario (individual scenarios 12 to 14) corresponding to the third scenario and the individual scenario 15 are grouped and shown as a difference scenario 12-15.

In this way, the scenario structure tree TC is optimized, and based on the common scenario A, the difference scenario 2-5 corresponding to the first scenario, the difference scenario 7-10 corresponding to the second scenario, and the third scenario An optimized scenario structure tree TCopt in which the difference scenarios 12-15 corresponding to the scenarios are connected is generated.
<4. Creating an execution plan>
Referring to FIG. 2, in step S104, an execution plan is created based on the optimized scenario structure tree.

  Taking FIG. 3 as an example, as an execution plan, a common scenario A, difference scenarios 2-5, 7-10, 12-15, and a simulation execution order by a combination thereof are created. The created execution plan is output to the divided simulation execution management unit 40 as described above.

  Next, simulation execution processing by the simulation apparatus 100 according to the present embodiment will be described.

  FIG. 4 is a flowchart illustrating an example of a simulation execution process performed by the simulation apparatus 100 according to the present embodiment. Specifically, the operation of the entire simulation apparatus 100 when the division simulation execution management unit 40 causes the simulator 51 to execute a simulation based on a common scenario or a differential scenario according to the execution plan input from the scenario division unit 30 is shown. ing.

  In step S201, the virtual machine 50s in the saved state corresponding to the target scenario (common scenario or differential scenario) is transferred from the virtual machine storage unit 60 to the virtual machine 50 in response to the environment preparation command PC from the divided simulation execution management unit 40. To be loaded. However, when the simulation according to the first scenario is executed, this step is skipped because the corresponding virtual machine 50s does not exist.

  In step S202, the divided simulation execution management unit 40 transmits an execution instruction (simulation operation instruction, parameter change instruction, midway storage instruction) to the simulator execution management unit 52 on the loaded virtual machine 50.

  In step S203, according to the execution instruction from the divided simulation execution management unit 40, the simulator execution management unit 52 changes the time-series parameter 51c according to the target scenario, and the simulator 51 performs simulation until the set time. Let it run.

  In step S204, it is determined whether the target scenario is a common scenario or a differential scenario.

  When the target scenario is a common scenario, the simulator execution management unit 52 temporarily stops the simulator 51 in response to an execution instruction (halfway save instruction) from the divided simulation execution management unit 40, and sets the virtual machine 50 to a virtual machine. The data is saved in the storage unit 60, and the current process is terminated. At this time, the virtual machine 50 is stored in the virtual machine storage unit 60 in a state associated with the common scenario (corresponding scenario).

  On the other hand, if the target scenario is a differential scenario, it means that the simulation by the verification scenario corresponding to the differential scenario is terminated. Therefore, the simulator execution management unit 52 outputs the verification result from the simulator 51 and performs the current process. finish.

  Next, the operation of the simulation apparatus 100 according to this embodiment will be described.

  The simulation apparatus 100 according to the present embodiment shares a partial scenario common to a plurality of verification scenarios as a common scenario, determines in advance whether there is an effect due to the common scenario, and corresponds to each verification scenario when there is no effect. Decompose into differential scenarios.

  Specifically, compared to the case where simulations are performed using each verification scenario from the beginning of the common scenario, the simulations based on the common scenario are shared among the verification scenarios, and the simulation is performed using each verification scenario from the end of the common scenario. In this case, it is determined whether or not the processing time is shortened. If the processing time is not shortened, release the common scenario, break it down into the differential scenarios corresponding to each verification scenario, and execute the simulation with each verification scenario (corresponding differential scenario) from the start point of the common scenario . As a result, even if a common scenario exists in each verification scenario, if the processing time deteriorates due to an increase in overhead time accompanying the division of the verification scenario, a simulation is executed for each verification scenario. Therefore, it is possible to suppress the deterioration of the processing time.

  In addition, the simulation apparatus 100 according to the present embodiment temporarily stops the simulator 51 on the virtual machine 50 and stores the virtual machine 50 in the virtual machine storage unit 60. In addition, the virtual machine 50s stored in the virtual machine storage unit 60 can be loaded into the virtual machine 50, and the simulation can be resumed from the time when the simulator 51 is temporarily stopped. Thereby, it is possible to divide a plurality of verification scenarios into a common scenario and a difference scenario and execute a simulation without depending on whether or not the simulator 51 has an intermediate storage function, that is, without depending on the function of the simulator 51. it can. Therefore, it is possible to reduce the processing time required for the simulation with a plurality of verification scenarios without depending on the function of the simulator 51.

  As mentioned above, although the form for implementing this invention was explained in full detail, this invention is not limited to this specific embodiment, In the range of the summary of this invention described in the claim, various Can be modified or changed.

1-15 Individual scenario 2-5, 7-10, 11-15 Difference scenario 20 Computer 30 Scenario division unit 40 Division simulation execution management unit 50, 50s Virtual machine 51 Simulator 51a Inspection model 51b External input model 51c Time series parameter 52 Simulator Execution management unit 60 Virtual machine storage unit 100 Simulation device A, B Common scenario EI Execution instruction EP Execution plan PC environment preparation instruction

Claims (1)

A simulation device for executing a simulation according to an input scenario,
A first case in which a partial scenario shared by a plurality of input scenarios is shared as a common scenario, and the simulation is performed by each of the plurality of scenarios from the start point of the common scenario without performing the sharing; The simulation by the common scenario is shared by the plurality of scenarios, and the processing time including the simulation execution time in the second case of executing the simulation by the plurality of scenarios from the end point of the common scenario is compared in advance. When the processing time in the second case is not shortened compared to the case of 1, the commonization is canceled, and the simulation with each of the plurality of scenarios is executed from the start point of the common scenario. ,
Simulation device.

Images