What problem does it solve? Ascend C operator developers often hit opaque runtime failures—aclnn error codes like 161xxx, 361xxx, 561xxx, or vector core exception 507035—without a clear path to root cause. This Skill provides a systematic debugging workflow that maps error codes to concrete root causes and remediation steps. ## Core Features & Use Cases - Error Code Triage: Classifies aclnn return codes (161xxx parameter errors, 361xxx runtime errors, 561xxx internal errors, 507035 vector core exceptions) and routes each to targeted diagnostic flows covering Tiling faults, kernel lookup failures, and environment misconfiguration. - Kernel Binary Debugging: Diagnoses build-system issues such as stale compile caches, TilingKey/SEL mismatches, missing dtype entries, multi-version vendor package conflicts, and opParaSize mismatches. - plog Log Parsing: Ships a parse_plog.py script that extracts and classifies ERROR/WARN entries from Ascend plog logs to accelerate root-cause analysis. - Use Case: Your custom operator returns 561003 (kernel not found) after installation. The Skill walks you through checking the installed .so under $ASCEND_OPP_PATH, verifying vendor_name and SOC consistency, and validating ASCEND_OPP_PATH and LD_LIBRARY_PATH environment variables. ## Quick Start Ask the assistant to diagnose the Ascend C operator runtime error code you received, for example by pasting the aclnn return code and error message.
