Simulation deduction-oriented scene breakpoint resetting scheduling method

Abstract

The invention relates to a simulation deduction-oriented scene breakpoint reset scheduling method, which comprises the following steps of: S1, slicing simulation deduction data according to time periods, and compressing and storing the slices based on the simulation deduction data; s2, identifying a key breakpoint of the simulation scene; s3, loading a simulation scene data fragment where the key breakpoint is located to a simulation engine for pre-deduction to obtain pre-deduction data; and S4, carrying out simulation scene baseline merging. The method is suitable for debugging the simulation scene of the large-scale spacecraft system, and can solve the problem that the simulation scene of the large-scale spacecraft system cannot be effectively debugged.

Description

Technical Field

[0001] The present invention relates to the technical field of spacecraft system simulation, and in particular to a scenario breakpoint resetting scheduling method oriented to simulation deduction. Background Art

[0002] In recent years, with the rapid development of computer technology and aerospace technology, computer simulation and deduction technology has become an essential means of spacecraft system simulation. Applying simulation and deduction technology to simulate spacecraft systems, taking advantage of the large-capacity storage and high-speed computing of computers, combined with simulation scenario debugging methods, can fully explore the shortcomings of the system process and payload capacity of spacecraft, and provide data support for the optimization of spacecraft systems. The scale of spacecraft systems has become a trend in the development of spacecraft systems, with the characteristics of an increasing number of spacecraft, increasingly complex spacecraft payloads, and an increasing amount of data transmitted between satellites and the ground.

[0003] The existing spacecraft system simulation and deduction technology is limited by computer storage capacity and computing speed, as well as the limitations of simulation and deduction debugging technology. It is impossible to effectively debug large-scale spacecraft system simulations. This is specifically reflected in high debugging playback latency, debugging process jams, and slow debugging result output. Summary of the invention

[0004] In order to solve the technical problems existing in the above-mentioned prior art, the purpose of the present invention is to provide a scene breakpoint reset scheduling method for simulation deduction, which can solve the problem that large-scale spacecraft system simulation scenes cannot be effectively debugged.

[0005] To achieve the above-mentioned object of the invention, the present invention provides a scenario breakpoint reset scheduling method for simulation deduction, comprising the following steps:

[0006] The following steps are involved:

[0007] Step S1, slicing the simulation data according to time periods, and compressing and storing the simulation data slices;

[0008] Step S2, identifying key breakpoints of the simulation scenario;

[0009] Step S3, loading the simulation scene data fragment where the key breakpoint is located into the simulation engine for pre-deduction to obtain pre-deduction data;

[0010] Step S4: merging simulation scene baselines.

[0011] According to a technical solution of the present invention, step S1 specifically includes:

[0012] Step S11, determining whether the simulation scenario is being run for the first time, if not, directly obtaining the simulation deduction data compression slice of the simulation scenario from the database; if so, obtaining the scenario start time and end time of the simulation scenario, and calculating the simulation duration of the simulation scenario;

[0013] Step S12: judging whether it is necessary to adjust the length of the deduction data slice time period according to the simulation duration; if the simulation duration exceeds 24 hours, increasing the length of the simulation data slice time period;

[0014] Step S13, calculating the scene duration of the simulation scene, and slicing the simulation scene according to the length of the simulation deduction data slicing time period;

[0015] Step S14: after starting the simulation, obtaining the simulation data of each simulation slice from the simulation scene according to the slice duration;

[0016] Step S15, compressing the simulation data slices to remove redundant data in the simulation data slices;

[0017] Step S16: using a data compression tool to further compress the simulation data slices;

[0018] Step S17: Associating the simulation data slices with the simulation scenarios and storing them in a database.

[0019] According to a technical solution of the present invention, in step S15, when the simulation deduction data slice is compressed, for satellite orbit data, the orbital elements are recorded; for static targets, the coordinate positions are recorded; for moving targets, their running trajectory data are recorded; for data, the data content and the sending and receiving times are recorded;

