Vehicle Simulation Test Program Step Visualization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Vehicle simulation test programs based on C codes lack visual representation of their running state, making it difficult to determine which action is being executed, whether it is destructive, and if test determination failures occur, leading to inefficiencies in monitoring and troubleshooting.
Innovation Solution
A program step visualization implementation method and system that sets mark parameters for activation and non-activation states for each execution box in a C code-based graphics program, dynamically changing display marks based on execution state changes and time periods to provide visual feedback on the test process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If C code-based vehicle simulation test programs are used, then the program can be executed to perform simulation tests, but the running state cannot be visually displayed during execution
Solution Approach 1:
The patent applies color changes to execution boxes to indicate different running states. When an execution box is being executed, it changes color (e.g., to yellow) to provide visual feedback. This allows operators to see which part of the C code program is currently running, resolving the information loss about program execution state while maintaining test reliability.
Solution Approach 2:
The patent introduces an intermediary visualization layer between the C code execution and the operator. This layer includes execution boxes with visual marks that mediate the information flow, translating internal program state into visible indicators without interfering with the actual test execution reliability.
2Device complexity
If no visual display is provided during test execution, then the system remains simple, but it is unknown which action is being executed and whether it is destructive
Solution Approach 1:
The patent segments the test program into discrete execution boxes, each representing a specific action or test step. This segmentation allows individual visualization of each executable unit's state without overwhelming complexity. Each box can be independently marked and tracked, making it easy to detect which specific action is currently executing while maintaining overall system simplicity.
Solution Approach 2:
The patent uses color changes and visual marks on execution boxes to indicate current execution state. This provides immediate visual detection of which action is being executed and whether it is destructive, without adding significant system complexity. The visual feedback mechanism is lightweight and integrates seamlessly with the existing C code execution framework.
3Device complexity
If conventional log record methods are used to determine test failures, then the system remains simple, but the troubleshooting efficiency is low
Solution Approach 1:
The patent implements real-time visual feedback by marking execution boxes that are currently running or have just completed. When a test determination failure occurs, the corresponding execution box is visually highlighted, providing immediate feedback about the failure location. This eliminates the need to manually search log records, dramatically improving troubleshooting efficiency while keeping the monitoring system relatively simple.
Solution Approach 2:
The visualization system automatically tracks and displays execution state without requiring external intervention. The system serves itself by maintaining visual marks on execution boxes throughout the test process, enabling operators to quickly identify failures without manual log analysis. This self-service capability boosts productivity while minimizing added complexity.
4Reliability
If test logics with many branches and cycles are used, then the test coverage is improved, but it is unknown that the test logics runs through which branches and enters which state
Solution Approach 1:
The patent segments complex test logics with branches and cycles into distinct execution boxes, each representing a specific path or state transition. This segmentation makes it possible to visually track which branch is currently being executed and what state the test logic has entered, even in complex scenarios with multiple paths. Each execution box maintains its own visual mark, preserving execution path information throughout the test process.
Solution Approach 2:
The patent uses color changes and visual marks on execution boxes to indicate the current execution path and state in complex test logics. When the test logic enters different branches or states, the corresponding execution boxes are visually marked, allowing operators to trace the execution flow through complex conditional logic and cycles. This maintains full visibility of the execution path while supporting comprehensive test coverage.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
The present disclosure relates to the field of vehicle simulation test programs, and in particular to a program step visualization implementation method in a simulation test process. The method includes: respectively setting a mark parameter of an activation state or a non-activation state corresponding to the corresponding execution state for each execution box in a graphics program; when the execution state of the execution box changes, changing a display mark of the execution box into an activation state mark corresponding to the new execution state; and when a current execution state of the execution box remains unchanged for a preset period of time, changing the display mark of the execution box from the activation state mark into a non-activation state mark.