Laboratory Automation Log Evaluation Using State Machines
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Laboratory automation devices generate log files with error messages that are insufficient for identifying the exact cause of protocol aborts, requiring in-depth understanding of instrument control software, making error analysis difficult.
Innovation Solution
A method using state machines to parse log files and determine the states of laboratory automation devices, enabling automated error cause identification by encoding states and transitions based on log file entries, with optional manual creation by experts for enhanced reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If log files are used to record events during assay protocol, then error messages are captured, but the log file entries alone are insufficient to identify the exact error cause
Solution Approach 1:
The patent applies preliminary action by pre-defining state machines that encode all possible states and transitions of the laboratory automation device before errors occur. These state machines are created in advance based on the device's control software logic, allowing the system to automatically determine device states at the time of errors without requiring real-time analysis or deep software understanding during error diagnosis.
Solution Approach 2:
The patent introduces state machines as an intermediary layer between the raw log file entries and the error analysis process. The state machines translate complex control software states into simplified, interpretable state representations that bridge the gap between detailed device operations and human-understandable error contexts, making error causes identifiable without requiring deep software expertise.
2Measurement precision
If in-depth understanding of instrument control software is required to reconstruct device states, then accurate error diagnosis can be achieved, but the process becomes difficult and time-consuming
Solution Approach 1:
The patent creates simplified copies of the control software's state logic through state machines. Instead of requiring analysts to understand the complex original control software, the state machines provide simplified replicas that capture essential device states and transitions. These copied state representations can be automatically processed to determine device states at error moments, achieving accurate error diagnosis without requiring deep software understanding or significant time investment.
3Adaptability or versatility
If multiple faults lead to the same error message, then error messages become ambiguous, but analyzing each possibility manually is impractical
Solution Approach 1:
The patent segments the overall error analysis problem into distinct device states and transitions defined by separate state machines. Each state machine represents a specific module or aspect of the device, breaking down the complex ambiguity of multiple faults into manageable, isolated state segments. This segmentation allows automatic determination of which specific state the device was in when an error occurred, eliminating the need to manually analyze all possible fault combinations while maintaining comprehensive error coverage.
Data Source
AI summary
A method for determining states of a laboratory automation device includes: receiving a log file from the laboratory automation device, the log file including entries of events that occurred during a procedure performed by the laboratory automation device, wherein the events have been created by components of the laboratory automation device and each entry includes at least an event time and an event type; providing a state machine of the laboratory automation device, the state machine encoding states of the laboratory automation device and transitions between the states, wherein each transition is starting at a state and points to another state and wherein each transition is associated with an entry scheme in the log file, the entry scheme including at least an event type; setting a current state of the laboratory automation device to a beginning state; moving through the entries of the log file along increasing event time and associating the entries with the current state; during the moving, when an entry scheme associated with a transition starting at the current state is identified in the log file, changing the current state to the state to which the transition (60) is pointing.