[0020] Among them, static targets include at least ground stations and measurement and control stations; moving targets include at least aircraft, vehicles, and ships; data include at least business data streams and communication data streams.

[0021] According to a technical solution of the present invention, step S2 specifically includes:

[0022] Step S21, in the simulation scene debugging mode, obtaining the moment when the breakpoint is set in the simulation scene, and determining the simulation deduction data slice corresponding to the breakpoint moment;

[0023] Step S22, obtaining the number of historical breakpoints of the simulation deduction data slice, and adding 1 to the count of the number of historical breakpoints;

[0024] Step S23, setting a historical breakpoint count threshold for deduced data slices;

[0025] Step S24: sort the deduction data slices from high to low according to the number of historical breakpoints, obtain the top-ranked deduction data slices as key deduction data segments, and set all historical breakpoints in the corresponding slices as key breakpoints;

[0026] Step S25: determine whether the key breakpoint has changed. If the key breakpoint has changed, determine whether the key deduction data slice has changed, and update the maintained key deduction data slice in time.

[0027] According to a technical solution of the present invention, the historical breakpoint count threshold is set based on the complexity of the simulation scenario and the debugging focus to accurately locate key breakpoints, and the setting range of the historical breakpoint count threshold is 1-10.

[0028] According to a technical solution of the present invention, step S3 specifically includes:

[0029] Step S31, obtaining key deduction data slices and key breakpoints maintained by the simulation scenario, obtaining the start time, end time, simulation scenario initialization state, event data, and simulation scenario time where the key breakpoints are located for the key deduction data slices;

[0030] Step S32: calling the simulation engine, pushing the acquired key deduction data slices and related data to the simulation engine for deduction, and recording the complete simulation scenario deduction data during the deduction process;

[0031] Step S33, extract the simulation scene deduction data at the critical breakpoint moment separately, using the breakpoint ID as the index and the simulation scene deduction data at the breakpoint moment as the value;

[0032] Step S34, putting the key deduction data slices, complete deduction data and breakpoint simulation deduction data into the memory.

[0033] According to a technical solution of the present invention, step S4 specifically includes:

[0034] Step S41: in the simulation scene debugging mode, locate the simulation deduction data slice at the current deduction moment;

[0035] Step S42: Open the baseline branch according to the modification instruction, and use the engine to promote simulation deduction;

[0036] Step S43: Compare the branch and baseline slice data to complete merging branches or cleaning data.

[0037] According to a technical solution of the present invention, the step S41 includes:

[0038] Step S411: in the simulation scene debugging mode, determining the current simulation deduction moment of the user, and determining the simulation deduction data slice corresponding to the simulation deduction moment;

[0039] Step S412: determine whether the user has modified the simulation scene state based on the human-in-the-loop. If modified, obtain the simulation data slice where the simulation scene is located at the time of modification.

[0040] According to a technical solution of the present invention, step S42 includes:

[0041] Step S421, opening a branch for the current simulation scenario baseline, modifying the current simulation deduction data slice according to the modification result of the user, and putting it into the simulation engine for simulation deduction;

[0042] Step S422, determining whether the user has completed debugging within the current simulation data slice time period;

[0043] Step S423: If the user fails to complete debugging within the current simulation data slice time period, the simulation data at the end of the current simulation data slice is used as the initialization data for the next simulation data slice, and the simulation engine is called for deduction.

[0044] According to a technical solution of the present invention, step S43 includes:

[0045] Step S431: after completing the simulation and deduction of a simulation and deduction data slice, obtain the simulation and deduction data at the end time of the current simulation and deduction data slice, and compare it with the initialization data of the next simulation and deduction data slice in the baseline. If the comparison result is less than the threshold, the simulation engine is not called to deduce the next simulation and deduction slice, but the next simulation and deduction data slice in the baseline is directly used as the next simulation and deduction data slice of the branch;

