data-analysis

Diagnose machine faults by analyzing Task_ListWithTime.csv state records from HT9045 DoStateRecord.

Updated May 28, 2026
One-click install
npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill data-analysis-hpi-jimmy-chiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-analysis
Source: https://github.com/HPI-Jimmy-Chiu/HT904_V899/tree/main/.agents/skills/data-analysis
Command: npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill data-analysis-hpi-jimmy-chiu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a machine stalls, times out, or slows down, engineers must manually read long state-record logs to find where the process got stuck. This Skill quickly analyzes the Task_ListWithTime.csv produced by DoStateRecord to pinpoint the abnormal time window, the stuck State/Task, and the most likely root cause. ## Core Features & Use Cases - Anomaly Localization: Detects abnormal segments via excessive durations, repeated states, and error keywords, then isolates the 20-50 records around the fault. - Root Cause Hypotheses: Produces a ranked Top-3 root cause list (sensor, motor axis, communication, fixture, logic, or parameters) with the shortest verification steps for each. - Structured Reporting: Outputs a fixed format covering problem summary, key evidence, hypotheses, verification steps, and temporary/permanent fixes. - Use Case: An operator reports the machine stopped mid-cycle. Provide the Task_ListWithTime.csv and receive an immediate answer identifying which State it stalled in, how long it stayed there, and what to check first on the floor. ## Quick Start Analyze this Task_ListWithTime.csv from DoStateRecord and tell me where the machine got stuck and the most likely root cause.

Frequently Asked Questions about data-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find where a machine got stuck from a state record CSV?▼

Analyze the Task_ListWithTime.csv by locating the last successfully completed State and the first State showing abnormal delay or repetition. The stuck point is where dwell time spikes or the same State repeats without progressing.

What is Task_ListWithTime.csv from DoStateRecord used for?▼

Task_ListWithTime.csv is a state record log produced by DoStateRecord on HT9045 equipment, containing timestamps, State/Task names, and durations. It is used to trace machine behavior and diagnose faults like stalls, timeouts, and cycle time increases.

What input files are needed for machine fault analysis?▼

The minimum required input is Task_ListWithTime.csv. For better accuracy, also provide Error logs, configuration files such as system/ATC.ini or config/config.ini, and the approximate incident time reported by the operator.

Why does a machine state repeat in a loop without progressing?▼

A repeating A-B-A-B state loop usually indicates a position sensor signal not stabilizing, a completion condition never being satisfied, or a retry mechanism without an upper limit. Check sensor inputs and condition logic for that State first.

What are the limitations of CSV state record analysis?▼

Analysis quality depends on CSV completeness: missing timestamp, state name, or duration columns reduce reliability, and non-monotonic timestamps flag data trustworthiness risks. Without supplementary error logs or config files, root cause conclusions remain hypotheses requiring on-site verification.