Scenario breakpoint reset scheduling method for simulation deduction

Abstract

The present invention relates to a scenario breakpoint resetting and scheduling method for simulation deduction, comprising: step S1, slicing simulation deduction data according to time periods, and compressing and storing the simulation deduction data slices based on the simulation deduction data slices; step S2, identifying key breakpoints in the simulation scenario; step S3, loading the simulation scenario data segments at the key breakpoints into a simulation engine for pre-deduction to obtain pre-deduction data; and step S4, merging simulation scenario baselines. This method is suitable for debugging large-scale spacecraft system simulation scenarios and can solve the problem of ineffective debugging of large-scale spacecraft system simulation scenarios.

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 and aerospace technologies, computer simulation and deduction technology has become essential for spacecraft system simulation. Applying simulation and deduction technology to spacecraft system simulation, leveraging the advantages of computers' large storage capacity and high-speed computing, combined with simulation scenario debugging methods, can fully explore the shortcomings of spacecraft system processes and payload capacity, providing data support for spacecraft system optimization. The scale-up of spacecraft systems has become a trend in spacecraft system development, characterized by an increasing number of spacecraft, increasingly complex spacecraft payloads, and increasing amounts of data transmitted between satellites and the Earth.

[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, which 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 scenario breakpoint reset scheduling method for simulation deduction, which can solve the problem that large-scale spacecraft system simulation scenarios 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: Slice the simulation data according to time periods, and compress and store the simulation data slices;

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

[0009] Step S3: Load 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: determine whether the simulation scenario is being run for the first time. If not, directly obtain the simulation deduction data compression slice of the simulation scenario from the database; if so, obtain the scene start time and end time of the simulation scenario, and calculate the simulation duration of the simulation scenario;

[0013] Step S12: Determine whether the length of the simulation data slice time period needs to be adjusted according to the simulation duration. If the simulation duration exceeds 24 hours, increase the simulation data slice time period.

[0014] Step S13: Calculate the duration of the simulation scenario and slice the simulation scenario according to the length of the simulation deduction data slicing time period;

[0015] Step S14: After starting the simulation, obtain 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 element number is recorded; for static targets, the coordinate position is recorded; for moving targets, the trajectory data is 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; and 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, obtain the moment when the breakpoint is set in the simulation scene, and determine the simulation deduction data slice corresponding to the breakpoint moment;

[0023] Step S22: Obtain the number of historical breakpoints of the simulation data slice, and add 1 to 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 by the number of historical breakpoints from high to low, 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. 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: Acquire key deduction data slices and key breakpoints maintained by the simulation scenario, and obtain the start time, end time, simulation scenario initialization state, event data, and simulation scenario moment where the key breakpoint is located of the key deduction data slice;

[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: Slice the key deduction data, 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 scenario debugging mode, locate the simulation data slice at the current simulation moment;

[0035] Step S42: Open the baseline branch according to the modification instruction and use the engine to advance the 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, 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 so, 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: Open a branch for the current simulation scenario baseline, modify the current simulation deduction data slice according to the user's modification result, and put it into the simulation engine for simulation deduction;

[0042] Step S422: determine whether the user has completed debugging within the current simulation data slicing 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 of a simulation data slice, obtain the simulation data at the end of the current simulation data slice and compare it with the initialization data of the next simulation data slice in the baseline. If the comparison result is less than a threshold, do not call the simulation engine to perform deduction on the next simulation data slice, but directly use the next simulation data slice in the baseline as the next simulation data slice of the branch.

[0046] Step S432: Determine whether the user merges the branch deduction data into the baseline. If it is merged into the baseline, delete the simulation deduction data slice after the intersection point with the branch in the baseline, and merge the simulation deduction data slice in the branch into the baseline; if it is not merged into the baseline, delete the simulation deduction data slice in the branch.

[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. Simulation deduction data slice compression storage obtains simulation scenario deduction data from the simulation deduction data storage to generate simulation deduction data slices. Through simulation scenario key breakpoint identification, key simulation deduction data slices and key breakpoints in the simulation scenario are identified. A simulation deduction engine is called to perform pre-deduction on the key simulation deduction data slices and key breakpoints, obtain key simulation pre-deduction data, and generate a new baseline in the human-in-the-loop simulation deduction scenario. The merged simulation scenario baseline is then stored. The present invention is suitable for debugging large-scale spacecraft system simulation scenarios and can solve the problem of inability to effectively debug large-scale spacecraft system simulation scenarios.

[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 high-efficiency resetting of simulation scene breakpoints of large-scale spacecraft system, and further realizes high-efficiency and effective debugging of large-scale spacecraft simulation deduction. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] 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 the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be derived from these drawings without inventive effort.

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

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

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

[0054] Figure 4 Schematically showing an operation flow chart of 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] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only 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 making creative efforts shall fall 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 includes the following steps:

[0058] Step S1, Slice and compress the simulation data for storage: For the running address simulation scenario, slice the simulation data according to the time sequence and time period. The default slicing time length is 600 seconds, and the slicing time length can be set. The simulation data is compressed and stored, specifically including:

[0059] Step S11: determine whether the simulation scenario is being run for the first time. If not, directly obtain the simulation deduction data compression slice of the simulation scenario from the database; if so, obtain the scene start time and end time of the simulation scenario, and calculate the simulation duration of the simulation scenario;

[0060] Step S12: Determine whether the length of the simulation data slice time period needs to be adjusted according to the simulation duration. If the simulation duration exceeds 24 hours, increase the simulation data slice time period.

[0061] Step S13: Calculate the duration of the simulation scenario and slice the simulation scenario according to the length of the simulation deduction data slicing time period;

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

[0063] Step S15: compress 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 element number; for static targets, record the coordinate position; for moving targets, record their trajectory data; for data, record the data content and 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; and 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] By simulating and deducing the data slicing, compression, and storage process, we ensured efficient data organization and storage during the initial phase. We rationally planned the slicing duration for the first run, rapidly acquired data during non-first runs, compressed data to remove redundancy, and associated storage for quick subsequent access. This laid a solid data foundation for the entire debugging process, reduced data retrieval and loading time, and improved system responsiveness.

[0068] Step S2, Identification of Key Breakpoints in Simulation Scenario: Supports setting breakpoints during simulation debugging. Obtain the simulation data slice where the breakpoint is located, count the number of historical breakpoints in the data slice, sort the data slices by count, identify the breakpoints in the top 5 data slices with the highest counts as key breakpoints, and record all instantaneous simulation data of the simulation scenario at the key breakpoint. The historical breakpoint count threshold of the simulation data slice can be set, specifically including:

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

[0070] Step S22: Obtain the number of historical breakpoints of the simulation data slice, and add 1 to the number of historical breakpoints;

[0071] Step S23, set 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 by the number of historical breakpoints from high to low, 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 breakpoint history counting and sorting, it dynamically focuses on key debugging areas, can flexibly adjust thresholds according to different simulation scenarios, and timely update key breakpoint information, guiding debuggers to quickly locate problem-prone links, effectively saving debugging effort and improving the accuracy and efficiency of troubleshooting.

[0075] Step S3, pre-deduction of simulation scene debugging segments: When entering the simulation deduction debugging mode, the simulation scene data segments 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: Acquire key deduction data slices and key breakpoints maintained by the simulation scenario, and obtain the start time, end time, simulation scenario initialization state, event data, and simulation scenario moment where the key breakpoint is located of the key deduction data slice;

[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: Slice the key deduction data, complete deduction data, and breakpoint simulation deduction data into the memory.

[0080] By pre-processing key breakpoint segments with the simulation engine, the simulation data is fully stored and stored in memory in a specific manner. This allows for immediate access to key breakpoint data during debugging, eliminating the need for real-time simulation waiting, significantly accelerating debugging, and enhancing the real-time nature of system interactions.

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

[0082] Step S41: In the simulation scenario debugging mode, locate the simulation data slice at the current simulation moment;

[0083] Step S42: Open the baseline branch according to the modification instruction and use the engine to advance the 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 consistency 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 so, 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: Open a branch for the current simulation scenario baseline, modify the current simulation deduction data slice according to the user's modification result, and put it into the simulation engine for simulation deduction;

[0091] Step S422: determine whether the user has completed debugging within the current simulation data slicing 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 of a simulation data slice, obtain the simulation data at the end of the current simulation data slice and compare it with the initialization data of the next simulation data slice in the baseline. If the comparison result is less than a threshold, do not call the simulation engine to perform deduction on the next simulation data slice, but directly use the next simulation data slice in the baseline as the next simulation data slice of the branch.

[0095] Step S432: Determine whether the user merges the branch deduction data into the baseline. If it is merged into the baseline, delete the simulation deduction data slice after the intersection point with the branch in the baseline, and merge the simulation deduction data slice in the branch into the baseline; if it is not merged into the baseline, delete the simulation deduction data slice in the branch.

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

[0097] Step A: Enter the simulation scenario debugging mode and determine whether the simulation scenario is associated with the simulation deduction data slice. If not, call the simulation deduction data slice compression storage function to associate the simulation scenario 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 segment pre-deduction function to pre-deduce 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 moment 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 moment 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 moment 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 has not completed 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 to perform simulation and the simulation data is presented to the user. If the next simulation data slice is a critical simulation data slice, the simulation data is directly called from 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 of the simulation scene 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 deduction.

[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. The method compresses and stores simulation deduction data in slices according to a set time period, performs statistics on historical breakpoints within the simulation deduction data slices, identifies key simulation deduction data slices and key breakpoints, uses a simulation engine to pre-decode the key simulation deduction data slices, and then stores the simulation deduction data in memory, thereby achieving rapid scheduling and access to simulation deduction data. For human-in-the-loop simulation deduction debugging application scenarios, the concept of simulation deduction scenario baselines is introduced, and simulation deduction data slices are used to achieve other branch merging. At the same time, by comparing the deduction slice data at the end moment and the deduction slice data at the start moment 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. Therefore, the present invention is not limited to the above-mentioned 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: Slice the simulation data according to time periods, and compress and store the simulation data slices; Step S2, identifying key breakpoints in the simulation scenario; Step S3: Load the simulation scene data fragment where the key breakpoint is located into the simulation engine for pre-deduction to obtain pre-deduction data, specifically including: Step S31: Acquire key deduction data slices and key breakpoints maintained by the simulation scenario, and obtain the start time, end time, simulation scenario initialization state, event data, and simulation scenario moment where the key breakpoint is located of the key deduction data slice; 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: Slice the key deduction data, complete deduction data, and simulation deduction data at the breakpoint into memory; Step S4, merging simulation scene baselines, specifically includes: Step S41: In the simulation scenario debugging mode, locate the simulation data slice at the current simulation moment; Step S42: Open the baseline branch according to the modification instruction and use the engine to advance the simulation deduction; Step S43: Compare the branch and baseline slice data to complete merging branches or cleaning data.

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: determine whether the simulation scenario is being run for the first time. If not, directly obtain the simulation deduction data compression slice of the simulation scenario from the database; if so, obtain the scene start time and end time of the simulation scenario, and calculate the simulation duration of the simulation scenario; Step S12: Determine whether the length of the simulation data slice time period needs to be adjusted according to the simulation duration. If the simulation duration exceeds 24 hours, increase the simulation data slice time period. Step S13: Calculate the duration of the simulation scenario and slice the simulation scenario according to the length of the simulation deduction data slicing time period; Step S14: After starting the simulation, obtain 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 simulation-based scenario breakpoint reset scheduling method according to claim 2, wherein: In step S15, when the simulation 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 trajectory data are recorded; for data, the data content and the time of sending and receiving 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; and 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, obtain the moment when the breakpoint is set in the simulation scene, and determine the simulation deduction data slice corresponding to the breakpoint moment; Step S22: Obtain the number of historical breakpoints of the simulation data slice, and add 1 to the number of historical breakpoints; Step S23: Setting a historical breakpoint count threshold for deduced data slices; Step S24: Sort the deduction data slices by the number of historical breakpoints from high to low, 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 simulation-based scenario breakpoint reset scheduling method according to claim 4, 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 simulation-based scenario breakpoint reset scheduling method according to claim 1, 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 so, obtain the simulation data slice where the simulation scene is located at the time of modification.

7. The simulation-based scenario breakpoint reset scheduling method according to claim 1, characterized in that: The step S42 includes: Step S421: Open a branch for the current simulation scenario baseline, modify the current simulation deduction data slice according to the user's modification result, and put it into the simulation engine for simulation deduction; Step S422: determine whether the user has completed debugging within the current simulation data slicing 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.

8. The scenario breakpoint reset scheduling method for simulation deduction according to claim 1 is characterized in that: The step S43 includes: Step S431: After completing the simulation of a simulation data slice, obtain the simulation data at the end of the current simulation data slice and compare it with the initialization data of the next simulation data slice in the baseline. If the comparison result is less than a threshold, do not call the simulation engine to perform deduction on the next simulation data slice, but directly use the next simulation data slice in the baseline as the next simulation data slice of the branch. Step S432: Determine whether the user merges the branch deduction data into the baseline. If it is merged into the baseline, delete the simulation deduction data slice after the intersection point with the branch in the baseline, and merge the simulation deduction data slice in the branch into the baseline; if it is not merged into the baseline, delete the simulation deduction data slice in the branch.

Images