[0046] Step S432, determine whether the user merges the branch deduction data into the baseline. If merged into the baseline, the simulation deduction data slices after the intersection with the branch in the baseline are deleted, and the simulation deduction data slices in the branch are merged into the baseline; if not merged into the baseline, the simulation deduction data slices in the branch are deleted.

[0047] Compared with the prior art, the present invention has the following beneficial effects:

[0048] The present invention proposes a scenario breakpoint reset scheduling method for simulation deduction, which compresses and stores simulation deduction data slices, obtains simulation scenario deduction data from the simulation deduction data storage, generates simulation deduction data slices, and identifies key simulation deduction data slices and key breakpoints in the simulation scenario through simulation scenario key breakpoint identification. The simulation deduction engine is called to pre-decode key simulation deduction data slices and key breakpoints, obtain key simulation pre-deduction data, and generate a new baseline in the simulation deduction scenario of a person in the loop, and the merged simulation scenario baseline is stored. The present invention is suitable for debugging simulation scenarios of large-scale spacecraft systems, and can solve the problem that simulation scenarios of large-scale spacecraft systems cannot be effectively debugged.

[0049] The present invention, based on simulation scene data slicing compression storage and key breakpoint identification technology, introduces the concepts of simulation scene debugging baseline and simulation scene pre-deduction, realizes efficient resetting of simulation scene breakpoints of large-scale spacecraft system, and further realizes efficient and effective debugging of large-scale spacecraft simulation. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0051] Figure 1 A flowchart schematically showing a scenario breakpoint reset scheduling method for simulation deduction according to an embodiment of the present invention;

[0052] Figure 2 A schematic diagram showing an operation flow chart of compression and storage of simulation deduction data slices according to an embodiment of the present invention;

[0053] Figure 3 Schematically showing an operation flow chart of critical breakpoint identification of a simulation scenario according to an embodiment of the present invention;

[0054] Figure 4 A flowchart schematically showing a simulation scenario debugging segment pre-play according to an embodiment of the present invention;

[0055] Figure 5 The flowchart schematically shows the operation of merging simulation scenario baseline branches according to one embodiment of the present invention. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0057] like Figures 1 to 5 As shown, a scenario breakpoint reset scheduling method for simulation deduction of the present invention comprises the following steps:

[0058] Step S1, slicing and compressing simulation data for storage: For the running address simulation scenario, the simulation data is sliced ​​according to the time period in chronological order. The default length of the slice is 600 seconds, and the slice length can be set. The simulation slice data is compressed and stored, specifically including:

[0059] Step S11, determining whether the simulation scenario is being run for the first time, if not, directly obtaining the simulation deduction data compression slice of the simulation scenario from the database; if so, obtaining the scenario start time and end time of the simulation scenario, and calculating the simulation duration of the simulation scenario;

[0060] Step S12: judging whether it is necessary to adjust the length of the deduction data slice time period according to the simulation duration; if the simulation duration exceeds 24 hours, increasing the length of the simulation data slice time period;

[0061] Step S13, calculating the scene duration of the simulation scene, and slicing the simulation scene according to the length of the simulation deduction data slicing time period;

[0062] Step S14: after starting the simulation, obtaining the simulation data of each simulation slice from the simulation scene according to the slice duration;

[0063] Step S15, compressing the simulation data slices to remove redundant data in the simulation data slices; when compressing the simulation data slices, for satellite orbit data, record the orbital elements; for static targets, record the coordinate positions; for moving targets, record their running trajectory data; for data, record the data content and the sending and receiving times;

[0064] Among them, static targets include at least ground stations and measurement and control stations; moving targets include at least aircraft, vehicles, and ships; data include at least business data streams and communication data streams.

[0065] Step S16: using a data compression tool to further compress the simulation data slices;

[0066] Step S17: Associating the simulation data slices with the simulation scenarios and storing them in a database.

[0067] Through simulation and deduction of the data slicing compression and storage process, we ensure that data is efficiently organized and stored in the initial stage. During the first run, we plan the slicing time reasonably, quickly obtain data during non-first run, compress and remove redundancy, and associate storage for quick subsequent calls, which lays a solid data foundation for the entire debugging process, reduces data retrieval and loading time, and improves system response speed.

[0068] Step S2, identification of critical breakpoints in simulation scenarios: support setting breakpoints during simulation debugging. Get the simulation data slice where the breakpoint is located, count the number of historical breakpoints of the data slice, sort the data slices according to the count, identify the breakpoints in the top 5 data slices with the highest count as critical breakpoints, and record all instantaneous simulation data of the simulation scenario at the critical breakpoint. The historical breakpoint count threshold of the simulation data slice can be set, including:

[0069] Step S21, in the simulation scene debugging mode, obtaining the moment when the breakpoint is set in the simulation scene, and determining the simulation deduction data slice corresponding to the breakpoint moment;

[0070] Step S22, obtaining the number of historical breakpoints of the simulation deduction data slice, and adding 1 to the count of the number of historical breakpoints;

[0071] Step S23, setting the historical breakpoint count threshold of the deduction data slice; the historical breakpoint count threshold is set based on the complexity of the simulation scenario and the debugging focus to accurately locate the key breakpoints. The setting range of the historical breakpoint count threshold is 1-10. Under normal circumstances, the default threshold is 5.

[0072] Step S24: sort the deduction data slices from high to low according to the number of historical breakpoints, obtain the top-ranked deduction data slices as key deduction data segments, and set all historical breakpoints in the corresponding slices as key breakpoints;

[0073] Step S25: determine whether the key breakpoint has changed. If the key breakpoint has changed, determine whether the key deduction data slice has changed, and update the maintained key deduction data slice in time.

[0074] Based on the breakpoint history counting and sorting, it dynamically focuses on the key debugging areas, can flexibly adjust the threshold according to different simulation scenarios, and timely update the key breakpoint information, guiding the debugging personnel to quickly locate the problem-prone links, effectively saving debugging energy and improving the accuracy and efficiency of troubleshooting.

[0075] Step S3, pre-deduction of simulation scene debugging fragments: When entering the simulation deduction debugging mode, the simulation scene data fragments where the key breakpoints are located are loaded into the simulation engine for pre-deduction, and the pre-deduction data is completely stored, specifically including:

[0076] Step S31, obtaining key deduction data slices and key breakpoints maintained by the simulation scenario, obtaining the start time, end time, simulation scenario initialization state, event data, and simulation scenario time where the key breakpoints are located for the key deduction data slices;

[0077] Step S32: calling the simulation engine, pushing the acquired key deduction data slices and related data to the simulation engine for deduction, and recording the complete simulation scenario deduction data during the deduction process;

[0078] Step S33, extract the simulation scene deduction data at the critical breakpoint moment separately, using the breakpoint ID as the index and the simulation scene deduction data at the breakpoint moment as the value;

[0079] Step S34, putting the key deduction data slices, complete deduction data and breakpoint simulation deduction data into the memory.

[0080] By using the simulation engine to process the segments where the key breakpoints are located in advance, the deduction data is completely stored and stored in the memory in a specific way. This allows the key breakpoint data to be obtained immediately during the debugging process, avoiding the need to wait for real-time deduction, significantly speeding up the debugging rhythm, and enhancing the real-time nature of system interaction.

[0081] Step S4, merging simulation scene baselines, specifically includes:

[0082] Step S41: in the simulation scene debugging mode, locate the simulation deduction data slice at the current deduction moment;

[0083] Step S42: Open the baseline branch according to the modification instruction, and use the engine to promote simulation deduction;

[0084] Step S43: Compare the branch and baseline slice data to complete merging branches or cleaning data.

[0085] From the precise judgment of branch opening, to the orderly deduction after branch creation, to the intelligent optimization of slice connection and the flexible merging or cleaning of the final branch, it not only meets the diverse debugging needs, but also avoids resource waste and ensures the continuity and efficiency of the simulation.

[0086] In some embodiments of the present invention, step S41 includes:

[0087] Step S411: in the simulation scene debugging mode, determining the current simulation deduction moment of the user, and determining the simulation deduction data slice corresponding to the simulation deduction moment;

[0088] Step S412: determine whether the user has modified the simulation scene state based on the human-in-the-loop. If modified, obtain the simulation data slice where the simulation scene is located at the time of modification.

[0089] In some embodiments of the present invention, step S42 includes:

[0090] Step S421, opening a branch for the current simulation scenario baseline, modifying the current simulation deduction data slice according to the modification result of the user, and putting it into the simulation engine for simulation deduction;

[0091] Step S422, determining whether the user has completed debugging within the current simulation data slice time period;

[0092] Step S423: If the user fails to complete debugging within the current simulation data slice time period, the simulation data at the end of the current simulation data slice is used as the initialization data for the next simulation data slice, and the simulation engine is called for deduction.

[0093] In some embodiments of the present invention, step S43 includes:

[0094] Step S431: after completing the simulation and deduction of a simulation and deduction data slice, obtain the simulation and deduction data at the end time of the current simulation and deduction data slice, and compare it with the initialization data of the next simulation and deduction data slice in the baseline. If the comparison result is less than the threshold, the simulation engine is not called to deduce the next simulation and deduction slice, but the next simulation and deduction data slice in the baseline is directly used as the next simulation and deduction data slice of the branch;

[0095] Step S432, determine whether the user merges the branch deduction data into the baseline. If merged into the baseline, the simulation deduction data slices after the intersection with the branch in the baseline are deleted, and the simulation deduction data slices in the branch are merged into the baseline; if not merged into the baseline, the simulation deduction data slices in the branch are deleted.

[0096] The present invention provides a simulation-oriented breakpoint reset scheduling method, which can be performed according to the following steps during specific operation:

[0097] Step A: Enter the simulation scene debugging mode to determine whether the simulation scene is associated with the simulation deduction data slice. If not, call the simulation deduction data slice compression storage function to associate the simulation scene with the simulation deduction data slice and store it in the database.

[0098] Step B: Record the breakpoints set by the user in the simulation scenario, call the simulation scenario key breakpoint identification function, and identify the key breakpoints and key simulation deduction data slices in the simulation scenario.

[0099] Step C: Call the simulation scenario debugging fragment pre-deduction function to pre-decode the key simulation deduction data slice, and store the simulation deduction data at the key breakpoint moment of the pre-deduction complete data of the time period where the key simulation deduction data slice is located into the memory.

[0100] Step D: Determine whether the user starts single-step debugging from the breakpoint. After starting single-step debugging, determine whether the current breakpoint is a critical breakpoint. If it is a critical breakpoint, directly obtain the simulation and deduction data at the critical breakpoint from the memory and present it to the user; if the current breakpoint is not a critical breakpoint, but is in a critical simulation and deduction data slice, obtain the simulation and deduction data within the critical simulation and deduction data slice time period from the memory, locate the simulation and deduction data at the breakpoint and present it to the user; if neither of the above two situations is true, load the simulation and deduction data slice, use the simulation engine for deduction, and present the simulation and deduction data at the breakpoint to the user.

[0101] Step E: Determine whether the user has completed debugging within the current simulation data slicing time period.

[0102] Step F: If the user does not complete debugging within the current simulation data slice time period, the simulation data at the end of the current simulation data slice is used as the initialization data for the next simulation data slice, the simulation engine is called for deduction, and the simulation data is presented to the user. If the next simulation data slice is a key simulation data slice, the simulation data is directly called from the memory and presented to the user.

[0103] Step G: Determine whether the user has modified the simulation scene state based on the human-in-the-loop. If so, obtain the simulation data slice where the simulation scene is located at the time of modification.

[0104] Step H: Open a branch for the current simulation scenario baseline, modify the current simulation data slice according to the user's modification results, and put it into the simulation engine for simulation.

[0105] Step I: If the user fails to complete debugging within the current simulation data slice time period, the simulation data at the end of the current simulation data slice is used as the initialization data for the next simulation data slice, and the simulation engine is called for deduction.

[0106] Step J: After completing the simulation and deduction of a simulation and deduction data slice, obtain the simulation and deduction data at the end time of the current simulation and deduction data slice, and compare it with the initialization data of the next simulation and deduction data slice in the baseline. If the comparison result is less than the threshold, the simulation engine is not called to deduce the next simulation and deduction slice, but the next simulation and deduction data slice in the baseline is directly used as the next simulation and deduction data slice of the branch.

[0107] Step K: Call the simulation scenario baseline branch merging function to merge the simulation scenario baseline branches.

[0108] The present invention provides a scenario breakpoint reset scheduling method for simulation deduction, which compresses and stores simulation deduction data according to a set time period, counts historical breakpoints in the simulation deduction data slices, identifies key simulation deduction data slices and key breakpoints, uses a simulation engine to pre-decode key simulation deduction data slices, and then stores the simulation deduction data in memory, thereby realizing rapid scheduling and access to simulation deduction data. For the simulation deduction debugging application scenario of human in the loop, the concept of simulation deduction scenario baseline is introduced, and simulation deduction data slices are used to realize other branch merging. At the same time, by comparing the deduction slice data at the end time and the deduction slice data at the start time of two consecutive simulation deduction data slices, the simulation engine is avoided from repeated deduction, computer computing resources and storage resources are saved, and debugging efficiency is improved.

[0109] Parts of the present invention that are not described in detail belong to the well-known technology in the art.

[0110] It should be noted that although the embodiments of the present invention described above are illustrative, they are not intended to limit the present invention, and therefore the present invention is not limited to the above specific embodiments. Without departing from the principles of the present invention, any other embodiments obtained by those skilled in the art under the guidance of the present invention are deemed to be within the protection of the present invention.

Claims

1. A scenario breakpoint reset scheduling method for simulation deduction, characterized in that: The following steps are involved: Step S1, slicing the simulation data according to time periods, and compressing and storing the simulation data slices; Step S2, identifying key breakpoints of the simulation scenario; Step S3, loading the simulation scene data fragment where the key breakpoint is located into the simulation engine for pre-deduction to obtain pre-deduction data; Step S4: merging simulation scene baselines.

2. The scenario breakpoint reset scheduling method for simulation deduction according to claim 1 is characterized in that: The step S1 specifically includes: Step S11, determining whether the simulation scenario is being run for the first time, if not, directly obtaining the simulation deduction data compression slice of the simulation scenario from the database; if so, obtaining the scenario start time and end time of the simulation scenario, and calculating the simulation duration of the simulation scenario; Step S12: judging whether it is necessary to adjust the length of the deduction data slice time period according to the simulation duration; if the simulation duration exceeds 24 hours, increasing the length of the simulation data slice time period; Step S13, calculating the scene duration of the simulation scene, and slicing the simulation scene according to the length of the simulation deduction data slicing time period; Step S14: after starting the simulation, obtaining the simulation data of each simulation slice from the simulation scene according to the slice duration; Step S15, compressing the simulation data slices to remove redundant data in the simulation data slices; Step S16: using a data compression tool to further compress the simulation data slices; Step S17: Associating the simulation data slices with the simulation scenarios and storing them in a database.

3. The scenario breakpoint reset scheduling method for simulation deduction according to claim 2 is characterized in that: In step S15, when the simulation deduction data slices are compressed, for satellite orbit data, the orbital elements are recorded; for static targets, the coordinate positions are recorded; for moving targets, their running trajectory data are recorded; for data, the data content and the sending and receiving times are recorded; Among them, static targets include at least ground stations and measurement and control stations; moving targets include at least aircraft, vehicles, and ships; data include at least business data streams and communication data streams.

4. The scenario breakpoint reset scheduling method for simulation deduction according to claim 1 is characterized in that: The step S2 specifically includes: Step S21, in the simulation scene debugging mode, obtaining the moment when the breakpoint is set in the simulation scene, and determining the simulation deduction data slice corresponding to the breakpoint moment; Step S22, obtaining the number of historical breakpoints of the simulation deduction data slice, and adding 1 to the count of the number of historical breakpoints; Step S23, setting a historical breakpoint count threshold for deduced data slices; Step S24: sort the deduction data slices from high to low according to the number of historical breakpoints, obtain the top-ranked deduction data slices as key deduction data segments, and set all historical breakpoints in the corresponding slices as key breakpoints; Step S25: determine whether the key breakpoint has changed. If the key breakpoint has changed, determine whether the key deduction data slice has changed, and update the maintained key deduction data slice in time.

5. The scenario breakpoint reset scheduling method for simulation deduction according to claim 4 is characterized in that: The historical breakpoint count threshold is set based on the complexity of the simulation scenario and the debugging focus to accurately locate key breakpoints. The setting range of the historical breakpoint count threshold is 1-10.

6. The scenario breakpoint reset scheduling method for simulation deduction according to claim 1 is characterized in that: The step S3 specifically includes: Step S31, obtaining key deduction data slices and key breakpoints maintained by the simulation scenario, obtaining the start time, end time, simulation scenario initialization state, event data, and simulation scenario time where the key breakpoints are located for the key deduction data slices; Step S32: calling the simulation engine, pushing the acquired key deduction data slices and related data to the simulation engine for deduction, and recording the complete simulation scenario deduction data during the deduction process; Step S33, extract the simulation scene deduction data at the critical breakpoint moment separately, using the breakpoint ID as the index and the simulation scene deduction data at the breakpoint moment as the value; Step S34, putting the key deduction data slices, complete deduction data and breakpoint simulation deduction data into the memory.

7. The scenario breakpoint reset scheduling method for simulation deduction according to claim 1 is characterized in that: The step S4 specifically includes: Step S41: in the simulation scene debugging mode, locate the simulation deduction data slice at the current deduction moment; Step S42: Open the baseline branch according to the modification instruction, and use the engine to promote simulation deduction; Step S43: Compare the branch and baseline slice data to complete merging branches or cleaning data.

8. The scenario breakpoint reset scheduling method for simulation deduction according to claim 7 is characterized in that: The step S41 includes: Step S411: in the simulation scene debugging mode, determining the current simulation deduction moment of the user, and determining the simulation deduction data slice corresponding to the simulation deduction moment; Step S412: determine whether the user has modified the simulation scene state based on the human-in-the-loop. If modified, obtain the simulation data slice where the simulation scene is located at the time of modification.

9. The scenario breakpoint reset scheduling method for simulation deduction according to claim 7, characterized in that: The step S42 includes: Step S421, opening a branch for the current simulation scenario baseline, modifying the current simulation deduction data slice according to the modification result of the user, and putting it into the simulation engine for simulation deduction; Step S422, determining whether the user has completed debugging within the current simulation data slice time period; Step S423: If the user fails to complete debugging within the current simulation data slice time period, the simulation data at the end of the current simulation data slice is used as the initialization data for the next simulation data slice, and the simulation engine is called for deduction.

10. The scenario breakpoint reset scheduling method for simulation deduction according to claim 7, characterized in that: The step S43 includes: Step S431: after completing the simulation and deduction of a simulation and deduction data slice, obtain the simulation and deduction data at the end time of the current simulation and deduction data slice, and compare it with the initialization data of the next simulation and deduction data slice in the baseline. If the comparison result is less than the threshold, the simulation engine is not called to deduce the next simulation and deduction slice, but the next simulation and deduction data slice in the baseline is directly used as the next simulation and deduction data slice of the branch; Step S432, determine whether the user merges the branch deduction data into the baseline. If merged into the baseline, the simulation deduction data slices after the intersection with the branch in the baseline are deleted, and the simulation deduction data slices in the branch are merged into the baseline; if not merged into the baseline, the simulation deduction data slices in the branch are deleted.

Images